如何解决打游戏三角洲电脑蓝屏133问题，拜谢大佬！

Question

*******************************************************************************
*                                                                             *
*                        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: fffff80276905330, 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: 3218

    Key  : Analysis.Elapsed.mSec
    Value: 20474

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

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

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

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

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

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

    Key  : Analysis.Version.DbgEng
    Value: 10.0.27829.1001

    Key  : Analysis.Version.Description
    Value: 10.2503.24.01 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2503.24.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x133

    Key  : Bugcheck.Code.TargetModel
    Value: 0x133

    Key  : Dump.Attributes.AsUlong
    Value: 0x1008

    Key  : Dump.Attributes.DiagDataWrittenToHeader
    Value: 1

    Key  : Dump.Attributes.ErrorCode
    Value: 0x0

    Key  : Dump.Attributes.KernelGeneratedTriageDump
    Value: 1

    Key  : Dump.Attributes.LastLine
    Value: Dump completed successfully.

    Key  : Dump.Attributes.ProgressPercentage
    Value: 0

    Key  : Failure.Bucket
    Value: 0x133_DPC_nt!KeAccumulateTicks

    Key  : Failure.Hash
    Value: {88dc98ce-f842-4daa-98d0-858621db6b0f}

    Key  : Stack.Pointer
    Value: ISR


BUGCHECK_CODE:  133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80276905330

FILE_IN_CAB:  051925-8406-01.dmp

DUMP_FILE_ATTRIBUTES: 0x1008
  Kernel Generated Triage Dump

FAULTING_THREAD:  b

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:  
ffffb901`75ab49e8 fffff802`75f2d6be     : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffb901`75ab49f0 fffff802`75f2d141     : 00000170`811e4698 ffffb901`00000500 00000000`00000297 fffff802`75f9c945 : nt!KeAccumulateTicks+0x39e
ffffb901`75ab4a60 fffff802`75f2a176     : 00000000`00009229 00000000`0000571e 00000001`5c791509 00000000`00000000 : nt!KiUpdateRunTime+0x61
ffffb901`75ab4ac0 fffff802`75f2b482     : fffff105`542cee80 00000000`00000000 fffff802`7682b3a0 00000000`00000000 : nt!KiUpdateTime+0x686
ffffb901`75ab4eb0 fffff802`75f28db2     : fffff105`542cee80 ffff8008`5114c210 ffff8008`00000000 00000000`00000002 : nt!KeClockInterruptNotify+0x272
ffffb901`75ab4f40 fffff802`75f15e40     : 00000001`5c90774f ffff8008`5114c160 00000000`00000001 ffff8008`51143040 : nt!HalpTimerClockInterrupt+0xe2
ffffb901`75ab4f70 fffff802`7601f8ca     : fffff105`542cef00 ffff8008`5114c160 00000000`00000000 ffffb901`75a50fe0 : nt!KiCallInterruptServiceRoutine+0xa0
ffffb901`75ab4fb0 fffff802`76020137     : 00000000`00000000 00000000`00000000 fffff105`542cf098 fffff802`76020144 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffff105`542cee80 fffff802`75e5c58c     : ffffffff`ffffffd1 fffff802`75e5c872 00000000`00000010 00000000`00000286 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffff105`542cf010 fffff802`75e5c883     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KeYieldProcessorEx+0x1c
fffff105`542cf040 fffff802`75f1d391     : fffff105`542cf400 fffff105`1bf62129 ffffb901`75a4c4c0 00000000`00000000 : nt!KiSwapDirectoryTableBaseTarget+0x53
fffff105`542cf090 fffff802`75f1c392     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x491
fffff105`542cf290 fffff802`7602253e     : 00000000`00000000 ffffb901`75a49180 ffffb901`75a55340 ffff8008`819a5080 : nt!KiRetireDpcList+0x2a2
fffff105`542cf540 00000000`00000000     : fffff105`542d0000 fffff105`542c9000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop+0x9e


STACK_COMMAND: ~11 ; .cxr ; kb

SYMBOL_NAME:  nt!KeAccumulateTicks+39e

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.22000.2538

BUCKET_ID_FUNC_OFFSET:  39e

FAILURE_BUCKET_ID:  0x133_DPC_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

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

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

Answer 1

这是一个DPC或者ISR执行时间过长导致超时的错误，多半是硬件驱动问题、硬件故障或者是CPU/内存极高负载导致的，可以通过更新或者回滚驱动（解决第一个问题）、观察平时有没有此情况（排查第二个问题）和关注使用率（排查第三个问题）解决