win10 系统蓝屏

Question

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

Loading Dump File [C:\Windows\Minidump\041322-11453-01.dmp]
Mini Kernel Dump File: Only registers and stack trace are available

************* Path validation summary **************
Response Time (ms) Location
Deferred srv*
Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 14393 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 14393.2214.amd64fre.rs1_release_1.180402-1758
Machine Name:
Kernel base = 0xfffff801a2a76000 PsLoadedModuleList = 0xfffff801a2d7e140
Debug session time: Wed Apr 13 10:12:14.805 2022 (UTC + 8:00)
System Uptime: 0 days 13:11:48.938
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.......
Loading User Symbols
Loading unloaded module list
...........................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff801a2bd16c0 48894c2408 mov qword ptr [rsp+8],rcx ss:fffff801a4a58d90=0000000000000133
0: 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: 0000000000000001, The system cumulatively spent an extended period of time at
DISPATCH_LEVEL or above. The offending component can usually be
identified with a stack trace.
Arg2: 0000000000001e00, The watchdog period.
Arg3: fffff801a2e20540, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

Debugging Details:

---

KEY_VALUES_STRING: 1

Key  : Analysis.CPU.mSec
Value: 3202

Key  : Analysis.DebugAnalysisManager
Value: Create

Key  : Analysis.Elapsed.mSec
Value: 3336

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

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

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

Key  : WER.OS.Branch
Value: rs1_release_1

Key  : WER.OS.Timestamp
Value: 2018-04-02T17:58:00Z

Key  : WER.OS.Version
Value: 10.0.14393.2214

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff801a2e20540

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: ffffcd012bcdf7e0 -- (.trap 0xffffcd012bcdf7e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000001ee8 rbx=0000000000000000 rcx=00000000d6b08bac
rdx=0000000000000001 rsi=0000000000000000 rdi=0000000000000000
rip=fffff801a2aae83a rsp=ffffcd012bcdf978 rbp=ffffcd012bcdfac0
r8=0000000000000002 r9=fffff801a2a76000 r10=fffff801a2dbbca0
r11=ffffa805e9471460 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei ng nz na po nc
nt!KeYieldProcessorEx+0x1a:
fffff801`a2aae83a c3 ret
Resetting default scope

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: dwm.exe

IRP_ADDRESS: ffffffffffffff88

STACK_TEXT:
fffff801a4a58d88 fffff801a2acdf4a : 0000000000000133 0000000000000001 0000000000001e00 fffff801a2e20540 : nt!KeBugCheckEx
fffff801a4a58d90 fffff801a2acb539 : 00001d9556f74991 0000000000000000 ffffa805e4eb1080 fffff78000000320 : nt!KeAccumulateTicks+0x42a
fffff801a4a58df0 fffff801a2a04366 : ffffcd012bcdf7e0 fffff801a2a4f3f0 0000000000000002 00001d9556f7190d : nt!KeClockInterruptNotify+0x469
fffff801a4a58f40 fffff801a2b53ec6 : fffff801a2a4f3f0 fffff801a2ad338c fffff801a4a58f50 0000000000000010 : hal!HalpTimerClockInterrupt+0x56
fffff801a4a58f70 fffff801a2bd2efa : ffffcd012bcdf860 fffff801a4a4fbc0 fffff801a2dbb180 0000000000000000 : nt!KiCallInterruptServiceRoutine+0x106
fffff801a4a58fb0 fffff801a2bd3407 : 0000000000000046 fffff801a2bd348e ffffa805e8ea1300 ffffa805e8ea1300 : nt!KiInterruptSubDispatchNoLockNoEtw+0xea
ffffcd012bcdf7e0 fffff801a2aae83a : fffff801a2bf2a97 ffffa805e9471460 0000000000000000 ffffcd012bcdfb80 : nt!KiInterruptDispatchNoLockNoEtw+0x37
ffffcd012bcdf978 fffff801a2bf2a97 : ffffa805e9471460 0000000000000000 ffffcd012bcdfb80 0000000000000008 : nt!KeYieldProcessorEx+0x1a
ffffcd012bcdf980 fffff801a2ac8704 : 0000000000000000 000000e8e6f7e3f0 0000000000000000 fffff28dd6b08bac : nt!IopCompleteRequest+0x133347
ffffcd012bcdfa70 fffff801a2bd55df : 00000210b784e720 ffffa805e6fc0010 0000000000000000 fffff2d900000000 : nt!KiDeliverApc+0x134
ffffcd012bcdfb00 00007ff950a3f491 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : nt!KiApcInterrupt+0x39f
000000e8e6f7ec50 0000000000000000 : 0000000000000000 0000000000000000 0000000000000000 0000000000000000 : 0x00007ff9`50a3f491

SYMBOL_NAME: nt!KeAccumulateTicks+42a

MODULE_NAME: nt

IMAGE_NAME: ntkrnlmp.exe

IMAGE_VERSION: 10.0.14393.2214

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 42a

FAILURE_BUCKET_ID: 0x133_ISR_nt!KeAccumulateTicks

OS_VERSION: 10.0.14393.2214

BUILDLAB_STR: rs1_release_1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {65350307-c3b9-f4b5-8829-4d27e9ff9b06}

Followup: MachineOwner

---

Answer 1

Hi @lack_ye

This bug check indicates that the DPC watchdog executed, either because it detected a single long-running deferred procedure call (DPC), or because the system spent a prolonged time at an interrupt request level (IRQL) of DISPATCH_LEVEL or above.

It's occurred due to some specific reasons, like unsupported SSD firmware, old SSD driver version, hardware incompatibility issues, or system files being corrupted.

These crashes are related to memory corruption and are probably caused by a driver. You can follow these below articles to find the driver and memory leak which is causing you this BSOD.

Driver verifier is a utility built into the OS that will often find the driver/drivers that are the underlying cause of BSOD/Crashes.

Driver Verifier-- tracking down a mis-behaving driver.
https://answers.microsoft.com/en-us/windows/forum/all/driver-verifier-tracking-down-a-mis-behaving/f5cb4faf-556b-4b6d-95b3-c48669e4c983

Memtest is easy to use and is an accurate test of your computer memory. It can tell you if your memory is bad, a motherboard slot is bad, etc.

Memory problems.
https://answers.microsoft.com/en-us/windows/forum/all/memory-problems/21c3f63f-f570-4522-b2ef-ecc7b7ff6461

Hope this resolves your Query!!

-----------

--If the reply is helpful, please Upvote and Accept it as an answer–

Answer 2

Please modify the default language to English so that log files can be scanned and read.

https://www.tenforums.com/tutorials/3813-add-remove-change-display-language-windows-10-a.html

https://www.tenforums.com/tutorials/136792-change-display-language-windows-10-a.html

Search for: C:\windows\memory.dmp
If the file size is < 2 GB then save to the downloads folder then ZIP and post a separate share link into this thread that only has the zipped memory dump file.

Then run the V2 log collector and post a share link into this thread using one drive, drop box, or google drive.

https://www.tenforums.com/bsod-crashes-debugging/2198-bsod-posting-instructions.html

https://www.elevenforum.com/t/bsod-posting-instructions.103/

.
.
.
.
.

Please remember to vote and to mark the replies as answers if they help.

On the bottom of each post there is:

Propose as answer = answered the question

On the left side of each post there is /\ with a number: click = a helpful post
.
.
.
.
.