以下是WinDbg Preview读取结果:The following is the reading result of WinDbg preview:For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff804`3ca17d40 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:fffff804`3b981080=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. The offending component can usually be identified with a stack trace. Arg2: 0000000000001e00, The watchdog period. Arg3: fffff8043d305330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains additional information regarding the cumulative timeout Arg4: 0000000000000000 Debugging Details: ------------------ *** WARNING: Unable to verify timestamp for nvlddmkm.sys ************************************************************************* *** *** *** *** *** 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify checksum for win32k.sys DBGHELP: Timeout to store: https://msdl.microsoft.com/download/symbols DBGHELP: Timeout to store: https://msdl.microsoft.com/download/symbols DBGHELP: Timeout to store: https://msdl.microsoft.com/download/symbols DBGHELP: Timeout to store: https://msdl.microsoft.com/download/symbols KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4999 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 731640 Key : Analysis.Init.CPU.mSec Value: 2030 Key : Analysis.Init.Elapsed.mSec Value: 1047098 Key : Analysis.Memory.CommitPeak.Mb Value: 104 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.Register Value: 0x133 Key : WER.OS.Branch Value: co_release Key : WER.OS.Timestamp Value: 2021-06-04T16:28:00Z Key : WER.OS.Version Value: 10.0.22000.1 FILE_IN_CAB: 090322-6140-01.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 1 BUGCHECK_P2: 1e00 BUGCHECK_P3: fffff8043d305330 BUGCHECK_P4: 0 DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED TRAP_FRAME: fffff8043b981690 -- (.trap 0xfffff8043b981690) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=0000000000000000 rbx=0000000000000000 rcx=000000000018470c rdx=0000000000611c30 rsi=0000000000000000 rdi=0000000000000000 rip=fffff804667cf778 rsp=fffff8043b981820 rbp=ffff80074fb0ca40 r8=fffff8043b981868 r9=0000000000611c30 r10=fffff8043b981a08 r11=000000000000000c r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na po nc nvlddmkm 0x8f778: fffff804`667cf778 488b5c2430 mov rbx,qword ptr [rsp 30h] ss:0018:fffff804`3b981850=ffff80074fb0c000 Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: fffff804`3b981078 fffff804`3c8b71ef : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`3d305330 : nt!KeBugCheckEx fffff804`3b981080 fffff804`3c8b6e01 : 000026f5`7d7ddc26 00000000`00000000 ffff27d0`527b36db ffff8007`524e6000 : nt!KeAccumulateTicks 0x20f fffff804`3b9810f0 fffff804`3c8b3e36 : 00000000`00148fa0 00000000`000c415d 00000031`0575e3f8 00000000`00000000 : nt!KiUpdateRunTime 0x61 fffff804`3b981150 fffff804`3c8b5142 : fffff804`3b981690 00000000`00000000 fffff804`3d22b270 00000000`00000000 : nt!KiUpdateTime 0x686 fffff804`3b981540 fffff804`3c8b2a72 : fffff804`3b981690 fffff804`3d2f7f60 fffff804`00000000 00000000`0000000c : nt!KeClockInterruptNotify 0x272 fffff804`3b9815d0 fffff804`3c8913d0 : 00000031`059a6060 fffff804`3d2f7eb0 ffffd100`ea7e9d30 00000000`00000000 : nt!HalpTimerClockInterrupt 0xe2 fffff804`3b981600 fffff804`3ca1994a : fffff804`3b981710 fffff804`3d2f7eb0 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa0 fffff804`3b981640 fffff804`3ca19f17 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa fffff804`3b981690 fffff804`667cf778 : 00000000`00611c30 00000000`00611c30 00000000`00000000 fffff804`3b981a01 : nt!KiInterruptDispatchNoLockNoEtw 0x37 fffff804`3b981820 00000000`00611c30 : 00000000`00611c30 00000000`00000000 fffff804`3b981a01 00000000`00000020 : nvlddmkm 0x8f778 fffff804`3b981828 00000000`00611c30 : 00000000`00000000 fffff804`3b981a01 00000000`00000020 fffff804`668c3e19 : 0x611c30 fffff804`3b981830 00000000`00000000 : fffff804`3b981a01 00000000`00000020 fffff804`668c3e19 ffff8007`4fb0c000 : 0x611c30 SYMBOL_NAME: nvlddmkm 8f778 MODULE_NAME: nvlddmkm IMAGE_NAME: nvlddmkm.sys STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 8f778 FAILURE_BUCKET_ID: 0x133_ISR_nvlddmkm!unknown_function OS_VERSION: 10.0.22000.1 BUILDLAB_STR: co_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {f97493a5-ea2b-23ca-a808-8602773c2a86} 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键）看下是否恢复正常。
