Frequent irql_not_less_or_equal caused by ntoskrnl.exe

morristhehorris · May 26, 2013

Frequently I have been getting this BSOD error whilst using my computer, but I have no idea what is specifically making it happen. I have used BlueScreenView to find that ntoskrnl.exe is causing it. There are millions of variations of problems relating to this stop error so I have know idea where to start. My sf diagnostic zip is attached and if you require any other specs, ask me. This is annoying me as I only ever used to get BSODs from playing games, this happens even when just on the web. Any direction or help would be greatly appreciated.

cluberti · May 26, 2013

NT isn't causing it, but it's blamed in the crash because it was walking information in a list that superfetch is supposed to have, but it's been corrupted in some way it seems:

Code:

3: kd> kL
  *** Stack trace for last set context - .thread/.cxr resets it
Child-SP          RetAddr           Call Site
fffff880`17c7d4a0 fffff802`5ca1308d nt!MiFindNodeOrParent+0xf
fffff880`17c7d4e0 fffff802`5ca13438 nt!MiLocateIdInTree+0x1d
fffff880`17c7d540 fffff802`5c9b6385 nt!MiGetSharedProtos+0x64
fffff880`17c7d570 fffff802`5c9b991c nt! ?? ::FNODOBFM::`string'+0x3749f
fffff880`17c7d620 fffff802`5cd60aa1 nt!MiIdentifyPfnWrapper+0x3c
fffff880`17c7d650 fffff802`5cd28b59 nt!PfpPfnPrioRequest+0xc7
fffff880`17c7d6c0 fffff802`5ccca9ab nt!PfQuerySuperfetchInformation+0x2e9
fffff880`17c7d7f0 fffff802`5ccc6c3b nt!ExpQuerySystemInformation+0x1ccb
fffff880`17c7dac0 fffff802`5c8e2453 nt!NtQuerySystemInformation+0x2b
fffff880`17c7db00 000007f8`cb952f4a nt!KiSystemServiceCopyEnd+0x13
000000f9`c555afd8 00000000`00000000 0x000007f8`cb952f4a

3: kd> r
Last set context:
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000000
rdx=fffff88017c7d500 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8025c942a7f rsp=fffff88017c7d4a0 rbp=0000000000000000
 r8=fffff88017c7d550  r9=0000000000000000 r10=024000000031bd37
r11=8000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na po nc
cs=0010  ss=0018  ds=0000  es=0000  fs=0000  gs=0000             efl=00010286
nt!MiFindNodeOrParent+0xf:
fffff802`5c942a7f 4c8b5918        mov     r11,qword ptr [rcx+18h] ds:00000000`00000018=????????????????

3: kd> u
nt!MiFindNodeOrParent+0xf:
fffff802`5c942a7f 4c8b5918        mov     r11,qword ptr [rcx+18h]
fffff802`5c942a83 498bf0          mov     rsi,r8
fffff802`5c942a86 488bfa          mov     rdi,rdx
fffff802`5c942a89 488be9          mov     rbp,rcx
fffff802`5c942a8c 49f7c300ffffff  test    r11,0FFFFFFFFFFFFFF00h
fffff802`5c942a93 0f84da000000    je      nt!MiFindNodeOrParent+0x103 (fffff802`5c942b73)
fffff802`5c942a99 49c1eb05        shr     r11,5
fffff802`5c942a9d 48895c2440      mov     qword ptr [rsp+40h],rbx

3: kd> !sysinfo machineid
Machine ID Information [From Smbios 2.7, DMIVersion 39, Size=2630]
BiosVendor = Intel Corp.
BiosVersion = BLH6710H.86A.0159.2012.0927.1423
BiosReleaseDate = 09/27/2012
SystemManufacturer =                                  
SystemProductName =                                  
SystemVersion =                                  
BaseBoardManufacturer = Intel Corporation
BaseBoardProduct = DH67CL
BaseBoardVersion = AAG10212-207

3: kd> !sysinfo cpuinfo
[CPU Information]
~MHz = REG_DWORD 3392
Component Information = REG_BINARY 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
Configuration Data = REG_FULL_RESOURCE_DESCRIPTOR ff,ff,ff,ff,ff,ff,ff,ff,0,0,0,0,0,0,0,0
Identifier = REG_SZ Intel64 Family 6 Model 42 Stepping 7
ProcessorNameString = REG_SZ Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Update Status = REG_DWORD 6
VendorIdentifier = REG_SZ GenuineIntel
MSR8B = REG_QWORD 2800000000

Unfortunately, the data uploaded being a set of minidumps it's impossible to say exactly what caused the problem - could be a CPU hardware issue, a BIOS problem, or it could be security software, etc. - without a kernel memory dump, this can't really be pinpointed for sure. However, there is a BIOS update for your motherboard from December 4th of 2012 that I would recommend updating to, as it does contain fixes which could improve system reliability. I can't of course say it's going to help in this scenario, as the data isn't all that helpful due to it being minidump data, but updating all of your drivers and the BIOS would be a good idea here - I've seen this be hardware/BIOS issues more often than not.

Frequent irql_not_less_or_equal caused by ntoskrnl.exe

morristhehorris

New Member

My Computer

System One

cluberti

Cat herder

My Computer

System One