How to fix DPC Watchdog Violation Error

Question

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: 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: fffff8061bafb320, 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: 4421

    Key  : Analysis.Elapsed.mSec
    Value: 8918

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

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

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

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

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

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

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_DPC_mouclass!MouseClassServiceCallback

    Key  : Failure.Hash
    Value: {3fa01bd8-d2f7-df82-2794-89aa20021973}

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Version
    Value: 10.0.19041.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff8061bafb320

FILE_IN_CAB:  042024-13000-01.dmp

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8061ea73870 -- (.trap 0xfffff8061ea73870)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000004 rbx=0000000000000000 rcx=0000000000000001
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8061b319e32 rsp=fffff8061ea73a08 rbp=fffff8061ea73a79
 r8=0000000000000020  r9=0000000000000010 r10=0000000000000004
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe nc
nt!KiFindBiasedProcessorIndex+0x76:
fffff806`1b319e32 490fbcc0        bsf     rax,r8
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
fffff806`1ea82e18 fffff806`1b234e70     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff806`1ea82e20 fffff806`1b04b543     : 000006fe`8c189914 fffff806`16d32180 00000000`00000000 fffff806`16d32180 : nt!KeAccumulateTicks+0x1e70b0
fffff806`1ea82e80 fffff806`1b04b02a     : fffff806`1baf39c0 fffff806`1ea738f0 fffff806`1de57900 00000000`0000b301 : nt!KeClockInterruptNotify+0x453
fffff806`1ea82f30 fffff806`1b112d45     : fffff806`1baf39c0 fffff806`1ea82f40 00000000`00000010 ffff4ed8`70c2cf2d : nt!HalpTimerClockIpiRoutine+0x1a
fffff806`1ea82f60 fffff806`1b1ffa7a     : fffff806`1ea738f0 fffff806`1baf39c0 ffffbd01`458af180 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
fffff806`1ea82fb0 fffff806`1b2002a7     : fffff806`16d32180 fffff806`1b2002b4 00000000`00000035 fffff806`1ea73a64 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff806`1ea73870 fffff806`1b319e32     : fffff806`1b320ad6 ffff9781`4ce88000 00000000`00000020 fffff806`1d3b2160 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff806`1ea73a08 fffff806`1b320ad6     : ffff9781`4ce88000 00000000`00000020 fffff806`1d3b2160 fffff806`261080b7 : nt!KiFindBiasedProcessorIndex+0x76
fffff806`1ea73a10 fffff806`1b22cdbc     : fffff806`16d32180 ffff9781`480cf000 00000000`00000004 fffff806`1ea73b1c : nt!KiHeteroChooseTargetProcessor+0x426
fffff806`1ea73ae0 fffff806`1b035e91     : 00000000`00000000 00000000`00000000 00000000`00000000 ffff9781`483b7a98 : nt!KiDeferredReadySingleThread+0x1f6c6c
fffff806`1ea73cd0 fffff806`1b055c24     : 00000000`00000000 fffff806`1ea73db9 ffff9781`497a4001 fffff806`17d5129b : nt!KiExitDispatcher+0x141
fffff806`1ea73d40 fffff806`1b054c67     : ffff9781`4e7328b0 fffff806`1ea73e06 00000000`00000000 00000000`00000000 : nt!IopfCompleteRequest+0xfa4
fffff806`1ea73e20 fffff806`26495056     : 00000000`00000018 fffff806`1ea73ec0 ffff9781`4e7328b0 ffff9781`46fd4ef8 : nt!IofCompleteRequest+0x17
fffff806`1ea73e50 fffff806`23daebc6     : 00000000`00000002 fffff806`23d80000 00000000`00000000 fffff806`1ea74044 : mouclass!MouseClassServiceCallback+0x476
fffff806`1ea73ef0 00000000`00000002     : fffff806`23d80000 00000000`00000000 fffff806`1ea74044 00000000`00000000 : vgk+0x2ebc6
fffff806`1ea73ef8 fffff806`23d80000     : 00000000`00000000 fffff806`1ea74044 00000000`00000000 fffff806`00000000 : 0x2
fffff806`1ea73f00 00000000`00000000     : fffff806`1ea74044 00000000`00000000 fffff806`00000000 fffff806`1b03ad30 : vgk


SYMBOL_NAME:  mouclass!MouseClassServiceCallback+476

MODULE_NAME: mouclass

IMAGE_NAME:  mouclass.sys

IMAGE_VERSION:  10.0.19041.1030

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  476

FAILURE_BUCKET_ID:  0x133_DPC_mouclass!MouseClassServiceCallback

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {3fa01bd8-d2f7-df82-2794-89aa20021973}

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

This is not the only Error Code I got the past days and when I search them it always says one of my drivers is not up to date or something but I dont know which of my 1000000 drivers.

please help

Answer 1

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

BSOD - Posting Instructions - Windows 10 Forums (tenforums.com)

BSOD - Posting Instructions | Windows 11 Forum (elevenforum.com)

Make sure that links are available without sign in.

Answer 2

Hello

According to the dump result, the "vgk" is the most suspicious part.

According to my research, it could be related to riot games.

"vgk.sys marking points at Vanguard, which is an anti-cheat system for Riot games."

We could run "lmvm vgk" to check more information of this component. There should be path for this component, then check the property of this compont.

If it is a part of the game component, we could try to update or uninstall the game.

I hope the following link may be useful.

Vgk.sys Blue Screen When Playing Valorant [Fix] (windowsreport.com)

Of course, we may consider ask for help from the game support if the issue is related to the game.