question

Maxwell-3623 avatar image
0 Votes"
Maxwell-3623 asked Docs-4663 edited

Need help on blue screen win11 dump file analysis

Hi guys, my laptop crashed lately, it can't start windows 11 normally then I tried to restore it to previous point. It failed to restore to previous point, but it somehow allow me to run windows 11 normally again. So I check the dump file but I can not understand it, any help I will be grateful!


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


Loading Dump File [C:\Windows\Minidump\041922-37187-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 22000 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 22000.1.amd64fre.co_release.210604-1628
Machine Name:
Kernel base = 0xfffff806`29a00000 PsLoadedModuleList = 0xfffff806`2a629c10
Debug session time: Tue Apr 19 16:07:17.365 2022 (UTC - 4:00)
System Uptime: 1 days 0:56:37.257
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.........................................................
Loading User Symbols
Loading unloaded module list
....................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff806`29e169a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff806`30e1dde0=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: fffff8062a705330, cast to nt!DPC_WATCHDOG_GLOBAL_TRIAGE_BLOCK, which contains
additional information regarding the cumulative timeout
Arg4: 0000000000000000

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: 5421

 Key  : Analysis.DebugAnalysisManager
 Value: Create

 Key  : Analysis.Elapsed.mSec
 Value: 19635

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

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

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

 Key  : WER.OS.Branch
 Value: co_release

 Key  : WER.OS.Timestamp
 Value: 2021-06-04T16:28:00Z

 Key  : WER.OS.Version
 Value: 10.0.22000.1


FILE_IN_CAB: 041922-37187-01.dmp

BUGCHECK_CODE: 133

BUGCHECK_P1: 1

BUGCHECK_P2: 1e00

BUGCHECK_P3: fffff8062a705330

BUGCHECK_P4: 0

DPC_TIMEOUT_TYPE: DPC_QUEUE_EXECUTION_TIMEOUT_EXCEEDED

TRAP_FRAME: fffffb857a897310 -- (.trap 0xfffffb857a897310)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff8062e7cb490
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80629d6511f rsp=fffffb857a8974a0 rbp=fffffb857a897579
r8=ffffbb07049e31a0 r9=ffffbb0704a57010 r10=fffff80629d310b0
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na pe nc
nt!KxWaitForLockChainValid+0x1f:
fffff806`29d6511f 488b07 mov rax,qword ptr [rdi] ds:00000000`00000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff806`30e1ddd8 fffff806`29c5483f : 00000000`00000133 00000000`00000001 00000000`00001e00 fffff806`2a705330 : nt!KeBugCheckEx
fffff806`30e1dde0 fffff806`29c54451 : 00004cb7`9f51085e fffff806`29d2c6a1 ffffbb07`04a73100 fffff806`29c4fb78 : nt!KeAccumulateTicks+0x20f
fffff806`30e1de50 fffff806`29c5263a : fffff806`27a0e200 fffffb85`7a897310 fffff806`27a0e360 00000000`00000c18 : nt!KiUpdateRunTime+0x61
fffff806`30e1deb0 fffff806`29c52426 : fffff806`2a6f7dd0 fffff806`2a6f7e80 00000000`00000000 ffffbb07`0a2f4590 : nt!KeClockInterruptNotify+0x11a
fffff806`30e1df40 fffff806`29c21440 : fffff806`2a6f7dd0 fffff806`29d394cc fffff806`2e7cb490 fffff806`29e1834b : nt!HalpTimerClockIpiRoutine+0x16
fffff806`30e1df70 fffff806`29e185aa : fffffb85`7a897390 fffff806`2a6f7dd0 00004cb6`6ff2daf4 00000000`00000004 : nt!KiCallInterruptServiceRoutine+0xa0
fffff806`30e1dfb0 fffff806`29e18b77 : 00000000`1050ea86 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffb85`7a897310 fffff806`29d6511f : fffffb85`7a897500 fffff806`2e77eae4 00000000`00000005 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffb85`7a8974a0 fffff806`29d31129 : fffff806`2e7cb490 00000000`00000010 fffff806`27a05180 fffff806`29c423fa : nt!KxWaitForLockChainValid+0x1f
fffffb85`7a8974d0 fffff806`2f25d3b9 : ffffbb07`04a59810 fffff806`2a6231c0 ffffbb07`0a2f4590 ffffbb07`07c00110 : nt!KeReleaseInStackQueuedSpinLock+0x79
fffffb85`7a897500 fffff806`2e712312 : 00000000`00000002 ffffbb07`04a57010 fffff806`2e7cb488 fffff806`2f2349c0 : storport!StorPortNotification+0x289
fffffb85`7a8975e0 00000000`00000002 : ffffbb07`04a57010 fffff806`2e7cb488 fffff806`2f2349c0 ffffbb07`0388c240 : iaStorA+0x12312
fffffb85`7a8975e8 ffffbb07`04a57010 : fffff806`2e7cb488 fffff806`2f2349c0 ffffbb07`0388c240 00000000`0000000c : 0x2
fffffb85`7a8975f0 fffff806`2e7cb488 : fffff806`2f2349c0 ffffbb07`0388c240 00000000`0000000c 00000000`00000000 : 0xffffbb07`04a57010
fffffb85`7a8975f8 fffff806`2f2349c0 : ffffbb07`0388c240 00000000`0000000c 00000000`00000000 fffff806`2e711866 : iaStorA+0xcb488
fffffb85`7a897600 ffffbb07`0388c240 : 00000000`0000000c 00000000`00000000 fffff806`2e711866 00000000`00000001 : iaStorA+0xb349c0
fffffb85`7a897608 00000000`0000000c : 00000000`00000000 fffff806`2e711866 00000000`00000001 ffffbb07`04a59810 : 0xffffbb07`0388c240
fffffb85`7a897610 00000000`00000000 : fffff806`2e711866 00000000`00000001 ffffbb07`04a59810 00000000`0000000c : 0xc


SYMBOL_NAME: iaStorA+12312

MODULE_NAME: iaStorA

IMAGE_NAME: iaStorA.sys

STACK_COMMAND: .cxr; .ecxr ; kb

BUCKET_ID_FUNC_OFFSET: 12312

FAILURE_BUCKET_ID: 0x133_ISR_iaStorA!unknown_function

OS_VERSION: 10.0.22000.1

BUILDLAB_STR: co_release

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

FAILURE_ID_HASH: {29cacd5a-937e-6aba-da60-e5daeb0ebcc5}

Followup: MachineOwner



windows-11
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.

1 Answer

Docs-4663 avatar image
0 Votes"
Docs-4663 answered Docs-4663 edited

There may have been one or two misbehaving drivers.

Please 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/



Search for C:\windows\memory.dmp
Check the file size.
If the file size is < 2.5 GB then save to the downloads folder > ZIP > post a share link that only has the zipped memory dump file.



.
.
.
.
.

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

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.