蓝屏代码：DPC WATCHDOG VIOLATION 求解决

蓝屏代码：DPC WATCHDOG VIOLATION 小白没能看出来什么地方的问题QAQWinDbg分析如下：Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\Windows\Minidump\090622-8546-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 22000 MP (6 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Machine Name:
Kernel base = 0xfffff807`7fc00000 PsLoadedModuleList = 0xfffff807`808297b0
Debug session time: Tue Sep  6 13:20:42.211 2022 (UTC + 8:00)
System Uptime: 0 days 0:37:16.047
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:
fffff807`8001acf0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8680`ae1dade0=0000000000000133
4: 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: fffff80780905330, 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: 1781

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 3889

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 1808

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  090622-8546-01.dmp

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


DUMP_FILE_ATTRIBUTES: 0x1808
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80780905330

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  r5apex.exe

STACK_TEXT: 
ffff8680`ae1dadd8 fffff807`7fed800e     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffff8680`ae1dade0 fffff807`7fed7a91     : 00000796`49a2fdde ffff8680`00000500 00000000`00000002 fffff807`7fed31b8 : nt!KeAccumulateTicks+0x39e
ffff8680`ae1dae50 fffff807`7fed5c7a     : ffff8680`ae1c9200 ffffab85`b0a678f0 ffff8680`ae1c93b0 ffffe085`62e4e000 : nt!KiUpdateRunTime+0x61
ffff8680`ae1daeb0 fffff807`7fed5a66     : ffffe085`62d149a0 ffffe085`62d14a50 ffffab85`00000000 fffff807`83dc3239 : nt!KeClockInterruptNotify+0x11a
ffff8680`ae1daf40 fffff807`7fe0d2d0     : fffff807`8001fd70 00000000`00003001 ffffab85`ba9e73a0 fffff807`800213f0 : nt!HalpTimerClockIpiRoutine+0x16
ffff8680`ae1daf70 fffff807`8001c8fa     : ffffab85`b0a67970 ffffe085`62d149a0 00000785`10df3648 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa0
ffff8680`ae1dafb0 fffff807`8001cec7     : ffff8680`00000000 00000000`00000000 00000000`80000000 fffff807`8001ced4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffab85`b0a678f0 fffff807`7ff225fc     : ffffffff`ffffffd2 fffff807`7ff81c50 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffab85`b0a67a80 fffff807`7ff81c69     : ffffe085`62d3f050 00000000`00000cd8 ffffe085`75d88080 00000000`00000000 : nt!KeYieldProcessorEx+0x1c
ffffab85`b0a67ab0 fffff807`7fec7c11     : ffffab85`b0a67e70 ffffe085`204967d7 ffffab85`b0a67e00 ffff8680`00000002 : nt!ExpGetPoolTagInfoTarget+0x149
ffffab85`b0a67b00 fffff807`7fec6c12     : 00000000`00000000 00000000`00000001 00000000`000224bb 00000000`0000000f : nt!KiExecuteAllDpcs+0x491
ffffab85`b0a67d00 fffff807`80022ab5     : 00000000`00000000 ffff8680`ae1c0180 00000000`00000000 00000073`e7a2d4d0 : nt!KiRetireDpcList+0x2a2
ffffab85`b0a67fb0 fffff807`80022890     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffffab85`ba04f820 fffff807`80021eb6     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDispatchInterruptContinue
ffffab85`ba04f850 fffff807`8002d1d5     : ffffe085`745a0000 ffffe085`745ac380 00000182`9f146960 ffffe085`754d9101 : nt!KiDpcInterrupt+0x326
ffffab85`ba04f9e0 00007ff8`43264244     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceUser+0xbb
00000073`e7a2d2a8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ff8`43264244


SYMBOL_NAME:  nt!KeAccumulateTicks+39e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.918

STACK_COMMAND:  .cxr; .ecxr ; kb

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