Windows 10: CLOCK_WATCHDOG_TIMEOUT

Any help would be greatly appreciated. Thanks in advance.This is the report:

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


Loading Dump File [C:\Users\qty94\Downloads\061019-37921-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff800`83a00000 PsLoadedModuleList = 0xfffff800`83e432b0
Debug session time: Mon Jun 10 00:53:14.914 2019 (UTC + 8:00)
System Uptime: 0 days 1:08:40.047
Loading Kernel Symbols
...............................................................
................................................................
................................................
Loading User Symbols
Loading unloaded module list
......
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`83bbc8a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff800`87689b00=0000000000000101
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

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: 0000000000000030, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff9680abd79180, The PRCB address of the hung processor.
Arg4: 0000000000000002, The index of the hung processor.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 9

Key : Analysis.Elapsed.Sec
Value: 23

Key : Analysis.Memory.CommitPeak.Mb
Value: 69


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 400

BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202

SYSTEM_PRODUCT_NAME: To Be Filled By O.E.M.

SYSTEM_SKU: To Be Filled By O.E.M.

SYSTEM_VERSION: To Be Filled By O.E.M.

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: P1.40

BIOS_DATE: 05/21/2012

BASEBOARD_MANUFACTURER: ASRock

BASEBOARD_PRODUCT: A55iCafe

BASEBOARD_VERSION:

DUMP_TYPE: 2

BUGCHECK_P1: 30

BUGCHECK_P2: 0

BUGCHECK_P3: ffff9680abd79180

BUGCHECK_P4: 2

BUGCHECK_STR: CLOCK_WATCHDOG_TIMEOUT

FAULTING_PROCESSOR: 2

PROCESS_NAME: Steam.exe

CPU_COUNT: 4

CPU_MHZ: aeb

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 12

CPU_MODEL: 1

CPU_STEPPING: 0

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT

CURRENT_IRQL: d

ANALYSIS_SESSION_HOST: DESKTOP-PR5VP4U

ANALYSIS_SESSION_TIME: 06-11-2019 05:01:52.0422

ANALYSIS_VERSION: 10.0.18869.1002 amd64fre

LAST_CONTROL_TRANSFER: from fffff80083bebb22 to fffff80083bbc8a0

STACK_TEXT:
fffff800`87689af8 fffff800`83bebb22 : 00000000`00000101 00000000`00000030 00000000`00000000 ffff9680`abd79180 : nt!KeBugCheckEx
fffff800`87689b00 fffff800`83a1f764 : 00000000`00000000 00000000`00000000 00000000`00040603 fffff800`7fc26180 : nt!KeAccumulateTicks+0x1c9262
fffff800`87689b60 fffff800`8395e4b2 : 00000000`00000000 ffffba8c`f02a6c30 ffffba8c`f02a6cb0 00000000`0000000c : nt!KeClockInterruptNotify+0x6c4
fffff800`87689f30 fffff800`83a02e15 : 00000009`97d2aa4a fffff800`839cbcf0 fffff800`839cbda0 00000000`00000000 : hal!HalpTimerClockInterrupt+0xf2
fffff800`87689f60 fffff800`83bbe30a : ffffba8c`f02a6cb0 fffff800`839cbcf0 00000000`00000001 fffff800`839cbcf0 : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`87689fb0 fffff800`83bbe857 : 00000000`92483016 ffffba8c`f02a6cb0 fffff800`839cbcf0 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffba8c`f02a6c30 fffff800`83abaea0 : 00000000`00000000 fffff800`7fc26180 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffba8c`f02a6dc0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!MiFlushTbList+0x3a0


THREAD_SHA1_HASH_MOD_FUNC: dc8736af616fc8dbbe5744546b76f6197d522250

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: f83251215b5c77f255c4ca8bb5458675110e916d

THREAD_SHA1_HASH_MOD: 77b99fd8d0bba6459fea0474c255a54ffe46d91a

FOLLOWUP_IP:
nt!KeAccumulateTicks+1c9262
fffff800`83bebb22 cc int 3

FAULT_INSTR_CODE: cb8b48cc

SYMBOL_STACK_INDEX: 1

SYMBOL_NAME: nt!KeAccumulateTicks+1c9262

FOLLOWUP_NAME: MachineOwner

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

DEBUG_FLR_IMAGE_TIMESTAMP: 0

IMAGE_VERSION: 10.0.18362.145

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1c9262

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

PRIMARY_PROBLEM_CLASS: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

TARGET_TIME: 2019-06-09T16:53:14.000Z

OSBUILD: 18362

OSSERVICEPACK: 145

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: unknown_date

BUILDDATESTAMP_STR: 190318-1202

BUILDLAB_STR: 19h1_release

BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME: 5b1a

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:clock_watchdog_timeout_invalid_context_nt!keaccumulateticks

FAILURE_ID_HASH: {95498f51-33a9-903b-59e5-d236937d8ecf}

Followup: MachineOwner
---------

:)

 

CLOCK_WATCHDOG_TIMEOUT After Leaving PC for 5-10 Minutes


Daemon tools, Alcohol 120% and Power Archiver Pro uses SCSI Pass Through Direct (SPTD), which is a well known cause for BSOD's.
Please remove Daemon Tools and run the SPTD pass through remover.

1. Uninstall Daemon Tools
2. Download the SPTD standalone installer and follow these steps:
   • Double click the executable to open it
   • Click on the button shown below

If the button is grayed out, like in the image, there is no more SPTD installation on your system, and you can close the window.

The 0x101(CLOCK_WATCHDOG_TIMEOUT) is mostly caused by BIOS or hardware problem, the challenge is to find software problems.
I suggest to update your BIOS.
Code:

Code:

BIOS Version:              American Megatrends Inc. 2001   , 7/8/2011

Attachment 51031

 

CLOCK_WATCHDOG_TIMEOUT after a fresh install

 

Blue screen error with Clock_Watchdog_Timeout error code.

Hi Charlie,

The CLOCK_WATCHDOG_TIMEOUT error can be caused by a faulty processor. This error may also be triggered by an outdated driver. To isolate your concern, we suggest that you consider the following:

• Ensure that your CPU's temperature is within standard and nothing is overheating.
  
• Clear your CMOS (or load optimized BIOS defaults) to ensure there's no improper BIOS setting or to clear overclock settings.
  
• Update your BIOS.
• Run
  Windows Update to install the latest driver on your system.

Note: For steps 2 & 3, it's best to get an assistance from your system manufacturer to ensure that all settings will be properly configured.

Feel free to post back if you encounter any challenges along the process.