[SOLVED] KMODE_EXCEPTION_NOT_HANDLED

[TooOldForThis]

Hello all,

I've been experiencing frequent BSOD issues over the past month or so and haven't been able to get any kind of idea what is going wrong with my computer. I had a look through a number of threads on this forum as well as various other places online and haven't found an answer. At least part of the problem is that as the years have passed, I have become distressingly computer illiterate and I simply don't understand a lot of what I'm reading. I'm hoping some kind soul might have the patience to walk me through diagnosis and solution with the understanding you might need to ELI5 (ELI80, perhaps?!).

My system is:

CPU: Intel Core i5-2500K
GPU: Sapphire Pulse Radeon RX 580 4Gb
SSD: Samsung 850 Evo 250Gb
HDD: Samsung HD502HJ 500Gb
RAM: HyperX Fury DDR3 1866 C10 2x4Gb
MBD: Asus P8P67 Pro

• There has not been a consistent trigger for the BSOD and the error code is KMODE_EXCEPTION_NOT_HANDLED. There is no driver code or further detail provided.
• I checked and updated all drivers as best I could.
• I uninstalled as many recent installs as I could.
• I removed and re-seated the RAM.
• I backed up all files to OneDrive and performed a clean install of Windows 10

Roughly fifteen minutes after the clean install of Windows finished, the BSOD appeared again. I'm at a total loss and have no idea how to proceed any further. Can anyone help?

Thanks,

D

 

[PC Tailor]

Managed to get some individual files uploaded, if it's at all useful: https://www.dropbox.com/sh/9oxwkeykmc6bzw2/AAAZOOEW6hOtAw58x2GkFPd_a?dl=0

Was this after you enabled Driver Verifier? Or have you not done that yet?
The attached dump files say the exact same story so I won't post another report.

But you said the issue disappeared in Safe Mode?

 

[TooOldForThis]

Was this after you enabled Driver Verifier? Or have you not done that yet?
The attached dump files say the exact same story so I won't post another report.

But you said the issue disappeared in Safe Mode?

I have enabled Driver Verification, yes. Did that a few hours ago. Confirmed verifier /querysettings in CMD at the time and just double-checked now to be sure.

I haven't experienced a crash in Safe Mode, no.

 

[TooOldForThis]

At this stage, it might be best to just leave this unsolved. Unfortunately, my system has now died again and boots into an Automatic Repair couldn’t repair your PC error. That then cycles and I can’t get anywhere near an actual Windows screen.

I have a horrific sense that perhaps my computer just needs replaced, unless you have a suitably magic wand that can make this better. I’ve moved fairly thoroughly from the sleep-derived mania of the last few hours into a pretty epic despondency and honestly I just don’t have the energy to keep bashing my head against this problem any longer.

Gutted.

 

[PC Tailor]

At this stage, it might be best to just leave this unsolved. Unfortunately, my system has now died again and boots into an Automatic Repair couldn’t repair your PC error. That then cycles and I can’t get anywhere near an actual Windows screen.

I have a horrific sense that perhaps my computer just needs replaced, unless you have a suitably magic wand that can make this better. I’ve moved fairly thoroughly from the sleep-derived mania of the last few hours into a pretty epic despondency and honestly I just don’t have the energy to keep bashing my head against this problem any longer.

Gutted.

If you're getting a boot into repair loop, how many storage drives do you have?

 

[boogiman69]

Hi
I had a similar problem at my company with this just yesterday,
I isolated it to 6 certain configurations (only happened on the i5 8600 with windows 10 2004) It all happened on these machines at the same time and the previous windows updates was 2 weeks ago. I used 1909 instead and they work fine with that.
In my case i tried the following
memtest (even though super unlikely that all 6 of these configurations had failed memory
Bios update,
enabled / disabled fast boot
Driver updates

 

[Colif]

At this stage, it might be best to just leave this unsolved. Unfortunately, my system has now died again and boots into an Automatic Repair couldn’t repair your PC error. That then cycles and I can’t get anywhere near an actual Windows screen.

I did warn you. have you got a win 10 installer? If you do, and created a restore point before starting, you can try to roll system back to how it was before you started driver verifer
boot from installer
on screen after languages, choose repair this pc, not install.
choose troubleshoot
choose advanced
choose system restore
pick the restore point you created before running driver verifer.
Windows should boot and let you into safe mode since that is only place that works

Your PC is old enough for me to state that yes, a new PC would help. Its at the age parts just stop working from being used for 8 years. Running fine in safe mode can also mean that the parts aren't being asked to do as much, safe isn't as stressing on PC as normal.

Since we think its just drivers, and all your files are backed up, just reinstall win 10 again and see if we can get it working properly. If you do have a copy of 1909, try that.

 

[TooOldForThis]

Well I'm back, nana-na na na nana-na na na kshh!

Ok, I took a couple days to rest up and recharge and I'm back in the game, baby, yeah! I'll have a good read through all comments and see where to go from here. I did very briefly notice Colif's "I told you so" and yeah, you did. And yeah, I prepped for it. I created a USB boot drive and also created a restore point, so really it shouldn't pose a problem.

Woop-woop!

 

[foolest1]

Hello @TooOldForThis

, I've had today the same problem and from what I've seen in the internet is that we usually have similar Hardware (from 2012).
In my case:
Asrock Extreme4 P67
i5 2500k

I've uninstalled antiviruses I had (360, malwarebytes), reinstalled sound and graphic drivers. But nothing changed.
Finally I've updated my BIOS,and for now it hasn't BSODed again.

So I've just registered to tell you this, update your BIOS! (maybe you already did, I did not read all 3 pages :S)

Another thing I resolved with the BIOS update is Task manager was always showing CPU at 100% even when doing nothing. I dont know if CPUwas really always at 100 but well, problem fixed

Look this thread, same error and similar hardware!
https://answers.microsoft.com/en-us...-crashes/7286e27a-f968-4dd0-b45b-63729cf2e1f7