Windows 10: BSOD CLOCK_WATCHDOG_TIMEOUT 101

BSOD'd with this error. I've crashed many times with no bsod. The computer screen locks followed by a short static soundsometimes.

Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright c Microsoft Corporation. All rights reserved.Loading Dump File [C:\Windows\MEMORY.DMP]Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 8 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff800`35e00000 PsLoadedModuleList = 0xfffff800`36a2a2b0Debug session time: Sat Jan 2 20:02:39.950 2021 UTC - 6:00System Uptime: 7 days 8:33:32.594Loading Kernel Symbols..................................................................................................................................................Page 1d6c6e not present in the dump file. Type ".hh dbgerr004" for details................................................Loading User SymbolsPEB is paged out Peb.Ldr = 00000000`0a13a018. Type ".hh dbgerr001" for detailsLoading unloaded module list..........................For analysis of this file, run !analyze -vnt!KeBugCheckEx:fffff800`361f5780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`3d46cc90=00000000000001010: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************CLOCK_WATCHDOG_TIMEOUT 101An expected clock interrupt was not received on a secondary processor in anMP system within the allocated interval. This indicates that the specifiedprocessor is hung and not processing interrupts.Arguments:Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.Arg2: 0000000000000000, 0.Arg3: ffffd401f014e180, The PRCB address of the hung processor.Arg4: 0000000000000002, The index of the hung processor.Debugging Details:------------------KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 11077 Key : Analysis.DebugAnalysisProvider.CPP Value: Create: 8007007e on DESKTOP-A2BG146 Key : Analysis.DebugData Value: CreateObject Key : Analysis.DebugModel Value: CreateObject Key : Analysis.Elapsed.mSec Value: 12733 Key : Analysis.Memory.CommitPeak.Mb Value: 286 Key : Analysis.System Value: CreateObject Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 101BUGCHECK_P1: 18BUGCHECK_P2: 0BUGCHECK_P3: ffffd401f014e180BUGCHECK_P4: 2FAULTING_PROCESSOR: 2PROCESS_NAME: RustClient.exeFAULTING_THREAD: ffff95065d3c3340BLACKBOXBSD: 1 !blackboxbsdBLACKBOXNTFS: 1 !blackboxntfsBLACKBOXPNP: 1 !blackboxpnpBLACKBOXWINLOGON: 1BAD_STACK_POINTER: ffffd401efde3020STACK_COMMAND: .thread 0xffff95065d3c3340 ; kbSYMBOL_NAME: nt!KiPageFault+3cMODULE_NAME: ntIMAGE_NAME: ntkrnlmp.exeBUCKET_ID_FUNC_OFFSET: 3cFAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_STACKPTR_ERROR_nt!KiPageFaultOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {e60d7807-5730-e0ca-55b3-3b4f578c8903}Followup: MachineOwner

:)

 

CLOCK_WATCHDOG_TIMEOUT BSOD

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:

 

BSOD whea_uncorrectable_error and clock_watchdog_timeout

Hello,

After Cmos reset and clean Windows 10 install I'm started getting some BSODs.
First time I've got whea_uncorrectable_error and some time later clock_watchdog_timeout.

Now I'm getting clock_watchdog_timeout all the time when I try to start AIDA64 stability test and in the middle game of CS:GO.

Here is dump from bluescreenview:
http://tintaiexcess.com/dmp.htm

And here is the dump files from "C:\Windows\Minidump":
http://www.mediafire.com/download/q2oy1mc5ku7girx/080315-7468-01.dmp
http://www.mediafire.com/download/ap25qa4ilr4gtc0/080315-7359-01.dmp

My CPU is running at 4.6G at 1.328V. RAM at 1866Mhz at 1.5V.
Stock looks stable.

Thanks
Tintai

 

BSOD whea_uncorrectable_error and clock_watchdog_timeout

drop your overclock to stock and run it, W10 has some teething to get through