通过

频繁蓝屏 代码为 0x133_DPC_nt!KeAccumulateTicks，希望能解决一下问题

匿名
2024-03-16T15:54:58+00:00

************* 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 [D:\1111\031024-15140-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 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff807`73400000 PsLoadedModuleList = 0xfffff807`74013550
Debug session time: Sun Mar 10 21:23:45.308 2024 (UTC + 8:00)
System Uptime: 0 days 2:40:29.094
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 000000f1`2fa67018).  Type ".hh dbgerr001" for details
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff807`73816c30 48894c2408      mov     qword ptr [rsp+8],rcx ss:fffff807`789109f0=0000000000000133
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8077411c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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

*************************************************************************
***                                                                   ***
***                                                                   ***
***    Either you specified an unqualified symbol, or your debugger   ***
***    doesn't have full symbol information.  Unqualified symbol      ***
***    resolution is turned off by default. Please either specify a   ***
***    fully qualified symbol module!symbolname, or enable resolution ***
***    of unqualified symbols by typing ".symopt- 100". Note that     ***
***    enabling unqualified symbol resolution with network symbol     ***
***    server shares in the symbol path may cause the debugger to     ***
***    appear to hang for long periods of time when an incorrect      ***
***    symbol name is typed or the network symbol server is down.     ***
***                                                                   ***
***    For some commands to work properly, your symbol path           ***
***    must point to .pdb files that have full type information.      ***
***                                                                   ***
***    Certain .pdb files (such as the public OS symbols) do not      ***
***    contain the required information.  Contact the group that      ***
***    provided you with these symbols if you need this command to    ***
***    work.                                                          ***
***                                                                   ***
***    Type referenced: TickPeriods                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 2328

    Key  : Analysis.Elapsed.mSec
    Value: 12038

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x133_DPC_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {88dc98ce-f842-4daa-98d0-858621db6b0f}

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 1497cf94

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 1

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 0

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 0

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 4853999

    Key  : Hypervisor.Flags.ValueHex
    Value: 4a10ef

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 3f7

BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8077411c340

FILE_IN_CAB:  031024-15140-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b

DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  HuntGame.exe

FAULTING_THREAD:  000000000000000f

STACK_TEXT:  
fffff807`789109e8 fffff807`73612d55     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff807`789109f0 fffff807`73612421     : 00001cdb`343fbb39 00000000`00096746 00000000`00096745 00000000`00000000 : nt!KeAccumulateTicks+0x3d5
fffff807`78910a50 fffff807`7360fa2f     : 00000000`00000010 00000000`00001388 00000000`00096700 00000000`00059ad8 : nt!KiUpdateRunTime+0xd1
fffff807`78910c00 fffff807`73610618     : 00000000`00000000 00000000`00000000 fffff807`714dc180 00000000`00000000 : nt!KiUpdateTime+0x63f
fffff807`78910ea0 fffff807`7360feda     : fffff807`7405ff88 00000000`00000001 00000000`00000001 00000000`00000002 : nt!KeClockInterruptNotify+0x228
fffff807`78910f40 fffff807`73724cdc     : 00000016`6b663b24 fffff807`7410d4f0 fffff807`7410d5a0 fffff807`73818b8b : nt!HalpTimerClockInterrupt+0x10a
fffff807`78910f70 fffff807`73818dea     : fffff807`78909580 fffff807`7410d4f0 fffff807`78909798 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
fffff807`78910fb0 fffff807`73819697     : 00000000`00000000 00001f80`008102a4 00000000`42f0b0fb fffff807`789096cc : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`78909500 fffff807`7366f9c0     : 00000000`80000000 fffff807`739685fe 0000ffff`f8077396 000000ff`fff80773 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`78909690 fffff807`739685fe     : 0000ffff`f8077396 000000ff`fff80773 00000000`fffff807 00000000`00fffff8 : nt!KeYieldProcessorEx+0x20
fffff807`789096a0 fffff807`73745b2b     : 00000000`00000000 ffffbd85`f3ec9000 fffff807`78909790 fffff807`78909798 : nt!KiConfigureHeteroProcessorsTarget+0x6e
fffff807`78909740 fffff807`737c356e     : 00000000`00000010 00000010`00000001 00000000`00000000 ffffbb81`510ef570 : nt!KiInitiateGenericCallDpc+0x97
fffff807`78909790 fffff807`7367148c     : 00000000`00000000 fffff807`78909e00 00000000`00000001 ffffbd86`08936080 : nt!KiGenericCallDpcInitiatorDpc+0x2e
fffff807`789097c0 fffff807`73672741     : 00000000`00000028 ffffbd85`00000001 fffff780`00000014 00000000`000597f5 : nt!KiExecuteAllDpcs+0x42c
fffff807`78909d00 fffff807`73820265     : 00000000`00000000 00000000`00000000 fffff807`714dc180 00000268`07323b80 : nt!KiRetireDpcList+0x1b1
fffff807`78909fb0 fffff807`7382020f     : ffffbb81`5127fa39 fffff807`736609d5 00000000`00000000 00000000`00000000 : nt!KxSwapStacksAndRetireDpcList+0x5
ffffbb81`5127f9a0 fffff807`736609d5     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff2187`018e6f1c : nt!KiPlatformSwapStacksAndCallReturn
ffffbb81`5127f9b0 fffff807`7381f650     : ffffbb81`5127fb20 00000000`0000000a 00000268`072bc220 00000268`075d83e0 : nt!KiDispatchInterrupt+0xd5
ffffbb81`5127faa0 00007ffc`1cb636a8     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x350
000000f1`32ddfc30 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffc`1cb636a8

STACK_COMMAND:  ~15 ; .cxr ; kb

SYMBOL_NAME:  nt!KeAccumulateTicks+3d5

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22621.3155

BUCKET_ID_FUNC_OFFSET:  3d5

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup:     MachineOwner
---------
Windows Server 性能和维护系统性能

锁定的问题。 此问题已从 Microsoft 支持社区迁移。 你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。 为了保护隐私，对于已迁移的问题，用户个人资料是匿名的。

0 个注释

1 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. 匿名
    2024-03-18T07:38:03+00:00

    此响应已自动翻译。 因此，可能存在语法错误或奇异的措辞。

    你好

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

    根据描述，我理解您的问题与 Bug Check 0x133： DPC_WATCHDOG_VIOLATION 有关。

    DPC_WATCHDOG_VIOLATION bug 检查的值为 0x00000133。此 bug 检查表明 DPC 监视器已执行，因为它检测到单个长时间运行的延迟过程调用 （DPC），或者因为系统在中断请求级别 （IRQL） DISPATCH_LEVEL 或更高级别花费了很长时间。

    若要确定具体原因并创建代码修复，需要编程经验和对故障模块源代码的访问。

    有关详细的故障排除，请参阅此文章：

    Bug 检查0x133 DPC_WATCHDOG_VIOLATION - Windows drivers |Microsoft 学习

    有好的一天。 

    此致敬意

    莫莉

    0 个注释