Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\Minidump\100622-7750-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 (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Machine Name: Kernel base = 0xfffff806`1c600000 PsLoadedModuleList = 0xfffff806`1d22a2b0 Debug session time: Thu Oct 6 02:49:37.200 2022 (UTC 8:00) System Uptime: 0 days 0:00:17.906 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: fffff806`1c9f7dd0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:fffff806`1fa8fc90=0000000000000101 0: kd> !analyze -v ******************************************************************************* * * * Bugcheck Analysis * * * ******************************************************************************* CLOCK_WATCHDOG_TIMEOUT (101) An expected clock interrupt was not received on a secondary processor in an MP system within the allocated interval. This indicates that the specified processor is hung and not processing interrupts. Arguments: Arg1: 0000000000000018, Clock interrupt time out interval in nominal clock ticks. Arg2: 0000000000000000, 0. Arg3: ffff9801d1e1f180, The PRCB address of the hung processor. Arg4: 0000000000000003, The index of the hung processor. Debugging Details: ------------------ KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 3218 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 10940 Key : Analysis.Init.CPU.mSec Value: 749 Key : Analysis.Init.Elapsed.mSec Value: 15359 Key : Analysis.Memory.CommitPeak.Mb Value: 86 Key : Bugcheck.Code.DumpHeader Value: 0x101 Key : Bugcheck.Code.Register Value: 0x101 Key : Dump.Attributes.AsUlong Value: 8 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 FILE_IN_CAB: 100622-7750-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 101 BUGCHECK_P1: 18 BUGCHECK_P2: 0 BUGCHECK_P3: ffff9801d1e1f180 BUGCHECK_P4: 3 FAULTING_PROCESSOR: 3 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: WerFault.exe STACK_TEXT: fffff806`1fa8fc88 fffff806`1ca36f60 : 00000000`00000101 00000000`00000018 00000000`00000000 ffff9801`d1e1f180 : nt!KeBugCheckEx fffff806`1fa8fc90 fffff806`1c864c7d : 00000000`00000000 fffff806`17588180 00000000`00000246 00000000`0000047a : nt!KeAccumulateTicks 0x1d5500 fffff806`1fa8fcf0 fffff806`1c865221 : 00000000`00000200 00000000`000002ab fffff806`17588180 00000000`00000001 : nt!KiUpdateRunTime 0x5d fffff806`1fa8fd40 fffff806`1c85f093 : fffff806`17588180 00000000`00000000 fffff806`1d231540 00000000`00000000 : nt!KiUpdateTime 0x4a1 fffff806`1fa8fe80 fffff806`1c867a92 : ffffbe85`10dd3dd0 ffffbe85`10dd3e50 ffffbe85`10dd3e00 00000000`0000000c : nt!KeClockInterruptNotify 0x2e3 fffff806`1fa8ff30 fffff806`1c82d885 : 00000000`0ac2e6d4 fffff806`1d2f3a60 fffff806`1d2f3b10 00000000`00000000 : nt!HalpTimerClockInterrupt 0xe2 fffff806`1fa8ff60 fffff806`1c9f987a : ffffbe85`10dd3e50 fffff806`1d2f3a60 00000000`00000001 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 fffff806`1fa8ffb0 fffff806`1c9f9de7 : 00000000`59858c81 fffff806`17588180 00000000`00000002 fffff806`1758b130 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffffbe85`10dd3dd0 fffff806`1c885850 : 00000000`00000000 00000000`00000000 00000000`00000002 ffffa980`05571cf0 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffffbe85`10dd3f60 fffff806`1c885688 : 00000000`00000000 ffffbe85`10dd4200 00000000`00000000 00000000`00000000 : nt!KeFlushMultipleRangeTb 0x160 ffffbe85`10dd4000 fffff806`1c88d343 : fffff806`1d24efc0 ffffa980`00000000 fffff806`00000000 ffffbe85`10dd4088 : nt!MiFlushTbList 0x88 ffffbe85`10dd4030 fffff806`1c80ff02 : 00000000`00000000 00000000`00000000 00000000`00000000 ffffecfc`030b9640 : nt!MiTerminateWsleCluster 0x363 ffffbe85`10dd41e0 fffff806`1c83c341 : ffffd904`9eb86890 00000000`00000000 fffff806`00000004 00000000`00000000 : nt!MiRemoveMappedPtes 0x1f2 ffffbe85`10dd42a0 fffff806`1cbf5f31 : fffff806`1d24cbe8 fffff806`1cc56901 00000000`00000001 00000000`00000001 : nt!MiRemoveFromSystemSpace 0x31d ffffbe85`10dd43d0 fffff806`1cc56b45 : 00000000`0000000e ffffbe85`10dd4670 ffff8001`c24c98a0 00000000`000c8000 : nt!MiUnmapImageInSystemSpace 0x31 ffffbe85`10dd4400 fffff806`1cc58495 : ffffbe85`10dd4840 ffffbe85`10dd4840 ffffbe85`10dd4670 00000000`00000002 : nt!MiParseComAndCetHeaders 0x38d ffffbe85`10dd4570 fffff806`1cc236fb : ffffd904`9ed3d970 ffffbe85`10dd4840 ffffbe85`10dd4840 ffffd904`985570c0 : nt!MiCreateNewSection 0x2b9 ffffbe85`10dd46d0 fffff806`1cc22d44 : ffffbe85`10dd4700 ffff8001`c24c98a0 ffffd904`9ed3d970 00000000`00000000 : nt!MiCreateImageOrDataSection 0x2db ffffbe85`10dd47c0 fffff806`1cc22a87 : 00000000`11000000 ffffbe85`10dd4b80 00000000`00000001 00000000`00000002 : nt!MiCreateSection 0xf4 ffffbe85`10dd4940 fffff806`1cc2280c : 00000050`1f6dbbf8 00000000`00000005 00000000`00000000 00000000`00000001 : nt!MiCreateSectionCommon 0x207 ffffbe85`10dd4a20 fffff806`1ca097b8 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!NtCreateSection 0x5c ffffbe85`10dd4a90 00007ffd`6c88d684 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd 0x28 00000050`1f6dbb88 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffd`6c88d684 SYMBOL_NAME: nt!KeAccumulateTicks 1d5500 MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1766 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1d5500 FAILURE_BUCKET_ID: CLOCK_WATCHDOG_TIMEOUT_INVALID_CONTEXT_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {95498f51-33a9-903b-59e5-d236937d8ecf} Followup: MachineOwner --------- NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\atlmfc.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\ObjectiveC.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\concurrency.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\cpp_rest.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Kernel.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\stl.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Data.Json.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Geolocation.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Devices.Sensors.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\Windows.Media.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\windows.natvis' NatVis script unloaded from 'C:\Program Files\WindowsApps\Microsoft.WinDbg_1.2206.19001.0_x64__8wekyb3d8bbwe\amd64\Visualizers\winrt.natvis' Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved.
HiIamDave,Iwillhelpyouwiththis.PleasechecktoseeifyourPCisproducinganyminidumpfiles,Iwillcheckthosetoseeiftheyprovideanyinsightintoapotentialcauseofthesystemcrashes.PleaseNote,IcannotdownloadfromBaiduCloudDrive,pleaseuseadifferentCloudServicefortheupload.OpenWindowsFileExplorer.NavigatetoC:\Windows\MinidumpCopyanyminidumpfilesontoyourDesktop,thenzipthoseup.UploadthezipfiletotheCloud(OneDrive,DropBox.etc.),thenchoosetosharethoseandgetasharelink.Thenpostthelinkheretothezipfile,sowecantakealookforyou.
已上传到OneDrive上，是最近三次同样情况的崩溃文件链接：https://1drv.ms/u/s!AtjIOA7IMJfHtFMUXdB9WQPQoT8s?e=Fpuf34此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
你好我道歉，我离线了。您的小型转储文件仅表明内存(RAM)损坏未列出特定驱动程序1转到制造商网站上您的PC或主板的支持页面，然后从那里下载并安装他们推荐的芯片组驱动程序版本，并在那里检查可能需要安装的任何BIOS更新2等待看看您的系统是否稳定，如果没有，最好的选择是下载广泛可用的免费实用程序MemTest86，然后运行完整的4遍扫描以测试您的RAM是否存在物理错误___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
