一个watch dog 的蓝屏，与nvlddmkm文件有关，求解决方案

Question

一个watch dog 的蓝屏，与nvlddmkm文件有关，求解决方案

匿名

以下是dump文件： ************* Preparing the environment for Debugger Extensions Gallery repositories ************** ExtensionRepository : Implicit UseExperimentalFeatureForNugetShare : false AllowNugetExeUpdate : false AllowNugetMSCredentialProviderInstall : false AllowParallelInitializationOfLocalRepositories : true

   -- Configuring repositories
      ----> Repository : LocalInstalled, Enabled: true
      ----> Repository : UserExtensions, Enabled: true

>>>>>>>>>>>>> Preparing the environment for Debugger Extensions Gallery repositories completed, duration 0.000 seconds

************* Waiting for Debugger Extensions Gallery to Initialize **************

>>>>>>>>>>>>> Waiting for Debugger Extensions Gallery to Initialize completed, duration 0.015 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 36

Microsoft (R) Windows Debugger Version 10.0.25877.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\Minidump\020824-14078-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
Symbol search path is: srv*
Executable search path is: 
Windows 10 Kernel Version 22621 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Kernel base = 0xfffff805`7a800000 PsLoadedModuleList = 0xfffff805`7b4134a0
Debug session time: Thu Feb  8 01:04:41.401 2024 (UTC + 8:00)
System Uptime: 0 days 0:41:23.076
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.............................
Loading User Symbols

Loading unloaded module list
..............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`7ac16b00 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff805`7ee90c90=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: fffff8057b51d340, 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                                   ***
***                                                                   ***
*************************************************************************

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 406

    Key  : Analysis.Elapsed.mSec
    Value: 5229

    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: 93

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

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

    Key  : Bugcheck.Code.LegacyAPI
    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

    Key  : Failure.Bucket
    Value: 0x133_ISR_nvlddmkm!unknown_function

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

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8057b51d340

BUGCHECK_P4: 0

FILE_IN_CAB:  020824-14078-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

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:  
fffff805`7ee90c88 fffff805`7aa12bb9     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`7b51d340 : nt!KeBugCheckEx
fffff805`7ee90c90 fffff805`7aa12421     : 00000617`339c102f 00000000`00026cc4 00000000`00026cc3 00000000`00000000 : nt!KeAccumulateTicks+0x239
fffff805`7ee90cf0 fffff805`7aa104b1     : 00000000`00000000 ffffcb00`8b3e4500 fffff805`77b89180 00000000`00000000 : nt!KiUpdateRunTime+0xd1
fffff805`7ee90ea0 fffff805`7aa0feda     : fffff805`7b460070 ffffcb00`8b3e45b0 ffffcb00`8b3e45b0 00000000`00000002 : nt!KeClockInterruptNotify+0xc1
fffff805`7ee90f40 fffff805`7ab24b2c     : 00000005`c81f5537 fffff805`7b50d5b0 fffff805`7b50d660 00000000`ffffffff : nt!HalpTimerClockInterrupt+0x10a
fffff805`7ee90f70 fffff805`7ac18cba     : fffff805`7ee80aa0 fffff805`7b50d5b0 ffff9686`0396fbe8 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
fffff805`7ee90fb0 fffff805`7ac19567     : 00000000`0010000b ffff6fd4`00000001 00000000`00000003 00000000`00000001 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff805`7ee80a20 fffff805`a17997ac     : 00000000`00000000 00000000`00b8101c ffff9686`0396f000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff805`7ee80bb0 00000000`00000000     : 00000000`00b8101c ffff9686`0396f000 00000000`00000000 00000000`00000020 : nvlddmkm+0x997ac

SYMBOL_NAME:  nvlddmkm+997ac

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  997ac

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

0: kd> lmvm nvlddmkm
Browse full module list
start             end                 module name
fffff805`a1700000 fffff805`a5019000   nvlddmkm T (no symbols)           
    Loaded symbol image file: nvlddmkm.sys
    Image path: nvlddmkm.sys
    Image name: nvlddmkm.sys
    Browse all global symbols  functions  data
    Timestamp:        Fri Nov 10 05:35:30 2023 (654D50A2)
    CheckSum:         03804E98
    ImageSize:        03919000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
    Information from resource tables:
0: kd> lmDv
start             end                 module name

锁定的问题。此问题已从 Microsoft 支持社区迁移。你可投票决定它是否有用，但不能添加评论或回复，也不能关注问题。为了保护隐私，对于已迁移的问题，用户个人资料是匿名的。

1 个答案

Answer 1

Hello

Thank you for posting in Microsoft Community forum.

It seems like you're encountering a DPC_WATCHDOG_VIOLATION error with the bugcheck code 133, and the analysis indicates involvement of the nvlddmkm.sys driver, which is typically associated with NVIDIA graphics cards.

Here are some steps you can take to troubleshoot and potentially resolve this issue:

Update Graphics Drivers: Ensure that your graphics card drivers are up to date. You can download the latest drivers from the NVIDIA website.

Rollback Graphics Drivers: If you've recently updated your graphics drivers and started experiencing this issue, try rolling back to a previous version of the drivers to see if the problem resolves.

Check for Overheating: Overheating can sometimes cause issues with graphics cards. Make sure your GPU isn't overheating by checking its temperature using software like MSI Afterburner or HWMonitor.

Check for Hardware Issues: If you suspect hardware issues with your GPU, consider running diagnostic tests or stress tests to check for any problems.

Check for Windows Updates: Ensure that your Windows operating system is up to date by installing any available updates.

Check for System File Corruption: Run the System File Checker (SFC) tool to scan for and repair any corrupted system files. Open Command Prompt as an administrator and run the command sfc /scannow.

Check for Memory Issues: Memory problems can sometimes cause system crashes. Use Windows Memory Diagnostic or Memtest86 to check for any memory errors.

Disable Overclocking: If you've overclocked your GPU or CPU, try reverting to default clock speeds to see if the problem persists.

Check for Conflicting Software: Sometimes third-party software or drivers can conflict with system processes. Try booting into Safe Mode and see if the issue persists. If it doesn't, it could indicate a software conflict.

Perform a Clean Boot: Perform a clean boot to start Windows with minimal drivers and startup programs. This can help identify if a third-party application is causing the issue.

Contact NVIDIA Support: If you're unable to resolve the issue on your own, consider reaching out to NVIDIA support for further assistance.

If none of these steps resolve the issue, the issue may be more complex, please consider purchasing a Microsoft ticket for online support:

Contact Us - Microsoft Support

Best Regards,

Wesley Li

通过

一个watch dog 的蓝屏，与nvlddmkm文件有关，求解决方案

1 个答案