F5F Stay Refreshed Hardware Desktop Occasional random freezes can cause CPU spikes.

Occasional random freezes can cause CPU spikes.

Occasional random freezes can cause CPU spikes.

M
MaZie_SwS
Member
Find
66
06-23-2020, 09:19 PM
#1
In short, this happened unexpectedly after a stable period. Yesterday evening I experienced a sudden crash—like a freeze—forcing me to shut down the PC. I resumed browsing and shopping, then went to sleep. After returning from work, I decided to play a game to unwind. The moment it started, the computer froze briefly, then the bottom half of the screen turned black while the rest remained blank, and it rebooted. I checked logs and saw an unexpected recovery from shutdown. Task Manager showed high CPU usage at 100%, but no reboot occurred. I tried running Cinebench to test the CPU and noticed a freeze without restarting. After rebooting, the issue disappeared, and Cinebench ran smoothly. I suspect the problem might be related to my GPU being removed or reinstalled recently. The specs are an i5-8600K with an RTX 3060TI, and I haven’t overclocked it. Could a recent change have triggered this alert?
Reply
Reply
M
MaZie_SwS
06-23-2020, 09:19 PM #1

In short, this happened unexpectedly after a stable period. Yesterday evening I experienced a sudden crash—like a freeze—forcing me to shut down the PC. I resumed browsing and shopping, then went to sleep. After returning from work, I decided to play a game to unwind. The moment it started, the computer froze briefly, then the bottom half of the screen turned black while the rest remained blank, and it rebooted. I checked logs and saw an unexpected recovery from shutdown. Task Manager showed high CPU usage at 100%, but no reboot occurred. I tried running Cinebench to test the CPU and noticed a freeze without restarting. After rebooting, the issue disappeared, and Cinebench ran smoothly. I suspect the problem might be related to my GPU being removed or reinstalled recently. The specs are an i5-8600K with an RTX 3060TI, and I haven’t overclocked it. Could a recent change have triggered this alert?

Reply
Reply