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: fffff80316efa320, 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 *** *** *** ************************************************************************* *** WARNING: Unable to verify checksum for win32k.sys KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 4874 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 152708 Key : Analysis.Init.CPU.mSec Value: 436 Key : Analysis.Init.Elapsed.mSec Value: 3671 Key : Analysis.Memory.CommitPeak.Mb Value: 84 Key : WER.OS.Branch Value: vb_release Key : WER.OS.Timestamp Value: 2019-12-06T14:06:00Z Key : WER.OS.Version Value: 10.0.19041.1 BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff80316efa320 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED TRAP_FRAME: ffffa0862947ef60 -- (.trap 0xffffa0862947ef60) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000001f64503f rbx=0000000000000000 rcx=ffffa0862947f178 rdx=ffffa08631d4ee50 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80316480ddb rsp=ffffa0862947f0f0 rbp=ffffa08631d4ec60 r8=ffffa08631d4ec60 r9=ffffa08631d4ec70 r10=fffff8031670cdb0 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei ng nz na po nc nt!KeYieldProcessorEx 0x1b: fffff803`16480ddb 5b pop rbx Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffb881`283f9c88 fffff803`1661f4fa : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffb881`283f9c90 fffff803`1641c53d : 00001361`7256fb73 ffffb881`28400180 00000000`00000246 00000000`00064b3a : nt!KeAccumulateTicks 0x2061da ffffb881`283f9cf0 fffff803`1641cae1 : 00000000`00064600 00000000`0003c05d ffffb881`28400180 00000000`00000001 : nt!KiUpdateRunTime 0x5d ffffb881`283f9d40 fffff803`16416953 : ffffb881`28400180 00000000`00000000 fffff803`16e317b8 00000000`00000000 : nt!KiUpdateTime 0x4a1 ffffb881`283f9e80 fffff803`1641f312 : ffffa086`2947ef60 ffffa086`2947efe0 ffffa086`2947ef00 00000000`00000002 : nt!KeClockInterruptNotify 0x2e3 ffffb881`283f9f30 fffff803`164de055 : 0000000f`018ddbaf ffffa18a`1e327380 ffffa18a`1e327430 ffff7b55`d43a9596 : nt!HalpTimerClockInterrupt 0xe2 ffffb881`283f9f60 fffff803`165f8c6a : ffffa086`2947efe0 ffffa18a`1e327380 00000000`80000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffb881`283f9fb0 fffff803`165f91d7 : ffffa086`00000000 00001f80`005f02e4 00000000`1f641d39 ffffa086`2947f178 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffffa086`2947ef60 fffff803`16480ddb : ffffa086`31d4ee50 fffff803`1670ce8c 00000000`00000001 ffffa086`2947f110 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffffa086`2947f0f0 fffff803`1670ce8c : 00000000`00000001 ffffa086`2947f110 00000000`00010001 00000000`00000000 : nt!KeYieldProcessorEx 0x1b ffffa086`2947f100 fffff803`1649a3be : ffffb881`28403240 ffffa086`2947f260 00000000`00000000 ffffa18a`1f64503f : nt!KiConfigureHeteroProcessorsTarget 0xdc ffffa086`2947f160 fffff803`164996a4 : 00000000`00000000 00000000`00000000 00000000`00140001 00000000`00000000 : nt!KiExecuteAllDpcs 0x30e ffffa086`2947f2d0 fffff803`165fad2e : ffffffff`00000000 ffffb881`28400180 ffffb881`2840b440 ffffa18a`4a52f080 : nt!KiRetireDpcList 0x1f4 ffffa086`2947f560 00000000`00000000 : ffffa086`29480000 ffffa086`29479000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x9e SYMBOL_NAME: nt!KeAccumulateTicks 2061da MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.19041.1237 STACK_COMMAND: .thread ; .cxr ; kb BUCKET_ID_FUNC_OFFSET: 2061da FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks OS_VERSION: 10.0.19041.1 BUILDLAB_STR: vb_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f} Followup: MachineOwner

HiIamDave,Iwillhelpyouwiththis.PleasechecktoseeifyourPCisproducinganyminidumpfiles,Iwillcheckthosetoseeiftheyprovideanyinsightintoapotentialcauseofthesystemcrashes.PleaseNote,Icannotdownloadfrompan.baidu,pleaseuseadifferentCloudServicefortheupload.OpenWindowsFileExplorer.NavigatetoC:\Windows\MinidumpCopyanyminidumpfilesontoyourDesktop,thenzipthoseup.UploadthezipfiletotheCloud(OneDrive,DropBox.etc.),thenchoosetosharethoseandgetasharelink.Thenpostthelinkheretothezipfile,sowecantakealookforyou.


https://onedrive.live.com/redir?resid=6995A221C75590DB!1704&authkey=!AEHdPisOVt6_w5Q&e=s10zgt此是否有帮助?是否抱歉,这没有帮助。太棒了!感谢你的反馈。你对此的满意度如何?感谢你的反馈,它能帮助改进网站。你对此的满意度如何?感谢你的反馈。


HiYourminidumpfilesjustindicatememory(RAM)corruptionnospecificdriverislistedGotothesupportpageforyourPCorMotherboardonthemanufacturerswebsite,thenfromthere,downloadandinstalltheversionofChipsetdriverstheyrecommendandwhilethere,checkforanyBIOSupdatethatmayneedtobeinstalledWaittoseeifyoursystemstabilizes,ifnot,thebestoptionistodownloadthewidelyavailablefreeutilityMemTest86,thenrunafull4passscanwiththattotestyourRAMforphysicalerrors


点赞(64) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部