Question CLOCK_WATCHDOG_TIMEOUT crash

Jul 6, 2022
1
0
10
0
Hello
My computer started to crash a few months ago with the following crash code: "CLOCK_WATCHDOG_TIMEOUT". This crash mostly happens in games but sometimes it happens when I'm on my desktop after a game or immediately after the computer restarts after a crash when all of my software starts up. I tried to format my computer but it did not help. All of my drivers are up to date and I checked my hardware integrity using memtest, it didn't show anything out of the ordinary. I'm pasting below a few analysis of dump files from crashes. My computer is seven years old so I guess it is a hardware problem but I just can't seem to understand what it is exactly.

One more thing I forgot to mention, I have reset my BIOS settings to default, but it didn't help.

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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 5218

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 36888

Key : Analysis.Init.CPU.mSec
Value: 1484

Key : Analysis.Init.Elapsed.mSec
Value: 50779

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

Key : Bugcheck.Code.DumpHeader
Value: 0x101

Key : Bugcheck.Code.Register
Value: 0x101

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.1


FILE_IN_CAB: 062522-8562-01.dmp

BUGCHECK_CODE: 101

BUGCHECK_P1: 18

BUGCHECK_P2: 0

BUGCHECK_P3: ffffa8816b5ac180

BUGCHECK_P4: 3

FAULTING_PROCESSOR: 3

PROCESS_NAME: TslGame.exe

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
fffff8026ace2c88 fffff80267436f60 : 0000000000000101 0000000000000018 0000000000000000 ffffa8816b5ac180 : nt!KeBugCheckEx
fffff8026ace2c90 fffff80267264c7d : 0000000000000000 fffff80262862180 0000000000000246 000000000033411b : nt!KeAccumulateTicks+0x1d5500
fffff8026ace2cf0 fffff80267265221 : 0000000000333f00 00000000001e8cc9 fffff80262862180 0000000000000001 : nt!KiUpdateRunTime+0x5d
fffff8026ace2d40 fffff8026725f093 : fffff80262862180 0000000000000000 fffff80267c31630 0000000000000000 : nt!KiUpdateTime+0x4a1
fffff8026ace2e80 fffff80267267a92 : fffff685f22eadd0 fffff685f22eae50 fffff685f22eae00 000000000000000c : nt!KeClockInterruptNotify+0x2e3
fffff8026ace2f30 fffff8026722d885 : 0000007a3464df76 fffff80267cf3a60 fffff80267cf3b10 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2
fffff8026ace2f60 fffff802673f987a : fffff685f22eae50 fffff80267cf3a60 000000000000000d 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff8026ace2fb0 fffff802673f9de7 : 000000004a43bfb2 fffff80262862180 0000000000000002 fffff80262865130 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff685f22eadd0 fffff80267285850 : 0000000000000000 0000000000000001 0000000000000002 000001ec5e1ff000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff685f22eaf60 fffff80267268c8f : fffff685f22eb560 0000000000000000 fffff080f62f0f00 fffff685f22eb560 : nt!KeFlushMultipleRangeTb+0x160
fffff685f22eb000 fffff802672a5edd : 0000000000000004 0000000000000000 ffff85022945b740 850000000a4c7847 : nt!MiAgeWorkingSetTail+0xef
fffff685f22eb040 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!MiWalkPageTablesRecursively+0xc6d


SYMBOL_NAME: nt!KeAccumulateTicks+1d5500

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1766

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1d5500

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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


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: ffffae81599ac180, The PRCB address of the hung processor.
Arg4: 0000000000000003, The index of the hung processor.

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2468

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 8386

Key : Analysis.Init.CPU.mSec
Value: 499

Key : Analysis.Init.Elapsed.mSec
Value: 45611

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

Key : Bugcheck.Code.DumpHeader
Value: 0x101

Key : Bugcheck.Code.Register
Value: 0x101

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: 070322-11796-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 101

BUGCHECK_P1: 18

BUGCHECK_P2: 0

BUGCHECK_P3: ffffae81599ac180

BUGCHECK_P4: 3

