IRQL_NOT_LESS_OR_EQUAL error

[shedlord2]

Hi,

I'm getting fairly random bluescreens and wondered if anyone can suggest what to do. I've posted an analysis of a minidump file below. thanks

..............
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

BugCheck 1000000A, {58, 2, 0, 80500ce8}

Probably caused by : win32k.sys ( win32k!xxxSleepThread+192 )

Followup: MachineOwner
---------

kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

IRQL_NOT_LESS_OR_EQUAL (a)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high. This is usually
caused by drivers using improper addresses.
If a kernel debugger is available get the stack backtrace.
Arguments:
Arg1: 00000058, memory referenced
Arg2: 00000002, IRQL
Arg3: 00000000, bitfield :
bit 0 : value 0 = read operation, 1 = write operation
bit 3 : value 0 = not an execute operation, 1 = execute operation (only on chips which support this level of status)
Arg4: 80500ce8, address which referenced memory

Debugging Details:
------------------


READ_ADDRESS: 00000058

CURRENT_IRQL: 2

FAULTING_IP:
nt!KiSwapThread+48
80500ce8 8a4f58 mov cl,byte ptr [edi+58h]

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: DRIVER_FAULT

BUGCHECK_STR: 0xA

PROCESS_NAME: explorer.exe

LAST_CONTROL_TRANSFER: from 804f9d72 to 80500ce8

STACK_TEXT:
a8406b0c 804f9d72 00000200 e2965eb0 00001000 nt!KiSwapThread+0x48
a8406b34 bf802f35 00000000 0000000d 00000001 nt!KeWaitForSingleObject+0x1c2
a8406b70 bf8412b4 00000200 a8406b5c 00000000 win32k!xxxSleepThread+0x192
a8406c0c bf8141aa bbe6a628 0000004a 000100c4 win32k!xxxInterSendMsgEx+0x7f6
a8406c58 bf834051 bbe6a628 0000004a 000100c4 win32k!xxxSendMessageTimeout+0x11f
a8406cbc bf8588d8 bbe6a628 0000004a 000100c4 win32k!xxxSendMessageEx+0x7a
a8406d08 bf80eebe bbe6a628 0000004a 000100c4 win32k!NtUserfnCOPYDATA+0x82
a8406d40 8053d648 00030054 0000004a 000100c4 win32k!NtUserMessageCall+0xae
a8406d40 7c90e514 00030054 0000004a 000100c4 nt!KiFastCallEntry+0xf8
WARNING: Frame IP not in any known module. Following frames may be wrong.
01c7f3f4 00000000 00000000 00000000 00000000 0x7c90e514


STACK_COMMAND: kb

FOLLOWUP_IP:
win32k!xxxSleepThread+192
bf802f35 8945fc mov dword ptr [ebp-4],eax

SYMBOL_STACK_INDEX: 2

SYMBOL_NAME: win32k!xxxSleepThread+192

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: win32k

IMAGE_NAME: win32k.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 49e87572

FAILURE_BUCKET_ID: 0xA_win32k!xxxSleepThread+192

BUCKET_ID: 0xA_win32k!xxxSleepThread+192

Followup: MachineOwner
---------

 

[linney]

Are they, the BSOD, occurring at Bootup or midway through any session?

Do you remember the last piece of hardware or software that you might have installed prior to the episodes, or have you been plagued with this problem since new?

Causes, and tips for debugging, a STOP 0x0000000A (IRQL_NOT_LESS_OR_EQUAL) bugcheck/blue screen - Part 1

http://www.adopenstatic.com/cs/blog...-bugcheck_2F00_blue-screen-_2D00_-Part-1.aspx

These are some links specifically concerning win32k.sys and BSOD. I notice in your file identification it specifically states "xxxSleepThread+192", here are some links that mention that too.

Blue screens

http://www.techsupportforum.com/microsoft-support/windows-xp-support/321856-blue-screens.html

http://www.google.com/search?hl=en&...xxxSleepThread+192"&btnG=Search&aq=f&oq=&aqi=

Here is a another long and winding thread concerning your's and similar error message, if you read it you will see that there are many causes, suggestions, and workarounds for you to try.

DRIVER_IRQL_NOT_LESS_OR_EQUAL error
thread779-308429

 

[goombawaho]

Testing the RAM and the hard drive are some of the first things you should do. The Ultimate Boot CD (free download) has tools to do both of these by booting to it.

Then I would update things like video, sound and network card drivers (wired or wireless). Try doing it from safe mode if regular mode is not reachable or stable.

 

[gbaughma]

Chipset drivers.

Every time.



Just my 2¢

"What the captain doesn't realize is that we've secretly replaced his Dilithium Crystals with new Folger's Crystals."

--Greg

http://parallel.tzo.com

 

[donb01]

I've been having the same problem for months and have been watching related topics with interest.

Mine only seems to pop up the blue halt screen when it is idle for some time (usually overnight). Microsloth says it's a driver issue but won't say which one - this computer has been unchanged for years.

It's not a solution to the problem, but I leave my computer on 24/7 and usually let the screen saver and locked office door secure it at night, but have found that logging off when I leave for the day seems to significantly lessen the occurrance (but not completely eliminate it). This has led me to believe that some process that runs at night is the culprit - could be the virus scanner - those usually have drivers that integrate into the network flow, or also the malware scanner - but I only have that running once a week.

Mine is in a corporate environment so it could also be some sneaky process that IS is running at night, or something along those lines...

If this turns on any light bulbs for anyone I hope we all can benefit!