Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\WINDOWS\Minidump\111322-18921-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 (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff800`0c200000 PsLoadedModuleList = 0xfffff800`0ce2a2b0 Debug session time: Sun Nov 13 00:35:35.184 2022 (UTC 8:00) System Uptime: 0 days 8:23:50.250 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`0c5f92d0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffa101`b0fd2e20=0000000000000133 10: 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: fffff8000cefb320, 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: 2515 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 10780 Key : Analysis.IO.Other.Mb Value: 10 Key : Analysis.IO.Read.Mb Value: 0 Key : Analysis.IO.Write.Mb Value: 20 Key : Analysis.Init.CPU.mSec Value: 734 Key : Analysis.Init.Elapsed.mSec Value: 173192 Key : Analysis.Memory.CommitPeak.Mb Value: 87 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: 111322-18921-01.dmp TAG_NOT_DEFINED_202b: *** Unknown TAG in analysis list 202b DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8000cefb320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System FAULTING_THREAD: 000000000000000b STACK_TEXT: ffffa101`b0fd2e18 fffff800`0c65be7e : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffa101`b0fd2e20 fffff800`0c4d2973 : 00003cb9`f0c4e579 ffffa101`b0f80180 00000000`00000000 ffffa101`b0f80180 : nt!KeAccumulateTicks 0x186cae ffffa101`b0fd2e80 fffff800`0c4d245a : ffffd78d`6c719780 ffff8c83`434bf5d0 00000000`00000000 fffff800`0cf24a00 : nt!KeClockInterruptNotify 0x453 ffffa101`b0fd2f30 fffff800`0c408a45 : ffffd78d`6c719780 00000000`00000000 00000000`00000000 ffff1392`0eaae81d : nt!HalpTimerClockIpiRoutine 0x1a ffffa101`b0fd2f60 fffff800`0c5fb26a : ffff8c83`434bf5d0 ffffd78d`6c719780 00003caf`a7f9f34d 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffa101`b0fd2fb0 fffff800`0c5fba37 : 00000000`00000000 ffff3e10`fd1c33cd 00000000`80000000 fffff800`0c5fba44 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffff8c83`434bf550 fffff800`0c41bfe7 : 00000000`00000010 00000000`00000a87 ffff8c83`434bf708 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffff8c83`434bf6e0 fffff800`0c52a8b9 : ffff8c83`434bfa38 ffff8c83`434bfa31 ffff8c83`434bfa60 00000000`00000000 : nt!KeYieldProcessorEx 0x17 ffff8c83`434bf710 fffff800`0c43489e : ffffa101`b0f83240 00000000`1c4de3c0 ffffd78d`6c6be040 00000000`0000002f : nt!ExpGetPoolTagInfoTarget 0x149 ffff8c83`434bf760 fffff800`0c433b84 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e ffff8c83`434bf8d0 fffff800`0c5fdbce : 00000000`00000000 ffffa101`b0f80180 ffffa101`b0f8b340 ffffd78d`7e66f080 : nt!KiRetireDpcList 0x1f4 ffff8c83`434bfb60 00000000`00000000 : ffff8c83`434c0000 ffff8c83`434b9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e STACK_COMMAND: ~11 ; .cxr ; kb SYMBOL_NAME: nt!KeAccumulateTicks 186cae MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.2251 BUCKET_ID_FUNC_OFFSET: 186cae FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f} Followup: MachineOwner --------- 附上近三次的minidump文件： 链接: https://pan.baidu.com/s/1zoMGrzF_SXJP1ru8HZtb3Q?pwd=b7r3 提取码: b7r3 复制这段内容后打开百度网盘手机App，操作更方便哦
HiHaoyuan,I'mDyari.Thanksforreachingout.Iwillbehappytoassistyouinthisregard.KindlycheckC:\Windows\MinidumpandcopyavailableminidumpfilestothedesktopthensharethemviaOneDriveorGoogleDriveinordertobeanalyzedandindicatewhichfileiscausingthecrash.Regards,你好Haoyuan，迪亚里。感谢您伸出援手。我很乐意在这方面为您提供帮助。请检查C:\Windows\Minidump并将可用的minidump文件复制到桌面，然后通过OneDrive或GoogleDrive共享它们，以便分析并指出导致崩溃的文件。问候，
HiHaoyuan,I'mDyari.Thanksforreachingout.Iwillbehappytoassistyouinthisregard.KindlycheckC:\Windows\MinidumpandcopyavailableminidumpfilestothedesktopthensharethemviaOneDriveorGoogleDriveinordertobeanalyzedandindicatewhichfileiscausingthecrash.Regards,你好Haoyuan，迪亚里。感谢您伸出援手。我很乐意在这方面为您提供帮助。请检查C:\Windows\Minidump并将可用的minidump文件复制到桌面，然后通过OneDrive或GoogleDrive共享它们，以便分析并指出导致崩溃的文件。问候，您好，这是近三次的minidump文件，请帮助分析：——————————————————————————————————————————————————————————————链接:https://pan.baidu.com/s/1zoMGrzF_SXJP1ru8HZtb3Q?pwd=b7r3提取码:b7r3复制这段内容后打开百度网盘手机App，操作更方便哦——————————————————————————————————————————————————————————————万分感谢！此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
你好Haoyuan，感谢分享minidump文件，抱歉晚了minidump文件没有命名任何驱动程序，仅表明ntkrnlmp.exe是一个Windows组件，这意味着其他原因导致系统出现故障，或者它可能是通常由于驱动程序不兼容而发生的内存损坏。如果只出现一次，可能是更新驱动或驱动不兼容造成的。如果它经常发生，请尝试以下步骤来解决此问题：1-检查更新：转到设置>更新和安全>检查更新>安装所有待处理的更新2-使用DDU免费工具完全卸载显卡驱动：https://www-guru3d-com.translate.goog/files-det.然后，安装制造商网站上提供的最新驱动程序。3-卸载任何第三方安全软件并使用免费的Malwarebytes扫描病毒和恶意软件：https://www-malwarebytes-com.translate.goog/mwb.4-以管理员身份运行命令提示符。键入此命令并按回车键：dism.exe/online/cleanup-image/restorehealth然后，键入此命令并按回车键：sfc/scannow5-如果您要超频您的PC，请尝试以它们的库存速度运行所有东西（CPU、GPU、系统内存）。看看问题是否仍然可以重现。或者，关闭XMP配置文件或将其设置为自动。6-从制造商的网站下载并安装最新版本的BIOS和芯片组驱动程序。7-使用免费实用程序MemTest86测试RAM，然后运行完整的8次扫描以测试您的RAM是否存在物理错误：https://www-tenforums-com.translate.goog/tutori.8-运行Windows内存诊断：https://www-howtogeek-com.translate.goog/260813.运行硬盘诊断：https://www-lifewire-com.translate.goog/free-ha.9-如果您愿意这样做，请取出所有系统内存条，检查它们是否有任何明显的缺陷，然后将它们重新插入插槽。确保它们正确安装在插槽中。如果您安装了多根系统内存并且您怀疑其中一根有故障，则可以尝试的一件事是一次仅使用一根内存模块重现该问题。这将帮助您隔离故障模块。10-如果执行上述步骤后问题仍然存在，请启用驱动程序验证程序并让计算机崩溃3次，然后将其禁用并共享新创建的minidump文件：https://www-tenforums-com.translate.goog/tutori.请随时询问您是否需要进一步的帮助。
