dpc_watchdog_violation 蓝屏---image_name: ntkrnlmp.exe

      本人电脑是联想拯救者R9000K 2021H，最近出现DPC WATCHDOG VIOLATION蓝屏，用winDbg分析代码如下：请帮忙分析一下问题所在。 Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.   Loading Dump File [C:\Windows\Minidump\091222-15515-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 = 0xfffff802`57600000 PsLoadedModuleList = 0xfffff802`5822a250 Debug session time: Mon Sep 12 20:59:23.954 2022 (UTC + 8:00) System Uptime: 25 days 7:33:08.093 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: fffff802`579f88c0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffaa01`d5092e20=0000000000000133 13: 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: 0000000000000001, The system cumulatively spent an extended period of time at     DISPATCH_LEVEL or above. The offending component can usually be     identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: fffff802582fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains     additional information regarding the cumulative timeout Arg4: 0000000000000000  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: 3296      Key  : Analysis.DebugAnalysisManager     Value: Create      Key  : Analysis.Elapsed.mSec     Value: 16215      Key  : Analysis.Init.CPU.mSec     Value: 827      Key  : Analysis.Init.Elapsed.mSec     Value: 346012      Key  : Analysis.Memory.CommitPeak.Mb     Value: 95      Key  : Bugcheck.Code.DumpHeader     Value: 0x133      Key  : Bugcheck.Code.Register     Value: 0x133      Key  : Dump.Attributes.AsUlong     Value: c      Key  : Dump.Attributes.InsufficientDumpfileSize     Value: 1      Key  : Dump.Attributes.KernelGeneratedTriageDump     Value: 1      Key  : Dump.Attributes.RequiredDumpfileSize     Value: 0x1e56680b4   FILE_IN_CAB:  091222-15515-01.dmp  DUMP_FILE_ATTRIBUTES: 0xc   Insufficient Dumpfile Size   Kernel Generated Triage Dump  BUGCHECK_CODE:  133  BUGCHECK_P1: 1  BUGCHECK_P2: 1e00  BUGCHECK_P3: fffff802582fb320  BUGCHECK_P4: 0  DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED  BLACKBOXACPI: 1 (!blackboxacpi)   BLACKBOXBSD: 1 (!blackboxbsd)   BLACKBOXNTFS: 1 (!blackboxntfs)   BLACKBOXPNP: 1 (!blackboxpnp)   BLACKBOXWINLOGON: 1  CUSTOMER_CRASH_COUNT:  1  PROCESS_NAME:  System  STACK_TEXT:   ffffaa01`d5092e18 fffff802`57a2a998     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`582fb320 : nt!KeBugCheckEx ffffaa01`d5092e20 fffff802`5784b573     : 00109c67`85cfe282 ffffaa01`d5040180 00000000`00000000 ffffaa01`d5040180 : nt!KeAccumulateTicks+0x1dcbc8 ffffaa01`d5092e80 fffff802`5784b05a     : ffffc982`18cee900 fffff18d`85b9f3f0 fffff802`62c5d800 00000000`00008502 : nt!KeClockInterruptNotify+0x453 ffffaa01`d5092f30 fffff802`578d9405     : ffffc982`18cee900 00000000`00000000 00000000`00000000 ffffb676`08486388 : nt!HalpTimerClockIpiRoutine+0x1a ffffaa01`d5092f60 fffff802`579fa36a     : fffff18d`85b9f3f0 ffffc982`18cee900 00000000`00025176 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5 ffffaa01`d5092fb0 fffff802`579fa8d7     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa fffff18d`85b9f370 fffff802`578e9499     : ffffffff`ffffffd2 fffff802`578e91bd 00000000`00000010 00000000`00000206 : nt!KiInterruptDispatchNoLockNoEtw+0x37 fffff18d`85b9f500 fffff802`578e91e5     : ffffaa01`00000000 00001f80`00d30280 fffff780`00000320 ffffaa01`d5040180 : nt!KiChargeSchedulingGroupCycleTime+0x9 fffff18d`85b9f530 fffff802`578e67c5     : ffffaa01`d5040100 ffffc982`18d39000 ffffedfa`58f8be00 fffff802`00000000 : nt!KiTransitionSchedulingGroupGeneration+0x105 fffff18d`85b9f5d0 fffff802`578e830e     : ffffaa01`d5040180 00000000`00000000 00000000`0857ed05 00000000`00000000 : nt!KiGroupSchedulingGenerationEnd+0x55 fffff18d`85b9f620 fffff802`578e7898     : 00000000`00000000 fffff18d`85b9f6c0 00000000`00000000 fffff18d`85b9f6d0 : nt!KiGroupSchedulingQuantumEnd+0xce fffff18d`85b9f6b0 fffff802`579ff736     : 00000048`0e107000 00000000`00000004 00000000`00000000 fffff802`579fefd5 : nt!KiQuantumEnd+0x148 fffff18d`85b9f7b0 fffff802`579fedee     : 00000000`00000000 00000000`00000000 ffffc982`288cf921 ffff8101`2ec2d000 : nt!KiDispatchInterruptContinue+0x16 fffff18d`85b9f7e0 fffff802`578b2688     : ffffc982`18d39080 fffff802`578b1b3f 40010001`0000000d ffffc982`00000000 : nt!KiDpcInterrupt+0x2ee fffff18d`85b9f970 fffff802`578b1b3f     : 40010001`0000000d ffffc982`00000000 00000000`00000000 fffff802`00000000 : nt!KiSwapThread+0x578 fffff18d`85b9f980 fffff802`5780ca9b     : ffffaa01`00000000 ffffaa01`00000000 ffffc982`00000000 00000000`00000000 : nt!KiCommitThreadWait+0x14f fffff18d`85b9fa20 fffff802`579b27c6     : ffffaa01`d50432ae 00000000`00000080 ffffc982`18d39080 00000000`00000000 : nt!KeWaitForGate+0xcb fffff18d`85b9fa70 fffff802`57958235     : ffffc982`18d39080 ffffc982`18d39080 00000000`00000080 00000000`00000000 : nt!KiExecuteDpc+0x86 fffff18d`85b9fbd0 fffff802`579fff48     : ffffaa01`d5040180 ffffc982`18d39080 fffff802`579581e0 00000000`00000000 : nt!PspSystemThreadStartup+0x55 fffff18d`85b9fc20 00000000`00000000     : fffff18d`85ba0000 fffff18d`85b99000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28   SYMBOL_NAME:  nt!KeAccumulateTicks+1dcbc8  MODULE_NAME: nt  IMAGE_NAME:  ntkrnlmp.exe  IMAGE_VERSION:  10.0.19041.1889  STACK_COMMAND:  .cxr; .ecxr ; kb  BUCKET_ID_FUNC_OFFSET:  1dcbc8  FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks  OSPLATFORM_TYPE:  x64  OSNAME:  Windows 10  FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}  Followup:     MachineOwner ---------      您好！不客气，如果之后您或您的朋友有其他的疑问，子来提问，这里的网友们会与你们一起携手研究与了解您的问题并给予全力的帮助！谢谢您对的支持！（
        您可到以下的连接，输入您的主机编号，下载所有最新版本的驱动更新一下，然后重启电脑：（蓝牙+芯片组+网卡+声卡+显卡+BIOS）（建议不要使用第三方软件更新驱动）Lenovo：https://think.lenovo.com.cn/support/driver/main.
       
        Jason，您好我更新了BIOS、蓝牙、声卡的驱动，同时也进行了windowsupdate的升级，现在并没有出现上述问题了。谢谢！此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
        您好！不客气，如果之后您或您的朋友有其他的疑问，子来提问，这里的网友们会与你们一起携手研究与了解您的问题并给予全力的帮助！谢谢您对的支持！（