BSOD on Win 8.1, ntkrnlmp.exe, 0x1a / 0x5003

W

win8bsod

Member
Joined
Jan 25, 2015
Posts
7
· OS - Windows 8.1 (x64)
· Custom built desktop, <1yr, original OS installation
· CPU: Intel i5-4670K
· Video Card: GeForce GTX 780
· MotherBoard - Gigabyte GA-Z87X-UD3H
· Power Supply - Seasonic 850, bronze

Got a BSOD just now while using the mouse within Chrome. PC wasn't under heavy load.

I can't run perfmon /report:

Code: 
[Administrator: Command Prompt]
> perfmon /report
perfmon GUI opens with "Error: An error occured while attempting to generate the report. The operator or administrator has refused the request."

WinDBG points to ntkrnlmp.exe with STOP code 0x0000001a, parameter 1 of 0x00005003. Output of `k`:

Code: 
3: kd> kChild-SP          RetAddr           Call Site
ffffd000`38acf7b8 fffff803`adb83501 nt!KeBugCheckEx
ffffd000`38acf7c0 fffff803`ada5be48 nt! ?? ::FNODOBFM::`string'+0xe651
ffffd000`38acf820 fffff803`ada7eaa0 nt!MiResolveDemandZeroFault+0x428
ffffd000`38acf940 fffff803`adb6ec2f nt!MmAccessFault+0x4e0
ffffd000`38acfb00 00000000`0fb002d6 nt!KiPageFault+0x12f
00000000`0038e968 00000000`00000000 0xfb002d6

I'm already running verifier and memory tests have always come back clean. Any idea what's going on?

I've been using an older version of Nvidia drivers because newer ones have been unstable for me. Currently on 337.88.

Thanks!
 
Code: 
3: kd> .bugcheck
Bugcheck code 0000001A
Arguments 00000000`00005003 fffff580`10804000 00000000`000064b0 0000033f`c040c960

5003 first parameter, this indicates the working set free list is corrupt.

Code: 
3: kd> !wsle fffff58010804000

Working Set @ fffff58010804000
    FirstFree     64b0  FirstDynamic        5
    LastEntry     738c  NextSlot            5  LastInitialized     739b
    NonDirect        0  HashTable           0  HashTableSize          0

Code: 
3: kd> ~0
0: kd> k
Child-SP          RetAddr           Call Site
ffffd001`e9fff7d0 fffff803`ada37d58 nt!MiFreeWsleList+0x717
ffffd001`e9fffa00 fffff803`ada37bcb nt!MiEmptyWorkingSetHelper+0x104
ffffd001`e9fffa30 fffff803`adc0b576 nt!MiEmptyWorkingSet+0x10b
ffffd001`e9fffb40 fffff803`ae08e721 nt!MiTrimAllSystemPagableMemory+0x286
ffffd001`e9fffb90 fffff803`ae0a1959 nt!MmVerifierTrimMemory+0xa1
ffffd001`e9fffbc0 fffff803`adaec280 nt!ViKeTrimWorkerThreadRoutine+0x29
ffffd001`e9fffc00 fffff803`adb6afc6 nt!PspSystemThreadStartup+0x58
ffffd001`e9fffc60 00000000`00000000 nt!KiStartSystemThread+0x16

[HR][/HR]
0: kd> ~1
1: kd> k
Child-SP          RetAddr           Call Site
ffffd001`e9fbc8e8 fffff800`77aa11f7 intelppm!MWaitIdle+0x18
ffffd001`e9fbc8f0 fffff803`ada69848 intelppm!AcpiCStateIdleExecute+0x17
ffffd001`e9fbc920 fffff803`ada692a6 nt!PpmIdleExecuteTransition+0x3e8
ffffd001`e9fbcb10 fffff803`adb684bc nt!PoIdle+0x2f6
ffffd001`e9fbcc60 00000000`00000000 nt!KiIdleLoop+0x2c

[HR][/HR]
1: kd> ~2
2: kd> k
Child-SP          RetAddr           Call Site
ffffd001`eea6a8e8 fffff800`77aa11f7 intelppm!MWaitIdle+0x18
ffffd001`eea6a8f0 fffff803`ada69848 intelppm!AcpiCStateIdleExecute+0x17
ffffd001`eea6a920 fffff803`ada692a6 nt!PpmIdleExecuteTransition+0x3e8
ffffd001`eea6ab10 fffff803`adb684bc nt!PoIdle+0x2f6
ffffd001`eea6ac60 00000000`00000000 nt!KiIdleLoop+0x2c

[HR][/HR]

Every core minus the thread on cpu #3 that bug checked is idle.

Code: 
Verify Flags Level 0x0002892b

  STANDARD FLAGS:
    [X] (0x00000000) Automatic Checks
    [X] (0x00000001) Special pool
    [X] (0x00000002) Force IRQL checking
    [X] (0x00000008) Pool tracking
    [ ] (0x00000010) I/O verification
    [X] (0x00000020) Deadlock detection
    [ ] (0x00000080) DMA checking
    [X] (0x00000100) Security checks
    [X] (0x00000800) Miscellaneous checks
    [X] (0x00020000) DDI compliance checking

  ADDITIONAL FLAGS:
    [ ] (0x00000004) Randomized low resources simulation
    [ ] (0x00000200) Force pending I/O requests
    [ ] (0x00000400) IRP logging
    [ ] (0x00002000) Invariant MDL checking for stack
    [ ] (0x00004000) Invariant MDL checking for driver
    [X] (0x00008000) Power framework delay fuzzing
    [ ] (0x00040000) Systematic low resources simulation
    [ ] (0x00080000) DDI compliance checking (additional)
    [ ] (0x00200000) NDIS/WIFI verification
    [ ] (0x00800000) Kernel synchronization delay fuzzing
    [ ] (0x01000000) VM switch verification

Verifier is also enabled with a multitude of flags.

Almost guaranteeing this is bad RAM or another hardware issue such as CPU. Have you run Memtest?
 
Patrick said:
Verifier is also enabled with a multitude of flags.

Almost guaranteeing this is bad RAM or another hardware issue such as CPU. Have you run Memtest?
Click to expand...

Yes, I was trying to diagnose failure to wake from sleep earlier (re-installing an older gfx driver seemed to fix it). That's when I enabled verifier and removed the Gigabyte apps.

I'll set up a 24-hour run and see what happens. Would hate for it to be a CPU or GPU issue. Thanks.
 
Do you have integrated video on that motherboard to use if you remove the GPU for testing? If so, do it and see if you crash without the video card. If you don't, it's the video card. If you do, most likely CPU.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top