FAULTING_PROCESSOR: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
ffffae8159abfc88 fffff8051b636f60 : 0000000000000101 0000000000000018 0000000000000000 ffffae81599ac180 : nt!KeBugCheckEx
ffffae8159abfc90 fffff8051b464c7d : 0000000000000000 ffffae8159aa6180 0000000000000246 00000000029392cd : nt!KeAccumulateTicks+0x1d5500
ffffae8159abfcf0 fffff8051b465221 : 0000000002939100 00000000018922eb ffffae8159aa6180 0000000000000001 : nt!KiUpdateRunTime+0x5d
ffffae8159abfd40 fffff8051b45f093 : ffffae8159aa6180 0000000000000000 fffff8051be31570 0000000000000000 : nt!KiUpdateTime+0x4a1
ffffae8159abfe80 fffff8051b467a92 : fffffd0fc56533c0 fffffd0fc5653440 fffffd0fc5653400 0000000000000002 : nt!KeClockInterruptNotify+0x2e3
ffffae8159abff30 fffff8051b42d885 : 000006249476bed0 ffff9d8ce58c3ac0 ffff9d8ce58c3b70 ffff76e03223004c : nt!HalpTimerClockInterrupt+0xe2
ffffae8159abff60 fffff8051b5f987a : fffffd0fc5653440 ffff9d8ce58c3ac0 0000000000000000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffae8159abffb0 fffff8051b5f9de7 : 0000000000000000 0000000000000000 ffffae8159aa6180 fffff8051b5f9df4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffd0fc56533c0 fffff8051b4f9b4d : 0000000000000010 0000000000000282 fffffd0fc5653578 0000000000000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffd0fc5653550 fffff8051b44729c : 0000000000000000 ffff9d8cf23900c0 fffffd0fc5653661 0000000000000000 : nt!KeYieldProcessorEx+0xd
fffffd0fc5653580 fffff8051b445fbb : fffff80515ea8180 fffff80500000000 0000000000000000 0000000000000000 : nt!KiChooseTargetProcessor+0x64c
fffffd0fc56536c0 fffff8051b4f988d : 00000000018921f5 fffffd0fc5653b10 0000000000000080 ffffae8159aa6180 : nt!KiDeferredReadySingleThread+0x28b
fffffd0fc56538b0 fffff8051b4400c0 : ffffae8159aa6180 0000000000000000 ffff9d8cf2390230 ffff9d8d081e12b0 : nt!KiReadyThread+0x4d
fffffd0fc56538e0 fffff8051b4a0eed : 0000000000000000 0000000000000000 0000000000140001 00000000018921f5 : nt!KiProcessExpiredTimerList+0x290
fffffd0fc56539d0 fffff8051b5fb93e : ffffffff00000000 ffffae8159aa6180 ffffae8159ab1240 ffff9d8cfa0f1500 : nt!KiRetireDpcList+0x5dd
fffffd0fc5653c60 0000000000000000 : fffffd0fc5654000 fffffd0fc564e000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME: nt!KeAccumulateTicks+1d5500

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1766

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1d5500

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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



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

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


KEY_VALUES_STRING: 1

Key : Analysis.CPU.mSec
Value: 2421

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 10227

Key : Analysis.Init.CPU.mSec
Value: 452

Key : Analysis.Init.Elapsed.mSec
Value: 10927

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

Key : Bugcheck.Code.DumpHeader
Value: 0x101

Key : Bugcheck.Code.Register
Value: 0x101

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: 070322-6375-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 101

BUGCHECK_P1: 18

BUGCHECK_P2: 0

BUGCHECK_P3: ffffd081da3ac180

BUGCHECK_P4: 3

FAULTING_PROCESSOR: 3

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: steamwebhelper

STACK_TEXT:
ffffd081da67fc88 fffff8022d636f60 : 0000000000000101 0000000000000018 0000000000000000 ffffd081da3ac180 : nt!KeBugCheckEx
ffffd081da67fc90 fffff8022d464c7d : 0000000000000000 ffffd081da5dc180 0000000000000246 0000000000001842 : nt!KeAccumulateTicks+0x1d5500
ffffd081da67fcf0 fffff8022d465221 : 0000000000001600 0000000000000e75 ffffd081da5dc180 0000000000000001 : nt!KiUpdateRunTime+0x5d
ffffd081da67fd40 fffff8022d45f093 : ffffd081da5dc180 0000000000000000 fffff8022de31570 0000000000000000 : nt!KiUpdateTime+0x4a1
ffffd081da67fe80 fffff8022d467a92 : ffffa4092c96b390 ffffa4092c96b410 ffffa4092c96b400 0000000000000002 : nt!KeClockInterruptNotify+0x2e3
ffffd081da67ff30 fffff8022d42d885 : 0000000039ec8164 ffff848417ac6380 ffff848417ac6430 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2
ffffd081da67ff60 fffff8022d5f987a : ffffa4092c96b410 ffff848417ac6380 1000000000000020 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffd081da67ffb0 fffff8022d5f9de7 : 000000003a272b03 0000000000000001 0000000000000000 fffff4ee5c502000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffa4092c96b390 fffff8022d4a8278 : 0000000000000014 00004e960e73ffff 0000000000000000 ffff84842a054790 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffa4092c96b520 fffff8022d4a7d09 : 0000007ffffffff8 ffff848400000000 00004e960e72c000 00004e960e73ffff : nt!MiLockPageTableInternal+0x2b8
ffffa4092c96b590 fffff8022d4b2dec : ffff8484276a4700 0000000000000000 ffff848400000002 ffffe4f253a58398 : nt!MiFastLockLeafPageTable+0x169
ffffa4092c96b610 fffff8022d8375fa : ffff84842af46a10 0000000000000000 0000000000014001 0000000000000002 : nt!MiCommitExistingVad+0x6cc
ffffa4092c96b760 fffff8022d84b36b : 0000000000000000 ffff290000000000 0000000000000000 000000751dcff250 : nt!MiAllocateVirtualMemory+0x2aa
ffffa4092c96b8e0 fffff8022d6097b8 : ffffffffffffffff ffff8484276c3580 0000000000000000 000000751dcff228 : nt!NtAllocateVirtualMemory+0x1ab
ffffa4092c96ba90 00007ffd21b8d044 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000751dcff208 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd21b8d044


