BSOD - Intermittent Clock Watchdog Timeout

JB615 · Sep 19, 2023

V2 Log

Hi,
I've been getting intermittent BSOD with the Clock_Watchdog_Timeout error.

I've updated BIOS, NVIDIA drivers, and Windows update, but can't seem to find the problem. It happens once every few days. It's driving me nuts. Hope you can help!

zbook · Sep 19, 2023

There were WHEA fatal and BSOD bugcheck 101 errors.

These are most often seen with malfunctioning hardware.

To potentially identify malfunctioning hardware start with software stress testing then plan hardware swap testing.

Please perform the following steps:

1) Run:

https://www.tenforums.com/attachments/bsod-crashes-debugging/360137d1645183388-batch-files-use-bsod-debugging-tuneup_plus_log.bat

https://www.tenforums.com/attachments/bsod-crashes-debugging/358470d1643456903-batch-files-use-bsod-debugging-gather_additional_dump_files.bat

Batch files for use in BSOD debugging - Windows 10 Help Forums

Information This thread is for use by the BSOD team to store batch files that can be used to collect additional data, fix settings or anything else that is useful in debugging BSOD problems in Windows 10. The way I see it working is the first

www.tenforums.com

Post share links into this thread using one drive, drop box, or google drive.

2) Download and install one of these temperature monitoring software:

Download Speccy | Find your computer specs, free!

Speccy - find the details of your computer's specs. Great for spotting issues or finding compatible upgrades. Download the latest version today.

www.ccleaner.com

HWMONITOR | Softwares | CPUID

HWMonitor for Windows® x86/x64 is a hardware monitoring program that reads PC systems main health sensors : voltages, temperatures, powers, currents, fans speed, utilizations, clock speeds ... The program handles : CPU and GPU-level hardware monitoring...

www.cpuid.com

SpeedFan - Access temperature sensor in your computer

3) Run Prime95 continuously for 3 hours

See the warnings about when to abort testing.

Record the continuous test duration and highest temperature.

Prime95 - Stress Test Your CPU

Stress test your CPU for stability issues with Prime95

www.tenforums.com

Post images or share links into this thread using one drive, drop box, or google drive.

4) Search for C:\windows\memory.dmp > save to the downloads folder > zip > post a separate share link with only the zipped memory dump

5) Run Samsung Magician on supported drives (all tabs) > post images or share links into this thread using one drive, drop box, or google drive

Samsung Magician Software | Samsung Semiconductor USA

Samsung Magician software is designed to help you manage your Samsung SSD with a simple, intuitive user interface. Download files & find supported models.

semiconductor.samsung.com

6) Run HD Sentinel (free or trial version) (all drives)

Hard Disk Sentinel - HDD health and temperature monitoring

Monitoring hard disk health and temperature. Test and repair HDD problems, predict disk failure.

www.hdsentinel.com

Post images or share links into this thread for results on these tabs:
a) Overview
b) Temperature
c) SMART

JB615 · Sep 20, 2023

Thanks for replying. I have all but the Prime95 test done. Will get that done and uploaded tomorrow.
Hard Disk Sentinel
Samsung Magician
Debugging bat log 1
Debugging bat log 2
Memory dmp

zbook · Sep 20, 2023

Nice progress.

When available post HD Sentinel images or share links for Z: or Samsung SSD 980 PRO 1TB

Also Run: OCCT one hour tests

OCBASE/OCCT : Free, all-in-one stability, stress test, benchmark and monitoring tool for your PC

Ocbase is the home of OCCT, the most popular all-in-one stability / stress testing / benchmarking / monitoring tool available for PC

www.ocbase.com

Post images or share links into this thread

zbook · Sep 20, 2023

For any new BSOD run the V2 log collector and post a share link into the newest post.

BrianInEngland · Sep 20, 2023

I was getting this error a while back, same error every time so wasn't likely the RAM. Turns out my CPU failed, the error was due to one of the cores failing.

JB615 · Sep 20, 2023

Hmm..currently running the OCCT test. It has only been 6 minutes, but I can see the CPU temp at 100 degrees C.

JB615 · Sep 20, 2023

Hard Disk Sentinel for Z:
OCCT 1 Hour

JB615 · Sep 20, 2023

Prime95

zbook · Sep 20, 2023

The HD Sentinel results were excellent.
(these are prediction results)

OCCT and Prime 95 each displayed pass.
OCCT as compared to Prime95 is designed to abort testing as needed.
Please run different OCCT one hour stress tests to see if it is possible to trigger BSOD or test fails.
For any new BSOD run the V2 log collector and post a share link into the newest post.

If there are more confirmatory WHEA 124 and / BSOD bugcheck 101 then plan to swap test the Intel CPU.

ubuysa · Sep 21, 2023

0x101 bugchecks often turn out to be a bad CPU, it is possible for a rogue driver to cause these bugchecks but that's far less common. Since your 0x101 bugchecks are intermittent that might point more towards this being a driver caused BSOD?

If you have a kernel dump of a 0x101 bugcheck I can take a look and confirm whether a driver was (or was not) responsible. For me to be able to do this your most recent dump must have been a 0x101 and you'll need to upload the file C:\Windows\Memory.dmp to the cloud with a link to it here (be sure to make it public). There's no point in uploading minidumps, you can't fully analyse a 0x101 from a minidump.

JB615 · Sep 21, 2023

This is from C:\windows\memory.dmp

Memory dmp 2

PerpetualCycle · Sep 21, 2023

