Question "BSOD Clock Watchdog Timeout" - - - PC freezing when under load and when idling ?

[da1016]

Hello,

I built my PC and have owned it for over two years. For the past few days I've either gotten a BSOD or my PC freezes when either playing a videogame or when idling. The issue started a few days ago when I accidently left my pc on when I went to sleep and came back to see my PC had frozen. Temps do not seem bad, but my CPU when idling is about 20 degrees higher than average and is much higher than my liquid temperature. Usually there is a correlation between the two, and they are close in temperature.

There has also not been a change in ambient room temperatures. I've seen it jump to 80-90 degrees when opening a new game or when the load gets to 100%, which has never happened before (previously highest temps on CPU were no more than 65 degrees). I plan on reapplying thermal paste but given that my CPU temps are no higher than 65 degrees when crashing, I'm not sure that is the issue.
My GPU temps never get hotter than 65 degrees even under 100% load.

My dump file is 33GB, so I'm not sure how I can share that. I opened it in WinDbg and have shared the link if that helps. I've never overclocked my PC, and everything in the BIOs is set to auto, including the the RAM profile (so no XMP or XMP II). I believe the issue is the motherboard, but I'm not super knowledgeable so I'd appreciate any help ya'll could give me to help fix the issue.

Google Drive Link
https://drive.google.com/file/d/1-Cdi3jL6Jnm-Lbz7mJQ8ITP6paDBWmru/view?usp=drive_link

So far, I've attempted the following:

• Updating drivers
• Resetting bios and updating to most recent Bios
• Reinstalling windows
• Testing RAM on memtest86
• Moved RAM to different slots (from 2&4 to 1&3)
• Tested CPU briefly, but temps were too high
• Checked cable connections
• Ran Chkdsk to check storage
• Used DDU to remove old GPU drivers and installed newest driver
• Tried to limit voltage for CPU on asus mobo (not sure if I did this right, but voltage is still higher than what I set it at)

Specs:

Operating system: Microsoft Windows 11 Home,
CPU: 12th Gen Intel(R) Core(TM) i9-12900K with Corsair H150i Elite
GPU processor: MSI SUPRIM LIQUID GeForce RTX 4090
RAM: Corsair Vengeance 32GB (2x16GBJ) DDR5 5200MhZ c40 UDIMM
MOBO: ROG STRIX Z690-E GAMING WIFI
PSU: EVGA SuperNOVA 1300w GT Power Supply
SSD1 - Samsung 980 2 TB NVME
SSD2 - Samsung 990 2 TB NVME
SSD3 - Samsung SSD860 EVO 4TB
HDD - Seagate 14.6TB


Display (3): AW3225QF
Resolution: 3840 x 2160 (native)
Refresh rate: 60 Hz

Display (2): LC32G7xT
Resolution: 2560 x 1440 (native)
Refresh rate: 240 Hz

Display (1): DELL S3220DGF
Resolution: 2560 x 1440 (native)

 

[KingLoki]

Have a read of this post, it might help?

https://forums.tomshardware.com/thr...100c-with-volt-of-1-45.3753248/#post-22632025

 

[KingLoki]

Voltage issues may be the problem, especially the overheating cpu.
Try using the Intel Xtreme Tuning Utility as other posts suggest in link above. Check back in with results. Cheers.

 

[ubuysa]

I'd like to see that dump, can you make it public please (anyone with the link)? From the 33GB size that will be the full kernel memory dump, which is what we need for this bugcheck. The 0x101 bugcheck cannot be analysed with a minidump.

Do you have an overclock on the CPU? If so please remove it. Also, remove any undervolt that you may have. We need the CPU at stock voltages and frequencies to be sure that these were not causing the problem.

What cooler do you have on that CPU?

 

[johnbl]

Hello,

I built my PC and have owned it for over two years. For the past few days I've either gotten a BSOD or my PC freezes when either playing a videogame or when idling. The issue started a few days ago when I accidently left my pc on when I went to sleep and came back to see my PC had frozen. Temps do not seem bad, but my CPU when idling is about 20 degrees higher than average and is much higher than my liquid temperature. Usually there is a correlation between the two, and they are close in temperature. There has also not been a change in ambient room temperatures. I've seen it jump to 80-90 degrees when opening a new game or when the load gets to 100%, which has never happened before (previously highest temps on CPU were no more than 65 degrees). I plan on reapplying thermal paste but given that my CPU temps are no higher than 65 degrees when crashing, I'm not sure that is the issue.
My GPU temps never get hotter than 65 degrees even under 100% load.