SYMBOL_NAME: nt!KeAccumulateTicks+1d5500

MODULE_NAME: [U]nt
[/U]
IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1766

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1d5500

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

*******************************************************************************
[LIST]
[*]*
[*]Bugcheck Analysis *
[*]*
[/LIST]
*******************************************************************************

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: ffffba80a4b40180, 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: 2421

Key : Analysis.DebugAnalysisManager
Value: Create

Key : Analysis.Elapsed.mSec
Value: 2533

Key : Analysis.Init.CPU.mSec
Value: 577

Key : Analysis.Init.Elapsed.mSec
Value: 30587

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

Key : Bugcheck.Code.DumpHeader
Value: 0x101

Key : Bugcheck.Code.Register
Value: 0x101

Key : Dump.Attributes.AsUlong
Value: 8

Key : Dump.Attributes.KernelGeneratedTriageDump
Value: 1


FILE_IN_CAB: 070622-10796-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump

BUGCHECK_CODE: 101

BUGCHECK_P1: 18

BUGCHECK_P2: 0

BUGCHECK_P3: ffffba80a4b40180

BUGCHECK_P4: 2

FAULTING_PROCESSOR: 2

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: firefox.exe

STACK_TEXT:
fffff806
39ce2c88 fffff80637036f60 : 0000000000000101 0000000000000018 0000000000000000 ffffba80a4b40180 : nt!KeBugCheckEx
fffff806
39ce2c90 fffff80636e64c7d : 0000000000000000 fffff80631995180 0000000000000246 0000000000a1dd92 : nt!KeAccumulateTicks+0x1d5500
fffff806
39ce2cf0 fffff80636e65221 : 0000000000a1dc00 0000000000607ab7 fffff80631995180 0000000000000001 : nt!KiUpdateRunTime+0x5d
fffff806
39ce2d40 fffff80636e5f093 : fffff80631995180 0000000000000000 fffff806378315e8 0000000000000000 : nt!KiUpdateTime+0x4a1
fffff806
39ce2e80 fffff80636e67a92 : ffff9d0d45117460 ffff9d0d451174e0 ffff9d0d45117400 000000000000000c : nt!KeClockInterruptNotify+0x2e3
fffff806
39ce2f30 fffff80636e2d885 : 00000181ee9e30cd fffff806378f3a60 fffff806378f3b10 0000000000000000 : nt!HalpTimerClockInterrupt+0xe2
fffff806
39ce2f60 fffff80636ff987a : ffff9d0d451174e0 fffff806378f3a60 0000000000000001 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806
39ce2fb0 fffff80636ff9de7 : 00000000597ad7b6 fffff80631998088 ffff9d0d45117591 ffce86a288bb2004 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff9d0d
45117460 fffff80636e85856 : 0000000000000000 0000000000000001 0000000000000002 ffffa7d3e9e04758 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff9d0d
451175f0 fffff80636e85688 : ffffa7811d62b930 00000000002ad600 ffffa7811d62b900 ffff9d0d451177c0 : nt!KeFlushMultipleRangeTb+0x166
ffff9d0d
45117690 fffff80636e0a74d : ffffe30225390070 ffffa7811d62b928 ffffa78100000003 ffff9d0d00000000 : nt!MiFlushTbList+0x88
ffff9d0d
451176c0 fffff8063721918b : ffff9d0d45117b80 0000000000000004 0000023ac5725fff ffffe302183f6080 : nt!MiProtectPrivateMemory+0x5ad
ffff9d0d
45117870 fffff80637237cff : ffffe302183f6080 ffffe302183f6080 ffff9d0d451179e8 ffff9d0d451179f8 : nt!MmProtectVirtualMemory+0x42b
ffff9d0d
451179a0 fffff806370097b8 : 0000000009e10ddd 0000000000000308 0000000000000040 ffff9d0d45117b80 : nt!NtProtectVirtualMemory+0x1bf
ffff9d0d
45117a90 00007ffc46f0d744 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x28
000000ea
79ffb438 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffc46f0d744


SYMBOL_NAME: nt!KeAccumulateTicks+1d5500

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.19041.1766

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1d5500

FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

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

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

<Moderator Note: Please use the "spoiler" tags around long log listings>
 
Last edited by a moderator:
timeout was 18 clock ticks, this is a very short timeout so most likely one cpu core was trying to talk to another cpu core and did not get a response.

to figure out the cause of the problem you will have to change the memory dump type to kernel, reboot then put the memory dump file c:\windows\memory.dmp
onto a cloud server so the dump can be looked at with the microsoft debugger.

Generally when I see this it turns out that one core is attempting to install some plug and play device while another core is attempting to use the device. Problem is that the first core fails the install and keeps trying and the second core thinks the first core is not working and calls a bugcheck.

if you have a kernel memory dump you can run
!pnptriage
to see what device is failing the install. the command only works on a kernel memory dump.
 

ASK THE COMMUNITY