Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\070922-15687-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 = 0xfffff804`0c600000 PsLoadedModuleList = 0xfffff804`0d22a2b0 Debug session time: Sat Jul 9 20:43:29.986 2022 (UTC 8:00) System Uptime: 0 days 0:52:42.687 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: fffff804`0c9f7dd0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffac81`e81b4e20=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: fffff8040d2fb320, 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: 2327 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 7220 Key : Analysis.Init.CPU.mSec Value: 812 Key : Analysis.Init.Elapsed.mSec Value: 34370 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: 070922-15687-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8040d2fb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffac81`e81b4e18 fffff804`0ca36fec : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffac81`e81b4e20 fffff804`0c85f203 : 00000933`8bec5b01 ffffac81`e81c0180 00000000`00000000 ffffac81`e81c0180 : nt!KeAccumulateTicks 0x1d558c ffffac81`e81b4e80 fffff804`0c85ecea : ffff890f`f41049a0 fffff38f`cb65f6a0 00000000`00000000 00000000`00000050 : nt!KeClockInterruptNotify 0x453 ffffac81`e81b4f30 fffff804`0c82d885 : ffff890f`f41049a0 00000000`00000000 00000000`00000000 ffffde8c`7db0aaf5 : nt!HalpTimerClockIpiRoutine 0x1a ffffac81`e81b4f60 fffff804`0c9f987a : fffff38f`cb65f6a0 ffff890f`f41049a0 00000000`80000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffac81`e81b4fb0 fffff804`0c9f9de7 : fffff38f`00000000 00001f80`009f02f4 00000000`389bbfec fffff38f`cb65f838 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa fffff38f`cb65f620 fffff804`0c8f9b5c : fffff804`0cb0d3ac ffff890f`fb8ed660 fffff38f`cb65faf4 fffff38f`cb65faf8 : nt!KiInterruptDispatchNoLockNoEtw 0x37 fffff38f`cb65f7b8 fffff804`0cb0d3ac : ffff890f`fb8ed660 fffff38f`cb65faf4 fffff38f`cb65faf8 fffff38f`cb65faf1 : nt!KeYieldProcessorEx 0x1c fffff38f`cb65f7c0 fffff804`0c8a181e : ffffac81`e81c3240 fffff38f`cb65f920 00000000`00000000 ffffac81`389c1e9d : nt!KiConfigureHeteroProcessorsTarget 0xdc fffff38f`cb65f820 fffff804`0c8a0b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e fffff38f`cb65f990 fffff804`0c9fb93e : ffffffff`00000000 ffffac81`e81c0180 ffffac81`e81cb440 ffff8900`057b7080 : nt!KiRetireDpcList 0x1f4 fffff38f`cb65fc20 00000000`00000000 : fffff38f`cb660000 fffff38f`cb659000 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 ---------
HiAkkoMuggleIamDave,Iwillhelpyouwiththis.PleasechecktoseeifyourPCisproducinganyminidumpfiles,Iwillcheckthosetoseeiftheyprovideanyinsightintoapotentialcauseofthesystemcrashes.PleaseNote,IcannotdownloadfromBaiduCloudDrive,pleaseuseadifferentCloudServicefortheupload.OpenWindowsFileExplorer.NavigatetoC:\Windows\MinidumpCopyanyminidumpfilesontoyourDesktop,thenzipthoseup.UploadthezipfiletotheCloud(OneDrive,DropBox.etc.),thenchoosetosharethoseandgetasharelink.Thenpostthelinkheretothezipfile,sowecantakealookforyou.
