question

06820596 avatar image
0 Votes"
06820596 asked CarlFan-MSFT answered

蓝屏日志 请问怎么处理呢

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 = 0xfffff806`83400000 PsLoadedModuleList = 0xfffff806`83848130
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:
fffff806`835c1220 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffe000`f50eeb10=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:
ffffe000`f50eeb08 fffff806`835ee83d : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
ffffe000`f50eeb10 fffff806`8341f857 : 00000a08`901ffb3b ffffe000`f5100180 00000000`00000286 ffffac8e`2e62f5c0 : nt!KeAccumulateTicks+0x1cbe1d
ffffe000`f50eeb70 fffff806`83eb91e1 : 00000000`00000000 ffffce07`4b8bc400 ffffac8e`2e62f640 ffffce07`4b8bc4b0 : nt!KeClockInterruptNotify+0xc07
ffffe000`f50eef30 fffff806`834029e5 : ffffce07`4b8bc400 00000000`00000000 00000000`00000000 ffffc707`cd854132 : hal!HalpTimerClockIpiRoutine+0x21
ffffe000`f50eef60 fffff806`835c2cba : ffffac8e`2e62f640 ffffce07`4b8bc400 00000000`00000000 00000000`00000000 : nt!KiCallInterruptServiceRoutine+0xa5
ffffe000`f50eefb0 fffff806`835c3227 : ffffce07`562853f0 00000000`00989680 ffffce07`5f74fe20 fffff806`835c3234 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
ffffac8e`2e62f5c0 fffff806`8341b9eb : ffffffff`ffffffd2 fffff806`839ab57b 00000000`00000010 00000000`00000246 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffac8e`2e62f750 fffff806`839ab585 : 00000000`00000000 00000000`00000001 00000000`00000000 00000015`dd804e98 : nt!KeYieldProcessorEx+0x1b
ffffac8e`2e62f780 fffff806`839aa6e5 : 00000000`18f4a479 ffffe000`f5100180 ffffce07`5f74fe20 00000000`00000000 : nt!IopLiveDumpProcessCorralStateChange+0x2d
ffffac8e`2e62f7b0 fffff806`8346b065 : ffffe000`f5102f80 00000000`00000001 ffffac8e`2e62f7a8 00000000`00000000 : nt!IopLiveDumpCorralDpc+0x55
ffffac8e`2e62f7f0 fffff806`8346a6bf : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiExecuteAllDpcs+0x305
ffffac8e`2e62f930 fffff806`835c4d64 : ffffffff`00000000 ffffe000`f5100180 ffffe000`f5111240 ffffce07`5cb0f080 : nt!KiRetireDpcList+0x1ef
ffffac8e`2e62fb60 00000000`00000000 : ffffac8e`2e630000 ffffac8e`2e629000 00000000`00000000 00000000`00000000 : 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
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I would start by checking your PC vendor's web site and make sure that your BIOS/firmware/drivers are up to date. Some vendors will also provide an update utility similar to Windows Update, that checks your hardware and software for required updates.

0 Votes 0 ·

1 Answer

CarlFan-MSFT avatar image
0 Votes"
CarlFan-MSFT answered

Hi,
Few steps you could follow below:
1. Ensure all third-party drivers are up to date.

  1. Ensure all firmware is up to date.

  2. Update all third-party applications.

  3. 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



5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.