DPC WATCHDOG VIOLATION蓝屏分析，带WinDbg Preview分析代码

dmp源文件见链接，下面贴出分析结果，请帮忙建议如何解决链接：https://pan.baidu.com/s/1-ITX8QH9LA5tnBPyqwZtWA  提取码：3s03*******************************************************************************
*                                                                             *
*                        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. The offending component can usually be
    identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff80477afb320, 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: 2233

    Key  : Analysis.DebugAnalysisManager
    Value: Create

    Key  : Analysis.Elapsed.mSec
    Value: 27732

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

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

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

    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:  090822-7187-01.dmp

DUMP_FILE_ATTRIBUTES: 0x8
  Kernel Generated Triage Dump

BUGCHECK_CODE:  133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff80477afb320

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE:  DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  msedge.exe

STACK_TEXT: 
ffffaa80`86d3ee18 fffff804`7722a998     : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff804`77afb320 : nt!KeBugCheckEx
ffffaa80`86d3ee20 fffff804`7704b573     : 00000d64`d84e99fa ffffaa80`86d40180 00000000`00000000 ffffaa80`86d40180 : nt!KeAccumulateTicks+0x1dcbc8
ffffaa80`86d3ee80 fffff804`7704b05a     : ffffd081`3a90a3e0 ffff8908`baaff560 ffff8908`b54bfa00 00000000`00000000 : nt!KeClockInterruptNotify+0x453
ffffaa80`86d3ef30 fffff804`770d9405     : ffffd081`3a90a3e0 ffffd081`3a90a500 ffffd081`3a90a5b0 ffff6de5`3c2f81d2 : nt!HalpTimerClockIpiRoutine+0x1a
ffffaa80`86d3ef60 fffff804`771fa36a     : ffff8908`baaff560 ffffd081`3a90a3e0 fffff804`76e00000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffaa80`86d3efb0 fffff804`771fa8d7     : ffffd081`44dc1080 ffff8908`baaff601 00000000`00000000 fffff804`771fa8e4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8908`baaff4e0 fffff804`770d08a7     : 00000000`00000010 00000000`00040202 ffff8908`baaff698 00000000`00000018 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8908`baaff670 fffff804`770b2e98     : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000008 : nt!KeYieldProcessorEx+0x17
ffff8908`baaff6a0 fffff804`770b26fc     : ffffaa80`86d40180 00000000`ffffffff ffffbc00`00000000 00000000`00000000 : nt!KiSearchForNewThreadOnProcessor+0xe8
ffff8908`baaff720 fffff804`770b1b3f     : ffffd081`0000000a 00000000`00000004 ffff8908`baaff8e0 00000000`00000000 : nt!KiSwapThread+0x5ec
ffff8908`baaff7d0 fffff804`770b13e3     : ffffaa80`000000ac fffff804`00000000 000fa4ef`bd9bbf01 ffffd081`47ac11c0 : nt!KiCommitThreadWait+0x14f
ffff8908`baaff870 fffff804`77426421     : ffffd081`482d4360 00000000`00000006 00000000`00000001 00000000`00000000 : nt!KeWaitForSingleObject+0x233
ffff8908`baaff960 fffff804`774264ca     : ffffd081`47ac1080 00000071`c822f5d8 00000000`00000000 000001ba`eef5b800 : nt!ObWaitForSingleObject+0x91
ffff8908`baaff9c0 fffff804`7720a2b5     : 000001ba`00000000 00000000`00000001 ffff8908`baaffa18 ffffffff`fffe7960 : nt!NtWaitForSingleObject+0x6a
ffff8908`baaffa00 00007ffa`2db2cfc4     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x25
00000071`c822f5a8 00000000`00000000     : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x00007ffa`2db2cfc4


SYMBOL_NAME:  nt!KeAccumulateTicks+1dcbc8

MODULE_NAME: nt

IMAGE_NAME:  ntkrnlmp.exe

IMAGE_VERSION:  10.0.19041.1889

STACK_COMMAND:  .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET:  1dcbc8

FAILURE_BUCKET_ID:  0x133_ISR_nt!KeAccumulateTicks

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup:     MachineOwner
---------感谢，建议参考以下链接，检测一下内存和硬盘：https://answers.microsoft.com/zh-hans/windows/f.
欢迎访问本站！。请问是偶然蓝屏还是经常在不同的情况下蓝屏？建议打开Edge，进入edge://settings/reset将设置还原为其默认值。进入edge://settings/system关闭启动增强关闭硬件加速关闭在MicrosoftEdge关闭后继续运行后台扩展和应用然后关闭Edge，打开文件夹，地址栏输入：%LocalAppData%\Microsoft进入该地址，删除Edge文件夹。然后执行一下干净启动，排除其他干扰：https://support.microsoft.com/zh-cn/help/929135.先卸载设备中全部的第三方反病毒软件与系统优化软件(例如360、联想电脑管家、360桌面、腾讯电脑管家、腾讯桌面、鲁大师，代理，加速器，虚拟机等)。然后鼠标右键单击开始菜单→运行（RUN）→输入：msconfig（按下Enter键）点击上面的“服务”勾选下面的“隐藏所有Microsoft服务”（请务必勾选）点击“全部禁用”。然后鼠标右键单击开始菜单→任务管理器，（点击底部“详细信息”），点击顶部”启动”，鼠标右键单击“状态”显示为“已启动”的项，选择“禁用”。（禁用所有启动项。）然后鼠标右键单击开始按钮（图标的按钮）→"WindowsPowerShell(I)（管理员)(A）”→输入：（WIndows11中可能显示Windows终端（管理员））sfc/SCANNOW（按下Enter键）Dism/Online/Cleanup-Image/ScanHealth（按下Enter键）Dism/Online/Cleanup-Image/CheckHealth（按下Enter键）DISM/Online/Cleanup-image/RestoreHealth（按下Enter键）完成后重启电脑，再次输入：sfc/SCANNOW（按下Enter键）看下是否还会蓝屏、
你好，。若是点击“”按钮后没有加载出输入框，无法内容，建议等待一会再尝试。很可能是网络等原因。https://answers.microsoft.com/zh-hans/windows/f.
照做了，今天还是出现了蓝屏，今天的崩溃代码如下Microsoft(R)WindowsDebuggerVersion10.0.25136.1001AMD64Copyright(c)MicrosoftCorporation.Allrightsreserved.LoadingDumpFile
感谢，建议参考以下链接，检测一下内存和硬盘：https://answers.microsoft.com/zh-hans/windows/f.
用MediaCreationTool进行做了无损修复/覆盖安装，下午游戏时没有出现卡死后蓝屏第一次进行这个游戏的时间是周三晚上，正常玩了两个多小时没有事，周四周五晚上开始玩一个多小时就会卡死，电脑鼠标键盘都没有反应，然后蓝屏。今天修复后，把游戏从全屏改成了窗口，游戏两小时左右没有卡死。