F5F Stay Refreshed Hardware Desktop Timeout for Clock Watchdog on Multipule Processors

Timeout for Clock Watchdog on Multipule Processors

Timeout for Clock Watchdog on Multipule Processors

R
153
11-05-2022, 03:12 AM
#1
Essentially, my computer worked okay for a while but now I frequently encounter Clock Watchdog Timeout and BSOD errors. When playing games, the system would abruptly close the game and jump to the desktop, or in more demanding titles it would freeze and then freeze at 43% before requiring a forced restart. The situation worsened to the point where downloading games on Steam could trigger crashes. I reinstalled Windows 10 version 22H2, updated drivers, ran a chkdsk on the CDRIVE/Windows drive, performed a memtest86 which showed all RAM sticks passed, and tested with tools like prime95, passmark, 3dmark, cinebench—each ran briefly before freezing. My specs are: Corsair RMx 1000W power supply, Asus ROG STRIX Z690-E motherboard, Corsair Dominator Platinum RGB 64GB DDR5-6200 RAM, EVGA GeForce RTX 3090 Ti 24GB, Intel Core i9-12900KS at 3.4GHz with Noctua NH-U9S cooler, auto settings enabled, CMOS removed and BIOS updated. XMP is disabled. Current BIOS version is 2.21.1278. Anyone have suggestions?
R
RinkAudenaerde
11-05-2022, 03:12 AM #1

Essentially, my computer worked okay for a while but now I frequently encounter Clock Watchdog Timeout and BSOD errors. When playing games, the system would abruptly close the game and jump to the desktop, or in more demanding titles it would freeze and then freeze at 43% before requiring a forced restart. The situation worsened to the point where downloading games on Steam could trigger crashes. I reinstalled Windows 10 version 22H2, updated drivers, ran a chkdsk on the CDRIVE/Windows drive, performed a memtest86 which showed all RAM sticks passed, and tested with tools like prime95, passmark, 3dmark, cinebench—each ran briefly before freezing. My specs are: Corsair RMx 1000W power supply, Asus ROG STRIX Z690-E motherboard, Corsair Dominator Platinum RGB 64GB DDR5-6200 RAM, EVGA GeForce RTX 3090 Ti 24GB, Intel Core i9-12900KS at 3.4GHz with Noctua NH-U9S cooler, auto settings enabled, CMOS removed and BIOS updated. XMP is disabled. Current BIOS version is 2.21.1278. Anyone have suggestions?

L
Life_in_Pixel
Junior Member
10
11-05-2022, 07:55 AM
#2
Some research suggests the issue may stem from hardware problems or even minor events like sneezing during a Windows crash. Since you reinstalled Windows, it’s unlikely the OS itself is the cause. Consider checking your BIOS and related firmware for SSD or GPU updates. Verify you have the latest BIOS version and perform a CMOS reset. If the problem persists, a hardware fault is probable. Start by booting with only essential components: power supply, CPU cooler, RAM, and boot drive. Run stress tests like prime95 to identify failures. Add components gradually—GPU, RAM, etc.—and retest. The failing component will reveal the issue. If everything works under minimal setup, the problem likely lies in a physical part. Recheck connections and test with another system if needed. Good luck!
L
Life_in_Pixel
11-05-2022, 07:55 AM #2

Some research suggests the issue may stem from hardware problems or even minor events like sneezing during a Windows crash. Since you reinstalled Windows, it’s unlikely the OS itself is the cause. Consider checking your BIOS and related firmware for SSD or GPU updates. Verify you have the latest BIOS version and perform a CMOS reset. If the problem persists, a hardware fault is probable. Start by booting with only essential components: power supply, CPU cooler, RAM, and boot drive. Run stress tests like prime95 to identify failures. Add components gradually—GPU, RAM, etc.—and retest. The failing component will reveal the issue. If everything works under minimal setup, the problem likely lies in a physical part. Recheck connections and test with another system if needed. Good luck!

