Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\100622-12546-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available ************* Path validation summary ************** Response Time (ms) Location Deferred srv* Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 19041 MP (16 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff802`1b800000 PsLoadedModuleList = 0xfffff802`1c42a290 Debug session time: Thu Oct 6 17:54:03.254 2022 (UTC 8:00) System Uptime: 0 days 4:15:24.985 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: fffff802`1bbf8fa0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffbe80`95392e20=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: fffff8021c4fb320, 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: 2514 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 2522 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: 343 Key : Analysis.Init.Elapsed.mSec Value: 9152 Key : Analysis.Memory.CommitPeak.Mb Value: 82 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: 100622-12546-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff8021c4fb320 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: ffffbe80`95392e18 fffff802`1bc596fe : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffbe80`95392e20 fffff802`1bad2973 : 00003a9f`ed604919 ffffbe80`95340180 00000000`00000000 ffffbe80`95340180 : nt!KeAccumulateTicks 0x18452e ffffbe80`95392e80 fffff802`1bad245a : ffffd006`d20dc3e0 ffff8308`668a76d0 fffff802`1d411600 0000000a`0000b101 : nt!KeClockInterruptNotify 0x453 ffffbe80`95392f30 fffff802`1ba08a45 : ffffd006`d20dc3e0 ffffbe80`95392f40 00000000`00000010 ffffec18`3a141646 : nt!HalpTimerClockIpiRoutine 0x1a ffffbe80`95392f60 fffff802`1bbfaa4a : ffff8308`668a76d0 ffffd006`d20dc3e0 00003a8c`5c144865 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffbe80`95392fb0 fffff802`1bbfafb7 : 00000b00`cca5eef6 ffffd190`c9a74f56 00000000`80000000 fffff802`1bbfafc4 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffff8308`668a7650 fffff802`1ba1bfe7 : 00000000`00000010 00000000`00000286 ffff8308`668a7808 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffff8308`668a77e0 fffff802`1bb2a779 : 00000000`00010001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx 0x17 ffff8308`668a7810 fffff802`1ba3489e : ffffbe80`95343240 00000000`46192fa6 00000000`00000004 ffffbe80`95340180 : nt!ExpGetPoolTagInfoTarget 0x149 ffff8308`668a7860 fffff802`1ba33b84 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e ffff8308`668a79d0 fffff802`1bbfcb3e : ffffffff`00000000 ffffbe80`95340180 ffffbe80`9534b440 ffffd006`e4b020c0 : nt!KiRetireDpcList 0x1f4 ffff8308`668a7c60 00000000`00000000 : ffff8308`668a8000 ffff8308`668a2000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e STACK_COMMAND: ~15 ; .cxr ; kb SYMBOL_NAME: nt!KeAccumulateTicks 18452e MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.2006 BUCKET_ID_FUNC_OFFSET: 18452e FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f} Followup: MachineOwner ---------
HiIamDave,Iwillhelpyouwiththis.PleasechecktoseeifyourPCisproducinganyminidumpfiles,Iwillcheckthosetoseeiftheyprovideanyinsightintoapotentialcauseofthesystemcrashes.PleaseNote,IcannotdownloadfromBaiduCloudDrive,pleaseuseadifferentCloudServicefortheupload.OpenWindowsFileExplorer.NavigatetoC:\Windows\MinidumpCopyanyminidumpfilesontoyourDesktop,thenzipthoseup.UploadthezipfiletotheCloud(OneDrive,DropBox.etc.),thenchoosetosharethoseandgetasharelink.Thenpostthelinkheretothezipfile,sowecantakealookforyou.
https://1drv.ms/u/s!Algee9cH9w5liyDaY2vln4Z2ZjOd?e=yJj8xc此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
你好您的小型转储文件仅表明内存(RAM)损坏未列出特定驱动程序1转到制造商网站上B450MMORTARMAX(MS-7B89)主板的支持页面，然后从那里下载并安装他们推荐的芯片组驱动程序版本，并在那里检查可能需要安装的任何BIOS更新,你的BIOS日期是2020启动到BIOS，发现您的RAM上设置了XMP配置文件，禁用它，将其设置为默认值。2等待看看您的系统是否稳定，如果没有，最好的选择是下载广泛可用的免费实用程序MemTest86，然后运行完整的4遍扫描以测试您的RAM是否存在物理错误___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
