Microsoft (R) Windows Debugger Version 10.0.25136.1001 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [D:\081322-12765-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 18362 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Edition build lab: 18362.1.amd64fre.19h1_release.190318-1202
Machine Name:
Kernel base = 0xfffff804`09400000 PsLoadedModuleList = 0xfffff804`09845f30
Debug session time: Sat Aug 13 17:33:23.778 2022 (UTC 8:00)
System Uptime: 0 days 1:37:23.844
Loading Kernel Symbols
...............................................................
................................................................
................................................................
......
Loading User Symbols
Loading unloaded module list
.....................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff804`095c3e40 48894c2408 mov qword ptr [rsp 8],rcx ss:0018:fffff804`0fc8cb10=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: 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: fffff80409971358, 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 ***
*** ***
*************************************************************************
KEY_VALUES_STRING: 1
Key : Analysis.CPU.mSec
Value: 9187
Key : Analysis.DebugAnalysisManager
Value: Create
Key : Analysis.Elapsed.mSec
Value: 54466
Key : Analysis.Init.CPU.mSec
Value: 1062
Key : Analysis.Init.Elapsed.mSec
Value: 15581
Key : Analysis.Memory.CommitPeak.Mb
Value: 90
Key : Bugcheck.Code.DumpHeader
Value: 0x133
Key : Bugcheck.Code.Register
Value: 0x133
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
FILE_IN_CAB: 081322-12765-01.dmp
BUGCHECK_CODE: 133
BUGCHECK_P1: 0
BUGCHECK_P2: 501
BUGCHECK_P3: 500
BUGCHECK_P4: fffff80409971358
DPC_TIMEOUT_TYPE: SINGLE_DPC_TIMEOUT_EXCEEDED
TRAP_FRAME: fffff8040fc84a80 -- (.trap 0xfffff8040fc84a80)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000001 rbx=0000000000000000 rcx=ffffa88159ce97c0
rdx=ffffa881522e8030 rsi=0000000000000000 rdi=0000000000000000
rip=fffff80409417ec0 rsp=fffff8040fc84c10 rbp=0000000000000000
r8=0000000000000000 r9=0000000000000000 r10=fffff80409417a20
r11=0000000000000000 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl nz na po nc
nt!KxWaitForSpinLockAndAcquire 0x30:
fffff804`09417ec0 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: Thunder.exe
STACK_TEXT:
fffff804`0fc8cb08 fffff804`095fa6ed : 00000000`00000133 00000000`00000000 00000000`00000501 00000000`00000500 : nt!KeBugCheckEx
fffff804`0fc8cb10 fffff804`09444477 : 00000cb2`9494b1b3 fffff804`075a6180 00000000`00000286 fffff804`0fc84a80 : nt!KeAccumulateTicks 0x1b801d
fffff804`0fc8cb70 fffff804`09eb8291 : 00000000`00000001 fffff804`09f25000 fffff804`0fc84b00 fffff804`09f250b0 : nt!KeClockInterruptNotify 0xc07
fffff804`0fc8cf30 fffff804`094f1845 : fffff804`09f25000 00000000`00000000 00000000`00000000 ffffc01d`2a3567a9 : hal!HalpTimerClockIpiRoutine 0x21
fffff804`0fc8cf60 fffff804`095c58ca : fffff804`0fc84b00 fffff804`09f25000 fffff804`2d01fcc0 00000000`00000000 : nt!KiCallInterruptServiceRoutine 0xa5
fffff804`0fc8cfb0 fffff804`095c5e37 : 00000000`00000070 ffffa881`56657da0 ffffa881`56657de0 fffff804`0f2eed8f : nt!KiInterruptSubDispatchNoLockNoEtw 0xfa
fffff804`0fc84a80 fffff804`09417ec0 : 00000000`00000000 ffffa881`4e0c40a0 fffff804`0fc84c60 00000000`00000000 : nt!KiInterruptDispatchNoLockNoEtw 0x37
fffff804`0fc84c10 fffff804`09417aa7 : ffffa881`59ce97c0 fffff804`075a6180 ffffa881`59ce9910 fffff804`2cf64ab5 : nt!KxWaitForSpinLockAndAcquire 0x30
fffff804`0fc84c40 fffff804`2cf655b5 : ffffa881`5c7e19d0 ffffa881`59ce97c0 ffffcb0d`a54e0001 ffffa881`00000001 : nt!KeAcquireSpinLockRaiseToDpc 0x87
fffff804`0fc84c70 fffff804`2cf69c59 : ffffa881`5c7e19d0 ffffa881`522e8030 00000000`00000000 fffff804`095c5924 : wdiwifi!CTxMgr::TxTargetDescDeinit 0x79
fffff804`0fc84cc0 fffff804`2cf698b7 : 00000000`00000000 ffffa881`522e8030 ffffa881`522e8030 00000000`00000001 : wdiwifi!CTxMgr::CompleteNdisNbl 0x81
fffff804`0fc84d20 fffff804`2cf6641a : 00000000`00000001 fffff804`2d01fcc0 fffff804`2d027040 00000000`00000000 : wdiwifi!CTxMgr::CompleteNBLs 0x5b
fffff804`0fc84d60 fffff804`2cf57b60 : 00000000`00000000 00000000`00000000 00000000`00000101 00000000`0000001f : wdiwifi!CTxMgr::TxTransferCompleteInd 0x68a
fffff804`0fc84e20 fffff804`2caf133b : ffffa881`4e0771d0 00000000`00000001 00000000`00000002 00000000`00000000 : wdiwifi!AdapterTxTransferCompleteInd 0x10
fffff804`0fc84e50 ffffa881`4e0771d0 : 00000000`00000001 00000000`00000002 00000000`00000000 00000000`00000000 : rtwlane 0x4133b
fffff804`0fc84e58 00000000`00000001 : 00000000`00000002 00000000`00000000 00000000`00000000 00000000`00000001 : 0xffffa881`4e0771d0
fffff804`0fc84e60 00000000`00000002 : 00000000`00000000 00000000`00000000 00000000`00000001 00000000`00000619 : 0x1
fffff804`0fc84e68 00000000`00000000 : 00000000`00000000 00000000`00000001 00000000`00000619 00000000`00000000 : 0x2
SYMBOL_NAME: wdiwifi!CTxMgr::TxTargetDescDeinit 79
MODULE_NAME: wdiwifi
IMAGE_NAME: wdiwifi.sys
IMAGE_VERSION: 10.0.18362.2158
STACK_COMMAND: .cxr; .ecxr ; kb
BUCKET_ID_FUNC_OFFSET: 79
FAILURE_BUCKET_ID: 0x133_DPC_wdiwifi!CTxMgr::TxTargetDescDeinit
OS_VERSION: 10.0.18362.1
BUILDLAB_STR: 19h1_release
OSPLATFORM_TYPE: x64
OSNAME: Windows 10
FAILURE_ID_HASH: {a996d487-243c-02e7-b45a-ebdb9a82680f}
Followup: MachineOwner
---------
0: kd> lmvm wdiwifi
Browse full module list
start end module name
fffff804`2cf50000 fffff804`2d03a000 wdiwifi # (pdb symbols) C:\ProgramData\Dbg\sym\WdiWiFi.pdb\817CF8AC2C8FD27DDCB6382180599D631\WdiWiFi.pdb
Loaded symbol image file: wdiwifi.sys
Mapped memory image file: C:\ProgramData\Dbg\sym\wdiwifi.sys\0C4FDCF5ea000\wdiwifi.sys
Image path: \SystemRoot\system32\DRIVERS\wdiwifi.sys
Image name: wdiwifi.sys
Browse all global symbols functions data
Image was built with /Brepro flag.
Timestamp: 0C4FDCF5 (This is a reproducible build file hash, not a timestamp)
CheckSum: 000EB010
ImageSize: 000EA000
File version: 10.0.18362.2158
Product version: 10.0.18362.2158
File flags: 0 (Mask 3F)
File OS: 40004 NT Win32
File type: 3.7 Driver
File date: 00000000.00000000
Translations: 0409.04b0
Information from resource tables:
CompanyName: Microsoft Corporation
ProductName: Microsoft® Windows® Operating System
InternalName: wdiwifi.sys
OriginalFilename: wdiwifi.sys
ProductVersion: 10.0.18362.2158
FileVersion: 10.0.18362.2158 (WinBuild.160101.0800)
FileDescription: WDI Driver Framework Driver
LegalCopyright: © Microsoft Corporation. All rights reserved.
0: kd> x /D /d wdiwifi!a*
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
fffff804`2d0174c0 wdiwifi!ActiveJobsList::`vftable' =
HiXKCIamDave,Iwillhelpyouwiththis.PleasechecktoseeifyourPCisproducinganyminidumpfiles,Iwillcheckthosetoseeiftheyprovideanyinsightintoapotentialcauseofthesystemcrashes.PleaseNote,IcannotdownloadfromBaiduCloudDrive,pleaseuseadifferentCloudServicefortheupload.OpenWindowsFileExplorer.NavigatetoC:\Windows\MinidumpCopyanyminidumpfilesontoyourDesktop,thenzipthoseup.UploadthezipfiletotheCloud(OneDrive,DropBox.etc.),thenchoosetosharethoseandgetasharelink.Thenpostthelinkheretothezipfile,sowecantakealookforyou.
https://1drv.ms/u/s!AsDWvp4cFn3WhSDnKhyq8ub1TVzg此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
XKC你好minidump文件表明是RealtekWiFi卡上的设备驱动程序导致蓝屏崩溃。转到制造商网站上您电脑的支持页面，然后从那里下载并安装他们推荐的RealtekWiFi(WLAN)卡设备驱动程序版本。___________________________________________________________________PowertotheDeveloper!MSIGV72-17.3",i7-8750H(HexCore),32GBDDR4,4GBGeForceGTX1050Ti,256GBNVMeM2,2TBHDD此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
感谢！电脑已恢复正常运行，怀疑Segatoolsv004修改了网卡参数导致一段时间后蓝屏。此是否有帮助？是否抱歉，这没有帮助。太棒了！感谢你的反馈。你对此的满意度如何?感谢你的反馈，它能帮助改进网站。你对此的满意度如何?感谢你的反馈。
