BSOD MACHINE_CHECK_EXCEPTION after Windows 10 mouse freezes

Associate
Joined
17 Apr 2017
Posts
36
Hi,

I have an overclocked i7-3970X running at 4.7 GHz with +0.025V offset VCore.

I'm experiencing infrequent (but at least once per day) mouse freezes in Windows (pretty much everything is frozen) then shortly after (like 10s or so) it BSOD with a MACHINE_CHECK_EXCEPTION.

However, no error information can be collected (it stays at 0% collecting error info) and I have to hard power off the pc.

Does anyone know of a cause? Is my VCore too low perhaps? I've tried upping the VCore slowly but the problem isn't going away. The whole problem is I have no debugging info to go on at the moment.

As far as I know all my drivers are up to date and I have the latest BIOS.

Anyone got a similar problem or know of a possible solution?
 
Interestingly my system with a 3920K has been experiencing Windows stop codes recently. I thought it might be a driver issue, so ran DDU and reinstalled the video drivers. This has certainly reduced the number of stops to blue screen, but not completely. When I try to read the memory dump there is no details of a fault/problem? My settings are exactly the same as they have been for over 2 years. This problem seems to have started around the time of the last large Windows update, but I can't be sure.

I had intended to upgrade this year to Z370, so hopefully I can too find and fix the problem as August is still a long way off !
 
Was this overclock very recent? I had the exact same issue when I pushed my CPU to 4.6ghz, but the problem completely goes away when it is back down to 4.5ghz.
 
I found the problem lessened when I changed my VTT settings from manual to auto. (or whatever the setting is for the 1st cpu cache voltage - I may have written the wrong name).
 
Does the problem go away if you do not overclock?

Of course. The issue is getting my pc stable with this overclock. I don't always get the error message either. Generally it all just hangs, so there is no debugging information or anything in the event logs. It's a hard one to solve.
 
Of course.

I'm sorry, that wasn't clear from your OP.

The issue is getting my pc stable with this overclock. I don't always get the error message either. Generally it all just hangs, so there is no debugging information or anything in the event logs. It's a hard one to solve.

I suggest you keep dialling the overclock back until it's 100% stable, then progress from there.
 
Back
Top Bottom