Jump to content

kmode_exception_not_handled without BSOD

Go to solution Solved by downinthemorgue,

An update to the situation:

 

Hey all,

 

Turns out my issue was 1) a bad seating on the GPU and 2) a badly seated sata connection to an NZXT controller. Thanks for all the help and hopefully this helps somebody in the future.

Hey all,

 

As the title suggests I've gotten kmode_exception_not_handled error without a BSOD occurring (Got this from WhoCrashed). Instead, randomly my PC will freeze up and restart with my MOBO logo loading into windows as if I just turned on the PC from a power off state even when Im not doing anything intensive. It's important to know this only started happening after I swapped my case and added some lian li infinity fans and Asia horse cable extensions to my MOBO and GPU. The error doesn't happen too often either maybe once or twice a day regardless of load.

 

So far Ive tried updating BIOS, Updating chip set, updating Windows 10, and updating GPU drivers. Ive also tried running Windows Memory Diagnostic (No Errors with EXPO enabled at 6000mhz CL30) and re-seating my RAM. I don't havce spare components to test everything seperately unfortunately so Im at a loss. Any help is aprecciated, thanks.

 

Specs: https://pcpartpicker.com/list/WJz8DZ

Capture.PNG

Link to comment
https://linustechtips.com/topic/1577332-kmode_exception_not_handled-without-bsod/
Share on other sites

Link to post
Share on other sites

17 minutes ago, downinthemorgue said:

Hey all,

 

As the title suggests I've gotten kmode_exception_not_handled error without a BSOD occurring (Got this from WhoCrashed). Instead, randomly my PC will freeze up and restart with my MOBO logo loading into windows as if I just turned on the PC from a power off state even when Im not doing anything intensive. It's important to know this only started happening after I swapped my case and added some lian li infinity fans and Asia horse cable extensions to my MOBO and GPU. The error doesn't happen too often either maybe once or twice a day regardless of load.

 

So far Ive tried updating BIOS, Updating chip set, updating Windows 10, and updating GPU drivers. Ive also tried running Windows Memory Diagnostic (No Errors with EXPO enabled at 6000mhz CL30) and re-seating my RAM. I don't havce spare components to test everything seperately unfortunately so Im at a loss. Any help is aprecciated, thanks.

 

Specs: https://pcpartpicker.com/list/WJz8DZ

Capture.PNG

Sounds like cache instability, do you have a X3D chip?

Link to post
Share on other sites

1 minute ago, downinthemorgue said:

Yes I have a 7800x3d

Ok so these chips have some issues with their V-Cache (the thing that makes the X3D part) making the chip unstable, it should be fixed with a BIOS update, but if that doesn't help send it back to AMD and ask for a new one

Link to post
Share on other sites

4 minutes ago, ArushM said:

Ok so these chips have some issues with their V-Cache (the thing that makes the X3D part) making the chip unstable, it should be fixed with a BIOS update, but if that doesn't help send it back to AMD and ask for a new one

I already updated my bios to f21, same issue. I'll probably send the chip back to AMD if I can't fix it with anything else.

Link to post
Share on other sites

12 hours ago, ArushM said:

NP good luck and goodnight

An Update: My PC crashed even after disabling EXPO and fast startup. What im trying next is updating my BIOS again but this time using the QFlash feature instead of GCC application like I did for BIOS f21. So far so good, will update later.

Link to post
Share on other sites

If you still crash, go to C:\Windows\Minidump and check if you have any minidump files. If you do, go back to the Windows folder and copy the Minidump folder itself to the Downloads folder (You can use the desktop if you don't have OneDrive syncing files). Zip the copied folder and attach it to a post. Please follow the instructions to the letter as Windows doesn't like you messing with files in this location.

Link to post
Share on other sites

  • 1 month later...

An update to the situation:

 

Hey all,

 

Turns out my issue was 1) a bad seating on the GPU and 2) a badly seated sata connection to an NZXT controller. Thanks for all the help and hopefully this helps somebody in the future.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×