How to fix DPC_WATCHDOG_VIOLATION (133)

Question

How to fix DPC_WATCHDOG_VIOLATION (133)

Dmitrii 0

************ Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*
OK                                             C:\Windows\Minidump

************* Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       srv*

************* Preparing the environment for Debugger Extensions Gallery repositories **************
   ExtensionRepository : Implicit
   UseExperimentalFeatureForNugetShare : true
   AllowNugetExeUpdate : true
   NonInteractiveNuget : true
   AllowNugetMSCredentialProviderInstall : true
   AllowParallelInitializationOfLocalRepositories : true
   EnableRedirectToChakraJsProvider : false

   -- 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.016 seconds
   ----> Repository : UserExtensions, Enabled: true, Packages count: 0
   ----> Repository : LocalInstalled, Enabled: true, Packages count: 46

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


Loading Dump File [C:\Windows\Minidump\033126-14578-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 26100 MP (24 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Kernel base = 0xfffff802`d4400000 PsLoadedModuleList = 0xfffff802`d52f50c0
Debug session time: Tue Mar 31 00:57:32.700 2026 (UTC + 7:00)
System Uptime: 1 days 12:35:13.516
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:
fffff802`d48fb990 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:fffff802`670959a0=0000000000000133
0: 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: fffff802d53c43b8, 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: 953

    Key  : Analysis.Elapsed.mSec
    Value: 7833

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29547.1002

    Key  : Analysis.Version.Description
    Value: 10.2602.27.2 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2602.27.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 0x21808

    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  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.System.BIOSRevision
    Value: 1.32.0.0


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff802d53c43b8

BUGCHECK_P4: 0

FILE_IN_CAB:  033126-14578-01.dmp

DUMP_FILE_ATTRIBUTES: 0x21808
  Kernel Generated Triage Dump

FAULTING_THREAD:  fffff802d53d15c0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff802`67095998 fffff802`d469c95c     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff802`d53c43b8 : nt!KeBugCheckEx
fffff802`670959a0 fffff802`d469be8b     : 00000000`00000000 00000000`0080a060 00000000`00000000 fffff802`60bfe180 : nt!KeAccumulateTicks+0x59c
fffff802`67095a10 fffff802`d469bb40     : 00000000`00000018 ffff9981`c8602300 00000000`0080a061 fffff802`67095cd0 : nt!KiUpdateRunTime+0x9b
fffff802`67095bd0 fffff802`d473a86a     : 00000000`00000000 fffff802`d53212f0 fffff802`60bfe180 00000000`00000000 : nt!KiUpdateTime+0x380
fffff802`67095e40 fffff802`d473b3cc     : fffff802`d5210e00 fffff802`d5210eb0 fffff802`d538eeb0 fffff802`00000000 : nt!KeClockInterruptNotify+0x28a
fffff802`67095f40 fffff802`d4aace3e     : 00000000`00400702 fffff802`d5210e00 0000a192`1e96b11c 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x32c
fffff802`67095fb0 fffff802`d4aad64c     : ffffb10f`788a4710 fffff802`67084d40 00000000`00000018 fffff802`83004571 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff802`67084bb0 fffff802`823977a3     : 00000000`00000000 00000000`00400714 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff802`67084d40 00000000`00000000     : 00000000`00400714 00000000`00000000 00000000`00000000 ffffb10f`6ad25000 : nvlddmkm+0xe77a3


SYMBOL_NAME:  nvlddmkm+e77a3

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xfffff802d53cef00; .thread /r /p 0xfffff802d53d15c0 ; kb

BUCKET_ID_FUNC_OFFSET:  e77a3

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 comments

2 answers

Your answer

Answer 1

DaveM121 863K Independent Advisor

Your minidump file data indicates that it is the device driver on your Nvidia graphics card that is causing the system to crash

Completely remove the current Nvidia device driver using the widely available free DDU utility, then restart your PC and go to the Nvidia website to download and install a couple of slightly older versions of the Nvidia device driver to try to find a version that is stable on your system.

Dmitrii 0 Reputation points

2026-04-02T04:56:02.6133333+00:00

Hello, i tried change many driver versions and i deleted previous drivers by DDU. This problem may not bother me for a week, or it may appear 2-3 times a day
Dmitrii 0 Reputation points

2026-04-02T04:57:05.37+00:00

But i deleted drivers with DDU utility not in safe mode
DaveM121 863K Reputation points Independent Advisor

2026-04-02T05:15:10.9366667+00:00

If your system continues to crash after performing those steps, please upload any new minidump files you may get for analysis.

Answer 2

The dump shows bug check 0x133 DPC_WATCHDOG_VIOLATION with parameter 1 = 1 and the NVIDIA display driver nvlddmkm.sys on the ISR stack, which matches the documented pattern of a driver spending too long at DISPATCH_LEVEL or above.

For parameter 1 = 1, the system has cumulatively spent an extended period of time at IRQL DISPATCH_LEVEL or above. This is typically caused by faulty or misbehaving driver code whose DPC/ISR routines exceed the watchdog timeout.

Recommended steps based on the documentation:

Treat this as a driver issue
- The stack and Failure.Bucket (0x133_ISR_nvlddmkm!unknown_function) indicate the NVIDIA GPU driver is the likely offender.
- In general, bug check 0x133 is caused by faulty driver code that does not complete its work within the allotted time frame.
Update or roll back the NVIDIA driver
- Check for an updated NVIDIA graphics driver that is compatible with the current Windows 10 build and install it.
- If the problem started after a recent driver update, roll back to a previous stable NVIDIA driver version.
Use basic troubleshooting if not doing kernel debugging
- If a driver is identified in the bug check (here, nvlddmkm.sys), disable or uninstall that driver to test stability, then reinstall a known-good or updated version from the manufacturer.
- Check the System log in Event Viewer for additional error messages around the time of the crash that reference the display driver or GPU.
Check hardware and compatibility
- Confirm that the GPU and any other recently added hardware are compatible with the installed Windows 10 version.
- If the issue persists even with a clean, current NVIDIA driver, test the GPU (and related hardware like PCIe slot, PSU) to rule out faulty hardware.
Advanced debugging (optional, for developers)
- For parameter 1 = 1, the code may not stop directly in the offending area. The documented approach is:
  - Use !analyze -v (already done) to display bug check information.
  - Cast Arg3 (nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK) to inspect cumulative timeout details.
  - Use !dpcs to display queued DPCs and identify which driver’s DPCs are running too long.
- To create a code fix, programming experience and access to the source code of the faulting module are required.

If the crashes continue after updating/rolling back the NVIDIA driver and verifying hardware, follow the general blue-screen troubleshooting guidance referenced in the documentation (driver isolation, hardware checks, and, if needed, engaging the device or system vendor).

References:

Share via

How to fix DPC_WATCHDOG_VIOLATION (133)

2 answers

Your answer