JB615 said:
Hmm..currently running the OCCT test. It has only been 6 minutes, but I can see the CPU temp at 100 degrees C.

No offense to anyone, but some of these suggested tests should not be run unless you have adequate cooling.

zbook · Sep 22, 2023

The BSOD bugcheck 101 is typically seen with malfunctioning CPU.

The WHEA 124 fatal supports malfunctioning hardware.

Additional BSOD bugchecks would be useful as 101 can be seen with malfunctioning RAM / motherboard (many types of bugchecks).

OCCT has default stop testing settings.

An older version of OCCT has a default stop testing if above 85 degrees.

Intel® Core™ i9-12900K Processor

Intel® Core™ i9-12900K Processor (30M Cache, up to 5.20 GHz) Product Specifications

Intel® Core™ i9-12900K Processor (30M Cache, up to 5.20 GHz) quick reference guide including specifications, features, pricing, compatibility, design documentation, ordering codes, spec codes and more.

ark.intel.com

Thermal Monitoring Technologies Yes

T JUNCTION 100°C

Code:

Thermal Monitoring Technologies
Thermal Monitoring Technologies protect the processor package and the system from thermal failure through
several thermal management features.
An on-die Digital Thermal Sensor (DTS) detects the core's temperature, and the thermal management features
reduce package power consumption and thereby temperature when required in order to remain within normal
operating limits.

Code:

Could my processor get damaged from overheating?
It's unlikely that a processor would get damaged from overheating, due to the operational safeguards in place.
Processors have two modes of thermal protection, throttling and automatic shutdown.
When a core exceeds the set throttle temperature, it will reduce power to maintain a safe temperature level.
The throttle temperature can vary by processor and BIOS settings.
If the processor is unable to maintain a safe operating temperature through throttling actions, it will automatically shut down
to prevent permanent damage.

ubuysa · Sep 22, 2023

Unfortunately both of the kernel dumps you uploaded are corrupted. I didn't comment on the first one just in case it was a glitch, but now you've had two it's not a glitch, it's a hardware problem

When a bugcheck occurs, the kernel cannot trust the normal disk I/O subsystem and drivers, the only storage media it has available that is all Microsoft drivers and is already open is the paging subsystem, so the kernel writes a kernel dump to the paging file as it displays the BSOD blue screen. That's whats the % counter is indicating, the progress of the kernel dump being written to the paging file.

Then it either reboots automatically or the user reboots. When the paging subsystem is first initialised on a boot, it checks to see whether there is a kernel dump in the paging file. If there is, then that dump is read into RAM and from there a minidump is extracted and written to the C:\Windows\Minidump folder, and the full kernel dump is written to the file C:\Windows\Memory.dmp, overwriting any earlier dump.

You can see from the above that there are two items of hardware where a problem can corrupt the dump; the paging file storage drive, and RAM.

Samsung Magician and the SMART data suggest that you paging device is good, so that leaves RAM. It's unusual for RAM to cause a 0x101 bugcheck, but it's not impossible. If you have more than one stick of RAM installed, then I suggest removing one stick and running on the other for long enough to see whether it BSODs. Then swap sticks and try running on the other, again for long enough to have had a BSOD.

You could try running Memtest86 (free) but no memory tester can find 100% of RAM problems, whereas removing one stick at a time can.

zbook · Sep 22, 2023

ubuysa said:
Unfortunately both of the kernel dumps you uploaded are corrupted. I didn't comment on the first one just in case it was a glitch, but now you've had two it's not a glitch, it's a hardware problem

Please recheck the links and dump files.

ubuysa · Sep 22, 2023

zbook said:
Please recheck the links and dump files.

Are you saying the dumps are not corrupted for you?

ubuysa · Sep 22, 2023

Downloaded with a different browser and still corrupt. Here's the first dump...

Code:

Microsoft (R) Windows Debugger Version 10.0.20348.1 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [D:\Users\Downloads\MEMORY (1)\MEMORY.DMP]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Dump completed successfully, progress percentage: 50


************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       cache*C:\MySymbols
Deferred                                       srv*https://msdl.microsoft.com/download/symbols
Symbol search path is: cache*C:\MySymbols;srv*https://msdl.microsoft.com/download/symbols
Executable search path is:
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Windows 10 Kernel Version 22621 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22621.1928.amd64fre.ni_release_svc_prod3.230622-0951
Machine Name:
Kernel base = 0xfffff800`5e600000 PsLoadedModuleList = 0xfffff800`5f2130e0
Debug session time: Wed Sep 20 02:38:31.688 2023 (UTC + 3:00)
System Uptime: 0 days 2:26:17.297
Missing image name, possible paged-out or corrupt data.
Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
WARNING: .reload failed, module list may be incomplete
Debugger can not determine kernel base address
Loading Kernel Symbols
Missing image name, possible paged-out or corrupt data.
.Unable to load image Unknown_Module_00000000`00000000, Win32 error 0n2
*** WARNING: Unable to verify timestamp for Unknown_Module_00000000`00000000
*** ERROR: Module load completed but symbols could not be loaded for Unknown_Module_00000000`00000000
Unable to add module at 00000000`00000000
Unable to read KLDR_DATA_TABLE_ENTRY at 00000000`00000000 - HRESULT 0x80004002

WARNING: .reload failed, module list may be incomplete
GetContextState failed, 0xD0000147
CS descriptor lookup failed
GetContextState failed, 0xD0000147
GetContextState failed, 0xD0000147

The second kernel dump is the same.