这个是dmp链接: https://pan.baidu.com/s/1a6KyhoK4d7j30oBKTO0U8w?pwd=kvmu 提取码: kvmu 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: fffff800360fb320, 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: 2733
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 154699
Key : Analysis.Init.CPU.mSec
Value: 421
Key : Analysis.Init.Elapsed.mSec
Value: 56746
Key : Analysis.Memory.CommitPeak.Mb
Value: 84
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-10156-01.dmp
DUMP_FILE_ATTRIBUTES: 0x8
Kernel Generated Triage Dump
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff800360fb320
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
BLACKBOXBSD: 1 (!blackboxbsd)
BLACKBOXNTFS: 1 (!blackboxntfs)
BLACKBOXPNP: 1 (!blackboxpnp)
BLACKBOXWINLOGON: 1
CUSTOMER_CRASH_COUNT: 1
PROCESS_NAME: r5apex.exe
STACK_TEXT:
ffffc400`d5d00e18 fffff800`358596fe : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffc400`d5d00e20 fffff800`356d2973 : 000000e3`eb974634 ffffc400`d5bb9180 00000000`00000000 ffffc400`d5bb9180 : nt!KeAccumulateTicks+0x18452e
ffffc400`d5d00e80 fffff800`356d245a : ffffe686`b7b14480 ffff8704`00c37a20 00000000`77464600 00000000`00d2fda0 : nt!KeClockInterruptNotify+0x453
ffffc400`d5d00f30 fffff800`35608a45 : ffffe686`b7b14480 00000000`00000000 00000000`00000000 ffff6a41`53199f5f : nt!HalpTimerClockIpiRoutine+0x1a
ffffc400`d5d00f60 fffff800`357faa4a : ffff8704`00c37a20 ffffe686`b7b14480 000000d7`d8a8196c 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffc400`d5d00fb0 fffff800`357fafb7 : 00000000`cb27ce05 ffffc400`d5bb9180 00000000`80000000 fffff800`357fafc4 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffff8704`00c379a0 fffff800`3561bfe7 : 00000000`00000010 00000000`00000a87 ffff8704`00c37b50 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffff8704`00c37b30 fffff800`3572a779 : ffffe686`b7fef910 00000000`00000a90 00000000`00000f44 00000000`00400a02 : nt!KeYieldProcessorEx+0x17
ffff8704`00c37b60 fffff800`3563489e : ffffc400`d5bbc240 ffffe686`1d9f7b38 00000000`00000000 ffff8704`00000002 : nt!ExpGetPoolTagInfoTarget+0x149
ffff8704`00c37bb0 fffff800`35633b84 : 56f9b982`6775da9a 56f8b983`6774da9b d6e83993`e7645a8b d6a839d3`e7245acb : nt!KiExecuteAllDpcs+0x30e
ffff8704`00c37d20 fffff800`35800015 : c85d820f`16aa3fe0 ffffc400`d5bb9180 00000000`00000000 00000000`00a7f666 : nt!KiRetireDpcList+0x1f4
ffff8704`00c37fb0 fffff800`357ffe00 : 00000000`00000002 00000000`ffffffff 00000000`00000000 00000000`00000000 : nt!KxRetireDpcList+0x5
ffff8704`029a79d0 fffff800`357ff4ce : ffffe686`de028080 ffff8704`029a7a10 ffffffff`00000000 ffffe686`00000000 : nt!KiDispatchInterruptContinue
ffff8704`029a7a00 000001ca`1891000c : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiDpcInterrupt+0x2ee
00000052`56c1f718 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x000001ca`1891000c
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
--------- 您电脑的型号是什么呢??可以到您电脑制造商的官网,下载所有最新版本的驱动更新一下。(蓝牙+芯片组+网卡+声卡+显卡+BIOS)(建议不要使用第三方软件更新驱动)如果您不了解您电脑的型号,您可按查找》输入“系统信息”(SystemInformation)》在主页的SystemSummary(系统摘要)下,截图或拍张照片上传上来吗??(以方便我帮您查找您电脑制造商的最新驱动下载链接,然后发那链接给您。)