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 = 0xfffff80629a00000 PsLoadedModuleList = 0xfffff8062a629c10
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:
fffff80629e169a0 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:fffff80630e1dde0=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:
fffff80629d6511f 488b07 mov rax,qword ptr [rdi] ds:0000000000000000=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT: 1

PROCESS_NAME: System

STACK_TEXT:
fffff80630e1ddd8 fffff80629c5483f : 0000000000000133 0000000000000001 0000000000001e00 fffff8062a705330 : nt!KeBugCheckEx
fffff80630e1dde0 fffff80629c54451 : 00004cb79f51085e fffff80629d2c6a1 ffffbb0704a73100 fffff80629c4fb78 : nt!KeAccumulateTicks+0x20f
fffff80630e1de50 fffff80629c5263a : fffff80627a0e200 fffffb857a897310 fffff80627a0e360 0000000000000c18 : nt!KiUpdateRunTime+0x61
fffff80630e1deb0 fffff80629c52426 : fffff8062a6f7dd0 fffff8062a6f7e80 0000000000000000 ffffbb070a2f4590 : nt!KeClockInterruptNotify+0x11a
fffff80630e1df40 fffff80629c21440 : fffff8062a6f7dd0 fffff80629d394cc fffff8062e7cb490 fffff80629e1834b : nt!HalpTimerClockIpiRoutine+0x16
fffff80630e1df70 fffff80629e185aa : fffffb857a897390 fffff8062a6f7dd0 00004cb66ff2daf4 0000000000000004 : nt!KiCallInterruptServiceRoutine+0xa0
fffff80630e1dfb0 fffff80629e18b77 : 000000001050ea86 0000000000000000 0000000000000000 0000000000000000 : nt!KiInterruptSubDispatchNoLockNoEtw+0xfa
fffffb857a897310 fffff80629d6511f : fffffb857a897500 fffff8062e77eae4 0000000000000005 0000000000000000 : nt!KiInterruptDispatchNoLockNoEtw+0x37
fffffb857a8974a0 fffff80629d31129 : fffff8062e7cb490 0000000000000010 fffff80627a05180 fffff80629c423fa : nt!KxWaitForLockChainValid+0x1f
fffffb857a8974d0 fffff8062f25d3b9 : ffffbb0704a59810 fffff8062a6231c0 ffffbb070a2f4590 ffffbb0707c00110 : nt!KeReleaseInStackQueuedSpinLock+0x79
fffffb857a897500 fffff8062e712312 : 0000000000000002 ffffbb0704a57010 fffff8062e7cb488 fffff8062f2349c0 : storport!StorPortNotification+0x289
fffffb857a8975e0 0000000000000002 : ffffbb0704a57010 fffff8062e7cb488 fffff8062f2349c0 ffffbb070388c240 : iaStorA+0x12312
fffffb857a8975e8 ffffbb0704a57010 : fffff8062e7cb488 fffff8062f2349c0 ffffbb070388c240 000000000000000c : 0x2
fffffb857a8975f0 fffff8062e7cb488 : fffff8062f2349c0 ffffbb070388c240 000000000000000c 0000000000000000 : 0xffffbb0704a57010 fffffb857a8975f8 fffff8062f2349c0 : ffffbb070388c240 000000000000000c 0000000000000000 fffff8062e711866 : iaStorA+0xcb488 fffffb857a897600 ffffbb070388c240 : 000000000000000c 0000000000000000 fffff8062e711866 0000000000000001 : iaStorA+0xb349c0 fffffb857a897608 000000000000000c : 0000000000000000 fffff8062e711866 0000000000000001 ffffbb0704a59810 : 0xffffbb070388c240
fffffb857a897610 0000000000000000 : fffff8062e711866 0000000000000001 ffffbb0704a59810 000000000000000c : 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