A
aliyah92
Junior Member
37
11-11-2022, 12:16 AM
#3
Currently, I’m certain it’s not Windows or driver-related. I performed a CMOS reset and waited about 30 minutes. I was able to boot into Windows’ Run Passmark Test (Extended Instructions with SSE), which is typically where my system experiences Clock Watchdog Timeout or BSOD. I was monitoring temperatures via CoreTemp. To my surprise, everything functioned correctly at first. Here are the BIOS default settings and CoreTemp readings. If I adjust the DRAM frequency to 4800MHz in BIOS, CoreVolt changes to 1.421 and MC voltage to 1.314 automatically. When I restart and run the Passmark test with CoreTemp, I encounter Clock Watchdog Timeout again. This suggests a possible connection between voltage or temperature settings.
A
aliyah92
11-11-2022, 12:16 AM #3

Currently, I’m certain it’s not Windows or driver-related. I performed a CMOS reset and waited about 30 minutes. I was able to boot into Windows’ Run Passmark Test (Extended Instructions with SSE), which is typically where my system experiences Clock Watchdog Timeout or BSOD. I was monitoring temperatures via CoreTemp. To my surprise, everything functioned correctly at first. Here are the BIOS default settings and CoreTemp readings. If I adjust the DRAM frequency to 4800MHz in BIOS, CoreVolt changes to 1.421 and MC voltage to 1.314 automatically. When I restart and run the Passmark test with CoreTemp, I encounter Clock Watchdog Timeout again. This suggests a possible connection between voltage or temperature settings.

W
Waverabbit
Senior Member
643
11-11-2022, 06:25 AM
#4
Just a brief update, I swapped out my CPU cooler and installed Intel XTU. After running the stress test for five minutes, it looks like my CPU is throttling its temperature. I suspect the cooler wasn’t sufficient and eventually caused damage over time. I’m planning to get a new one, the Noctua NH-U12A, in the hopes it’ll fix things. I’m really hoping it’s still alive.
W
Waverabbit
11-11-2022, 06:25 AM #4

Just a brief update, I swapped out my CPU cooler and installed Intel XTU. After running the stress test for five minutes, it looks like my CPU is throttling its temperature. I suspect the cooler wasn’t sufficient and eventually caused damage over time. I’m planning to get a new one, the Noctua NH-U12A, in the hopes it’ll fix things. I’m really hoping it’s still alive.

K
ktommer
Junior Member
6
11-12-2022, 10:25 AM
#5
Likely not. Standard air coolers aren't sufficient to handle the full power and speed of a 12900KS. Lowering turbo limits in BIOS can cause throttling. If PL1 and PL2 are set to unlimited, thermal throttling will occur. Adjusting CPU voltage, turbo limits, or speed may be necessary to manage high temperatures.
K
ktommer
11-12-2022, 10:25 AM #5

Likely not. Standard air coolers aren't sufficient to handle the full power and speed of a 12900KS. Lowering turbo limits in BIOS can cause throttling. If PL1 and PL2 are set to unlimited, thermal throttling will occur. Adjusting CPU voltage, turbo limits, or speed may be necessary to manage high temperatures.

D
DRzinho
Member
78
11-12-2022, 11:51 AM
#6
It's experiencing a crash under normal temperatures, with no significant spikes. I just began reviewing Event Viewer... forgot to check. Event1, WHEA-Logger: A fatal hardware error occurred. Details are in the data section of this event. Event ID: 1001 BugCheck: The system restarted after a bugcheck. The issue was 0x00000101 (address 0xfffff80277ea7180). A dump was saved at C:\Windows\MEMORY.DMP. Report ID: 00000000-0000-0000-0000-000000000000. Minidumps indicate ntoskrnl.exe + 3fd640 Memory and WHEA dumps.
D
DRzinho
11-12-2022, 11:51 AM #6

It's experiencing a crash under normal temperatures, with no significant spikes. I just began reviewing Event Viewer... forgot to check. Event1, WHEA-Logger: A fatal hardware error occurred. Details are in the data section of this event. Event ID: 1001 BugCheck: The system restarted after a bugcheck. The issue was 0x00000101 (address 0xfffff80277ea7180). A dump was saved at C:\Windows\MEMORY.DMP. Report ID: 00000000-0000-0000-0000-000000000000. Minidumps indicate ntoskrnl.exe + 3fd640 Memory and WHEA dumps.