Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [E:\062322-13796-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 Machine Name: Kernel base = 0xfffff800`46400000 PsLoadedModuleList = 0xfffff800`4702a2b0 Debug session time: Thu Jun 23 22:58:34.150 2022 (UTC 8:00) System Uptime: 1 days 2:38:54.844 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`467f7dd0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffa400`64348e20=0000000000000133 3: 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: fffff800470fb320, 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: 2655 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 21735 Key : Analysis.Init.CPU.mSec Value: 531 Key : Analysis.Init.Elapsed.mSec Value: 345045 Key : Analysis.Memory.CommitPeak.Mb Value: 94 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: 062322-13796-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff800470fb320 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 STACK_TEXT: ffffa400`64348e18 fffff800`46836fec : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffa400`64348e20 fffff800`4665f203 : 000049f8`74335adc ffffa400`642f6180 00000000`00000000 ffffa400`642f6180 : nt!KeAccumulateTicks 0x1d558c ffffa400`64348e80 fffff800`4665ecea : ffffb482`9e703d40 ffff888a`7c44f6a0 fffff800`499b3c00 00000000`00007501 : nt!KeClockInterruptNotify 0x453 ffffa400`64348f30 fffff800`4662d885 : ffffb482`9e703d40 00000000`00000000 00000000`00000000 ffff542f`3eb4b85e : nt!HalpTimerClockIpiRoutine 0x1a ffffa400`64348f60 fffff800`467f987a : ffff888a`7c44f6a0 ffffb482`9e703d40 00000000`80000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffa400`64348fb0 fffff800`467f9de7 : ffff888a`00000000 00001f80`007f02f4 00000000`40335d72 ffff888a`7c44f838 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffff888a`7c44f620 fffff800`466f9b5b : ffff888a`81cbf520 fffff800`4690d3ac ffffb482`a5d83660 ffff888a`7c44faf4 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffff888a`7c44f7b0 fffff800`4690d3ac : ffffb482`a5d83660 ffff888a`7c44faf4 ffff888a`7c44faf8 ffff888a`7c44faf1 : nt!KeYieldProcessorEx 0x1b ffff888a`7c44f7c0 fffff800`466a181e : ffffa400`642f9240 ffff888a`7c44f920 ffff888a`7c44fae0 ffffa400`40342673 : nt!KiConfigureHeteroProcessorsTarget 0xdc ffff888a`7c44f820 fffff800`466a0b04 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e ffff888a`7c44f990 fffff800`467fb93e : ffffffff`00000000 ffffa400`642f6180 ffffa400`64301440 ffffb482`af443040 : nt!KiRetireDpcList 0x1f4 ffff888a`7c44fc20 00000000`00000000 : ffff888a`7c450000 ffff888a`7c449000 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 --------- dmp文件在这个链接里面https://pan.baidu.com/s/1SBZNHK2IpPSDpbmOaG2mWA?pwd=qwj4
文杰你好戴夫，我会帮你的。请
文杰你好戴夫，我会帮你的。请
文杰你好抱歉，该云服务还
文杰你好抱歉，该云服务还
文杰你好，谢谢你，我能够访问该转储文件。您的minidump文件仅表明内存(RAM)损坏未列出特定驱动程序1将您的PC放入BIOS，如果您的RAM上设置了XMP配置文件，请禁用它，将其设置为默认值。2等待看看您的系统是否稳定，如果没有，最好的选择是下载广泛可用的免费实用程序MemTest86，然后运行完整的4遍扫描以测试您的RAM是否存在物理错误___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
