Bsod – “kmode_exception_not_handled”

Topic

New Reply

Windows 10-64-AU. Tonight I started Google Chrome and the machine crashed with a KMODE_EXCEPTION_NOT_FOUND error. In preparation for trying to get more dump information, I changed Startup & Recovery options to take a complete memory dump on a different hard disk (S: drive, not the boot disk); I did this because the last time the machine tried to dump it didn’t take the complete dump; Event Log said the complete dump had to be deleted because I don’t have enough space on my boot drive (120GB SSD with a very large page file to support the complete dump).

I ran both BlueScreenView and WhoCrashed and neither “see” the complete MEMORY.DUMP on the S: drive but it’s there. They reported on the minidump and there wasn’t much information in there beyond the location of the crash (ntoskrnl.exe); it could not point to any errant drivers.

1) Is it valid to have the complete memory dump go to a different drive?
2) Is there a way for either BlueScreenView or WhoCrashed access the dump thinking it might shed more information?

I can’t believe Windows 7 ran so nicely on this machine and Windows 10 has been such a pain

Thanks!

Rob

Reply | Quote

Replies

Hi, Rob.

A STOP 0x0000001E KMODE_EXCEPTION_NOT_HANDLED is a common BSOD but it has many possible causes, please follow the collection procedure used in your previous topic (if this is the same PC, I’ll combine the topics as 5-10 days between crashes usually means the same fault).

Reply | Quote

Satrow: Attached is the data gathered from the Sysnative tool. Many thanks for looking into this (again).

Rob

Reply | Quote

Satrow: I think I’m having RAM issues. I’ve got 4 DIMMS of 8GB RAM; if I test the machine with all 32GB, I get errors (Memtest86, Memtest86+, and Windows built-in memory test). I’ve taken 16GB out of the machine and tested again with no problems so I need to narrow this down.

Reply | Quote

I’m going to mark this thread as solved and thank satrow for his help. I’m having an issue on my machine; I’ve got 4 DIMM sockets and when one of them is populated, I get memory errors. All 4 of my DIMM modules check out error-free when tested in pairs so I’m pretty confident it’s not a problem with the actual memory. I don’t know if this is the source of all of my BSOD issues but it can’t be a good thing.

Rob

Reply | Quote

When you are checking memory, it should be done on just one stick at a time and in different slots, before moving onto the next stick.

Reply | Quote