DPC_WATCHDOG_VIOLATION BSOD When Gaming

Question

Hi All,

Blue Screen of Death (BSOD) DPC_WATCHDOG_VIOLATION error code

I'm hoping someone can give me some pointers here on how to fix this error. It only occurs when I play 'intensive games' such as Apex Legends on my PC. It might happen once every 2-3 games. If I use my PC for work it will not crash for weeks on end. I've been trawling the forums and have done a few fixes with no avail.

Attempted Fixes and Notes to Consider

• Uninstalled my Nvidia GeForce Drivers using DDU in Safe Boot Mode
• Run ChkDsk and Repair Disk several times which found nothing
• I have not installed any new hardware since the PC was built
• I have reset windows to default settings
• I have reset my bios and updated it to it's latest version 2022
• I use an ethernet connection my PC does not have wireless connectivity
• Run firmware updates for all of my SSDs (Samsung and Western Digital)
• Looked into Event Viewer without much hope, it just says Error Kernel Power - System unexpectedly crashed or shutdown

I'm hoping someone with knowledge of reading the .dmp files can help me out here. I'm stumped. Onedrive line is pasted below (read only). This was created using

https://1drv.ms/u/s!ApzWwGtwBTf4gZQYYfGRmHwvct1oVg?e=bnHQXU

Thanks in advance,

Mike

Most Recent Dump Pasted Below

DPC_WATCHDOG_VIOLATION (133)
The DPC watchdog detected a prolonged run time at an IRQL of DISPATCH_LEVEL
or above.
Arguments:
Arg1: 0000000000000000, A single DPC or ISR exceeded its time allotment. The offending
component can usually be identified with a stack trace.
Arg2: 0000000000000501, The DPC time count (in ticks).
Arg3: 0000000000000500, The DPC time allotment (in ticks).
Arg4: fffff8073f4fb320, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding this single DPC timeout

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

Key  : Analysis.DebugAnalysisManager  
Value: Create  

Key  : Analysis.Elapsed.mSec  
Value: 2622  

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

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

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

Key  : Bugcheck.Code.DumpHeader  
Value: 0x133  

Key  : Bugcheck.Code.KiBugCheckData  
Value: 0x133  

Key  : Bugcheck.Code.Register  
Value: 0x133  

Key  : WER.OS.Branch  
Value: vb_release  

Key  : WER.OS.Timestamp  
Value: 2019-12-06T14:06:00Z  

Key  : WER.OS.Version  
Value: 10.0.19041.1  

FILE_IN_CAB: MEMORY.DMP

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8073f4fb320

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: fffff109a20479c0 -- (.trap 0xfffff109a20479c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=00000000412a5519 rbx=0000000000000000 rcx=fffff109a2047bb8
rdx=fffff109aa2376e8 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8073ead08ab rsp=fffff109a2047b50 rbp=00000000ffffffff
r8=fffff109aa237500 r9=fffff109aa237510 r10=0000fffff8073eb2
r11=ffff93782da00000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KeYieldProcessorEx+0x1b:
fffff807`3ead08ab 5b pop rbx
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

PROCESS_NAME: firefox.exe

STACK_TEXT:
ffffa380cb393e18 fffff8073ec2a914 : 0000000000000133 0000000000000000 0000000000000501 0000000000000500 : nt!KeBugCheckEx
ffffa380cb393e20 fffff8073ea4b573 : 00034c3a54c9b688 ffffa380cb340180 0000000000000000 ffffa380cb340180 : nt!KeAccumulateTicks+0x1dcb44
ffffa380cb393e80 fffff8073ea4b05a : ffff900388eb50e0 fffff109a2047a40 fffff80740c07900 0000000100006001 : nt!KeClockInterruptNotify+0x453
ffffa380cb393f30 fffff8073ead9405 : ffff900388eb50e0 ffffa380cb393f40 0000000000000010 ffff4a6fa4585102 : nt!HalpTimerClockIpiRoutine+0x1a
ffffa380cb393f60 fffff8073ebfa36a : fffff109a2047a40 ffff900388eb50e0 00034c27b0d431a0 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffa380cb393fb0 fffff8073ebfa8d7 : 0000000080000000 fffff8073ebfa8e4 0000000041205405 fffff109a2047bb8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff109a20479c0 fffff8073ead08ab : 0000000080000000 fffff8073eb2f249 ffff90038a2d6410 00000000000002d0 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff109a2047b50 fffff8073eb2f249 : ffff90038a2d6410 00000000000002d0 0000000000000f44 0000000000400a02 : nt!KeYieldProcessorEx+0x1b
fffff109a2047b60 fffff8073ea67f9e : ffffa380cb343240 ffff9003412a5519 ffffa380cb340180 fffff10900000002 : nt!ExpGetPoolTagInfoTarget+0x149
fffff109a2047bb0 fffff8073ea67284 : ffffa380cb340180 0000000000000000 0000000000000002 0000000000000004 : nt!KiExecuteAllDpcs+0x30e
fffff109a2047d20 fffff8073ebff935 : 0000000000000000 ffffa380cb340180 0000000000000000 000000afda3e9d18 : nt!KiRetireDpcList+0x1f4
fffff109a2047fb0 fffff8073ebff720 : ffff900300000000 ffff9003ab5de080 3fffffff00001901 fffff8073ebfefd5 : nt!KxRetireDpcList+0x5
fffff109ae367a90 fffff8073ebfedee : 00000000000019c8 ffff9003ab5de080 0000000000000000 ffff9003aa51a310 : nt!KiDispatchInterruptContinue
fffff109ae367ac0 00007ff8faf6541c : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiDpcInterrupt+0x2ee
000000afda3e9cc0 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff8`faf6541c

SYMBOL_NAME: nt!KeAccumulateTicks+1dcb44

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 1dcb44

FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks

OS_VERSION: 10.0.19041.1

BUILDLAB_STR: vb_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f}

Followup: MachineOwner

Answer 1

Try uninstalling the Firefox and restart your PC and see if the problem persists?
Open start and search for feedback and open the Feedback Hub app and report this issue and attach dump files there.

Answer 2

Please run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.

Answer 3

Hi @Reza-Ameri

Been testing this but the issue seems to still persist. I rolled back my GPU drivers after a using the DDU tool and it seemed to resolve for about a week. It has now started re-occuring sadly. I have some older PC hardware (HDD and RAM) that may be finally interfering?

Guess I'll need to keep testing