BSOD:DPC_WATCHDOG VIOLATION blue screen

Question

BSOD:DPC_WATCHDOG VIOLATION blue screen

SonofBear 0

i have been getting alot of random BSOD with same error
DPC_WATCHDOG VIOLATION blue screen

here is what i got from the latest minidump
can anyone help ?
some say is SSD issue and some say is GPU

ExtensionGallery settings after reading 'SOFTWARE\Microsoft\Debug Engine' registry:
ExtensionGallery ExtensionRepository: Implicit

************* 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.015 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\Minidumps\050626-8843-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 = 0xfffff805`e1000000 PsLoadedModuleList = 0xfffff805`e1ef5150
Debug session time: Wed May  6 13:06:21.855 2026 (UTC + 8:00)
System Uptime: 0 days 1:10:14.484
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000056`1f374018).  Type ".hh dbgerr001" for details
Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff805`e14fa330 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffff8081`d9b659a0=0000000000000133
1: kd> !analyze -v
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................
Loading User Symbols
PEB is paged out (Peb.Ldr = 00000056`1f374018).  Type ".hh dbgerr001" for details
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: fffff805e1fc43c8, 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: 1437

    Key  : Analysis.Elapsed.mSec
    Value: 5796

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

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

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

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

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

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

    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: 0x20008

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Failure.Bucket
    Value: 0x133_ISR_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff805e1fc43c8

BUGCHECK_P4: 0

FILE_IN_CAB:  050626-8843-01.dmp

DUMP_FILE_ATTRIBUTES: 0x20008
  Kernel Generated Triage Dump

FAULTING_THREAD:  ffffb706fd4f1080

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  Discord.exe

STACK_TEXT:  
ffff8081`d9b65998 fffff805`e129da8c     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff805`e1fc43c8 : nt!KeBugCheckEx
ffff8081`d9b659a0 fffff805`e129cfbb     : 00000000`00000000 00000000`00041d9e 00000000`00000000 ffff8081`d9b49180 : nt!KeAccumulateTicks+0x59c
ffff8081`d9b65a10 fffff805`e129cc70     : 00000000`00000018 ffff8081`d9002300 00000000`00041d9f ffff8081`d9b65cd0 : nt!KiUpdateRunTime+0x9b
ffff8081`d9b65bd0 fffff805`e12eb79a     : 00000000`00000000 fffff805`e1f214b8 ffff8081`d9b49180 00000000`00000000 : nt!KiUpdateTime+0x380
ffff8081`d9b65e40 fffff805`e12ec2fc     : ffffb706`db73d5a0 ffffb706`db73d650 fffff805`e1f8ec70 ffff8081`d9b49101 : nt!KeClockInterruptNotify+0x28a
ffff8081`d9b65f40 fffff805`e16ac46e     : 00000000`78cc860c ffffb706`db73d5a0 00000dd2`4a043ad3 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x32c
ffff8081`d9b65fb0 fffff805`e16acc7c     : 00000009`d0497e5c fffff30d`ae866e50 00000009`d0497e68 00000e2f`0a38b250 : nt!KiInterruptSubDispatchNoLockNoEtw+0x4e
fffff30d`ae866dd0 fffff805`e13b1032     : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x3c
fffff30d`ae866f60 fffff805`e13b0f9b     : fffff30d`ae867201 00000000`00000000 fffff30d`ae867201 fffff30d`ae8675a0 : nt!KiIpiStallOnPacketTargetsPrcb+0x32
fffff30d`ae866f90 fffff805`e1a188e5     : fffff30d`ae867208 fffff30d`ae867b20 ffffb706`fd4f1080 ffffb706`fca3a080 : nt!KeFlushProcessWriteBuffers+0x10f
fffff30d`ae866ff0 fffff805`e19a9653     : ffffb706`fca3a080 00000056`1fbfd110 ffffb706`db69c4c0 fffff30d`ae867401 : nt!PsQueryTotalCycleTimeProcess+0x25
fffff30d`ae867020 fffff805`e16bd958     : ffffb706`fd4f1080 00000000`00000000 fffff30d`ae867b20 00000000`00000000 : nt!NtQueryInformationProcess+0x2393
fffff30d`ae867a30 00007ffa`136a1e24     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x28
00000056`1fbfd0d8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`136a1e24


SYMBOL_NAME:  nt!KeAccumulateTicks+59c

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.26100.8246

STACK_COMMAND: .process /r /p 0xffffb706fca3a080; .thread /r /p 0xffffb706fd4f1080 ; kb

BUCKET_ID_FUNC_OFFSET:  59c

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

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

0 comments

2 answers

Your answer

Answer 1

DaveM121 (2) 13,715 Volunteer Moderator

Please upload any minidump files you have, I will check those to see if they provide any insight into a potential cause of the system crashes.

Please do not upload a very large Memory.dmp file.

Open Windows File Explorer.

Navigate to C:\Windows\Minidump

Copy any minidump files onto your Desktop, then zip those up.

Upload the zip file to the Cloud (OneDrive... etc.), then choose to share those and get a share link.

Then post the link here to the zip file, so I can take a look for you.

0 comments

Answer 2

The dump shows bug check 0x133 DPC_WATCHDOG_VIOLATION with:

Arg1 = 1 → the system cumulatively spent too long at IRQL DISPATCH_LEVEL or above.
Failure bucket: 0x133_ISR_nt!KeAccumulateTicks → the watchdog fired while handling timer/clock interrupts, but the dump does not directly identify a specific third‑party driver.

From the documentation, this stop code is almost always caused by faulty or misbehaving kernel‑mode driver code (including storage, GPU, or other device drivers) that runs too long in a DPC or ISR, or by hardware/firmware that causes such drivers to misbehave. The parameters in your dump match the documented “cumulative time at DISPATCH_LEVEL” case.

Because the dump does not clearly name a third‑party module, use the standard troubleshooting path for 0x133:

Check for a named driver in other dumps
- Open other minidumps in WinDbg and run !analyze -v.
- If any bugcheck 0x133 reports a specific driver in the stack (for example, a storage, network, or GPU driver), that driver is the primary suspect.
Update or roll back device drivers
- Update storage (SATA/NVMe), GPU, chipset, and network drivers from the system or component manufacturer.
- If the BSODs started after a specific driver update, roll that driver back to the previous stable version.
Check Event Viewer for correlation
- Open Event Viewer → Windows Logs → System.
- Look for critical or error events around the time of each 0x133 crash that mention a specific device or driver. That device/driver is a candidate for causing long‑running DPC/ISR activity.
Verify hardware compatibility and firmware
- Confirm that any recently added hardware (SSD, GPU, etc.) is supported on the installed Windows version.
- Update system BIOS/UEFI and device firmware (especially SSD and GPU) from the OEM if newer stable versions are available.
If no debugger expertise is available
- The official guidance for non‑debugger users is to:
  - Disable or uninstall any driver explicitly named in the bugcheck (if any appear in other dumps).
  - Keep Windows fully updated.
  - Remove or disconnect recently added hardware to see if the BSODs stop.

If, after driver updates and hardware checks, 0x133 persists, deeper WinDbg work is needed (examining queued DPCs, the nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, and driver stacks) to pinpoint the exact offending driver.

References:

Bug Check 0x133: DPC_WATCHDOG_VIOLATION

Share via

BSOD:DPC_WATCHDOG VIOLATION blue screen

2 answers

Your answer