Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\111122-8765-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 18362 MP (24 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202 Machine Name: Kernel base = 0xfffff801`35e00000 PsLoadedModuleList = 0xfffff801`36245ef0 Debug session time: Fri Nov 11 19:16:58.033 2022 (UTC 8:00) System Uptime: 0 days 0:12:09.734 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ .. Loading User Symbols Loading unloaded module list ....... For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff801`35fc46a0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffe400`0d93db10=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: fffff80136371358, 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 *** *** *** ************************************************************************* Unable to read KTHREAD address ffffd28fe87c4138 Unable to read KTHREAD address ffffd28fe87c4138 Unable to read KTHREAD address ffffd28fe87c4138 Unable to read KTHREAD address ffffd28fe87c4138 Unable to read KTHREAD address ffffd28fe87c4138 *** WARNING: Unable to verify checksum for win32k.sys Unable to read KTHREAD address ffffd28fe87c4138 Unable to read KTHREAD address ffffd28fe87c4138 Unable to read KTHREAD address ffffd28fe87c4138 Unable to read KTHREAD address ffffd28fe87c4138 KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 5421 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 9038 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: 1312 Key : Analysis.Init.Elapsed.mSec Value: 4665 Key : Analysis.Memory.CommitPeak.Mb Value: 96 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.Register Value: 0x133 Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1 FILE_IN_CAB: 111122-8765-01.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff80136371358 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED TAG_NOT_DEFINED_c000000a: *** Unknown TAG in analysis list c000000a BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 FAULTING_THREAD: 0000000000000002 STACK_TEXT: ffffe400`0d9fe270 fffff801`360ae48a : 00000000`00000000 ffffe400`0d9de180 00000000`0000000f 00000000`00000000 : nt!KiCheckStall 0x85 ffffe400`0d9fe2a0 fffff801`360a3f26 : ffffe400`0d9fe480 ffffe400`0d9fe468 00000000`00000000 fffff801`35e19bba : nt!KiFreezeTargetExecution 0x1ca ffffe400`0d9fe3a0 fffff801`360a8546 : 00000000`00000013 fffff801`36371358 ffffe400`0d9fe5a0 00000000`00000000 : nt!KiCheckForFreezeExecution 0x2a ffffe400`0d9fe3d0 fffff801`35fc47a7 : 00000000`00000000 fffff801`360a2faf ffffe400`0d9de180 00000000`00000002 : nt!KeBugCheck2 0xc86 ffffe400`0d9fead0 fffff801`35ff5867 : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx 0x107 ffffe400`0d9feb10 fffff801`35e354f7 : 0000027e`4f830316 ffffe400`0d9de180 00000000`00000286 ffff8889`5643ea50 : nt!KeAccumulateTicks 0x1c2117 ffffe400`0d9feb70 fffff801`35d5f291 : 00000000`00000000 ffffd28f`d54d0f00 ffff8889`5643ead0 ffffd28f`d54d0fb0 : nt!KeClockInterruptNotify 0xc07 ffffe400`0d9fef30 fffff801`35effc35 : ffffd28f`d54d0f00 00000000`0000000c ffffde43`16b07c89 ffff8889`58d2c678 : hal!HalpTimerClockIpiRoutine 0x21 ffffe400`0d9fef60 fffff801`35fc612a : ffff8889`5643ead0 ffffd28f`d54d0f00 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffe400`0d9fefb0 fffff801`35fc6697 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffff8889`5643ea50 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw 0x37 STACK_COMMAND: ~2 ; .cxr ; kb SYMBOL_NAME: nt!KiCheckStall 85 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.18362.2274 BUCKET_ID_FUNC_OFFSET: 85 FAILURE_BUCKET_ID: 0x133_OUT_OF_SYNC_PROCESSOR_nt!KiCheckStall OS_VERSION: 10.0.18362.1 BUILDLAB_STR: 19h1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {3b616ce5-7f33-572c-7daf-c98b1d8d9f66} Followup: MachineOwner ---------
HiENLIamDave,Iwillhelpyouwiththis.PleasechecktoseeifyourPCisproducinganyminidumpfiles,Iwillcheckthosetoseeiftheyprovideanyinsightintoapotentialcauseofthesystemcrashes.PleaseNote,IcannotdownloadfromBaiduCloudDrive,pleaseuseadifferentCloudServicefortheupload.OpenWindowsFileExplorer.NavigatetoC:\Windows\MinidumpCopyanyminidumpfilesontoyourDesktop,thenzipthoseup.UploadthezipfiletotheCloud(OneDrive,DropBox.etc.),thenchoosetosharethoseandgetasharelink.Thenpostthelinkheretothezipfile,sowecantakealookforyou.
https://1drv.ms/u/s!Aq1S5z4EV_zugXVSXcPeJ-oS9roN?e=soJj6q在这里，辛苦了此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
ENL你好您的minidump文件仅表明内存(RAM)损坏未列出特定驱动程序您的PC是否崩溃过一次，还是经常崩溃？你还有更多可以上传的mindiump文件进行分析吗？___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
您好，最近就是经常玩一款游戏然后经常崩溃这是另外的文件，麻烦您了https://1drv.ms/u/s!Aq1S5z4EV_zugXaz5u3Hu21Y0sLU?e=NLwfnV此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
ENL你好,您的小型转储文件仅表明内存(RAM)损坏未列出特定驱动程序要尝试强制Windows显示任何有故障的驱动程序，最好的选择是打开DriverVerifier，让您的PC崩溃3次，然后您必须关闭DriverVerifier，最后，上传任何新创建的minidump文件
