RE: IRQL_NOT_LESS_OR_EQUAL bugcheck, but address seems to be the drivers code itself.

I could be wrong but I don’t think 64M is a supported configuration. No the
OS will not page out sections not marked as pageable.

=====================
Mark Roddy

-----Original Message-----
From: Michael Kurz [mailto:xxxxx@sonydadc.com]
Sent: Thursday, November 20, 2003 1:46 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] IRQL_NOT_LESS_OR_EQUAL bugcheck, but address
seems to be the drivers code itself.

Hi,

I have a windows XP sp1 on a very old and limited PC.
(Pentium II 266 Mhz 64Mbyte ram)

And my driver, which works on a lot of other test pcs very
well, causes a IRQL_NOT_LESS_OR_EQUAL bluescreeen.

I tried to examine the problem and it seems that the address,
which is accessed from dispatch level is the address of the
code of my dispatch routine itself.

below is the info from the bugcheck:
(I replaced the actual address which was some 0x8… kernel
address, with my_address token)

Error code: 0x0000000a (my_address, 0x00000002, 0x00000000,
my_address).

Is there any circumstance, where parts of my driver code will
be paged by windows XP sp1 if the memory becomes very low?
(I did not add any special #pragmas for marking code as
discard or pageable)

Best Regards
Michael


Questions? First check the Kernel Driver FAQ at
http://www.osronline.com/article.cfm?id=256

You are currently subscribed to ntdev as:
xxxxx@stratus.com To unsubscribe send a blank email to
xxxxx@lists.osr.com