关于NT错误导致的蓝屏代码clock watchdog timeout

Question

哥帮帮我，三五天一次蓝屏，蓝屏界面显示的代码都是CLOCK_WATCHDOG_TIMEOUT

以下是dmp文件分析的结果

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true

   EnableRedirectToV8JsProvider : false

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 41

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

Loading Dump File [C:\Users\HaoGe\Desktop\041224-7328-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 19041 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff800`26000000 PsLoadedModuleList = 0xfffff800`26c2a730
Debug session time: Fri Apr 12 21:17:18.185 2024 (UTC + 8:00)
System Uptime: 0 days 12:24:05.891
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......................
Loading User Symbols

Loading unloaded module list
.........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff800`263fd890 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8680`51e9cc90=0000000000000101
2: 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: 0000000000000018, Clock interrupt time out interval in nominal clock ticks.
Arg2: 0000000000000000, 0.
Arg3: ffff868051dc1180, The PRCB address of the hung processor.
Arg4: 0000000000000001, The index of the hung processor.

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

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2233

    Key  : Analysis.Elapsed.mSec
    Value: 5553

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x101

    Key  : Bugcheck.Code.TargetModel
    Value: 0x101

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_nt!ObpIncrementHandleCountEx

    Key  : Failure.Hash
    Value: {6fba73b2-2de2-2dc2-2514-721fa67c95bd}

BUGCHECK_CODE:  101

BUGCHECK_P1: 18

BUGCHECK_P2: 0

BUGCHECK_P3: ffff868051dc1180

BUGCHECK_P4: 1

FILE_IN_CAB:  041224-7328-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

FAULTING_PROCESSOR: 1

FAULTING_THREAD:  ffffdf0806f63080

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

IP_IN_FREE_BLOCK: 0

STACK_TEXT:  
ffff8004`6f8e7370 ffffdf07`ef8f4d20     : fffff800`2664bd47 00000000`00000001 ffffdf07`00000000 fffff800`00000000 : 0x0
ffff8004`6f8e7378 fffff800`2664bd47     : 00000000`00000001 ffffdf07`00000000 fffff800`00000000 00000000`00000001 : 0xffffdf07`ef8f4d20
ffff8004`6f8e7380 ffffdf07`ef202280     : ffffdf07`f882a4c8 fffff800`26239565 ffff8004`6f8e7508 00000000`0000003f : nt!ObpIncrementHandleCountEx+0x267
ffff8004`6f8e7480 ffffdf07`f882a4c8     : fffff800`26239565 ffff8004`6f8e7508 00000000`0000003f ffffdf07`f882a4c0 : 0xffffdf07`ef202280
ffff8004`6f8e7488 fffff800`26239565     : ffff8004`6f8e7508 00000000`0000003f ffffdf07`f882a4c0 00000000`00000040 : 0xffffdf07`f882a4c8
ffff8004`6f8e7490 fffff800`2623934a     : 00010000`00000000 fffff800`3b094e32 00000000`00000010 00000000`00000000 : nt!RtlpHpVsChunkSplit+0x45
ffff8004`6f8e7550 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00040286 00000000`00000000 : nt!RtlpHpVsContextAllocateInternal+0x1fa

SYMBOL_NAME:  nt!ObpIncrementHandleCountEx+267

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.4170

STACK_COMMAND:  .process /r /p 0xffffdf07f89340c0; .thread 0xffffdf0806f63080 ; kb

BUCKET_ID_FUNC_OFFSET:  267

FAILURE_BUCKET_ID:  CLOCK_WATCHDOG_TIMEOUT_INTERRUPTS_DISABLED_nt!ObpIncrementHandleCountEx

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {6fba73b2-2de2-2dc2-2514-721fa67c95bd}

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

Answer 1

你好

感谢您在Microsoft社区论坛上发布。

您提供的错误消息指示*"clock_watchdog_timeout”*问题，通常发生在处理器无响应并且未能在预期的时间范围内处理 interrupt。

似乎在Windows内核中处理句柄计数存在问题，这与手柄计数的增加有关（ObpincrementHandLecountex）。

为了进一步解决问题，您可以尝试以下步骤：

更新驱动程序：确保您的所有驱动程序，尤其是与CPU这样的硬件组件相关的驱动程序，都是最新的。 您可以使用设备管理器或第三方软件检查驱动程序更新。

检查硬件：在硬件组件（尤其是CPU和内存模块）上运行诊断测试，以检查任何故障或问题。

检查Windows更新：确保您的Windows操作系统已完全更新。 有时，Microsoft会发布补丁程序或更新以解决已知问题。

检查超频：如果您已经超频了系统，请尝试将其重新发送到默认设置，并查看问题是否持续。

检查软件冲突：有时，第三方软件或驱动程序可能与系统流程冲突。 尝试执行干净的引导以隔离问题。

How to perform a clean boot in Windows - Microsoft Support

内存测试：运行内存诊断测试以检查系统内存中的任何问题。

Memory problems. - Microsoft Community

Best Regards,

Wesley Li