CLOCK_WATCHDOG_TIMEOUT BSOD

Question

Hello All,

My computer has been experiencing BSOD's starting last week. The BSOD will only occur while I am playing a videogame and even then the time in which the BSOD occurs will vary each time. I could have just booted the game or have been playing for an hour. The error code is CLOCK_WATCHDOG_TIMEOUT. I checked my minidump file and the Image Name was Unknown_Image. I need help as I don't know what to do to fix this. Minidump pasted here:

CLOCK_WATCHDOG_TIMEOUT (101)
An expected clock interrupt was not received on a secondary processor in an
MP system within the allocated interval. This indicates that the specified
processor is hung and not processing interrupts.
Arguments:
Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffffc4007ee00180, The PRCB address of the hung processor.
Arg4: 0000000000000004, 0.

Debugging Details:
------------------

***** Debugger could not find nt in module list, module list might be corrupt, error 0x80070057.

BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_8_PROC

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN8_DRIVER_FAULT

CURRENT_IRQL:  0

STACK_TEXT:  
fffff800`c9bdcb78 fffff800`c76a0378 : 00000000`00000101 00000000`00000018 00000000`00000000 ffffc400`7ee00180 : 0xfffff800`c764e490
fffff800`c9bdcb80 00000000`00000101 : 00000000`00000018 00000000`00000000 ffffc400`7ee00180 00000000`00000004 : 0xfffff800`c76a0378
fffff800`c9bdcb88 00000000`00000018 : 00000000`00000000 ffffc400`7ee00180 00000000`00000004 00000000`00000001 : 0x101
fffff800`c9bdcb90 00000000`00000000 : ffffc400`7ee00180 00000000`00000004 00000000`00000001 00000000`00000014 : 0x18

STACK_COMMAND:  kb

SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: Unknown_Module

IMAGE_NAME:  Unknown_Image

DEBUG_FLR_IMAGE_TIMESTAMP:  0

BUCKET_ID:  CORRUPT_MODULELIST

Followup: MachineOwner

Answer 1

We need log files(called dump files) that tell us what lead to crash.

Please share them with us for a better analysis of the problem. Instructions can be found here:

https://answers.microsoft.com/en-us/windows/for...

Please let us know if you need any assistance about posting dump files.

Answer 2

To know what exactly is causing the crashes, I need to analyze minidumps generated by crashes with WinDBG.

Go to C:\Windows\Minidump

Zip the contents of the folder corresponding to date and time of your crashes.

Upload the content to Onedrive or any other file sharing site for me to locate the problem

If you need help to generate Minidump - http://answers.microsoft.com/en-us/windows/wiki...

Answer 3

Hi there Lex, thanks for your question.

This error is commonly associated with errors with your CPU. You can try the below steps to see if the BSOD occurs again:

Check for updates on all drivers for all hardware, especially your motherboard.

Perform a clean boot:

https://support.microsoft.com/en-au/help/929135...

Boot into Safe Mode:

https://support.microsoft.com/en-au/help/12376/...

Run the System File Checker tool:

https://support.microsoft.com/en-us/help/929833...

If all else fails, you could try a system restore to a point before the issues began, or Repair Your PC.

https://support.microsoft.com/en-au/help/12415/...

Hopefully these steps help! Please let me know if you need further assistance. Thanks!

Answer 4

To evaluate the BSOD please post logs for troubleshooting.

Using administrative command prompt copy and paste this whole command.

Make sure the default language is English so that the logs can be scanned and read.

https://www.tenforums.com/tutorials/3813-language-add-remove-change-windows-10-a.html

The command will automatically collect the computer files and place them on the desktop.

Then use 7zip to organize the files and one drive or drop box to place share links into the thread for troubleshooting.

https://support.office.com/en-us/article/Share-OneDrive-files-and-folders-9fcc2f7d-de0c-4cec-93b0-a82024800c07

This command will automatically collect these files:  msinfo32, mini dumps, drivers, hosts, install, uninstall, services, startup, event viewer files, etc.

Open administrative command prompt and copy and paste the whole command:

copy %SystemRoot%\minidump\*.dmp "%USERPROFILE%\Desktop"&dxdiag /t %Temp%\dxdiag.txt&copy %Temp%\dxdiag.txt "%USERPROFILE%\Desktop\SFdebugFiles"&type %SystemRoot%\System32\drivers\etc\hosts >> "%USERPROFILE%\Desktop\hosts.txt"&systeminfo > "%USERPROFILE%\Desktop\systeminfo.txt"&driverquery /v > "%USERPROFILE%\Desktop\drivers.txt" &msinfo32 /nfo "%USERPROFILE%\Desktop\msinfo32.nfo"&wevtutil qe System /f:text > "%USERPROFILE%\Desktop\eventlog.txt"&reg export HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall "%USERPROFILE%\Desktop\uninstall.txt"&reg export "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Active Setup\Installed Components" "%USERPROFILE%\Desktop\installed.txt"&net start > "%USERPROFILE%\Desktop\services.txt"&REM wmic startup list full /format:htable >"%USERPROFILE%\Desktop\startup.html"&wmic STARTUP GET Caption, Command, User >"%USERPROFILE%\Desktop\startup.txt"

There are two files for you to find manually:

a) C:\Windows\MEMORY.DMP

Use file explorer > this PC > local C: drive > right upper corner search enter the above to find results.

b) dxdiag: 

In the left lower corner search type:  dxdiag > When the DirectX Diagnostic Tool opens click on the next page button so that each tab is opened > click on save all information > save to desktop > post one drive or drop box share link into the thread