Share via

Clock Watchdog Timeout BSOD

Anonymous
2024-07-09T09:13:33+00:00

Hi, I have a pretty serious problem wich seems to come from my cpu ( i9 12900k ) :
a BSOD error ( Clock Watchdog Timeout) occurs when running high cpu demanding programs such as benchmark softwares (cinebench r24) , Intel processor diagnostic tool, long video games sessions (modded red dead 2 , FiveM). First i monitored my temperatures and they were Extremely high so I thought the temperatures caused the crashes. But It apparently was not because i undervolted the cpu and the BSODs still occured.
So I ran memtest86 and no problem was found with the ram, ( ADATA XPG Lancer DDR5 )
same for the gpu using furmark. ( AMD Radeon 6900XT from XFX )
and since i don't know how to benchmark or diagnose my MOBO i didn't do anything to it ( gigabyte Z690 Gaming X DDR5 )
I am using windows 11.
I have also tried to : -reset CMOS
-update bios to latest version ( F29 )
-edit some settings in the reg edit : disabling MPO
And the now the problem got even worse, because after some time the PC starts to give some flickering black screens that last 5 to 20 seconds every 30min.
When these black screens started to happen i benchmarked the gpu using furmark and still nothing happened.
I now have no clue how to solve the problem, any help would be extremely apreciated !

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

1 answer

Sort by: Most helpful
  1. DYARI BARHAM 34,936 Reputation points Independent Advisor
    2024-07-09T11:02:10+00:00

    Hi Anas,

    I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

    Please go to C:\Windows\Minidump and copy any minidump files you find to your desktop. Afterward, share these files through OneDrive or Google Drive so we can analyze them and identify the specific file that's causing the crash.

    https://answers.microsoft.com/en-us/windows/for...

    Was this answer helpful?

    0 comments No comments