F5F Stay Refreshed Hardware Desktop Issues with the watchdog timeout causing BSOD on the clock watcher.

Issues with the watchdog timeout causing BSOD on the clock watcher.

Issues with the watchdog timeout causing BSOD on the clock watcher.

B
bennyplaymc
Member
136
10-04-2016, 06:01 AM
#1
I performed a fresh Windows installation on April 29 and experienced no problems for several days. Now I’m encountering the same BSOD again—it appears as CLOCK_WATCHDOG_TIMEOUT after the boot screen and during the loading screen. The spinning wheel freezes, then the crash occurs, but the PC restarts normally afterward. Afterward, Riot Vanguard fails to load properly. I’ve tried several fixes: re-seated RAM, cleaned CPU with new thermal paste, turned off PBO, and updated BIOS to version 3607 (file SB550EG.CAP). Performance monitor reports are still disabled.
B
bennyplaymc
10-04-2016, 06:01 AM #1

I performed a fresh Windows installation on April 29 and experienced no problems for several days. Now I’m encountering the same BSOD again—it appears as CLOCK_WATCHDOG_TIMEOUT after the boot screen and during the loading screen. The spinning wheel freezes, then the crash occurs, but the PC restarts normally afterward. Afterward, Riot Vanguard fails to load properly. I’ve tried several fixes: re-seated RAM, cleaned CPU with new thermal paste, turned off PBO, and updated BIOS to version 3607 (file SB550EG.CAP). Performance monitor reports are still disabled.

S
StainLord
Junior Member
6
10-04-2016, 02:15 PM
#2
Clock_Watchdog_Violation indicates the CPU is stuck (frozen). This often occurs due to unstable overclocking or undervoltage, though it can also point to a defective CPU. The power supply and motherboard might contribute too, but less commonly. Based on your previous actions, a bad CPU is the most likely cause.
S
StainLord
10-04-2016, 02:15 PM #2

Clock_Watchdog_Violation indicates the CPU is stuck (frozen). This often occurs due to unstable overclocking or undervoltage, though it can also point to a defective CPU. The power supply and motherboard might contribute too, but less commonly. Based on your previous actions, a bad CPU is the most likely cause.

S
Sqhizophrenic
Junior Member
11
10-04-2016, 10:52 PM
#3
Additional details are available in this discussion, and I’m also getting a feeling about the CPU. I thought it’d be good to check the socket/pins with a magnifying glass.
S
Sqhizophrenic
10-04-2016, 10:52 PM #3

Additional details are available in this discussion, and I’m also getting a feeling about the CPU. I thought it’d be good to check the socket/pins with a magnifying glass.

K
krazydude05
Junior Member
31
10-05-2016, 06:18 AM
#4
It seems the system isn't operating normally in safe mode, which can affect the CPU performance. There appears to be reduced workload, but I'm uncertain if the PPM process is active (Process Power Management controls power states for the CPU).
K
krazydude05
10-05-2016, 06:18 AM #4

It seems the system isn't operating normally in safe mode, which can affect the CPU performance. There appears to be reduced workload, but I'm uncertain if the PPM process is active (Process Power Management controls power states for the CPU).