Hey All,
I built a new system in August. The first few months, the system has been running fine. There had been some crashes while running Rust but at the time I thought that was related to EasyAntiCheat. But now, after 6 months of use I can barely boot into a clean install of Windows 11 without BSODing. I have been having this problem for multiple days now and I feel like I have tried everything the first page of Google tells me when I look up my error, so I’m hoping for some personalised advice.
My specs are:
Gigabyte z690 Aorus ELITE AX
Seasonic Focus GX 850
Intel core i9-12900K
Samsung 980 pro 2TB SSD
2x Kingston FURY beast 16 GB 5200MHz DDR5 (packaged separately)
MSi Ventus 3X 3070 Ti 8GB
What I have already tried:
Everytime I boot my pc, it is a matter of minutes until my pc crashes and shows the CLOCK_WATCHDOG_TIMEOUT error. A MEMORY.DMP file is made but is corrupt and cannot be analysed by WinDbg. Mini dump folder is empty. This is what WinDbg says about the crash MEMORY.DMP file for TomsHardware - Pastebin
UPDATE:
Finally a few crashes have been saved to the minidump folder.
These are:
Minidumpfile 1 - Pastebin
Minidumpfile 2 - Pastebin
The error does not always show and will sometimes just freeze the pc and I have to hard reset it with the power button.
this issue can be forced by running any program that will ask a lot from the CPU. During the clean install of windows it happened multiple times and starting a heavier game like Battlefield 2042 will also cause a crash.
I don’t know what to do anymore. I am afraid it might be a faulty CPU or that it just isn’t getting enough power.
I built a new system in August. The first few months, the system has been running fine. There had been some crashes while running Rust but at the time I thought that was related to EasyAntiCheat. But now, after 6 months of use I can barely boot into a clean install of Windows 11 without BSODing. I have been having this problem for multiple days now and I feel like I have tried everything the first page of Google tells me when I look up my error, so I’m hoping for some personalised advice.
My specs are:
Gigabyte z690 Aorus ELITE AX
Seasonic Focus GX 850
Intel core i9-12900K
Samsung 980 pro 2TB SSD
2x Kingston FURY beast 16 GB 5200MHz DDR5 (packaged separately)
MSi Ventus 3X 3070 Ti 8GB
What I have already tried:
- Reinstalling every hardware component except for my CPU
- Checking power requirements for my parts
- Checking for CPU overheating
- Clean install of windows (can barely complete this successfully, followed Tons Hardware instructions)
- DISM check
- Memory diagnostics check
- Changing my M2 SSD to the M2A _CPU slot on my motherboard
- (Hopefully) turned off any and all possible overclocking options in bios
- Updated bios to latest version 23Fa
- Checking if RAM is in motherboard recommended slots
- Tons of googling
- My two pci-e connectors to my GPU are 2 x 6-pin+loose 2-pin connectors. They are the ones supplied by my PSU and are labelled "PCIe".
- My computer is not plugged in directly to the mains but is connected via extension cable (not too sure if or why this would have any impact)
- I have not tested my RAM sticks via a bootable USB which was recommended in some other posts. Only downside is, I can’t boot into windows currently to download the program.
Everytime I boot my pc, it is a matter of minutes until my pc crashes and shows the CLOCK_WATCHDOG_TIMEOUT error. A MEMORY.DMP file is made but is corrupt and cannot be analysed by WinDbg. Mini dump folder is empty. This is what WinDbg says about the crash MEMORY.DMP file for TomsHardware - Pastebin
UPDATE:
Finally a few crashes have been saved to the minidump folder.
These are:
Minidumpfile 1 - Pastebin
Minidumpfile 2 - Pastebin
The error does not always show and will sometimes just freeze the pc and I have to hard reset it with the power button.
this issue can be forced by running any program that will ask a lot from the CPU. During the clean install of windows it happened multiple times and starting a heavier game like Battlefield 2042 will also cause a crash.
I don’t know what to do anymore. I am afraid it might be a faulty CPU or that it just isn’t getting enough power.
Last edited: