[SOLVED] kmode_exception_not_handled

[Appletax]

Caused by Ntoskrnl.exe.

This is a newer gaming machine. Tested the RAM and performed system file checker and check disk. Crashes every few minutes. Always the same BSOD. Recommendations are to fix driver issues, which I have no clue how to do given that I have no clue as to which driver is the issue, if any are an issue. No Google search suggestion has been helpful. I just want to nuke Windows at this point.

 

[Larry Sabo]

Just boot a Win PE and run Nirsoft's BlueScreenView.

 

[Appletax]

Just boot a Win PE and run Nirsoft's BlueScreenView.

That’s what I did.


Sent from my iPhone using Tapatalk Pro

 

[Appletax]

That’s what I did.


Sent from my iPhone using Tapatalk Pro

Should I post the BSOD dump? Try drive more verifier?


Sent from my iPhone using Tapatalk Pro

 

[Sky-Knight]

Google searches are useless on that error. It either means a driver is bad, or the system has defective RAM, and possibly (though far less commonly) a bad SSD or weak PSU.

It must be troubleshot via crash dump analysis after a full hardware diagnostic. Random yahoos out in the world aren't going to succeed here, so all you're going to find while searching is an endless warren of complaints without resolution. This one requires solid technical skills, it will NOT be easy.

 

[Mick]

You say it crashes every few minutes. Anything in Event Viewer, to narrow things down a bit? Could also run SDIO to see what it thinks about your existing drivers. Again - just trying to find a starting point.

 

[Appletax]

Google searches are useless on that error. It either means a driver is bad, or the system has defective RAM, and possibly (though far less commonly) a bad SSD or weak PSU.

It must be troubleshot via crash dump analysis after a full hardware diagnostic. Random yahoos out in the world aren't going to succeed here, so all you're going to find while searching is an endless warren of complaints without resolution. This one requires solid technical skills, it will NOT be easy.

I don't know how to do that Offered to reinstall Windows 10. Only thing I can think of that might fix the issue easily.

 

[Porthos]

I don't know how to do that Offered to reinstall Windows 10. Only thing I can think of that might fix the issue easily.

When I encounter strange seeming unfixable issues in Windows even a repair install does not address, I slap in my spare SSD and install windows from scratch and test.

 

[Sky-Knight]

A N&P will certainly clear any driver issues, and it's a ton quicker to do than a real fix...

So honestly, unless you're curious this is exactly the circumstances where a N&P is the proper solution. This specific blue screen tends to come back after being fixed... and I run into it far more commonly on units that were upgraded from Win7/8 to 10.

I can fix them, and have them come back in six months, or I can N&P and never see the unit again.

There is a catch though... this error CAN be due to hardware defect too... so if another drive / install doesn't resolve it... you get to figure that out by removing devices one at a time until you find it.

 

[Appletax]

Great responses!! I opted for a nuke and pave, but it's nice to know what's required to actually fix the issue.

Computer has not crashed once since nuking it. Fingers crossed it stays that way