KMODE_EXCEPTION_NOT_HANDLED

[gupott]

Hi there,

I have been having random BSOD with KMODE_EXCEPTION_NOT_HANDLED over the last few weeks. Its an older Win 10 PC with the following specs;

Palit GeForce GTX 970 Jetstream
i5-3570K @ 4.3ghz (1.23v) using a Noctua NHU12P
Gigabyte Z77-D3H mobo
Samsung 500GB SSD + 1TB + 3TB normal drives
Patriot Viper (2x4GB) DDR3 PC3-12800C9
Corsair TX 750w psu

It has been stable for years but something seems to have annoyed it recently. I have moved my desk around and it is actually in a cooler place, temps are around 55c normally. I have cleaned the case out and refitted the CPU. Everything has been updated as far as I know.

It will do Prime95 for hours and I have used it all day and it just occasionally gives a BSOD with the error message but nothing about a dodgy driver. There does not appear to be any logic to the crashes.

Anybody have any thoughts on what to try next?
Thanks

 

[gupott]

Thanks for the reply.

I had the same thoughts. I had it at stock for a while and still the same problem. So I took it back to the 'stable' overclock however the BSOD persisted all the same. Since then I have been fiddling around looking for stability. I am not sure I had this problem prior to the Microsoft Fall update which is the only real thing I can think of that changed. As I say, it will do Prime95 with the CPU's at 100% and be fine, it ran for 3-4 hours the other day no problem. It feels like a driver issue but I am not sure as the BSOD doesn't give me a clue.

Any more ideas?

 

[gupott]

I also just ran a memory test. The only thing notes was [NOTE] RAM may be vulnerable to high frequency row hammer bit flips. Now I don't know what that is (I will google), but it sounds amazing!

 

[gupott]

The PC is still BSOD at random occasions. I am not sure what to try next. I used it all day today and it just crashed, no idea why. Temps fine

Anybody else think of something else to try?