BSOD on IDLE IRQL_NOT_LESS_OR_EQUAL ntoskrnl.exe

Kit Ramos

Reputable
Apr 2, 2015
3
0
4,510
okay, this one has got me stumped. if I leave my computer on but not using it for a while, like if I get pulled away to do something else and it took longer then I thought. I'll come back to find my computer has BSOD'ed. if I'm actively using it then no problems at all, doesn't matter how long I'm on it it works the whole time. this only happens if I leave the computer sit unused for a while.
I thought it might be related to sleep or power save mode, so I went into the power options and turned off all the power save settings I could find. That did nothing. I hit the sleep button on the computer, I did some testing of sleep mode using the sleep button, it will enter sleep mode fine and I can leave it in sleep mode for extended periods and it'll come out of it just fine. I had tried setting it to turn off the monitor if idle for 1min down from the 60 it was at, let it idle long enough the screens turns all the way off, then tried to wake it up a minute after the monitors are off completely and it comes back fine.

it seems in order for this thing to bug out it has to be left setting idle for 15-20 mins. any less then that no problems. any more then that always bsod and always the same error
Also if I manually tell it to sleep right after I'm done using it then it's fine as well.

here's the dump files:
http://www.pawworks.net/minidump/

The Error messages:
IRQL_NOT_LESS_OR_EQUAL 0x0000000a
00000000`00000000
00000000`00000002
00000000`00000000
fffff800`032e19b5
ntoskrnl.exe+74ec0

The hardware info:
http://www.pawworks.net/minidump/TOWER.html
 

Kit Ramos

Reputable
Apr 2, 2015
3
0
4,510


I know the brand is: AMD Phenom II x4 965
I'm no expert about what goes into cpu's but from what searching I did about Haswell tech it looks like it's used by The Intel line of cpu's only. so since I don't got an Intel Chipset or CPU I'd say no it's probably not.

Haven't tried hibernate mode, in the tests using the sleep button that I did, the hybrid sleep option was enabled.
the "go to sleep after" timer has always been set to never.

I just noticed a "selective Suspend" option was enabled, and "Link State power Management" was set to max saving; I had some how missed both of those in my first look through the power options so I turned them both off. have yet to see if it helps.

Also just to see what would happen started up team fortress2 in full screen mode and left the computer sit to see if it makes a difference, left the computer sit for an hour with it on the title screen of the game not touching it, when I came back it had not crashed. not sure if it's the changes to the power save settings, that kept it from crashing or having the game running caused the computer to stay "active" all the other times I've left the computer alone and gotten the bsod I was using regular windowed programs or just had the desktop by itself
 

Karadjgne

Titan
Ambassador
Yeah, you basically set the pc to go into a sleep so deep, that with something, anything, running, it need voltage to the cpu, which was denied by the sleep setting, so the cpu was started to the point of failure. Same thing happens all the time with Haswells and Intel C-states.

Use the hybrid sleep, do not use hibernate, its for laptops and sucks on a desktop.

Glad to see you may have found your answer.
 

Kit Ramos

Reputable
Apr 2, 2015
3
0
4,510
Finally got my computer to stop crashing when i leave it alone for a long time.

Turns out the issue was caused by systrace.sys still being in the system even after I uninstalled the "Windows System State Analyzer" now makes me wonder what other messes did it leave behind.
 
bugcheck listed the driver as
Common Log File System Driver
\SystemRoot\system32\CLFS.SYS Tue Mar 03 19:21:12 2015
looks like the driver used a null memory pointer.

you would have to provide a kernel memory dump to figure out info about this bugcheck.
(sounds like you already figured out the cause, looks like a bugcheck during a install)