[SOLVED] KMODE_EXCEPTION_NOT_HANDLED

Toggle sidebar Toggle sidebar
T

TooOldForThis

Honorable
Oct 4, 2014
44
1
10,535
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
 
Solution
Colif
TooOldForThis said:
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.
Click to expand...

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...
Sort by date Sort by votes
Can you please upload the raw dump files for the BSOD onto a file sharing site for us to download and look through?

TooOldForThis said:
Roughly fifteen minutes after the clean install of Windows finished, the BSOD appeared again.
Click to expand...
So this really means 1 of 2 things, either:
  • It is a hardware related issue (this can be compatibility, or BIOS configuration/OC etc. also, not just the hardware itself being faulty).
  • The offending software is being reinstalled (this can be very common if you are using WiFi adapters or buggy mice/keyboard drivers for example).
Please upload any and ALL dump files.
If you are happy to, I would actually recommend running this which will automatically grab all dump files and system info for us to look through https://www.sysnative.com/forums/pages/bsodcollectionapp/
 
Upvote 0 Downvote
very unlucky if its number 2. Not normal for the same BSOD to survive a reinstall.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

Memtest is created as a bootable USB so that you don’t need windows to run it, just a spare USB drive.
 
Last edited:
  • Like
Reactions: PC Tailor
Upvote 0 Downvote
PC Tailor said:
Can you please upload the raw dump files for the BSOD onto a file sharing site for us to download and look through?


So this really means 1 of 2 things, either:
  • It is a hardware related issue (this can be compatibility, or BIOS configuration/OC etc. also, not just the hardware itself being faulty).
  • The offending software is being reinstalled (this can be very common if you are using WiFi adapters or buggy mice/keyboard drivers for example).
Please upload any and ALL dump files.
If you are happy to, I would actually recommend running this which will automatically grab all dump files and system info for us to look through https://www.sysnative.com/forums/pages/bsodcollectionapp/
Click to expand...

Hey, thanks for the super quick reply. I would absolutely love to upload all raw dump files, but this is where my illiteracy starts rearing its ugly head. I can follow your link, download the thingummy and run it - is that all that's involved, or do I need to do something further?

Re: the two options, the GPU got added into the system relatively recently, though we're still talking over a year ago at this point. Would compatibility issues potential evolve without changing hardware?

Colif said:
very unlucky if its number 2. Not normal for the same BSOD to survive a reinstall.

Try running memtest86 on each of your ram sticks, one stick at a time, up to 4 passes. Only error count you want is 0, any higher could be cause of the BSOD. Remove/replace ram sticks with errors.

Memtest is created as a bootable USB so that you don’t need windows to run it
Click to expand...

Again, thanks for the quick reply. As above, I'm very happy to download and run things, so will get on that ASAP. I had to order a flash drive as I don't currently have one available, so that will arrive tomorrow. Is there an alternative to running off a USB, or is that the only option?

Do you need me to upload any information once I've completed the tests, or is it simply a question of determining whether either of my RAM sticks are faulty?
 
Upvote 0 Downvote
it runs outside windows, i think it might do that to avoid conflicts with windows. One day isn't going to hurt so waiting is fine.

sysnative - you download program, run it, it creates a zip file. Upload zip file to a file sharing website and show link here.

GPU - 1 year is too long ago to likely be cause now.
 
Upvote 0 Downvote
Colif said:
it runs outside windows, i think it might do that to avoid conflicts with windows. One day isn't going to hurt so waiting is fine.

sysnative - you download program, run it, it creates a zip file. Upload zip file to a file sharing website and show link here.

GPU - 1 year is too long ago to likely be cause now.
Click to expand...

Annoyingly, my dotage has brought all of the Luddism but none of the patience that I anticipated. I want to know now!

I did read somewhere that particularly PSU components can degenerate over time - is it likely that my system being ~8 years old will have led to problems?

ETA: "I want to know now!" was intended as a humorous dig at myself, in classic British fashion. I only realised on re-reading that it may have come across as somewhat obnoxious, which wasn't my intent.
 
Upvote 0 Downvote
There is a memory tester in windows but its not as testing as Memtest.

Yes, 8 years is about right age for parts to start failing.

What PSU do you have?

Try running Samsung Magician on the ssd and check its health via the smart checking process, I don't know if it will work for the hdd given its made by them.

I don't think cause is the CPU but can always run https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

have you ever overclocked CPU? Is it overclocked now? that could cause BSOD.

after 8 years even parts of the motherboard can start to fail as well. Difficult to test that theory though.

I saw that you were being silly :)
 
Upvote 0 Downvote
Colif said:
There is a memory tester in windows but its not as testing as Memtest.

Yes, 8 years is about right age for parts to start failing.

What PSU do you have?

Try running Samsung Magician on the ssd and check its health via the smart checking process, I don't know if it will work for the hdd given its made by them.

