BSOD 0x00000101: CLOCK_WATCHDOG_TIMEOUT the past few days when gaming

Hello,

Recently I've started receiving a BSOD that says Clock_Watchdog_Timeout. This seems to happen at high CPU usage such as playing games like Monster Hunter World, it has periodically happened the past week and more frequently multiple times the past two days.

I run Windows 10 Version 1909 (OS Build 18363.836) I had my i5-4690k OC'd to 4.5GHz, but have reduced that to the basics still an issue. I don't know why it's doing this usually I can figure it out, but I've linked the scan from the v2 Log Collector: Attachment 278878. Let me know if I'm missing anything.

System Specs:
CPU: Intel Core i5-4690k
HDD: 500GB Samsung 850 Evo
GPU: Nvidia GeForce GTX 1070
RAM: 16GB DDR3 G.Skill Trident 2400MHz
OS: Windows 10 64-bit Version 1909 (OS Build 18363.836)
Keyboard: Ducky Shine7 Cherry MXReds
Mouse: Logitech g600

Hi djseaghost,

There were no mini dump files collected.

Search for C:\windows\memory.dmp > post a share link into the thread using one drive, drop box, or google drive

Code:

LastWriteTime         Size (MB) FullName             
-------------         --------- --------             
5/15/2020 10:06:49 PM   1258.55 C:\WINDOWS\MEMORY.DMP

Hello here is the link to the dump file: MEMORY.DMP - Google Drive

For all steps / tests please make sure images are posted into the thread:

Take Screenshot in Windows 10
https://support.microsoft.com/en-gb/...re-screenshots
How to Upload and Post Screenshots and Files at Ten Forums



1) Open administrative command prompt and type or copy and paste:
2) sfc /scannow
3) dism /online /cleanup-image /scanhealth
4) dism /online /cleanup-image /restorehealth
5) sfc /scannow
6) chkdsk /scan
7) wmic recoveros set autoreboot = false
8) wmic recoveros set DebugInfoType = 7
9) wmic recoveros get autoreboot
10) wmic recoveros get DebugInfoType
11) bcdedit /enum {badmemory}

12) When these have completed > right click on the top bar or title bar of the administrative command prompt box > left click on edit then select all > right click on the top bar again > left click on edit then copy > paste into the thread

13) Make sure that there is no over clocking while troubleshooting

The displayed RAM speed was 2400.
The maximum supported for the CPU is 1600.

Intel(R) Core™ i5-4690K Processor (6M Cache, up to 3.90 GHz) Product Specifications

14) In the left lower corner search type: system or system control > open system control panel > on the left pane click advanced system settings

a) > on the advanced tab under startup and recovery > click settings > post an image of the startup and recovery window into the thread

b) > on the advanced tab under performance > click on settings > on the performance options window > click on the advanced tab > under virtual memory > click on change > post an image of the virtual memory window into the thread

15) Open Ccleaner > click windows tab or custom clean > scroll down to system and advanced > post an image into the thread

16) Upgrade the BIOS: 31.03 > 32.01
MAXIMUS VII HERO Driver & Tools | Motherboards | ASUS USA

17) Choose one of the temperature monitoring software applications: Speecy, HW monitor, Speed fan:
Speccy - Free Download - Piriform: Speccy - System Information - Free
Download Speccy | Find your computer specs, free!
Download Speccy | Find your computer specs, free!
HWMONITOR | Softwares | CPUID: HWMONITOR | Softwares | CPUID
HWMONITOR | Softwares | CPUID
SpeedFan - Access temperature sensor in your computer: SpeedFan - Access temperature sensor in your computer
SpeedFan - Access temperature sensor in your computer

18) Run Prime95 - Stress Test Your CPU
Prime95 - Stress Test Your CPU Windows 10 Performance Maintenance Tutorials
Prime95 - Stress Test Your CPU
a) Record the maximum temperature and post the maximum temperature into the thread
b) Record test duration and post the uninterrupted test duration into the thread
c) Aim for testing > 3 hrs and abort testing as needed for freezing, temperature changes (see link)
d) Use the Microsoft snipping tool to post images into the thread.
Take Screenshot in Windows 10 Windows 10 General Tips Tutorials
Take Screenshot in Windows 10

19) Run IPDT > post images into the thread
https://downloadcenter.intel.com/dow...iagnostic-Tool

20) For any BSOD:

a) run the V2 log collector to collect new log files

b) open file explorer> this PC > C: > in the right upper corner search for: C:\Windows\memory.dmp
> if the file size is < 1.5 GB then zip > post a separate share link into the thread using one drive, drop box, or google drive

Here is the steps from CMD:
Microsoft Windows [Version 10.0.18363.836]
(c) 2019 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>dism /online /cleanup-image /scanhealth

Deployment Image Servicing and Management tool
Version: 10.0.18362.1
Image Version: 10.0.18363.836[==========================100.0%==========================] No component store corruption detected.The operation completed successfully.