My dump file is 33GB, so I'm not sure how I can share that. I opened it in WinDbg and have shared the link if that helps. I've never overclocked my PC, and everything in the BIOs is set to auto, including the the RAM profile (so no XMP or XMP II). I believe the issue is the motherboard, but I'm not super knowledgeable so I'd appreciate any help ya'll could give me to help fix the issue.

Google Drive Link
https://drive.google.com/file/d/10kZ9utatQ4VTsnNLOYLtpnSNM86ayfQV/view?usp=drive_link

So far, I've attempted the following:

1. Updating drivers
2. Resetting bios and updating to most recent Bios
3. Reinstalling windows
4. Testing RAM on memtest86
5. Moved RAM to different slots (from 2&4 to 1&3)
6. Tested CPU briefly, but temps were too high
7. Checked cable connections
8. Ran Chkdsk to check storage
9. Used DDU to remove old GPU drivers and installed newest driver
10. Tried to limit voltage for CPU on asus mobo (not sure if I did this right, but voltage is still higher than what I set it at)

Specs:

Operating system: Microsoft Windows 11 Home,
CPU: 12th Gen Intel(R) Core(TM) i9-12900K with Corsair H150i Elite
GPU processor: MSI SUPRIM LIQUID GeForce RTX 4090
RAM: Corsair Vengeance 32GB (2x16GBJ) DDR5 5200MhZ c40 UDIMM
MOBO: ROG STRIX Z690-E GAMING WIFI
PSU: EVGA SuperNOVA 1300w GT Power Supply
SSD1 - Samsung 980 2 TB NVME
SSD2 - Samsung 990 2 TB NVME
SSD3 - Samsung SSD860 EVO 4TB
HDD - Seagate 14.6TB


Display (3): AW3225QF
Resolution: 3840 x 2160 (native)
Refresh rate: 60 Hz

Display (2): LC32G7xT
Resolution: 2560 x 1440 (native)
Refresh rate: 240 Hz

Display (1): DELL S3220DGF
Resolution: 2560 x 1440 (native)

dump file not shared for public access.
kernel dump would be best if you got it. (memory.dmp)
you can compress the dump to reduce the size.
you can also provide a smaller minidump.

if your machine crashes often, then you can download and run microsoft rammap64.exe run it as an administrator, find the empty menu and run all of the options. later when your system bugchecks the kernel dump should be a smaller size or compress more.

you might consider using windows device manager and disable all sound sources that do not have a speaker connected to them. for example, the gpu sound can be disabled if the monitor does not have a speaker. motherboard sound can be disabled in bios if you are not using it.

also go into windows control panel device manager. look for any device that did not complete its install and fix those problems. (also tell device manager to show hidden devices and look for greyed out entries in the device tree and delete them)

 

[da1016]

dump file not shared for public access.
kernel dump would be best if you got it. (memory.dmp)
you can compress the dump to reduce the size.
you can also provide a smaller minidump.

if your machine crashes often, then you can download and run microsoft rammap64.exe run it as an administrator, find the empty menu and run all of the options. later when your system bugchecks the kernel dump should be a smaller size or compress more.

you might consider using windows device manager and disable all sound sources that do not have a speaker connected to them. for example, the gpu sound can be disabled if the monitor does not have a speaker. motherboard sound can be disabled in bios if you are not using it.

also go into windows control panel device manager. look for any device that did not complete its install and fix those problems. (also tell device manager to show hidden devices and look for greyed out entries in the device tree and delete them)

See attached for dump file https://drive.google.com/file/d/1-Cdi3jL6Jnm-Lbz7mJQ8ITP6paDBWmru/view?usp=drive_link . Thanks for the tip about compression, that helped reduce the file size quite a bit. Prior to this issue, I had a handful of pc crashes for the two years I built the pc, but I will download those programs and look at disabling all sound sources not in use.

I'd like to see that dump, can you make it public please (anyone with the link)? From the 33GB size that will be the full kernel memory dump, which is what we need for this bugcheck. The 0x101 bugcheck cannot be analysed with a minidump.

Do you have an overclock on the CPU? If so please remove it. Also, remove any undervolt that you may have. We need the CPU at stock voltages and frequencies to be sure that these were not causing the problem.