I don't think cause is the CPU but can always run https://downloadcenter.intel.com/download/19792/Intel-Processor-Diagnostic-Tool

have you ever overclocked CPU? Is it overclocked now? that could cause BSOD.

after 8 years even parts of the motherboard can start to fail as well. Difficult to test that theory though.

I saw that you were being silly :)
Click to expand...

PSU: Coolermaster Silent Pro 700W
  • Ran Samsung Magician and was prompted to update firmware, which has now been done.
  • Ran IPDT and all tests came back Passed.
  • Have never overclocked and isn't currently overclocked.
Edited to add: ran the Windows memory test and it didn't flag any problems.
 
Last edited:
Upvote 0 Downvote
TooOldForThis said:
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?
Click to expand...
that explains 1 question i had, why there is only the 8th of October on this report.

Did you update drivers after the clean install?
I see problems all day with WUDFHost which is used by windows to run user mode drivers & WinPBRDiag which I am struggling to figure out the meaning of. I think its actually the windows recovery partition - https://answers.microsoft.com/en-us...ge-drive/942d8ce3-9ed3-4709-b8d2-92c891b0e8c7

Maybe @PC Tailor can get more meaning out of that sysnative file. or the dump files.
 
Upvote 0 Downvote
I have run the dump file(s) and you can see the full report(s) in the link below.
If you are prompted to "Run only if trusted" simply click play/run and the html will be viewed. This warning is always present.

Report: https://jsfiddle.net/2d7p5eLb/show/

Summary of findings:
KMODE_EXCEPTION_NOT_HANDLED
Probably caused by : ntkrnlmp.exe
--------------------
KMODE_EXCEPTION_NOT_HANDLED
Probably caused by : ntkrnlmp.exe
--------------------
KMODE_EXCEPTION_NOT_HANDLED
Probably caused by : ntkrnlmp.exe
--------------------
KMODE_EXCEPTION_NOT_HANDLED
Probably caused by : ntkrnlmp.exe
--------------------
KMODE_EXCEPTION_NOT_HANDLED
Probably caused by : ntkrnlmp.exe
Click to expand...

Looks like they're all the same and all a Divide by Zero exception after executing DPCs.
Code: 
nt!KiDivideErrorFault+0x30a
Bugcheck 1E
Arg1: ffffffffc0000094

1: kd> .trap ffff8388`05e30860
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=000000000000ba9f rbx=0000000000000000 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8023023afa6 rsp=ffff838805e309f0 rbp=ffff838805e30aa9
r8=0000000000000001  r9=ffffa385327f8ba0 r10=000000000000005a
r11=000000000000ba9f r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!PpmPerfSelectProcessorState+0x1a6:
fffff802`3023afa6 f7f1            div     eax,ecx

The consistent nature of this would usually indicate it is a buggy driver performing the illegal divide operation. It's just finding out which one. There are not many loaded modules overall though.

There could be some related errors:
Code: 
Event[160]:
The AMD External Events Utility service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Event[161]:
A timeout was reached (45000 milliseconds) while waiting for the AMD External Events Utility service to connect.
The AMD utility only appears once before a crash so could be unrelated, but there are quite a few Intel Network related warnings and errors leading up to some crashes:

Code: 
Event[654]:
Intel(R) 82579V Gigabit Network Connection-  Network link is disconnected. (obviously this could be intentional or unrelated)

Event[1173]
The local adapter does not support Bluetooth Low Energy.

Event[881]
The network adapter with hardware address 04-8D-38-28-18-AB has indicated packet coalescing capability without indicating support for one or more prerequisite receive filter capabilities (IPv4 0x00000000).
These aren't necessarily all problems, just relaying info from the event viewer.

Tie that in with a Wireless LAN card dating back to 2015 and the Intel(R) Gigabit Adapter NDIS 6.x driver and it reoccuring after fresh installs - it might be something.
 
Last edited:
Upvote 0 Downvote
i was going to ask about the network card as it could be cause (I seen plenty of old wifi cards causing issues this year)

try running off ethernet and see if it makes any difference. At least its drivers are from 2019.

Your atheros BT drivers seem out of place, atheros are for Broadcom devices, which your WIFI card isn't. Unless you have a Bluetooth card as well?

[/QUOTE]
PC Tailor said:
These are necessarily all problems,
Click to expand...
I suspect he meant to say aren't :)
 
Upvote 0 Downvote
Whoaaaahhhhh... ok, thanks for the help!

There’s an awful lot to unpack here, so I’m going to go get working on this just now. For clarity, I haven’t yet run the USB boot memory test thing, but was going to do that this evening - from what I’m reading above, there’s not actually any need for that at this point, right?
 
Upvote 0 Downvote
TooOldForThis said:
There’s an awful lot to unpack here, so I’m going to go get working on this just now.
Click to expand...
Don't worry, the majority of the info I posted is for myself and Colif (and anyone else who wants to view it) the important bit is you follow Colif's follow up advice:
Colif said:
try running off ethernet and see if it makes any difference. At least its drivers are from 2019.

Your atheros BT drivers seem out of place, atheros are for Broadcom devices, which your WIFI card isn't. Unless you have a Bluetooth card as well?
Click to expand...
The short is your Internet and Bluetooth drivers are under suspicion :)
 
Upvote 0 Downvote
PC Tailor said:
Don't worry, the majority of the info I posted is for myself and Colif (and anyone else who wants to view it) the important bit is you follow Colif's follow up advice:

The short is your Internet and Bluetooth drivers are under suspicion :)
Click to expand...

Excellent, that had been my takeaway from the posts. So, to update:
  • I pulled the wireless card and connected to the router via ethernet
  • I opened Windows Update to check for driver updates and found six or seven Intel drivers being prompted. I checked them all to download.
  • Computer required a restart to allow internal computer elves to do clever internal driver update magic.
  • Computer hit KMODE_EXCEPTION_NOT_HANDLED BSOD on restart after Windows had loaded, but before I could complete login.
  • Computer restarted as per BSOD and I have now been logged in for a little under ten minutes.
I just noticed Windows Update still requires a restart, so I don't know if maybe something was interrupted during the previous restart. I'll go through another manual restart just now and report back. As yet, I haven't looked at the Bluetooth drivers.
 
Upvote 0 Downvote
Update to the update:

Went ahead with the restart. Computer loaded up, I opened Microsoft Edge and stared at my screen stupidly for a minute with a fairly blank expression on my face (I think I need coffee!) and then had another BSOD.

Having then restarted once again per BSOD, I went into Device Manager, disabled the Bluetooth device and uninstalled the drivers. I have no idea what in the computer is using Bluetooth, so, yeah, that.

Will run the sysnative app again just now and...

BSOD HAS ENTERED THE CHAT

... or, rather, I'll run the app again now and post up the results.
 
Upvote 0 Downvote
While the sysnative app is running, I want to mention that every time the system crashes and reloads, I get a notification that Default Radeon WattMan settings have been restored due to an unexpected system failure. I don't know if that has any relevance or import, but it's the only visible notification that I'm getting at the moment.
 
Upvote 0 Downvote
https://www.dropbox.com/sh/h6xc7gz175q1g1m/AAD35M-ljWT3z9u9KLN2LgAha?dl=0

I'm not sure if you need a link each time I upload the zipped files, but there you go. I'm also not sure if I've correctly set things up on DropBox so that you only have access to those files, or if you can see all of my shameful secrets when you follow that link. Shrugs

Now, if you don't mind, I'm off to run the sysnative app again on account of how I had two more BSOD since my last post.
 
Upvote 0 Downvote
I just realised there are more Bluetooth and other drivers I hadn't previously seen in the Device Manager, listed under Network adapters. I had previously been dealing with the stuff listed only under Bluetooth. Should I remove them, also?


p.png
 
Upvote 0 Downvote
Clearly it wasn't the wifi card since you continue to bsod without it

amdkmpfd.sysATIATI video card driver20/03/2019In 5 of 5 dumps
atikmpag.sysATIATI video card driver16/08/2019In 2 of 5 dumps
odd the display drivers only in 2 crashes.

Default Radeon WattMan settings has been restored due to unexpected system failure

This message typically occurs after the GPU driver crashes and can be caused by one or more of the following.
  • Windows missing critical and or important updates
  • Corrupted registry keys/and or system files
  • Display drivers with known issues
  • Corrupted display driver
  • A overclocked processor, graphics card or system memory can cause system instability and excess heat which can cause GPU driver crashes.
If you continue to experience the same issue after trying the steps above, you may have defective hardware. Here are some suggestions to try and isolate which hardware inside your system is faulty.
A defective graphics card:

  • Check that the power supply meets the requirements of the graphics card.
  • Check that power supply cables properly secured to the graphics card.
  • Try reseating the graphics card into the PCI-E lane.
  • Try moving the graphics card to a different PCI-E lane.
  • Try the graphics card in a different system.
A defective or inadequate power supply.

Defective system memory:

  • Test system memory DIMMs individually to look for errors. The following third-party utility can be used to check for memory errors: MemTest86

If you wish to receive additional support or suggestions on this issue, please open a new discussion and provide the essential information required as specified here: https://community.amd.com/thread/196209
Click to expand...

these are all from this link and each point has additional steps below it here - https://community.amd.com/thread/235037


Its unlikely to be top 2 as this is a new win 10 install

could be GPU drivers so try running ddu and install newer drivers from AMD - https://forums.tomshardware.com/faq...n-install-of-your-video-card-drivers.2402269/

its not an OC processor so next step is check hardware like the gpu. Have you cleaned inside PC recently? dust could make cause heat
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom