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
Could U imagine if the OS does such a thing then how many bugs there would
be ( countably infinte… :), so I dont think MS has any short and/or long
term plan to have such a feature 
:), so check where you are accessing bad
memory, also look/find the description of the bug-code …
-prokash
----- Original Message -----
From: “Michael Kurz”
To: “Windows System Software Devs Interest List”
Sent: Thursday, November 20, 2003 10:46 AM
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@garlic.com
> To unsubscribe send a blank email to xxxxx@lists.osr.com
>
>
Hi,
I ran into a similar problem with a driver that we had been using for some
time. The symptoms were similar to yours. When I traced it down it turned
out to be that the compiler located a locally defined character array in
code space (which is considered ROM) instead of data space. The array was
originally defined with initial values. We changed it to an uninitialized
array and that solved the problem.
As an example when we defined the array as follows
PWSTR String[1] = {L"0123456789ABCDEF"};
we got the IRQL_NOT_LESS_OR_EQUAL bluescreen when we tried to modify this
String. We then changed this to the following and it fixed the bluescreen.
PWSTR String[1];
WCHAR St1[16];
String[0] = (PWSTR)St1;
If you have done something similar then this may also be your problem.
John Nutter
“Michael Kurz” wrote in message
news:xxxxx@ntdev…
>
> 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
>
>
>