Executing CLOCK_WATCHDOG_TIMEOUT multiple times consistently.
Executing CLOCK_WATCHDOG_TIMEOUT multiple times consistently.
I've recently enhanced my setup by swapping out the Asrock H310M and i3-8100 with a Asrock B450M and a Ryzen 5 5600. The new components were put in more than two weeks ago, and I've been experiencing this BSOD for a day. It mostly appears after the system starts. I've even seen it on the login screen. I tried the memory diagnostic tool, ran malware scans, updated GPU and driver files, performed chkdsk, reattached the GPU, SATA SSD, and RAM. I've also encountered "irql_not_less_or_equal" twice and a "System service exception" once. Could someone assist? I have two folders for dump files—Minidump and Minidumps. The Minidump folder was empty, while the Minidumps contained those files. I attempted the PERFMON feature but couldn't save it because the option was grayed out. Operating system—Windows 10 x64 What OS was originally installed? - Windows 10 Age of system (hardware) - Motherboard and CPU (2 weeks), GPU (Almost 5 months), PSU and RAM (4 years, with one stick being replaced somewhere in between) Age of OS installation - Have you reinstalled the OS? - Yes, more than a year Desktop. MSI 6600XT (refurbished) Ryzen 5 5600 Asrock B450M Corsair Vengeance 2x8GB DDR4 3000 mhz Corsair VS450
It functioned at first then ceased? Likely a burn from failure, indicating hardware damage. A crash upon startup usually points to memory issues. The B450 is a Pre-Ryzen2 model, so a bios mismatch could be the cause if your system doesn’t support it. Updated June 2, 2023 by Bombastinator
I've been running smoothly after purchasing the components, but this issue just began yesterday. It doesn<|pad|> to start right away—it's slow at first, then it kicks in after a while. Once I launch Chrome and search for the error online, I notice the BSOD appears about 10 to 15 minutes after booting, according to what I've seen over the past couple of hours.
New code alert, everyone. I experimented without each stick and changed the slots, then went back to the original setup. Every time I tried to start, I got the "bad_system_config_info" BSOD again. Then it restarts and lands me on the automatic repair screen. I also noted that my PC has been booting into automatic repair for about 8 to 9 hours. I used startup repair, which got me back into Windows normally. After that, I powered down the PC and performed the RAM test above. Now it keeps going to automatic repair, but startup repair doesn’t bring me back to Windows.
Memory BSODs appear unpredictably, with multiple Clock_Watchdog_Error errors rarely occurring together. Such a scenario is extremely unlikely. The probability is nearly zero. This issue typically arises from an unstable CPU overclock or undervolt settings, so I’d first check the BIOS and disable PBO. As the OS repair message indicates, the problem stems from corrupted files. While crashes can cause this, the underlying cause might differ. The startup repair utility isn’t very effective for fixing corruption, which explains why it didn’t resolve the issue. Did you perform a clean installation after updating your motherboard? Make sure it included a full format and fresh setup.
Tried a different approach. PBO was turned off, but I still faced the irql_not_less_or_equal BSOD. To clarify, I've been encountering this issue for several days now. Irql appears intermittently—only a few times in the last couple of days—and the clock_watchdog_timeout shows up occasionally. I've run the Windows memory diagnostic multiple times, swapped RAM modules, tested with one drive at a time, changed SATA slots, and attempted to boot without any drives. I also performed a stress test twice. The error reported in the dump files points to ntkrnlmp.exe. This was a solution I found on the Microsoft forum after uploading my dump files. Regarding the operating system, I recently installed a brand new Windows version on an M.2 SSD. I also considered the possibility that my PSU might be insufficient, since 450W might not be enough, but the error persists even after disconnecting my SSDs and HDDs. I've reinstalled Windows a few times, and after each installation, the error disappears for about a day. I can play any game without issues—whether it's GTA, Rainbow Six, or MW2. However, whenever the error occurs, a game isn't open or I'm using alt-tab.