打游戏超过1分钟就蓝屏dcp_watchdog_violation

      https://pan.baidu.com/s/1R4KF-71eDGHqsaRZWH-Vdg?pwd=7pt71: 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: fffff80419cfb320, 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: 3046

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 17598

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

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

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

    Key  : Bugcheck.Code.DumpHeader
    Value: 0x133

    Key  : Bugcheck.Code.Register
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 8

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1


FILE_IN_CAB:  092722-9109-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80419cfb320

DPC_TIMEOUT_TYPE:  SINGLE_DPC_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT: 
ffffd500`b9700e18 fffff804`194596fe     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffd500`b9700e20 fffff804`192d2973     : 00000148`0a4adefe ffffd500`b95b9180 00000000`00000000 ffffd500`b95b9180 : nt!KeAccumulateTicks+0x18452e
ffffd500`b9700e80 fffff804`192d245a     : ffffbf82`d8914480 ffffd38f`7622f5d0 fffff804`1d3a3c00 00000000`00006301 : nt!KeClockInterruptNotify+0x453
ffffd500`b9700f30 fffff804`19208a45     : ffffbf82`d8914480 ffffd500`b9700f40 00000000`0000000c ffff6644`c0c6e4a1 : nt!HalpTimerClockIpiRoutine+0x1a
ffffd500`b9700f60 fffff804`193faa4a     : ffffd38f`7622f5d0 ffffbf82`d8914480 0000013b`f7c809dc 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffd500`b9700fb0 fffff804`193fafb7     : 00000000`00000000 00000000`01312d00 00000000`80000000 fffff804`193fafc4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffd38f`7622f550 fffff804`1921bfe7     : 00000000`00000010 00000000`00000a87 ffffd38f`7622f708 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffd38f`7622f6e0 fffff804`1932a779     : ffffd38f`7622fa38 ffffd38f`7622fa31 ffffd38f`7622fa60 00000000`00000000 : nt!KeYieldProcessorEx+0x17
ffffd38f`7622f710 fffff804`1923489e     : ffffd500`b95bc240 ffffbf82`1b6de02b ffffd38f`7622fa20 ffffd500`00000002 : nt!ExpGetPoolTagInfoTarget+0x149
ffffd38f`7622f760 fffff804`19233b84     : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs+0x30e
ffffd38f`7622f8d0 fffff804`193fcb3e     : ffffffff`00000000 ffffd500`b95b9180 ffffd500`b95c4340 ffffbf83`006e3080 : nt!KiRetireDpcList+0x1f4
ffffd38f`7622fb60 00000000`00000000     : ffffd38f`76230000 ffffd38f`76229000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


SYMBOL_NAME:  nt!KeAccumulateTicks+18452e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.2006

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  18452e

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

Followup:     MachineOwner
---------      您可以先到设备制造商的官网重装一下所有的驱动，以便判断是否是驱动的问题。