通过

又出现了蓝屏问题可以帮我看看这次是什么问题吗，这是我在windbg上分析的数据我看不懂

匿名
2025-01-27T11:37:31+00:00

************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : true AllowNugetExeUpdate : true NonInteractiveNuget : true AllowNugetMSCredentialProviderInstall : true AllowParallelInitializationOfLocalRepositories : true EnableRedirectToChakraJsProvider : 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.031 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 42

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

Loading Dump File [C:\Users\刘欣劼\Desktop\012725-11531-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 22000 MP (20 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff806`15a00000 PsLoadedModuleList = 0xfffff806`16629c20
Debug session time: Mon Jan 27 19:25:37.478 2025 (UTC + 8:00)
System Uptime: 0 days 0:11:19.156
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
...........................................
Loading User Symbols

Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`15e1d720 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffc001`d78acde0=0000000000000133
9: 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: fffff80616705330, 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: 3390

    Key  : Analysis.Elapsed.mSec
    Value: 11737

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27725.1000

    Key  : Analysis.Version.Description
    Value: 10.2408.27.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2408.27.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 1008

    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  : Stack.Pointer
    Value: ISR

BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80616705330

FILE_IN_CAB:  012725-11531-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  0000000000000013

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffc001`d78acdd8 fffff806`15c3493e     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffc001`d78acde0 fffff806`15c343c1     : 000001ac`e3696c06 ffffc001`00000500 00000000`00000002 fffff806`15c2fbde : nt!KeAccumulateTicks+0x39e
ffffc001`d78ace50 fffff806`15c325aa     : ffffc001`d7849200 fffffb0b`b2eaf4c0 ffffc001`d78493d8 fffff806`15d354db : nt!KiUpdateRunTime+0x61
ffffc001`d78aceb0 fffff806`15c32396     : ffffe184`93d38780 ffffe184`93d38830 00000000`00000000 00000000`00000000 : nt!KeClockInterruptNotify+0x11a
ffffc001`d78acf40 fffff806`15ce1f60     : 00000000`00000000 ffffe6d8`12fa0385 00000000`00000000 ffffe184`93d31040 : nt!HalpTimerClockIpiRoutine+0x16
ffffc001`d78acf70 fffff806`15e1f86a     : fffffb0b`b2eaf540 ffffe184`93d38780 00000000`00000000 ffffc001`d7847fe0 : nt!KiCallInterruptServiceRoutine+0xa0
ffffc001`d78acfb0 fffff806`15e200d7     : ffffc001`d7840180 ffffc001`d7840100 fffffb0b`b2eaf6d8 fffff806`15e200e4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffb0b`b2eaf4c0 fffff806`15cc222c     : ffffffff`ffffffd2 fffff806`15cc1672 00000000`00000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffb0b`b2eaf650 fffff806`15cc1683     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1c
fffffb0b`b2eaf680 fffff806`15c242c1     : fffffb0b`b2eafa40 fffffb0b`190c482b ffffc001`d78434c0 00000000`00000000 : nt!KiSwapDirectoryTableBaseTarget+0x53
fffffb0b`b2eaf6d0 fffff806`15c232c2     : 00000000`00000008 fffffb0b`b2eaf9d0 ffffc001`d7840180 00000000`00045ac0 : nt!KiExecuteAllDpcs+0x491
fffffb0b`b2eaf8d0 fffff806`15e224de     : 00000000`00000000 ffffc001`d7840180 ffffc001`d784c540 ffffe184`ab1e1080 : nt!KiRetireDpcList+0x2a2
fffffb0b`b2eafb80 00000000`00000000     : fffffb0b`b2eb0000 fffffb0b`b2ea9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e

STACK_COMMAND:  ~19 ; .cxr ; kb

SYMBOL_NAME:  nt!KeAccumulateTicks+39e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.2057

BUCKET_ID_FUNC_OFFSET:  39e

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------
Windows 商业版 适用于 IT 专业人员的 Windows 客户端 性能 应用程序技术和兼容性

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

0 个注释

1 个答案

排序依据： 非常有帮助
非常有帮助 最新 最早
  1. 匿名
    2025-01-28T02:02:03+00:00

    错误原因为单个 DPC 或 ISR 超过了其时间分配。

    由于导致崩溃的程序是系统内核组件，且您使用的系统为已结束支持多年的 Windows 11 21H2 版本，所以请前往下载 Windows 11下载并更新系统至最新受支持的 Windows 11 24H2 版本以尝试解决此问题。

    如您想了解如何深入调试请自行阅读：错误检查 0x133：DPC_WATCHDOG_VIOLATION。

    0 个注释