Question "BSOD Clock Watchdog Timeout" - - - PC freezes during high usage and when idle?
Question "BSOD Clock Watchdog Timeout" - - - PC freezes during high usage and when idle?
Hello,
I assembled my PC and have been using it for more than two years. Recently, I've experienced a BSOD or frequent freezing during gameplay or idle periods. The problem began a few days back when I left the computer on overnight and returned to find it had stopped working. The room temperature hasn't changed much, but my CPU temperature rises about 20 degrees above average when idle, while the liquid cooler's temperature is significantly higher. Typically these two metrics match, but lately they're not. There hasn't been any change in ambient conditions. I've noticed the temperature spikes to 80-90 degrees whenever a game loads or when the system reaches full load (previously max CPU temps stayed under 65 degrees). I intend to reapply thermal paste, though it's uncertain if this is the root cause since my CPU stays below 65 degrees during crashes. My GPU temperatures never exceed 65 degrees even at full load.
My backup file is 33GB, and I've shared it via WinDbg if that would assist. I haven't overclocked and all BIOS settings are in auto mode, including the RAM profile (no XMP or XMP II enabled). I suspect the issue might lie with the motherboard, though I'm not very experienced. I'd appreciate any advice you can offer to resolve this.
Google Drive Link
https://drive.google.com/file/d/1-Cdi3jL...drive_link
Would you like me to share that dump publicly? The 33GB file contains the complete kernel memory dump, which is necessary for this bug check. The 0x101 bug check can't be analyzed from a minidump. Also, please ensure there are no overclocks on the CPU and remove any undervolting. We should verify that the CPU operates at standard voltages and speeds to confirm the issue isn't due to them. What cooling solution is installed?
dump files are not available for public use.
a kernel dump would be ideal if you obtain it. (memory.dmp)
compressing the dump can help reduce its size.
you may also offer a more compact minidump.
if your system frequently crashes, you can download and execute microsoft rammap64.exe as an administrator, navigate through the options, and when the system checks the kernel dump, it should be smaller or better compressed.
consider using the Windows Device Manager and turning off all sound sources that aren’t connected to a speaker. For instance, disable the GPU sound if your monitor lacks one, or turn off motherboard sound in BIOS when not in use.
also, open the Windows Control Panel and Device Manager, search for any incomplete devices and resolve those issues. (remind the device manager to display hidden devices and remove greyed-out entries from the device tree)
Attached is the dump file you requested.
A note about compression helped significantly reduce the file size.
Before this problem, I experienced several PC crashes over the two years I built the machine. Now I plan to download the programs and disable all non-essential sound sources.
Updated link provided above; sorry for not sharing it earlier, as I’m new to this.
CPU and RAM are running at default or auto settings in BIOS.
I tried undervolting but likely failed.
The ASUS BIOS screen is quite complex, and I’m not very experienced with overclocking, so I’ll need more information before trying again.
Currently, all BIOS settings have been reset to defaults, so no OC or undervolt options remain.
My cooler is an AIO Corsair H150i Elite equipped with three 120mm fans and a 360mm radiator cooling system.
not confident about the dump. it seems like new stuff to me.
alternatively, you could check:
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 couldn't read bios info
the system halted early during boot (about 2 seconds). it was attempting to load drivers. the only third-party driver visible is asterovd.sys
FAILURE_BUCKET_ID: AV_nt!RtlRbRemoveNode
you mentioned a service called "dellinstumentation"
i didn't expect this, but your machine appears to be an asus system.
is this a remote dell admin tool?
if you can boot, i'd remove the service.
https://www.jamibi.co.uk/tutorials/delli...death-bsod
The dump file was the first usable one I managed to obtain. Most of the time (70 out of 30), my computer would freeze and I never encountered a BSOD. If it crashes again, I’ll send an updated dump file. It seems the problem occurs randomly—sometimes right after startup, during a game, or when I’m not using the PC for about ten minutes while it’s idle.
It appears that Kernel-mode Hardware-enforced Stack Protection was disabled by default. I turned it back on to check if it would resolve the issue.
When I first started experiencing crashes, I noticed the iaStorVD.sys driver (Intel® Rapid Storage Technology driver) had problems, as indicated by an exclamation mark in Device Manager. I was able to install a new driver, but I’m unsure if it caused conflicts with the one I downloaded from the ASUS website. Regardless, I reinstalled a fresh version of Windows and lost all my files.
My machine isn’t a remote Dell admin tool, but I did own a Dell PC before, and I currently have two Dell monitors (one is an Alienware). Following your advice, I removed the driver.
The Intel RST driver is recognized as a common issue, but it's only necessary if you're using Optane memory or a RAID setup. If present, it should be maintained up to date. Analysing the dump will take some time; the 0x101 bugcheck is particularly challenging to locate. The problem arises when a processor fails to respond to the clock synchronisation interrupt. I must identify which processor didn't respond and determine if a driver was interfering or if the processor was enabled for interrupts but didn't react. I'll start working on this today (Tue 22nd).
Well that was a letdown. The uploaded dump doesn't match the expected 0x101 CLOCK_WATCHDOG-TIMEOUT bugcheck, but instead points to a more frequent 0x7E SYSTEM_THREAD_EXCEPTION_NOT_HANDLED issue. There are numerous factors that might lead to this bugcheck, but it essentially shows an exception occurred in kernel code and the recovery processes failed, resulting in a BSOD. However, I notice you've installed Windows cleanly now, and the dump I've seen is from after the reinstall. This raises concerns—are these BSODs still occurring? Are you still facing issues post-reinstallation?