Windows 10: Sudden system freezes. No BSOD

Within a couple of hours after replacing my CPU cooler, my system froze on three separate occasions. No sound. No response from mouse or keyboard. Monitors kept showing a frozen image. On one of these occasions I waited a couple of minutes before resetting, but it stayed frozen.

The freezes were sudden. No graphical glitches. No BSOD. Nothing in the event viewer, as far as I can tell. On two of these occasions I had HWMonitor visible, and no temperature was above 60°C.

This happened two days ago and I had no freezes yesterday, nor so far today. Outside of those three freezes, the system is working just fine. I wasn't doing anything in particular when the freezes occurred that I haven't done since without issue.

While replacing the cooler, I unseated the CPU to more easily clean it around the sides. I was careful not to touch or damage the pins, but could this potentially have something to do with the problem? I was surprised the BIOS detected a hardware change on startup.

I'm at a loss to know how to diagnose this problem and the worry of it happening again and not knowing how to prevent it is eating me up. I could go into more detail about several of the circumstances, but since I have no idea what's causing this problem I don't know what would be relevant. If anyone could point me in the right direction or has any idea of what might be going on, I'd be grateful.

:)

 

Random hard resets with no errors, pop-ups, or bsod.


No record of new BSOD's
What kind of a crash was it?

• BSOD Crash
• Sudden restart/shutdown crash
• Freeze crash

 

BSOD and freezing

Yesterday I started up my laptop from hibernating and it freezes, after restarting several times I get a BSOD which freezed on the BSOD one time.
After restarting again the laptop freezed at the Welcome screen.
I have had the freezing before, it was gone for about 2 months.
I did not install any new hardware.
Now it seems to run fine again.

But what is causing the freezing and the BSOD?
I bought this laptop last January.

 

Getting BSOD 0x124 error

Ignore what everone said here.

0x124 BSOD is usually related to VCCIO (VTT), run Prime95 version 26.6 with custom sizes of 512K to 640K with 50% of your memory for at least 8 hours.

If you get a 0x124 BSOD, increase VCCIO voltage by small steps, run Prime95 again until your stable.

If you pass Prime95 512K to 640K without a BSOD, then its Vcore too low. I'd suggest running IntelBurnTest with 80% of your memory to verify stability (8 to 12 hours).

Oh, and yeah, if this problem appeared all of the sudden, the reason is CPU degradation, you can prevent it by enabling C-States or adjust your overclock to use lower voltages.