What cooler do you have on that CPU?

See above for updated link, sorry about not making it public before, I'm new to this. I don't have an overclock on my CPU or my RAM, everything is running at default or auto in the bios. I attempted to undervolt, but I think I failed. The ASUS bios screen is a bit complex, and I'm pretty ignorant when it comes to overclocking so I'll have to read more before attempting again (as of now all settings in the bios have been reset to default, so no oc or undervolt). As far as my cooler, I have an AIO Corsair H150i Elite with 3 120mm fans and a 360mm radiator cooling system.

 

[johnbl]

not sure about the dump. it looks like new stuff to me.
maybe this:
tps://www.elevenforum.com/t/enable-or-disable-kernel-mode-hardware-enforced-stack-protection-in-windows-11.14966/

notes:
iaStorVD.sys Thu Jun 29 02:04:12 2023
debugger could not read bios info

the system stopped very early in the boot process. (2 seconds)
it was trying to load drivers. the only 3rd party driver I see in the list is the
iastorvd.sys
FAILURE_BUCKET_ID: AV_nt!RtlRbRemoveNode

you had a service called "dellinstumentation"
i did not expect this, your machine looked like a asus machine.
is it a remote dell machine admin tool?
i would remove the service if you can boot.
https://www.jamibi.co.uk/tutorials/dellinstrumentationsys-blue-screen-of-death-bsod

 

[da1016]

not sure about the dump. it looks like new stuff to me.
maybe this:
tps://www.elevenforum.com/t/enable-or-disable-kernel-mode-hardware-enforced-stack-protection-in-windows-11.14966/

notes:
iaStorVD.sys Thu Jun 29 02:04:12 2023
debugger could not read bios info

the system stopped very early in the boot process. (2 seconds)
it was trying to load drivers. the only 3rd party driver I see in the list is the
iastorvd.sys
FAILURE_BUCKET_ID: AV_nt!RtlRbRemoveNode

you had a service called "dellinstumentation"
i did not expect this, your machine looked like a asus machine.
is it a remote dell machine admin tool?
i would remove the service if you can boot.
https://www.jamibi.co.uk/tutorials/dellinstrumentationsys-blue-screen-of-death-bsod

That dump file was the first usable file I was able to get. The majority of time (70/30 ratio) my pc just freezes and I never get a BSOD. If it crashes again I will send an updated dump file. I think part of the issue is that the crashes are random, sometimes right after bootup, during a game session, and when I'm away from my pc for 10 minutes while it idles.

Looks like Kernel-mode Hardware-enforced Stack Protection was turned off for me by default, I turned it on to see if that helps make a difference.

When I first started crashing I noticed that the iaStorVD.sys driver (Intel(R) Rapid Storage Technology driver) had issues with it as it had an exclamation mark under device manager. I managed to install a new driver, but I wonder if it conflicted with the driver that I downloaded from the asus website. Regardless, I installed a fresh new version of windows, and didn't bring back any of my files.

My machine is not a remote dell admin tool, but I previously owned a Dell pc, and I currently have two dell monitors (one is an Alienware). Regardless, I followed your advice and removed the driver.

 

[ubuysa]

The Intel RST driver is a known source of problems, though unless you're running Optane memory or a RAID array you don't actually need it. If you have it then it does need to be kept updated.

It will take a while for me to analyse that dump, the 0x101 bugcheck is a tricky one to track down. It happens because a processor didn't respond to the clock synchronisation interrupt, so I need to track down which processor failed to respond and then look to see whether a rogue driver was blocking the interrupt or whether the processor was enabled for interrupts and simply didn't respond. I'll get on that today (Tue 22nd).

 

[ubuysa]

Well that was a disappointment. The uploaded dump is not for the expected 0x101 CLOCK_WATCHDOG-TIMEOUT bugcheck, instead it's a more common 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED. There are many things that can cause this bugcheck, all it really indicates is that an exception occurred in kernel code and the recovery routines were unable to recover and so we got a BSOD.

However, I see that you have clean installed WIndows since this problem happened, and since the dump I've been using...

Regardless, I installed a fresh new version of windows, and didn't bring back any of my files.

That begs the question of whether these BSODs are still happening? Are you still having problems after the reinstall?

 

[johnbl]

there was a dellinstumentation root device connected to the device tree root
I think it was so it could do bios updates. I have never seen it before but I would not want it. if you can boot, i would try to remove it