How to fix DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED on my PC? My PC often freezes when I'm playing games.

Question

I used Windbg to run the Kernel minidump file, and this is the analysis:

*******************************************************************************
*                                                                             *
*                        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: fffff8070f71c340, 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: 1390

    Key  : Analysis.Elapsed.mSec
    Value: 1377

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27871.1001

    Key  : Analysis.Version.Description
    Value: 10.2505.01.02 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2505.1.2

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Failure.Bucket
    Value: 0x133_ISR_nvlddmkm!unknown_function

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

    Key  : Stack.Pointer
    Value: ISR

    Key  : WER.OS.Branch
    Value: ni_release

    Key  : WER.OS.Version
    Value: 10.0.22621.1


BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8070f71c340

BUGCHECK_P4: 0

FILE_IN_CAB:  010625-6515-01.dmp

FAULTING_THREAD:  ffff9908fd0b6080

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME:  fffff8070bcb0e40 -- (.trap 0xfffff8070bcb0e40)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=0000000000000002
rdx=0000000000000002 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8070ec1c99b rsp=fffff8070bcb0fd0 rbp=fffff8070bcb1130
 r8=0000000000000000  r9=fffff80738c8cfc0 r10=fffff80738c8cfb8
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl zr na po nc
nt!KzLowerIrql+0x1b:
fffff807`0ec1c99b 4883c420        add     rsp,20h
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  WmiPrvSE.exe

STACK_TEXT:  
fffff807`0bcb99e8 fffff807`0ec37a19     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff807`0f71c340 : nt!KeBugCheckEx
fffff807`0bcb99f0 fffff807`0ec37281     : 000000a8`33adc12a 00000000`00002755 00000000`00002754 00000000`00000000 : nt!KeAccumulateTicks+0x239
fffff807`0bcb9a50 fffff807`0ec3488f     : 00000000`0000000c 00000000`00001388 00000000`00002700 00000000`00001771 : nt!KiUpdateRunTime+0xd1
fffff807`0bcb9c00 fffff807`0ec35478     : 00000000`00000000 ffffe601`6dfaf600 fffff807`0a22f180 00000000`00000000 : nt!KiUpdateTime+0x63f
fffff807`0bcb9ea0 fffff807`0ec34d3a     : fffff807`0f65ff00 ffffe601`6dfaf6f0 ffffe601`6dfaf6f0 00000000`00000002 : nt!KeClockInterruptNotify+0x228
fffff807`0bcb9f40 fffff807`0ed15f8c     : 00000000`5e0db085 fffff807`0f70d430 fffff807`0f70d4e0 fffff807`0ee16ebb : nt!HalpTimerClockInterrupt+0x10a
fffff807`0bcb9f70 fffff807`0ee1711a     : fffff807`0bcb0ec0 fffff807`0f70d430 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0x9c
fffff807`0bcb9fb0 fffff807`0ee179e7     : 00000000`00000004 00000000`00000003 00000000`00000002 fffff807`0bcb25a8 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff807`0bcb0e40 fffff807`0ec1c99b     : fffff807`0bcb2580 00000000`00000000 fffff807`0bcb1130 fffff807`0ec8df41 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff807`0bcb0fd0 fffff807`37ba5c53     : 00000000`00000001 fffff807`0bcb2580 00000000`00000000 ffff0cb5`3ca296c2 : nt!KzLowerIrql+0x1b
fffff807`0bcb1000 00000000`00000001     : fffff807`0bcb2580 00000000`00000000 ffff0cb5`3ca296c2 00000000`00000001 : nvlddmkm+0xe5c53
fffff807`0bcb1008 fffff807`0bcb2580     : 00000000`00000000 ffff0cb5`3ca296c2 00000000`00000001 fffff807`37b8de0e : 0x1
fffff807`0bcb1010 00000000`00000000     : ffff0cb5`3ca296c2 00000000`00000001 fffff807`37b8de0e ffff9908`f9829000 : 0xfffff807`0bcb2580


SYMBOL_NAME:  nvlddmkm+e5c53

MODULE_NAME: nvlddmkm

IMAGE_NAME:  nvlddmkm.sys

STACK_COMMAND: .process /r /p 0xffff9908fd0a9080; .thread 0xffff9908fd0b6080 ; kb

BUCKET_ID_FUNC_OFFSET:  e5c53

FAILURE_BUCKET_ID:  0x133_ISR_nvlddmkm!unknown_function

OS_VERSION:  10.0.22621.1

BUILDLAB_STR:  ni_release

I don't have much programming skills, can anyone tell me what's wrong?

Answer 1

Hi,

I'm Sumit, here to help with your query on the Microsoft Q&A forums.

Apologies for any inconvenience you are experiencing. I am happy to help you today.

We need log files(called dump files) that tell us what lead to crash.

Please share them with us for a better analysis of the problem. Instructions can be found here:

https://learn.microsoft.com/en-us/answers/questions/2338401/article-how-to-post-blue-screen-of-death-dumps-on

To share files here, please see:

How to share diagnostic files/logs on Microsoft community

https://learn.microsoft.com/en-us/answers/questions/2338402/article-how-to-share-diagnostic-files-logs-on-micr

I look forward to your response and am eager to collaborate until we find a solution.