windbg analyze -v 分析结果

NDIS-20190617-2027.dmp

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


Loading Dump File [C:\Windows\LiveKernelReports\NDIS-20190617-2027.dmp]
Kernel Bitmap Dump File: Kernel address space is available, User address space may not be available.

Symbol search path is: srv*
Executable search path is:
Windows 10 Kernel Version 17763 MP (16 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 17763.1.amd64fre.rs5_release.180914-1434
Machine Name:
Kernel base = 0xfffff807`6fe9e000 PsLoadedModuleList = 0xfffff807`702b95d0
Debug session time: Mon Jun 17 20:27:49.921 2019 (UTC + 8:00)
System Uptime: 0 days 10:33:18.948
Loading Kernel Symbols
...............................................................
................................................................
................................................................
.....
Loading User Symbols

Loading unloaded module list
.............
For analysis of this file, run !analyze -v
nt!IopLiveDumpEndMirroringCallback+0x7e:
fffff807`704179ce 488d8e00010000 lea rcx,[rsi+100h]
0: kd> !analyze -v
*******************************************************************************
* *
* Bugcheck Analysis *
* *
*******************************************************************************

BUGCODE_NDIS_DRIVER_LIVE_DUMP (15e)
The operating system recovered from an error in a networking driver.
NDIS has detected and recovered from a serious problem in another network
driver. Although the system was not halted, this problem may later cause
connectivity problems or a fatal bugcheck.
Arguments:
Arg1: 0000000000000025, NDIS_BUGCHECK_WATCHDOG
An attempt to manage the network stack has taken too
long. When NDIS calls out into other drivers, NDIS
starts a watchdog timer to ensure the call completes
promptly. If the call takes too long, NDIS injects a
bugcheck.
This can be caused by a simple deadlock -- look with
"!stacks 2 ndis!" or similar to see if any threads
look suspicious. Pay special attention to the
PrimaryThread from the NDIS_WATCHDOG_TRIAGE_BLOCK.
This can be caused by lost NBLs, in which case
!ndiskd.pendingnbls may help. Check for OIDs that are
stuck using !ndiskd.oid.
Arg2: 0000000000000023, NDIS_BUGCHECK_WATCHDOG_MINIPORT_OID
There was a timeout while delivering an OID request to a
miniport adapter.
Arg3: ffffdf83d4075c78, Cast to ndis!_NDIS_WATCHDOG_TRIAGE_BLOCK. Interesting fields:
* StartTime shows what time the operation started,
in 100ns units, as returned by KeQueryInterruptTime.
* TimeoutMilliseconds shows how long NDIS waited, at a
minimum, before triggering this bugcheck.
Measured in milliseconds.
* TargetObject is a handle to the protocol, filter,
or miniport that NDIS is waiting on. Use with
!ndiskd.protocol, !ndiskd.filter, or !ndiskd.miniport.
* PrimaryThread is the thread on which NDIS initiated
the operation. Usually this is the first place to
look, although the thread may have gone elsewhere
if the operation is being handled asynchronously.
Arg4: 000000000d010310, The OID code of the stuck request. Use !ndiskd.help
or look in a header file to decode it.

Debugging Details:
------------------


KEY_VALUES_STRING: 1

Key : Analysis.CPU.Sec
Value: 2

Key : Analysis.Elapsed.Sec
Value: 67

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


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1


DUMP_CLASS: 1

DUMP_QUALIFIER: 401

BUILD_VERSION_STRING: 17763.1.amd64fre.rs5_release.180914-1434

SYSTEM_MANUFACTURER: BIOSTAR Group

SYSTEM_PRODUCT_NAME: B350GT5

SYSTEM_SKU: None

BIOS_VENDOR: American Megatrends Inc.

BIOS_VERSION: 5.12

BIOS_DATE: 03/14/2017

BASEBOARD_MANUFACTURER: BIOSTAR Group

BASEBOARD_PRODUCT: B350GT5

DUMP_FILE_ATTRIBUTES: 0x10
Live Generated Dump

DUMP_TYPE: 1

BUGCHECK_P1: 25

BUGCHECK_P2: 23

BUGCHECK_P3: ffffdf83d4075c78

BUGCHECK_P4: d010310

MODULE_NAME: wdiwifi

FAULTING_IP:
wdiwifi!MPWrapperOidRequest+0
fffff807`b99eca90 48895c2408 mov qword ptr [rsp+8],rbx

CPU_COUNT: 10

CPU_MHZ: bb2

CPU_VENDOR: AuthenticAMD

CPU_FAMILY: 17

CPU_MODEL: 1

CPU_STEPPING: 1

DEFAULT_BUCKET_ID: WINBLUE_LIVE_KERNEL_DUMP

BUGCHECK_STR: 0x15E

PROCESS_NAME: System

CURRENT_IRQL: 0

ANALYSIS_SESSION_HOST: VREADY

ANALYSIS_SESSION_TIME: 06-17-2019 21:16:31.0299

ANALYSIS_VERSION: 10.0.18869.1002 amd64fre

STACK_TEXT:
ffff9e8a`053025e0 fffff807`704055e2 : ffffffff`ffffffff 00000000`00000011 00000000`00000000 00000000`00000011 : nt!IopLiveDumpEndMirroringCallback+0x7e
ffff9e8a`05302630 fffff807`70417647 : 00000000`00000000 fffff807`00000000 ffffdf83`00000001 00000000`00000001 : nt!MmDuplicateMemory+0x26e
ffff9e8a`053026c0 fffff807`706bf80d : ffffdf83`e59c29a0 ffffdf83`e59c29a0 ffff9e8a`05302988 ffff9e8a`05302988 : nt!IopLiveDumpCaptureMemoryPages+0x7f
ffff9e8a`05302780 fffff807`706b30e2 : 00000000`00000000 ffffb70a`14dd4b90 ffffb70a`0e4c69b0 ffffb70a`14dd4b90 : nt!IoCaptureLiveDump+0x289
ffff9e8a`05302920 fffff807`706b3800 : ffffffff`80003a8c 00000000`00000000 00000000`00000000 00000000`0000015e : nt!DbgkpWerCaptureLiveFullDump+0x13a
ffff9e8a`05302980 fffff807`706b2f31 : 00000000`00000002 00000000`00000000 fffff807`a5396270 00000000`0000ffff : nt!DbgkpWerProcessPolicyResult+0x30
ffff9e8a`053029b0 fffff807`a535fbd1 : ffffdf83`d402a1a0 00000000`0000004c 00000000`00000023 ffffdf83`d4075c78 : nt!DbgkWerCaptureLiveKernelDump+0x1a1
ffff9e8a`05302a00 fffff807`a5414480 : 00000000`00000000 fffff807`a53d1d02 ffff9e8a`05302ac0 00000000`00000000 : ndis!ndisMLiveBugCheck+0x45
ffff9e8a`05302a60 fffff807`a5414309 : ffffdf83`e04e0040 ffffdf83`e23b1590 fffff807`a53b08d0 ffffdf83`d4075bb0 : ndis!ndisReportTimeoutWaitingForExternalDriver+0x108
ffff9e8a`05302aa0 fffff807`a54140f3 : 00000000`00000007 ffffdf83`df4b0ae8 fffff807`a5414740 00000000`00000000 : ndis!ndisFindSomeoneToBlame+0x111
ffff9e8a`05302b10 fffff807`a5414749 : ffffdf83`e04e0040 ffffdf83`cc487ce0 ffffdf83`e83c7110 ffffdf83`cc450ab0 : ndis!NdisWatchdogState::ReportTimeout+0x9f
ffff9e8a`05302b40 fffff807`6ff12bfa : ffffdf83`cc487ce0 00000058`00000000 00000000`00150000 ffff9e8a`00000000 : ndis!ndisWatchdogTimeoutWorkerRoutine+0x9
ffff9e8a`05302b70 fffff807`6fedbb35 : ffffdf83`e04e0040 ffffdf83`cc479040 ffffdf83`e04e0040 45005c8b`b07b148c : nt!ExpWorkerThread+0x16a
ffff9e8a`05302c10 fffff807`7005935c : ffff8a80`03c80180 ffffdf83`e04e0040 fffff807`6fedbae0 646e6572`3d657079 : nt!PspSystemThreadStartup+0x55
ffff9e8a`05302c60 00000000`00000000 : ffff9e8a`05303000 ffff9e8a`052fd000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x1c


THREAD_SHA1_HASH_MOD_FUNC: 7d26f065cc5f7a9b1231e38ffe4e9d4e6035a268

THREAD_SHA1_HASH_MOD_FUNC_OFFSET: 63bbffb191dee5b101e73f560a183a777d9f68f0

THREAD_SHA1_HASH_MOD: a1a368112b910824492aa83986113e0354351681

FOLLOWUP_IP:
wdiwifi!MPWrapperOidRequest+0
fffff807`b99eca90 48895c2408 mov qword ptr [rsp+8],rbx

FAULT_INSTR_CODE: 245c8948

SYMBOL_NAME: wdiwifi!MPWrapperOidRequest+0

FOLLOWUP_NAME: MachineOwner

IMAGE_NAME: wdiwifi.sys

DEBUG_FLR_IMAGE_TIMESTAMP: 63bdaa31

STACK_COMMAND: .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET: 0

FAILURE_BUCKET_ID: LKD_0x15E_MINI_StuckOID_D010310_wdiwifi!MPWrapperOidRequest

BUCKET_ID: LKD_0x15E_MINI_StuckOID_D010310_wdiwifi!MPWrapperOidRequest

PRIMARY_PROBLEM_CLASS: LKD_0x15E_MINI_StuckOID_D010310_wdiwifi!MPWrapperOidRequest

TARGET_TIME: 2019-06-17T12:27:49.000Z

OSBUILD: 17763

OSSERVICEPACK: 0

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK: 272

PRODUCT_TYPE: 1

OSPLATFORM_TYPE: x64

OSNAME: Windows 10

OSEDITION: Windows 10 WinNt TerminalServer SingleUserTS

OS_LOCALE:

USER_LCID: 0

OSBUILD_TIMESTAMP: 2021-07-31 23:45:35

BUILDDATESTAMP_STR: 180914-1434

BUILDLAB_STR: rs5_release

BUILDOSVER_STR: 10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME: 10749

ANALYSIS_SOURCE: KM

FAILURE_ID_HASH_STRING: km:lkd_0x15e_mini_stuckoid_d010310_wdiwifi!mpwrapperoidrequest

FAILURE_ID_HASH: {f7bac0b7-383a-20b5-f18d-23a920cd884e}

Followup: MachineOwner
---------