最近突然很常DPC WATCHDOG VIOLATION導致藍屏, 求幫助, 這是我的dump文件: Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\user\OneDrive\桌面\070422-20484-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff800`4f200000 PsLoadedModuleList = 0xfffff800`4fe2a2b0 Debug session time: Mon Jul 4 01:41:41.416 2022 (UTC 8:00) System Uptime: 0 days 0:22:22.375 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: fffff800`4f5f7dd0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffc080`60db8e20=0000000000000133 1: 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: fffff8004fefb320, 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: 3468 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 25844 Key : Analysis.Init.CPU.mSec Value: 1405 Key : Analysis.Init.Elapsed.mSec Value: 40673 Key : Analysis.Memory.CommitPeak.Mb Value: 96 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: 070422-20484-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8004fefb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffc080`60db8e18 fffff800`4f636fec : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffc080`60db8e20 fffff800`4f45f203 : 0000030f`847a8154 ffffc080`60dc0180 00000000`00000000 ffffc080`60dc0180 : nt!KeAccumulateTicks 0x1d558c ffffc080`60db8e80 fffff800`4f45ecea : ffffd209`6b8f6480 ffffee02`6ba2f5b0 fffff800`513afd00 00000001`00008101 : nt!KeClockInterruptNotify 0x453 ffffc080`60db8f30 fffff800`4f42d885 : ffffd209`6b8f6480 00000000`00000000 00000000`00000000 ffff3b62`f26ae423 : nt!HalpTimerClockIpiRoutine 0x1a ffffc080`60db8f60 fffff800`4f5f987a : ffffee02`6ba2f5b0 ffffd209`6b8f6480 00000303`e352664e 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffc080`60db8fb0 fffff800`4f5f9de7 : ffffc080`60dc8210 00000000`00000000 ffffee02`6ba2f740 fffff800`4f5f9df4 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffffee02`6ba2f530 fffff800`4f4f9b57 : ffffffff`ffffffd2 fffff800`4fbab4c4 00000000`00000010 00000000`00000246 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffffee02`6ba2f6c0 fffff800`4fbab4c9 : ffffd209`75459318 ffffc080`60dc0180 00000000`00000001 ffffee02`6ba2f710 : nt!KeYieldProcessorEx 0x17 ffffee02`6ba2f6f0 fffff800`4fba9da5 : 00000000`1f9370d1 ffffc080`60dc0180 ffffd209`81ff2970 00000000`00000000 : nt!IopLiveDumpProcessCorralStateChange 0x2d ffffee02`6ba2f720 fffff800`4f4a181e : ffffc080`60dc3240 00000000`00000000 00000000`00000004 ffffc080`60dc0180 : nt!IopLiveDumpCorralDpc 0x55 ffffee02`6ba2f760 fffff800`4f4a0b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e ffffee02`6ba2f8d0 fffff800`4f5fb93e : ffffffff`00000000 ffffc080`60dc0180 ffffc080`60dcb240 ffffd209`83611040 : nt!KiRetireDpcList 0x1f4 ffffee02`6ba2fb60 00000000`00000000 : ffffee02`6ba30000 ffffee02`6ba29000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e SYMBOL_NAME: nt!KeAccumulateTicks 1d558c MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1766 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1d558c FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f} Followup: MachineOwner --------- 1: 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: fffff8004fefb320, 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: 2703 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2704 Key : Analysis.Init.CPU.mSec Value: 4874 Key : Analysis.Init.Elapsed.mSec Value: 66519 Key : Analysis.Memory.CommitPeak.Mb Value: 97 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: 070422-20484-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8004fefb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffc080`60db8e18 fffff800`4f636fec : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffc080`60db8e20 fffff800`4f45f203 : 0000030f`847a8154 ffffc080`60dc0180 00000000`00000000 ffffc080`60dc0180 : nt!KeAccumulateTicks 0x1d558c ffffc080`60db8e80 fffff800`4f45ecea : ffffd209`6b8f6480 ffffee02`6ba2f5b0 fffff800`513afd00 00000001`00008101 : nt!KeClockInterruptNotify 0x453 ffffc080`60db8f30 fffff800`4f42d885 : ffffd209`6b8f6480 00000000`00000000 00000000`00000000 ffff3b62`f26ae423 : nt!HalpTimerClockIpiRoutine 0x1a ffffc080`60db8f60 fffff800`4f5f987a : ffffee02`6ba2f5b0 ffffd209`6b8f6480 00000303`e352664e 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffc080`60db8fb0 fffff800`4f5f9de7 : ffffc080`60dc8210 00000000`00000000 ffffee02`6ba2f740 fffff800`4f5f9df4 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffffee02`6ba2f530 fffff800`4f4f9b57 : ffffffff`ffffffd2 fffff800`4fbab4c4 00000000`00000010 00000000`00000246 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffffee02`6ba2f6c0 fffff800`4fbab4c9 : ffffd209`75459318 ffffc080`60dc0180 00000000`00000001 ffffee02`6ba2f710 : nt!KeYieldProcessorEx 0x17 ffffee02`6ba2f6f0 fffff800`4fba9da5 : 00000000`1f9370d1 ffffc080`60dc0180 ffffd209`81ff2970 00000000`00000000 : nt!IopLiveDumpProcessCorralStateChange 0x2d ffffee02`6ba2f720 fffff800`4f4a181e : ffffc080`60dc3240 00000000`00000000 00000000`00000004 ffffc080`60dc0180 : nt!IopLiveDumpCorralDpc 0x55 ffffee02`6ba2f760 fffff800`4f4a0b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e ffffee02`6ba2f8d0 fffff800`4f5fb93e : ffffffff`00000000 ffffc080`60dc0180 ffffc080`60dcb240 ffffd209`83611040 : nt!KiRetireDpcList 0x1f4 ffffee02`6ba2fb60 00000000`00000000 : ffffee02`6ba30000 ffffee02`6ba29000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e SYMBOL_NAME: nt!KeAccumulateTicks 1d558c MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1766 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1d558c FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f} Followup: MachineOwner --------- 1: kd> lmvm nt Browse full module list start end module name fffff800`4f200000 fffff800`50246000 nt (pdb symbols) C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\A7DD074C948F81ECF4D65E3609DF48391\ntkrnlmp.pdb Loaded symbol image file: ntkrnlmp.exe Mapped memory image file: C:\ProgramData\Dbg\sym\ntkrnlmp.exe\79C147481046000\ntkrnlmp.exe Image path: ntkrnlmp.exe Image name: ntkrnlmp.exe Browse all global symbols functions data Image was built with /Brepro flag. Timestamp: 79C14748 (This is a reproducible build file hash, not a timestamp) CheckSum: 00A64BC0 ImageSize: 01046000 File version: 10.0.19041.1766 Product version: 10.0.19041.1766 File flags: 0 (Mask 3F) File OS: 40004 NT Win32 File type: 1.0 App File date: 00000000.00000000 Translations: 0409.04b0 Information from resource tables: CompanyName: Microsoft Corporation ProductName: Microsoft® Windows® Operating System InternalName: ntkrnlmp.exe OriginalFilename: ntkrnlmp.exe ProductVersion: 10.0.19041.1766 FileVersion: 10.0.19041.1766 (WinBuild.160101.0800) FileDescription: NT Kernel & System LegalCopyright: © Microsoft Corporation. All rights reserved.
您好，A&K，前来提供帮助。您提供的信息显示了系统内核的问题，这是一个很普通的错误，可能是驱动程序导致的，但dump文件没有记录具体的驱动程序名称。建议先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。
