F5F Stay Refreshed Hardware Desktop Error WHAE_Unfixable and Clock_Watchdog_Timeout detected

Error WHAE_Unfixable and Clock_Watchdog_Timeout detected

Error WHAE_Unfixable and Clock_Watchdog_Timeout detected

Pages (3): 1 2 3 Next
B
badwill911
Junior Member
28
07-18-2021, 01:24 AM
#1
Details: i5 11400 Aorus Z590 Master 2x8 Corsair 3000mhz Vengeance RGB Pro WVGA GTX 970 EVGA 600w PSU. BSODs appear only when XMP is active. I ensured the motherboard runs the latest BIOS and tested both Windows 10 and 11. I re-seated CPU, GPU, RAM, and swapped drives to SATA. Tried different RAM slots one at a time. Consulted guides but changing C-States didn’t help. Possibly the CPU is the issue. No spare board available for testing. Need advice, thank you.
B
badwill911
07-18-2021, 01:24 AM #1

Details: i5 11400 Aorus Z590 Master 2x8 Corsair 3000mhz Vengeance RGB Pro WVGA GTX 970 EVGA 600w PSU. BSODs appear only when XMP is active. I ensured the motherboard runs the latest BIOS and tested both Windows 10 and 11. I re-seated CPU, GPU, RAM, and swapped drives to SATA. Tried different RAM slots one at a time. Consulted guides but changing C-States didn’t help. Possibly the CPU is the issue. No spare board available for testing. Need advice, thank you.

L
loltribo
Posting Freak
870
07-18-2021, 02:14 AM
#2
Hello, The issue lies in some motherboards not fully supporting XMP profiles, even when the RAM is correct. Certain CPU-RAM pairings can cause instability, leading to errors or crashes. It's usually safer to run without XMP enabled for a reliable setup.
L
loltribo
07-18-2021, 02:14 AM #2

Hello, The issue lies in some motherboards not fully supporting XMP profiles, even when the RAM is correct. Certain CPU-RAM pairings can cause instability, leading to errors or crashes. It's usually safer to run without XMP enabled for a reliable setup.

M
MasterMito0
Junior Member
28
07-20-2021, 02:56 AM
#3
Well, at least it's not something major I was concerned about. I was actually nervous I might have had a dead CPU or RAM sticks.
M
MasterMito0
07-20-2021, 02:56 AM #3

Well, at least it's not something major I was concerned about. I was actually nervous I might have had a dead CPU or RAM sticks.

B
BladeOBlood
Member
190
07-29-2021, 09:58 AM
#4
Aww well if it's running solid then you can rejoice and be happy! It just means you cannot run it at full speeds together but it still can be a good performer. If games run good then that's great!
B
BladeOBlood
07-29-2021, 09:58 AM #4

Aww well if it's running solid then you can rejoice and be happy! It just means you cannot run it at full speeds together but it still can be a good performer. If games run good then that's great!

J
JosephGamez
Member
141
07-29-2021, 11:29 PM
#5
Things are working much smoother now. I upgraded from a 4440s, which was a big improvement for me. Playing beatsaber has become a lot more fun since the upgrade.
J
JosephGamez
07-29-2021, 11:29 PM #5

Things are working much smoother now. I upgraded from a 4440s, which was a big improvement for me. Playing beatsaber has become a lot more fun since the upgrade.

L
lihlo
Junior Member
41
08-06-2021, 06:31 AM
#6
Great to hear from Yuchoji, it's nice to witness the significant power boost. Seeing that difference in actual gameplay is impressive. The VR experience is cool too—this shows what a great computer can do for immersion. It's enjoyable and thrilling!
L
lihlo
08-06-2021, 06:31 AM #6

Great to hear from Yuchoji, it's nice to witness the significant power boost. Seeing that difference in actual gameplay is impressive. The VR experience is cool too—this shows what a great computer can do for immersion. It's enjoyable and thrilling!

J
JamesHond7
Posting Freak
838
08-06-2021, 01:03 PM
#7
Details: i5 11400 Aorus Z590 Master 2x8 Corsair Vengeance RGB PRO 3000mhz EVGA GTX 970 EVGA 600w Power Supply. I contacted the forums about repeated BSODs. Initially, I thought it was XMP enabled, but crashes persisted. For about seven hours, the system ran smoothly without any interruptions until I tried launching RPCS3, which triggered another BSOD. Using WinDBG, I analyzed the MEMORY.DMP file and found some confusing data. I’m not sure what to do next. I’ve tried everything to understand the issue, but it’s really exhausting.

Key points:
- Clock watchdog timeout failed on a secondary processor
- Indicates the CPU was stuck and not handling interrupts
- Specific arguments and values provided
- Debug info shows CPU activity and timings
- System logs suggest a processor failure
- No clear resolution yet
J
JamesHond7
08-06-2021, 01:03 PM #7

Details: i5 11400 Aorus Z590 Master 2x8 Corsair Vengeance RGB PRO 3000mhz EVGA GTX 970 EVGA 600w Power Supply. I contacted the forums about repeated BSODs. Initially, I thought it was XMP enabled, but crashes persisted. For about seven hours, the system ran smoothly without any interruptions until I tried launching RPCS3, which triggered another BSOD. Using WinDBG, I analyzed the MEMORY.DMP file and found some confusing data. I’m not sure what to do next. I’ve tried everything to understand the issue, but it’s really exhausting.

Key points:
- Clock watchdog timeout failed on a secondary processor
- Indicates the CPU was stuck and not handling interrupts
- Specific arguments and values provided
- Debug info shows CPU activity and timings
- System logs suggest a processor failure
- No clear resolution yet

S
S4NP3I
Member
194
08-06-2021, 09:13 PM
#8
Hello, I'm sorry to hear that your issue persisted even after changing settings. The crash dump was logged in the new forum thread you created.
S
S4NP3I
08-06-2021, 09:13 PM #8

Hello, I'm sorry to hear that your issue persisted even after changing settings. The crash dump was logged in the new forum thread you created.

J
JessDu67
Junior Member
33
08-08-2021, 11:33 AM
#9
Check if crashes happen while the system is idle. Reinstalling Windows might resolve the issue.
J
JessDu67
08-08-2021, 11:33 AM #9

Check if crashes happen while the system is idle. Reinstalling Windows might resolve the issue.

C
cookiegal1410
Member
219
08-08-2021, 05:41 PM
#10
I experienced the same error when switching back to my previous SSD on an older system, and I've also attempted to reinstall Windows multiple times without success.
C
cookiegal1410
08-08-2021, 05:41 PM #10

I experienced the same error when switching back to my previous SSD on an older system, and I've also attempted to reinstall Windows multiple times without success.

Pages (3): 1 2 3 Next