Bsod : CLOCK_WATCHDOG_TIMEOUT

Question

hello

i get the bsod often when i play iracing .. here is one dumb fil and have attached a link to 5 files
best regards
LINK TO GOGGLE DRIVE: dmp files

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

Loading Dump File [C:\Windows\Minidump\121222-6578-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 22621 MP (24 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff80645200000 PsLoadedModuleList = 0xfffff80645e13410 Debug session time: Mon Dec 12 20:41:22.553 2022 (UTC + 1:00) System Uptime: 0 days 0:40:54.156 Loading Kernel Symbols ............................................................... ................................................................ ............................................................... Loading User Symbols Loading unloaded module list ............ For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff806456283c0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffb280a7eb49b0=0000000000000101 21: 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: 0000000000000008, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffffb280a7559180, The PRCB address of the hung processor. Arg4: 0000000000000004, The index of the hung processor.

Debugging Details:

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 609

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 2033

Key  : Analysis.IO.Other.Mb
Value: 0

Key  : Analysis.IO.Read.Mb
Value: 0

Key  : Analysis.IO.Write.Mb
Value: 0

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

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

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

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: 121222-6578-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump

BUGCHECK_CODE: 101

BUGCHECK_P1: 8

BUGCHECK_P2: 0

BUGCHECK_P3: ffffb280a7559180

BUGCHECK_P4: 4

FAULTING_PROCESSOR: 4

PROCESS_NAME: iRacingSim64DX

CUSTOMER_CRASH_COUNT: 1

STACK_TEXT:
ffffb280a7eb49a8 fffff80645678d46 : 0000000000000101 0000000000000008 0000000000000000 ffffb280a7559180 : nt!KeBugCheckEx ffffb280a7eb49b0 fffff80645422f74 : 00000005b6cce4d3 00000005b0676d2f 0000000000026589 0000000000000000 : nt!KeAccumulateTicks+0x254e46 ffffb280a7eb4a10 fffff80645422e56 : 0000000000000018 0000000000000000 ffffb280a7f11180 00000005b6ca3300 : nt!KiUpdateRunTime+0xf4 ffffb280a7eb4bd0 fffff8064542107e : 0000000000000000 ffffb280a7f11180 ffffffffffffffff 000000000000000c : nt!KiUpdateTime+0x13e6 ffffb280a7eb4e90 fffff8064542088a : fffff80645e5ff08 ffff9b8c82d74dd0 ffff9b8c82d74dd0 0000000000000000 : nt!KeClockInterruptNotify+0x3de ffffb280a7eb4f40 fffff80645545f9e : 00000005b6e2572b ffff9b8c82d74d20 ffffb280a7f11180 0000000000000000 : nt!HalpTimerClockInterrupt+0x10a ffffb280a7eb4f70 fffff8064562a51a : ffff98099f7df860 ffff9b8c82d74d20 ffffb280a7f11180 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x19e ffffb280a7eb4fb0 fffff8064562ad87 : 00000000243339f1 0000000000000000 ffff98099f7df8e1 0000000000000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa ffff98099f7df7e0 fffff8064541352a : 0000000000000000 0000000000000000 0000000000000000 fffff806455a91e0 : nt!KiInterruptDispatchNoLockNoEtw+0x37 ffff98099f7df970 fffff80645413415 : ffff9b8c98b840c0 ffff98099f7df900 0000000000000000 ffffc307b9685040 : nt!KiIpiStallOnPacketTargetsPrcb+0x2a ffff98099f7df9a0 fffff8064541332b : ffff9b8c9a170080 ffff98099f7dfaa0 0000000010a4c5d0 0000000000000000 : nt!KeFlushProcessWriteBuffers+0xd9 ffff98099f7df9f0 fffff8064563d1e5 : 00000000109d18d0 ffff9b8c9ba88080 0000000000000000 0000000000000000 : nt!NtFlushProcessWriteBuffers+0xb ffff98099f7dfa20 00007ffd49050c14 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiSystemServiceCopyEnd+0x25 000000049413fde8 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ffd`49050c14

SYMBOL_NAME: nt!KeAccumulateTicks+254e46

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.22621.819

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 254e46

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

Answer 1

Hi Benjamin,

I'm Dyari. Thanks for reaching out. I will be happy to assist you in this regard.

The minidump files did not name any driver only indicate ntkrnlmp.exe which is a Windows component that means something else drove the system to a fault or it could be a memory corruption that usually happens due to driver incompatibility.

To troubleshoot this issue, kindly try the steps below (Skip a step that you have already tried):

1-Check for updates:

Go to Settings > Update and Security > Check for update > install all the pending updates

2-Uninstall the graphics card driver completely using the DDU free tool:

https://www.guru3d.com/files-details/display-dr...

Then, install the latest driver provided on the manufacturer's website.

3-Uninstall any third-party security software and scan for viruses & malware with the free Malwarebytes:

https://www.malwarebytes.com/mwb-download

4-Run Command Prompt as administrator. Type this command and hit enter:

dism.exe /online /cleanup-image /restorehealth

Then, type this command and hit enter:

sfc /scannow

5-If you are overclocking your PC, try running everything (CPU, GPU, system memory) at their stock speeds. See if the issue is still reproducible. Or, turn off XMP profile or set it to Auto.

6-Download then install the latest version of BIOS & Chipset drivers from the manufacturer's website.

7-Test the RAM with the free utility MemTest86, then run a full 8 pass scan to test your RAM for physical errors:

https://www.tenforums.com/tutorials/14201-memte...

8-Run the Windows Memory Diagnostic:

https://www.howtogeek.com/260813/how-to-test-yo...

Run Hard Drive Diagnostic:

https://www.lifewire.com/free-hard-drive-testin...

9-If you are comfortable of doing so, take all the system memory sticks out, examine them for any obvious defects, and then reseat them into the sockets. Make sure that they are seated properly in their slots. If you have multiple sticks of system memory installed and you suspect one is faulty, one thing to try is to reproduce the issue with only one stick of memory module at a time. This will help you to isolate the faulty module.

10-If the issue still persists after the steps above, enable the driver verifier and let the computer crash 3 times then disable it and share the newly created minidump file:

https://www.tenforums.com/tutorials/5470-enable...

Please do not hesitate to ask if you need further assistance.

Stay safe

____________________________________________________________

Standard Disclaimer: There are links to non-Microsoft websites. The pages appear to be providing accurate, safe information. Watch out for ads on the sites that may advertise products frequently classified as a PUP (Potentially Unwanted Products). Thoroughly research any product advertised on the sites before you decide to download and install it.