dmp文件信息如下： Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Users\RinGenkou\Desktop\102122-13703-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`17a00000 PsLoadedModuleList = 0xfffff802`1862a270 Debug session time: Fri Oct 21 22:57:12.804 2022 (UTC 8:00) System Uptime: 1 days 5:05:19.687 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`17df90f0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffa681`197f8c90=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: fffff802186fb320, 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: 1765 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 1793 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: 374 Key : Analysis.Init.Elapsed.mSec Value: 9830 Key : Analysis.Memory.CommitPeak.Mb Value: 93 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: 102122-13703-01.dmp DUMP_FILE_ATTRIBUTES: 0x8 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff802186fb320 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: ffffa681`197f8c88 fffff802`17e597fe : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffa681`197f8c90 fffff802`17cd83ed : 00010d1d`c48efe60 ffffa681`19b40180 00000000`00000246 00000000`006643ec : nt!KeAccumulateTicks 0x18462e ffffa681`197f8cf0 fffff802`17cd8991 : 00000000`00663d00 00000000`003cf473 ffffa681`19b40180 00000000`00000001 : nt!KiUpdateRunTime 0x5d ffffa681`197f8d40 fffff802`17cd2803 : ffffa681`19b40180 00000000`00000000 fffff802`186315d8 00000000`00000000 : nt!KiUpdateTime 0x4a1 ffffa681`197f8e80 fffff802`17cdb1c2 : ffff948d`1ac2f590 ffff948d`1ac2f610 ffff948d`1ac2f600 00000000`00000002 : nt!KeClockInterruptNotify 0x2e3 ffffa681`197f8f30 fffff802`17c08a45 : 000000f3`d23f6ffd ffffe505`817135a0 ffffe505`81713650 ffff84d9`8784f000 : nt!HalpTimerClockInterrupt 0xe2 ffffa681`197f8f60 fffff802`17dfab9a : ffff948d`1ac2f610 ffffe505`817135a0 00010d0c`f3bbb95a 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffa681`197f8fb0 fffff802`17dfb107 : ffff948d`00000000 00001f80`00df0214 00000000`1e2db66c ffff948d`1ac2f760 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffff948d`1ac2f590 fffff802`17c1bfec : fffff802`183ab4f9 ffffe505`90224368 ffffa681`19b40180 00000000`00000001 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffff948d`1ac2f728 fffff802`183ab4f9 : ffffe505`90224368 ffffa681`19b40180 00000000`00000001 ffff948d`1ac2f750 : nt!KeYieldProcessorEx 0x1c ffff948d`1ac2f730 fffff802`183a9dd5 : 00000000`1e2de7ea ffffa681`19b40180 ffffe505`a10eca20 00000000`00000000 : nt!IopLiveDumpProcessCorralStateChange 0x2d ffff948d`1ac2f760 fffff802`17c3489e : ffffa681`19b43240 ffff948d`1ac2fa50 ffffa681`19b40180 ffffe505`a80a80c0 : nt!IopLiveDumpCorralDpc 0x55 ffff948d`1ac2f7a0 fffff802`17c33b84 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e ffff948d`1ac2f910 fffff802`17dfcc8e : ffffffff`00000000 ffffa681`19b40180 ffffa681`19b4b440 ffffe505`a3f1f5c0 : nt!KiRetireDpcList 0x1f4 ffff948d`1ac2fba0 00000000`00000000 : ffff948d`1ac30000 ffff948d`1ac29000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e SYMBOL_NAME: nt!KeAccumulateTicks 18462e MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.2130 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 18462e FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f} Followup: MachineOwner
欢迎访问本站！。没有看到具体错误的驱动等。若是有超频，降压等，建议恢复正常，xmp也关闭。然后到电脑品牌的官网更新一下bios，覆盖安装一下所有的驱动，请勿使用第三方的驱动安装程序。完成后执行一下干净启动，排除其他干扰：https://support.microsoft.com/zh-cn/help/929135.先卸载设备中全部的第三方反病毒软件与系统优化软件(例如360、联想电脑管家、360桌面、腾讯电脑管家、腾讯桌面、鲁大师，代理，加速器，虚拟机等)。然后鼠标右键单击开始菜单→运行（RUN）→输入：msconfig（按下Enter键）点击上面的“服务”勾选下面的“隐藏所有Microsoft服务”（请务必勾选）点击“全部禁用”。然后鼠标右键单击开始菜单→任务管理器，（点击底部“详细信息”），点击顶部”启动”，鼠标右键单击“状态”显示为“已启动”的项，选择“禁用”。（禁用所有启动项。）然后鼠标右键单击开始按钮（图标的按钮）→"WindowsPowerShell(I)（管理员)(A）”→输入：（WIndows11中可能显示Windows终端（管理员））sfc/SCANNOW（按下Enter键）Dism/Online/Cleanup-Image/ScanHealth（按下Enter键）Dism/Online/Cleanup-Image/CheckHealth（按下Enter键）DISM/Online/Cleanup-image/RestoreHealth（按下Enter键）完成后重启电脑，再次输入：sfc/SCANNOW（按下Enter键）看下是否有改善。
你好，。请问是否在进行上述操作时有无法进行的步骤，或者在完成操作后仍然有异常？若是点击“”按钮后没有加载出输入框，无法内容，建议等待一会再尝试。很可能是网络等原因。https://answers.microsoft.com/zh-hans/windows/f.
你好。经微星官网查询，主板BIOS已是最新版本，各设备驱动均来自官网或设备附带的安装盘。该蓝屏初次出现在16日系统完成更新后，猜测是某个应用的进程冲突，但由于该蓝屏的发生不具规律，难以复现，现在无法用上述的排除法找出具体应用。附上最近一次蓝屏的DMP文件链接：https://pan.baidu.com/s/1Ty8L0Lp2H1HgL9cNIdC-WQ提取码：4221此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
感谢，建议先如上述操作一下。若是仍然会出现蓝屏，建议分享一下最新的dmp文件，我将查看下情况。