C:\WINDOWS\system32>dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.18362.1Image Version: 10.0.18363.836[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.

C:\WINDOWS\system32>sfc /scannow
Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.Windows Resource Protection did not find any integrity violations.

C:\WINDOWS\system32>chkdsk /scan
The type of the file system is NTFS.
Stage 1: Examining basic file system structure ...
636416 file records processed.
File verification completed.
6097 large file records processed.
0 bad file records processed.

Stage 2: Examining file name linkage ...
1701 reparse records processed.
830968 index entries processed.
Index verification completed.
0 unindexed files scanned.
0 unindexed files recovered to lost and found.
1701 reparse records processed.

Stage 3: Examining security descriptors ...
Security descriptor verification completed.
97277 data files processed.
CHKDSK is verifying Usn Journal...
37429088 USN bytes processed.
Usn Journal verification completed.
Windows has scanned the file system and found no problems.
No further action is required.

487725628 KB total disk space.
351802840 KB in 484799 files.
288340 KB in 97278 indexes.
0 KB in bad sectors.
796092 KB in use by the system.
65536 KB occupied by the log file.
134838356 KB available on disk.
4096 bytes in each allocation unit.
121931407 total allocation units on disk.
33709589 allocation units available on disk.

C:\WINDOWS\system32>wmic recoveros set autoreboot = false
Updating property(s) of '\\LOGIC-BOMB\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"'
Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros set DebugInfoType = 7
Updating property(s) of '\\LOGIC-BOMB\ROOT\CIMV2:Win32_OSRecoveryConfiguration.Name="Microsoft Windows 10 Home|C:\\WINDOWS|\\Device\\Harddisk0\\Partition2"
'Property(s) update successful.

C:\WINDOWS\system32>wmic recoveros get autoreboot
AutoReboot
FALSE

C:\WINDOWS\system32>wmic recoveros get DebugInfoType
DebugInfoType
7

C:\WINDOWS\system32>bcdedit /enum {badmemory}
RAM Defects-----------identifier
{badmemory}C:\WINDOWS\system32>

---

Ensured OC was off.

Here is Startup & Recovery image:
Attachment 278879

Here is Virtual Memory:

Attachment 278880

Here is Ccleaner:

Attachment 278881

That's all I have for now, will update BIOS and do the stress test in the morning, hopefully this helps.

As for the DMP file and v2 previously collected I added them to a google drive here are the links:

Memory.dmp:
MEMORY.zip - Google Drive

V2 Log:
LOGIC-BOMB-(2020-05-15_22-24-38).zip - Google Drive

For startup and recovery system failure: (these should have been modified)
a) uncheck the box to automatically restart
b) change kernel memory to automatic memory dump
c) reboot to maintain settings


For Ccleaner uncheck:
a) Memory Dumps
b) Windows log files


Read these links on Windows driver verifier:

a) learn how to use the Windows Recovery Environment (RE) commands: reset and bootmode to turn off the tool

b) do not use the tool until it is communicated in the thread

Enable and Disable Driver Verifier in Windows 10
https://answers.microsoft.com/en-us/...3-c48669e4c983

Just to confirm do not use the Windows Driver Verifier until someone confirms and tells me to?

If your comfortable having used it you can make a new restore point and start the tool with the 3 customized test settings in the Ten Forums link.

Before using the tool:
a) upgrade the BIOS
b) return the RAM to stock
c) complete Prime95 and IPDT testing
d) make a new restore point


Create System Restore Point in Windows 10



Windows driver verifier is designed to stress test drivers.

If there are misbehaving drivers the computer will crash.

If dump files are created they can be debugged.

Misbehaving drivers are then uninstalled and reinstalled.

The tool is run for approximately 48 hours and then an additional 36 hours after the last BSOD.

If there are no further BSOD this concludes the use of the tool.

After each BSOD you must turn off the tool in order to return to the desktop.

Learn the Windows RE commands reset and bootmode.

These are ran in safe mode or safe mode with command prompt.

In case these fail the next option is system restore.

If system restore fails you can restore a backup image or use registry commands.

Start the tool with the 3 customized test settings in the Ten Forums link.

Increase the simultaneous customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link.

There can be performance problems and / or slow boot while using the tool.

If necessary the customized test settings can be modified.

Summary:
a) make a new restore point
b) test all non-Microsoft drivers
c) test no Microsoft drivers
d) start with the 3 customized test settings in the Ten Forums link
e) increase the customized test settings by 3 - 5 / hour up to the 19 customized test settings in the Microsoft link

BSOD 0x00000101: CLOCK_WATCHDOG_TIMEOUT is most often a hardware issue.
While waiting for a reply from the other helpers, you may want to start with these free hardware diagnostics:

- MemTest86 (4 passes): MemTest86 - Official Site of the x86 Memory Testing Tool

- Seagate Seatools for Windows (long/extended test on ALL drive): SeaTools for Windows |
Seagate

- OCCT (all tests): OCBASE / OCCT

- Furmark (run until temp's level out or there are problems - whichever comes first): FurMark > Home

- Prime95 Stress Testing (run for at least an hour - or until the temp's level out. If you get errors, STOP IMMEDIATELY): GIMPS - Free Prime95 software downloads - PrimeNet

- Intel Processor Diagnostic Tool (if equipped w/Intel CPU): The Intel(R) Processor Diagnostic Tool