• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

IRQL_NOT_LESS_OR_EQUAL... What????

Imaginer

Diamond Member
I am sitting here and the computer is running fine while reading Anandtech when the blue screen of death popped up in Win2k.

It showed this...


***STOP: 0x000000A (0x00000000, 0x00000002, 0x000000000, 0x80432432)
IRQL_NOT_LESS_OR_EQUAL

***Address 80432432 base at 80400000, Date Stamp 39760637 - ntoskrnl.exe

Beginning dump of physical memory.


I had this machine running for around 4 days straight. Anything wrong?
 


<< This is a Windows 2000 Executive character-mode STOP message. It indicates an attempt was made to touch pageable memory at a process IRQL (interrupt request level) that is too high. This is usually caused by drivers using incorrect addresses. The fourth parameter in the message parameter list is the memory address at which the fault happened. The second parameter shows the IRQL. If the IRQL was not equal to 2, then the interrupt most likely came from a driver. Compare the memory address in the fourth parameter with the base addresses of the drivers in the driver table on the STOP screen to find the driver that is the problem. Note that the third parameter encodes read/write access (0 = read, 1= write). >>



Microsoft Help Page

The fourth parameter will tell you which driver caused the crash. Check what memory range your device drivers are you using and the culprit is the range in which the fourth parameter is located.

edit actually since the second parameter is 0x00000002 then it probably wasn't a driver that caused the crash...but check anyways.

-GL
 
Back
Top