蓝屏日志 请问怎么处理呢

钊志 叶 1 Reputation point
2021-07-05T06:57:56.383+00:00

Microsoft (R) Windows Debugger Version 10.0.21349.1004 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.

Loading Dump File [C:\Windows\minidump\070521-13109-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
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff80683400000 PsLoadedModuleList = 0xfffff80683848130
Debug session time: Mon Jul 5 14:16:14.832 2021 (UTC + 8:00)
System Uptime: 0 days 2:36:50.875
Loading Kernel Symbols
...............................................................
................................................................
................................................................
..................................................
Loading User Symbols
Loading unloaded module list
...........
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806835c1220 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe000f50eeb10=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: fffff80683973358, 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: 6187

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 62569

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

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

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

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

BUGCHECK_CODE: 133

BUGCHECK_P1: 0

BUGCHECK_P2: 501

BUGCHECK_P3: 500

BUGCHECK_P4: fffff80683973358

DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffac8e2e62f5c0 -- (.trap 0xffffac8e2e62f5c0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000018f4a479 rbx=0000000000000000 rcx=ffffac8e2e62f7b0
rdx=ffffac8e2e62f7d0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8068341b9eb rsp=ffffac8e2e62f750 rbp=ffffac8e2e62f8f0
r8=ffffe000f5100280 r9=0000000000000000 r10=fffff806839aa690
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KeYieldProcessorEx+0x1b:
fffff806`8341b9eb 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:
ffffe000f50eeb08 fffff806835ee83d : 0000000000000133 0000000000000000 0000000000000501 0000000000000500 : nt!KeBugCheckEx
ffffe000f50eeb10 fffff8068341f857 : 00000a08901ffb3b ffffe000f5100180 0000000000000286 ffffac8e2e62f5c0 : nt!KeAccumulateTicks+0x1cbe1d
ffffe000f50eeb70 fffff80683eb91e1 : 0000000000000000 ffffce074b8bc400 ffffac8e2e62f640 ffffce074b8bc4b0 : nt!KeClockInterruptNotify+0xc07
ffffe000f50eef30 fffff806834029e5 : ffffce074b8bc400 0000000000000000 0000000000000000 ffffc707cd854132 : hal!HalpTimerClockIpiRoutine+0x21
ffffe000f50eef60 fffff806835c2cba : ffffac8e2e62f640 ffffce074b8bc400 0000000000000000 0000000000000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffe000f50eefb0 fffff806835c3227 : ffffce07562853f0 0000000000989680 ffffce075f74fe20 fffff806835c3234 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffac8e2e62f5c0 fffff8068341b9eb : ffffffffffffffd2 fffff806839ab57b 0000000000000010 0000000000000246 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffac8e2e62f750 fffff806839ab585 : 0000000000000000 0000000000000001 0000000000000000 00000015dd804e98 : nt!KeYieldProcessorEx+0x1b
ffffac8e2e62f780 fffff806839aa6e5 : 0000000018f4a479 ffffe000f5100180 ffffce075f74fe20 0000000000000000 : nt!IopLiveDumpProcessCorralStateChange+0x2d
ffffac8e2e62f7b0 fffff8068346b065 : ffffe000f5102f80 0000000000000001 ffffac8e2e62f7a8 0000000000000000 : nt!IopLiveDumpCorralDpc+0x55
ffffac8e2e62f7f0 fffff8068346a6bf : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiExecuteAllDpcs+0x305
ffffac8e2e62f930 fffff806835c4d64 : ffffffff00000000 ffffe000f5100180 ffffe000f5111240 ffffce075cb0f080 : nt!KiRetireDpcList+0x1ef
ffffac8e2e62fb60 0000000000000000 : ffffac8e2e630000 ffffac8e2e629000 0000000000000000 0000000000000000 : nt!KiIdleLoop+0x84

SYMBOL_NAME: nt!KeAccumulateTicks+1cbe1d

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.18362.387

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 1cbe1d

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


Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,092 questions
{count} votes

1 answer

Sort by: Most helpful
  1. Carl Fan 6,836 Reputation points
    2021-07-06T10:24:04.473+00:00

    Hi,
    Few steps you could follow below:

    1. Ensure all third-party drivers are up to date.
    2. Ensure all firmware is up to date.
    3. Update all third-party applications.
    4. Check for update to make sure you have installed the latest security update.

    Hope this helps and please help to accept as Answer if the response is useful.
    Best Regards,
    Carl

    0 comments No comments