dpc watchdog violation 蓝屏之ntkrnlmp.exe，已上传bug日志

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


Loading Dump File [C:\Windows\Minidump\092922-14281-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 (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff801`21000000 PsLoadedModuleList = 0xfffff801`21c2a290
Debug session time: Thu Sep 29 10:04:49.532 2022 (UTC + 8:00)
System Uptime: 0 days 0:18:57.203
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:
fffff801`213f8fa0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff9a01`c3148e20=0000000000000133
7: 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: fffff80121cfb320, 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: 2312

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 6615

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  092922-14281-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80121cfb320

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: 
ffff9a01`c3148e18 fffff801`214596fe     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff9a01`c3148e20 fffff801`212d2973     : 00000352`ff6fe6ff ffff9a01`c30f6180 00000000`00000000 ffff9a01`c30f6180 : nt!KeAccumulateTicks+0x18452e
ffff9a01`c3148e80 fffff801`212d245a     : ffffc189`736eaec0 fffffc02`0da8f6b0 00000000`77484600 00000000`1e2ffda0 : nt!KeClockInterruptNotify+0x453
ffff9a01`c3148f30 fffff801`21208a45     : ffffc189`736eaec0 00000000`00000000 00000000`00000000 ffffdbba`5110a4c8 : nt!HalpTimerClockIpiRoutine+0x1a
ffff9a01`c3148f60 fffff801`213faa4a     : fffffc02`0da8f6b0 ffffc189`736eaec0 00000344`1ec1207f 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffff9a01`c3148fb0 fffff801`213fafb7     : 00000000`00000000 00001f80`003f02c4 00000000`3f55e678 fffffc02`0da8f828 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffc02`0da8f630 fffff801`2121bfeb     : 00000000`80000000 fffff801`2132a779 fffffc02`0da8faf8 fffffc02`0da8faf1 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffc02`0da8f7c0 fffff801`2132a779     : fffffc02`0da8faf8 fffffc02`0da8faf1 fffffc02`0da8fb20 00000000`00000000 : nt!KeYieldProcessorEx+0x1b
fffffc02`0da8f7d0 fffff801`2123489e     : ffff9a01`c30f9240 ffffc189`3f56bafb fffffc02`0da8fae0 ffff9a01`00000002 : nt!ExpGetPoolTagInfoTarget+0x149
fffffc02`0da8f820 fffff801`21233b84     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
fffffc02`0da8f990 fffff801`213fcb3e     : ffffffff`00000000 ffff9a01`c30f6180 ffff9a01`c3101440 ffffc189`8d8f2080 : nt!KiRetireDpcList+0x1f4
fffffc02`0da8fc20 00000000`00000000     : fffffc02`0da90000 fffffc02`0da89000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!KeAccumulateTicks+18452e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2006

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  18452e

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------      您好，A&K，前来提供帮助。您提供的信息显示了系统内核的问题，这是一个很普通的错误，可能是驱动程序导致的，但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。