蓝屏 每天不定时蓝屏 win10 一直蓝 升级了win11 也蓝 快崩溃了 dmp文件 链接: https://pan.baidu.com/s/1L4CfBeOHSQ_Ej6TqKLoiSw?pwd=bijq 提取码: bijq 2: 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: 0000000000000001, The system cumulatively spent an extended period of time at DISPATCH_LEVEL or above. Arg2: 0000000000001e00, The watchdog period (in ticks). Arg3: fffff8047b51c340, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000 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: 3233 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 3357 Key : Analysis.IO.Other.Mb Value: 15 Key : Analysis.IO.Read.Mb Value: 4 Key : Analysis.IO.Write.Mb Value: 122 Key : Analysis.Init.CPU.mSec Value: 85046 Key : Analysis.Init.Elapsed.mSec Value: 4200948 Key : Analysis.Memory.CommitPeak.Mb Value: 538 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.Register Value: 0x133 Key : Dump.Attributes.AsUlong Value: 1808 Key : Dump.Attributes.DiagDataWrittenToHeader Value: 1 Key : Dump.Attributes.ErrorCode Value: 0 Key : Dump.Attributes.KernelGeneratedTriageDump Value: 1 Key : Dump.Attributes.LastLine Value: Dump completed successfully. Key : Dump.Attributes.ProgressPercentage Value: 0 FILE_IN_CAB: 102822-16625-01.dmp DUMP_FILE_ATTRIBUTES: 0x1808 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff8047b51c340 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffff8401`3d36b9a8 fffff804`7aa2413f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`7b51c340 : nt!KeBugCheckEx ffff8401`3d36b9b0 fffff804`7aa22f74 : 0000065f`0dbf5392 00000000`0000000d 00000000`0001e0db 00000000`00000000 : nt!KeAccumulateTicks 0x23f ffff8401`3d36ba10 fffff804`7aa22e56 : 00000000`00000010 00000000`00000000 ffff8401`3d351180 00000004`7a71e900 : nt!KiUpdateRunTime 0xf4 ffff8401`3d36bbd0 fffff804`7aa2107e : 00000000`00000000 ffff8401`3d351180 ffffffff`ffffffff 00000000`00000002 : nt!KiUpdateTime 0x13e6 ffff8401`3d36be90 fffff804`7aa2088a : fffff804`7b45ff30 ffffbf02`6d3312b0 ffffbf02`6d3312b0 00000000`00000000 : nt!KeClockInterruptNotify 0x3de ffff8401`3d36bf40 fffff804`7ab45f6e : 00000004`7a785e5c ffffbf02`6d331200 ffff8401`3d351180 00000000`00000000 : nt!HalpTimerClockInterrupt 0x10a ffff8401`3d36bf70 fffff804`7ac29d1a : ffff8304`9105f3f0 ffffbf02`6d331200 ffffbf02`6d413080 00000000`0000073c : nt!KiCallInterruptServiceRoutine 0x19e ffff8401`3d36bfb0 fffff804`7ac2a2e7 : ffff8401`3d351180 00000000`00000000 00000004`32f0902d 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffff8304`9105f370 fffff804`7ac2c111 : 00000000`00000000 ffffbf02`6d413080 ffffbf02`77808080 ffffbf02`77815080 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffff8304`9105f500 00000000`00000000 : ffff8304`91060000 ffff8304`91059000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x101 SYMBOL_NAME: nt!KeAccumulateTicks 23f MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.22621.674 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 23f FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06} 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键）看下是否有改善。
请问Intel?TurboBoostMax这个是否有影响？主板我刚刚更新了bios程序正在观察此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
感谢，建议先关闭TurboBoostMax。若是恢复正常，再逐个打开需要的功能等。
