如何解决我的 windows PC 上的 nvlddmkm.sys BSOD DPC_WATCHDOG_VIOLATION?

Question

电脑经常无故界面凝固不动，不响应任何指令，接着蓝屏显示DPC_WATCHDOG_VIOLATION后重启

这可能发生在任何时候，包括高负载运行和平时看视频时

分析dmp文件后检查到是nvlddmkm.sys的原因，我应该怎么做才能避免蓝屏

6: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
................................................................
..
Loading User Symbols

Loading unloaded module list
.................
*******************************************************************************
*                                                                             *
*                        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: fffff8020d11c340, 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: Check Image - Checksum mismatch - Dump: 0x201482, File: 0x201504 - C:\ProgramData\Dbg\sym\BTHport.sys\9BFC3B54202000\BTHport.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 593

    Key  : Analysis.Elapsed.mSec
    Value: 11754

    Key  : Analysis.IO.Other.Mb
    Value: 6

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 26

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 0x1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x133_ISR_nvlddmkm!unknown_function

    Key  : Failure.Hash
    Value: {f97493a5-ea2b-23ca-a808-8602773c2a86}

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8020d11c340

BUGCHECK_P4: 0

FILE_IN_CAB:  072825-12515-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffe389c2365040

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:  
ffffa781`36fbac88 fffff802`0c637a19     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`0d11c340 : nt!KeBugCheckEx
ffffa781`36fbac90 fffff802`0c637281     : 000021db`2576b8ab 00000000`000f0543 00000000`000f0542 00000000`00000000 : nt!KeAccumulateTicks+0x239
ffffa781`36fbacf0 fffff802`0c635311     : 00000000`00000000 ffffa781`387d6d00 ffffa781`36fa0180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
ffffa781`36fbaea0 fffff802`0c634d3a     : fffff802`0d05fe40 ffffa781`387d6d30 ffffa781`387d6d30 00000000`00000002 : nt!KeClockInterruptNotify+0xc1
ffffa781`36fbaf40 fffff802`0c715f8c     : 00000023`cfea7841 ffffe389`c237c380 ffffe389`c237c430 00000000`02149cb0 : nt!HalpTimerClockInterrupt+0x10a
ffffa781`36fbaf70 fffff802`0c81711a     : ffffba8b`576beb00 ffffe389`c237c380 ffffe389`d1ac3dd8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
ffffa781`36fbafb0 fffff802`0c8179e7     : 00000000`00000002 fffff802`3adf0f12 00000000`00000000 ffff1fe6`9a88c8a2 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffba8b`576bea80 fffff802`3a19fb83     : 00000000`00000001 ffffe389`d1ac3000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffba8b`576bec10 00000000`00000001     : ffffe389`d1ac3000 00000000`00000000 00000000`00000000 00000000`00b81000 : nvlddmkm+0xdfb83
ffffba8b`576bec18 ffffe389`d1ac3000     : 00000000`00000000 00000000`00000000 00000000`00b81000 ffff1fe6`9a88ced2 : 0x1
ffffba8b`576bec20 00000000`00000000     : 00000000`00000000 00000000`00b81000 ffff1fe6`9a88ced2 00000000`00b81014 : 0xffffe389`d1ac3000


SYMBOL_NAME:  nvlddmkm+dfb83

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xfffff8020d148f40; .thread 0xffffe389c2365040 ; kb

BUCKET_ID_FUNC_OFFSET:  dfb83

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {f97493a5-ea2b-23ca-a808-8602773c2a86}

Followup:     MachineOwner
---------

其余蓝屏dmp文件：

通过网盘分享的文件：BSOD

链接: https://pan.baidu.com/s/1ssiWtLHtYVRB-IPNLuzafw?pwd=wh39 提取码: wh39

Answer 1

你好！您遇到了由 nvlddmkm.sys 触发的 DPC_WATCHDOG_VIOLATION （0x133） BSOD，即 NVIDIA 图形驱动程序。

请尝试全新安装驱动程序：

1. 在安全模式下使用显示驱动程序卸载程序 （DDU） 完全卸载 GPU 驱动程序。
2. 重新启动并安装来自 NVIDIA 官方网站的最新 NVIDIA 驱动程序。
3. 在安装过程中，如果您不使用 HDMI 音频，请选择自定义（高级）并取消选中 NVIDIA 音频驱动程序 （nvhda64v.sys），因为它可能与 Realtek 音频驱动程序冲突

如果最新的驱动程序有问题，请尝试恢复到稍旧但稳定的版本。