DPC_WATCHDOG_VIOLATION蓝屏问题

windbg的分析报告如下：Microsoft (R) Windows Debugger Version 10.0.21306.1007 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.


Loading Dump File [C:\WINDOWS\Minidump\101222-5750-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 19041 MP (12 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Machine Name:
Kernel base = 0xfffff800`75600000 PsLoadedModuleList = 0xfffff800`7622a270
Debug session time: Wed Oct 12 11:25:00.793 2022 (UTC + 8:00)
System Uptime: 0 days 1:04:19.641
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:
fffff800`759f90e0 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff800`7b6934a0=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: fffff800762fb320, 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: 2499

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 7078

    Key  : Analysis.Init.CPU.mSec
    Value: 312

    Key  : Analysis.Init.Elapsed.mSec
    Value: 470373

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 74


DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff800762fb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXACPI: 1 (!blackboxacpi)


BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
fffff800`7b693498 fffff800`75a59882     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff800`762fb320 : nt!KeBugCheckEx
fffff800`7b6934a0 fffff800`758d2973     : 00000913`544beadd fffff800`733cb180 00000000`00000000 fffff800`733cb180 : nt!KeAccumulateTicks+0x1846b2
fffff800`7b693500 fffff800`758d245a     : fffff800`762f3940 fffff800`7b693700 00000000`00000000 fffff800`9e657054 : nt!KeClockInterruptNotify+0x453
fffff800`7b6935b0 fffff800`75808a45     : fffff800`762f3940 fffff800`75808a45 000c192c`6346338c fffff800`758d245a : nt!HalpTimerClockIpiRoutine+0x1a
fffff800`7b6935e0 fffff800`759fab8a     : fffff800`7b693700 fffff800`762f3940 fffff800`7b693a01 fffff800`75922d7a : nt!KiCallInterruptServiceRoutine+0xa5
fffff800`7b693630 fffff800`759fb0f7     : 00000000`00b81210 fffff800`759fb104 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff800`7b693680 fffff800`9e65f778     : 00000000`00611c30 00000000`00611c30 00000000`00000000 fffff800`7b693a01 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff800`7b693810 00000000`00611c30     : 00000000`00611c30 00000000`00000000 fffff800`7b693a01 00000000`00000020 : nvlddmkm+0x8f778
fffff800`7b693818 00000000`00611c30     : 00000000`00000000 fffff800`7b693a01 00000000`00000020 fffff800`9e753e19 : 0x611c30
fffff800`7b693820 00000000`00000000     : fffff800`7b693a01 00000000`00000020 fffff800`9e753e19 ffffbb86`0a014000 : 0x611c30


SYMBOL_NAME:  nvlddmkm+8f778

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  8f778

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

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键）看下是否恢复正常。若是48小时内没有新的，我将无法再收到提醒。
欢迎访问本站！。可能和英伟达显卡有关。若是有超频，降压等，建议恢复正常，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键）看下是否恢复正常。若是48小时内没有新的，我将无法再收到提醒。
好的，我已按上述进行操作，还有情况出现再请教，谢谢您的帮助！
不客气，期待好消息。若是48小时内没有新的，我将无法再收到提醒。
非常感谢您的帮助，目前一下午电脑未出现蓝屏现象，问题已解决，辛苦了！
不好意思我又来了。刚刚突然卡死，反馈如下：Microsoft(R)WindowsDebuggerVersion10.0.21306.1007AMD64Copyright(c)MicrosoftCorporation.Allrightsreserved.LoadingDumpFile[C:\WINDOWS\Minidump\101222-6234-01.dmp]MiniKernelDumpFile:OnlyregistersandstacktraceareavailableSymbolsearchpathis:srv*Executablesearchpathis:Windows10KernelVersion19041MP(12procs)Freex64Product:WinNt,suite:TerminalServerSingleUserTSPersonalMachineName:Kernelbase=0xfffff802`76a00000PsLoadedModuleList=0xfffff802`7762a270Debugsessiontime:WedOct1219:58:31.4802022(UTC+8:00)SystemUptime:0days5:28:32.328LoadingKernelSymbols.Pressctrl-c(cdb,kd,ntsd)orctrl-break(windbg)toabortsymbolloadsthattaketoolong.Run!symnoisybefore.reloadtotrackdownproblemsloadingsymbols..LoadingUserSymbolsLoadingunloadedmodulelist.Foranalysisofthisfile,run!analyze-vnt!KeBugCheckEx:fffff802`76df90e048894c2408movqwordptr[rsp+8],rcxss:0018:ffffa301`9ddb7e20=00000000000001334:kd>!analyze-v**********************************************************************************BugcheckAnalysis**********************************************************************************DPC_WATCHDOG_VIOLATION(133)TheDPCwatchdogdetectedaprolongedruntimeatanIRQLofDISPATCH_LEVELorabove.Arguments:Arg1:0000000000000001,ThesystemcumulativelyspentanextendedperiodoftimeatDISPATCH_LEVELorabove.Theoffendingcomponentcanusuallybeidentifiedwithastacktrace.Arg2:0000000000001e00,Thewatchdogperiod.Arg3:fffff802776fb320,casttont!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK,whichcontainsadditionalinformationregardingthecumulativetimeoutArg4:0000000000000000DebuggingDetails: