KMODE EXCEPTION NOT HANDLED BSOD after reinstalling windows 10

Malco · 30 Jul 2023

It was during normal mode.

Memory Dump

zbook · 30 Jul 2023

The Nvidia driver nvlddmkm.sys was misbehaving in the latest memory dump.

Please try a driver with a different version.

If computer instability persists with different driver versions then consider swap testing hardware or servicing in a local computer store.

Code:

Name	NVIDIA GeForce GTX 970
PNP Device ID	PCI\VEN_10DE&DEV_13C2&SUBSYS_85081043&REV_A1\4&80E7924&0&0008
Adapter Type	NVIDIA GeForce GTX 970, NVIDIA compatible
Adapter Description	NVIDIA GeForce GTX 970
Adapter RAM	(1,048,576) bytes
Installed Drivers	C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_5b6e4554b945d508\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_5b6e4554b945d508\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_5b6e4554b945d508\nvldumdx.dll,C:\Windows\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_5b6e4554b945d508\nvldumdx.dll
Driver Version	31.0.15.3640
INF File	oem3.inf (Section013 section)
Driver	C:\WINDOWS\SYSTEM32\DRIVERSTORE\FILEREPOSITORY\NV_DISPIG.INF_AMD64_5B6E4554B945D508\NVLDDMKM.SYS (31.0.15.3640, 56.28 MB (59,010,576 bytes), 27/07/2023 10:28)

31.0.15.3640
31.0.15.3179

Win10Warlord · 30 Jul 2023

zbook said:

The Nvidia driver nvlddmkm.sys was misbehaving in the latest memory dump.

I'm not sure where you've drawn this conclusion from other than running !thread with dps? You need to take the entire thread stack into context and just not blindly assume that because a third-party driver is listed there, then it is the problem. I've encountered many cases where multiple drivers are listed and only one of them is the actual cause or where none of them have been the problem.

Code:

1: kd> .trap ffffda01`c0430770
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000901c rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8061eeefa86 rsp=ffffda01c0430900 rbp=ffffda01c04309b9
 r8=0000000000000001  r9=ffffdd0523baf260 r10=000000000000005a
r11=000000000000901c r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!PpmPerfSelectProcessorState+0x1a6:
fffff806`1eeefa86 f7f1            div     eax,ecx

@Malco Since this is a divide-by-zero error, have you tried running Prime95 to ensure that there is no issues with the processor itself?

ubuysa · 30 Jul 2023

I'd bet that Prime95 will run OK. I've seen this before, it seems to bugcheck when it comes out of the idle loop, so I wonder whether it's failing power transitions?

zbook · 31 Jul 2023

Win10Warlord said:

I've encountered many cases where multiple drivers are listed and only one of them is the actual cause or where none of them have been the problem.

Seeing multiple drivers in the raw stack is relatively common.

So far in this thread nvlddmkm.sys was seen in the raw stack in three different crashes.

I'm anticipating malfunctioning hardware but following the DPS for now.

Post #4 step #5 was supposed to be performed before step #6.

If there are new debugging findings, safe mode crashes, test result findings / failures, etc. then will move in that direction.

Malco · 31 Jul 2023

I've tried various versions of the graphics driver with no luck, I have tried placing the card in different slots. I don't have a spare card so have ordered a cheap second hand card from ebay. I wasn't able to run step 5 from post 4, I can do another clean install and attempt this again if needed.

It completed prime95 in safe mode fine, I attempted to run it in normal mode and have only got through 4 of the tests so far before it crashes. I think this would just be a matter of patience though to get a stretch of time long enough to run all the tests before it crashes. Will do this if needed.

ubuysa · 31 Jul 2023

Can you post or take a screenshot of the Prime95 errors? A good system should be able to run Prime95 continuously, so crashes are not good.

Be sure to have a temperature monitor running whilst running Prime95.

Malco · 31 Jul 2023

I'll set this up when I get home, is it ok for it to be running in safe mode though as otherwise it will just crash at whatever random point in time it decides to.

ubuysa · 31 Jul 2023

Running in Safe Mode will do no harm to it at all.

Win10Warlord · 31 Jul 2023

ubuysa said:

I'd bet that Prime95 will run OK. I've seen this before, it seems to bugcheck when it comes out of the idle loop, so I wonder whether it's failing power transitions?

It crashes during a PPMCheck which is run periodically in order to make power management decisions for particular cores. There is a debugger command for this called !ppmcheck but it doesn't reveal much.

Malco said:

It completed prime95 in safe mode fine, I attempted to run it in normal mode and have only got through 4 of the tests so far before it crashes.

It's interesting that it crashes in normal mode but succeeds in safe mode.