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: fffff80482305330, 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: 1811 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 1813 Key : Analysis.IO.Other.Mb Value: 0 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 0 Key : Analysis.Init.CPU.mSec Value: 530 Key : Analysis.Init.Elapsed.mSec Value: 9021 Key : Analysis.Memory.CommitPeak.Mb Value: 142 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.Register Value: 0x133 Key : Dump.Attributes.AsUlong Value: 1808 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 FILE_IN_CAB: 112322-15000-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: fffff80482305330 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System FAULTING_THREAD: 000000000000000f STACK_TEXT: ffffe781`9e26cdd8 fffff804`81831a1e : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffe781`9e26cde0 fffff804`818314a1 : 0000035e`b0a2ec60 ffffe781`00000500 00000000`00000002 fffff804`8182cbc8 : nt!KeAccumulateTicks 0x39e ffffe781`9e26ce50 fffff804`8182f68a : ffffe781`9e209200 ffffa50f`be68f530 ffffe781`9e2093b0 fffff804`8191ed8b : nt!KiUpdateRunTime 0x61 ffffe781`9e26ceb0 fffff804`8182f476 : ffffbe8b`0eb276e0 ffffbe8b`0eb27790 00000000`00000000 00000000`00000000 : nt!KeClockInterruptNotify 0x11a ffffe781`9e26cf40 fffff804`81814600 : ffffbe8b`0eb276e0 fffff804`81875bdc 00000000`00000000 000001cd`027fad2c : nt!HalpTimerClockIpiRoutine 0x16 ffffe781`9e26cf70 fffff804`81a1d0ca : ffffa50f`be68f5b0 ffffbe8b`0eb276e0 00000000`00000000 ffffe781`9e207fe0 : nt!KiCallInterruptServiceRoutine 0xa0 ffffe781`9e26cfb0 fffff804`81a1d937 : 00000000`00000000 00001f80`00a10244 00000000`4171e4c6 ffffa50f`be68f6f0 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffffa50f`be68f530 fffff804`81818ad0 : 00000000`80000000 fffff804`81b6759a 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffffa50f`be68f6c0 fffff804`81b6759a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx 0x20 ffffa50f`be68f6d0 fffff804`818215e1 : ffffa50f`be68fac0 ffffbe8b`0eab2010 ffffa50f`be902490 ffffa50f`be9024a0 : nt!KiConfigureHeteroProcessorsTarget 0xba ffffa50f`be68f750 fffff804`818205e2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs 0x491 ffffa50f`be68f950 fffff804`81a1fd3e : 00000000`00000000 ffffe781`9e200180 ffffe781`9e20c440 ffffbe8b`259c5080 : nt!KiRetireDpcList 0x2a2 ffffa50f`be68fc00 00000000`00000000 : ffffa50f`be690000 ffffa50f`be689000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e STACK_COMMAND: ~15 ; .cxr ; kb SYMBOL_NAME: nt!KeAccumulateTicks 39e MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22000.1219 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 ---------
显示是与系统内核相关的问题。一般是驱动程序导致的，建议先尝试卸载所有主要设备驱动程序（GPU、芯片组等），然后前往设备制造商官网下载最新版本并重新安装。您可以在回答下方的“此是否有帮助？”处给出评分以向本站反馈，也许能够帮助到更多的人。在与某些特定身份的本站成员对话时，给出评分将会结束对话。这是一个公共的本站，请勿发送您的个人信息，一些信息可能会被自动屏蔽，比如邮箱地址。任何帮助回答他人问题的行为都值得赞赏，感谢您对本站的支持。AnalogKnight-Microsoft本站志愿者版主此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
