每天开机过一段时间DPC WATCHDOG VIOLATION 蓝屏 已持续一年未解决,非常影响正常使用以下为检测日志内容Microsoft (R) Windows Debugger Version 10.0.25200.1003 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [D:\112522-8937-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 22621 MP (12 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Machine Name: Kernel base = 0xfffff803`1e800000 PsLoadedModuleList = 0xfffff803`1f413410 Debug session time: Fri Nov 25 14:42:57.473 2022 (UTC 8:00) System Uptime: 0 days 20:02:51.296 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: fffff803`1ec283c0 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:fffff803`1dd36970=0000000000000133 0: 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: fffff8031f51c340, 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: 1421 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 6289 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: 109 Key : Analysis.Init.Elapsed.mSec Value: 21506 Key : Analysis.Memory.CommitPeak.Mb Value: 103 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.Register Value: 0x133 Key : Dump.Attributes.AsUlong Value: 1008 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: 112522-8937-01.dmp DUMP_FILE_ATTRIBUTES: 0x1008 Kernel Generated Triage Dump BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff8031f51c340 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: fffff803`1dd36968 fffff803`1ea2413f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff803`1f51c340 : nt!KeBugCheckEx fffff803`1dd36970 fffff803`1ea22f74 : 00006238`7239b00d 00000000`00000001 00000000`00467ad1 00000000`00000000 : nt!KeAccumulateTicks 0x23f fffff803`1dd369d0 fffff803`1ea21403 : fffff803`1f45fec0 00000000`00000000 fffff803`1c4e5180 fffff803`1dd36d00 : nt!KiUpdateRunTime 0xf4 fffff803`1dd36b90 fffff803`1ea2088a : fffff803`1f45fec0 fffff803`1f50d8e0 fffff803`1f50d8e0 00000000`00000000 : nt!KeClockInterruptNotify 0x763 fffff803`1dd36c40 fffff803`1eb45f9e : 000000a8`0a1a64fc fffff803`1f50d830 fffff803`1c4e5180 00000000`00000000 : nt!HalpTimerClockInterrupt 0x10a fffff803`1dd36c70 fffff803`1ec2a51a : fffff803`1dd36d80 fffff803`1f50d830 fffff803`1f45ffc0 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0x19e fffff803`1dd36cb0 fffff803`1ec2ad87 : 00000000`00000000 00000000`00000000 00006238`723855ed 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa fffff803`1dd36d00 fffff803`1ebda5ea : fffff803`1ebd6969 ffffe30f`4ac10d50 00000000`000009d0 ffffe30f`4a6ac640 : nt!KiInterruptDispatchNoLockNoEtw 0x37 fffff803`1dd36e98 fffff803`1ebd6969 : ffffe30f`4ac10d50 00000000`000009d0 ffffe30f`4a6ac640 00000000`00000010 : nt!HalpAcpiPmRegisterReadPort 0xa fffff803`1dd36ea0 fffff803`23979231 : 00000000`00000004 fffff803`1dd36f98 00000000`00000000 fffff803`1eb4f22d : nt!HalpAcpiPmRegisterRead 0x39 fffff803`1dd36ed0 fffff803`23944580 : 00000000`00000000 ffffad01`38940dc0 fffff803`377c1280 00000000`0000b201 : ACPI!ACPIReadGpeStatusRegister 0x85 fffff803`1dd36f10 fffff803`1eb45f6b : ffffad01`38940dc0 ffffad01`38940e70 fffff803`1c4e5180 ffffad01`38940dc0 : ACPI!ACPIInterruptServiceRoutine 0x50 fffff803`1dd36f50 fffff803`1ec2a29f : fffff803`1dd27170 ffffad01`38940dc0 fffff803`1f45ffc0 fffff803`1c4e5180 : nt!KiCallInterruptServiceRoutine 0x16b fffff803`1dd36f90 fffff803`1ec2a567 : 00000000`00000000 fffff803`1c4e5180 00000000`00000001 00000000`00000000 : nt!KiInterruptSubDispatch 0x11f fffff803`1dd270f0 fffff803`1ebda5ea : fffff803`1ebd6969 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatch 0x37 fffff803`1dd27288 fffff803`1ebd6969 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpAcpiPmRegisterReadPort 0xa fffff803`1dd27290 fffff803`23979231 : 00000000`0000000d 00000000`00000000 00000000`00000000 00000000`00000000 : nt!HalpAcpiPmRegisterRead 0x39 fffff803`1dd272c0 fffff803`23944334 : 00000000`00000000 00000000`00000000 ffff9696`26a50a67 fffff803`1dd27400 : ACPI!ACPIReadGpeStatusRegister 0x85 fffff803`1dd27300 fffff803`2394478f : 00000000`80010000 00000000`80000000 ffffe30f`4a6ac5e0 00000000`80010000 : ACPI!ACPIInterruptDispatchEvents 0x4c fffff803`1dd27330 fffff803`1eab98ba : 00000000`00000000 fffff803`1dd279b0 ffffad01`38940e70 fffff803`1c4e5180 : ACPI!ACPIInterruptServiceRoutineDPC 0x11f fffff803`1dd27360 fffff803`1eab90c4 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs 0x54a fffff803`1dd278b0 fffff803`1ec2d1be : 00000000`00000000 fffff803`1c4e5180 fffff803`1f54c6c0 ffffe30f`69c79080 : nt!KiRetireDpcList 0xfe4 fffff803`1dd27b40 00000000`00000000 : fffff803`1dd28000 fffff803`1dd21000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e SYMBOL_NAME: ACPI!ACPIReadGpeStatusRegister 85 MODULE_NAME: ACPI IMAGE_NAME: ACPI.sys IMAGE_VERSION: 10.0.22621.608 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 85 FAILURE_BUCKET_ID: 0x133_ISR_ACPI!ACPIReadGpeStatusRegister OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {9524459d-2f22-efe5-b0c9-f824c586f42c} Followup: MachineOwner ---------

欢迎访问本站!。若是有超频,降压等,建议恢复正常,xmp也关闭。然后到电脑品牌的官网更新一下bios,覆盖安装一下芯片组驱动,显卡驱动,声卡驱动,网卡驱动(包括有线网,无线网,蓝牙3个驱动),请勿使用第三方的驱动安装程序。完成后执行一下干净启动,排除其他干扰: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键)看下是否恢复正常。


点赞(43) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部