通过WinDbg Preview分析日记,结果代码如下:Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64 Copyright (c) Microsoft Corporation. All rights reserved. Loading Dump File [C:\Windows\070722-40671-01.dmp] Mini Kernel Dump File: Only registers and stack trace are available Symbol search path is: srv* Executable search path is: Windows 10 Kernel Version 18362 MP (8 procs) Free x64 Product: WinNt, suite: TerminalServer SingleUserTS Personal Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202 Machine Name: Kernel base = 0xfffff803`15c00000 PsLoadedModuleList = 0xfffff803`16045f30 Debug session time: Thu Jul 7 14:10:35.243 2022 (UTC 8:00) System Uptime: 0 days 0:47:58.718 Loading Kernel Symbols ............................................................... ................................................................ ................................................................ ....................................... Loading User Symbols Loading unloaded module list .............. For analysis of this file, run !analyze -v nt!KeBugCheckEx: fffff803`15dc3e40 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:ffffd801`1c374b10=0000000000000133 1: 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: fffff80316171358, 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 DBGHELP: Timeout to store: https://msdl.microsoft.com/download/symbols KEY_VALUES_STRING: 1 Key : Analysis.CPU.mSec Value: 6999 Key : Analysis.DebugAnalysisManager Value: Create Key : Analysis.Elapsed.mSec Value: 145831 Key : Analysis.Init.CPU.mSec Value: 952 Key : Analysis.Init.Elapsed.mSec Value: 66471 Key : Analysis.Memory.CommitPeak.Mb Value: 98 Key : Bugcheck.Code.DumpHeader Value: 0x133 Key : Bugcheck.Code.Register Value: 0x133 Key : WER.OS.Branch Value: 19h1_release Key : WER.OS.Timestamp Value: 2019-03-18T12:02:00Z Key : WER.OS.Version Value: 10.0.18362.1 FILE_IN_CAB: 070722-40671-01.dmp BUGCHECK_CODE: 133 BUGCHECK_P1: 0 BUGCHECK_P2: 501 BUGCHECK_P3: 500 BUGCHECK_P4: fffff80316171358 DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED TRAP_FRAME: ffff97801082f5c0 -- (.trap 0xffff97801082f5c0) NOTE: The trap frame does not contain all registers. Some register values may be zeroed or incorrect. rax=000000001b501e7a rbx=0000000000000000 rcx=ffff97801082f7b0 rdx=ffff97801082f7d0 rsi=0000000000000000 rdi=0000000000000000 rip=fffff80315c3c75b rsp=ffff97801082f750 rbp=ffff97801082f8f0 r8=ffffd8011c380280 r9=0000000000000000 r10=fffff803161a8520 r11=0000000000000000 r12=0000000000000000 r13=0000000000000000 r14=0000000000000000 r15=0000000000000000 iopl=0 nv up ei pl nz na pe nc nt!KeYieldProcessorEx 0x1b: fffff803`15c3c75b 4883c420 add rsp,20h Resetting default scope BLACKBOXBSD: 1 (!blackboxbsd) BLACKBOXNTFS: 1 (!blackboxntfs) BLACKBOXPNP: 1 (!blackboxpnp) BLACKBOXWINLOGON: 1 CUSTOMER_CRASH_COUNT: 1 PROCESS_NAME: System STACK_TEXT: ffffd801`1c374b08 fffff803`15dfa6ed : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx ffffd801`1c374b10 fffff803`15c44477 : 0000053b`fd3dedeb ffffd801`1c380180 00000000`00000286 ffff9780`1082f5c0 : nt!KeAccumulateTicks 0x1b801d ffffd801`1c374b70 fffff803`15b5f291 : 00000000`00000000 ffff8706`6c0d0400 ffff9780`1082f640 ffff8706`6c0d04b0 : nt!KeClockInterruptNotify 0xc07 ffffd801`1c374f30 fffff803`15cf1845 : ffff8706`6c0d0400 00000000`00000000 00000000`00000000 ffffbaa6`a19838e6 : hal!HalpTimerClockIpiRoutine 0x21 ffffd801`1c374f60 fffff803`15dc58ca : ffff9780`1082f640 ffff8706`6c0d0400 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5 ffffd801`1c374fb0 fffff803`15dc5e37 : ffff8706`72cbb890 ffff9780`1082f648 ffff8706`7ba5ae20 fffff803`15dc5e44 : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa ffff9780`1082f5c0 fffff803`15c3c75b : ffffffff`ffffffd2 fffff803`161a9403 00000000`00000010 00000000`00000282 : nt!KiInterruptDispatchNoLockNoEtw 0x37 ffff9780`1082f750 fffff803`161a9415 : ffff8706`72d8e1f0 00000000`00000000 ffff8706`72d8e318 00000006`a8031cb6 : nt!KeYieldProcessorEx 0x1b ffff9780`1082f780 fffff803`161a8575 : 00000000`1b501e7a ffffd801`1c380180 ffff8706`7ba5ae20 00000000`00000000 : nt!IopLiveDumpProcessCorralStateChange 0x2d ffff9780`1082f7b0 fffff803`15cc5a1a : ffffd801`1c382f80 00000000`00000001 ffff9780`1082f7d0 00000000`00000000 : nt!IopLiveDumpCorralDpc 0x55 ffff9780`1082f7f0 fffff803`15cc506f : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs 0x30a ffff9780`1082f930 fffff803`15dc796e : ffffffff`00000000 ffffd801`1c380180 ffffd801`1c391240 ffff8706`7403c600 : nt!KiRetireDpcList 0x1ef ffff9780`1082fb60 00000000`00000000 : ffff9780`10830000 ffff9780`10829000 00000000`00000000 00000000`00000000 : nt!KiIdleLoop 0x7e SYMBOL_NAME: nt!KeAccumulateTicks 1b801d MODULE_NAME: nt IMAGE_NAME: ntkrnlmp.exe IMAGE_VERSION: 10.0.18362.1556 STACK_COMMAND: .cxr; .ecxr ; kb BUCKET_ID_FUNC_OFFSET: 1b801d FAILURE_BUCKET_ID: 0x133_DPC_nt!KeAccumulateTicks OS_VERSION: 10.0.18362.1 BUILDLAB_STR: 19h1_release OSPLATFORM_TYPE: x64 OSNAME: Windows 10 FAILURE_ID_HASH: {88dc98ce-f842-4daa-98d0-858621db6b0f} Followup: MachineOwner ---------

欢迎咨询本站!。没有看到具体的错误驱动等。建议先升级一下系统,再查看是否有好转。可以参考以下链接使用MediaCreationTool进行系统的无损修复/覆盖安装:(正常情况下文件、设置、应用等将保持原样,并将系统更新到最新的Windows10正式版。)https://answers.microsoft.com/zh-hans/windows/f.(相关视频教程:https://www.microsoft.com/en-us/videoplayer/emb.)


点赞(93) 打赏

微信小程序

微信扫一扫体验

立即
投稿

微信公众账号

微信扫一扫加关注

发表
评论
返回
顶部