You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After a few hours running in system, We've got a BSOD. Can you guide me to how to fix it plz ?!
this is the result of !analyze -v
BUGCODE_NDIS_DRIVER (7c)
The operating system detected an error in a networking driver.
The BUGCODE_NDIS_DRIVER bugcheck identifies problems in network drivers.
Often, the defect is caused by a NDIS miniport driver. You can get a complete
list of NDIS miniport drivers using !ndiskd.netadapter. You can get a
big-picture overview of the network stack with !ndiskd.netreport.
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: 0000000000000011, NDIS_BUGCHECK_WATCHDOG_FILTER_PAUSE
There was a timeout while pausing a filter driver.
Arg3: ffffd78e90fb4fa8, 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: 0000000000000000
Hi & Tnx for your code
After a few hours running in system, We've got a BSOD. Can you guide me to how to fix it plz ?!
this is the result of !analyze -v
BUGCODE_NDIS_DRIVER (7c)
The operating system detected an error in a networking driver.
The BUGCODE_NDIS_DRIVER bugcheck identifies problems in network drivers.
Often, the defect is caused by a NDIS miniport driver. You can get a complete
list of NDIS miniport drivers using !ndiskd.netadapter. You can get a
big-picture overview of the network stack with !ndiskd.netreport.
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: 0000000000000011, NDIS_BUGCHECK_WATCHDOG_FILTER_PAUSE
There was a timeout while pausing a filter driver.
Arg3: ffffd78e90fb4fa8, 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: 0000000000000000
Debugging Details:
KEY_VALUES_STRING: 1
PROCESSES_ANALYSIS: 1
SERVICE_ANALYSIS: 1
STACKHASH_ANALYSIS: 1
TIMELINE_ANALYSIS: 1
DUMP_CLASS: 1
DUMP_QUALIFIER: 0
BUILD_VERSION_STRING: 18362.1.amd64fre.19h1_release.190318-1202
DUMP_TYPE: 0
BUGCHECK_P1: 25
BUGCHECK_P2: 11
BUGCHECK_P3: ffffd78e90fb4fa8
BUGCHECK_P4: 0
MODULE_NAME: wfplwfs
FAULTING_IP:
wfplwfs!LwfLowerPause+0
fffff805`081a61f0 48895c2408 mov qword ptr [rsp+8],rbx
CPU_COUNT: 4
CPU_MHZ: a22
CPU_VENDOR: GenuineIntel
CPU_FAMILY: 6
CPU_MODEL: 3e
CPU_STEPPING: 4
CPU_MICROCODE: 6,3e,4,0 (F,M,S,R) SIG: 427'00000000 (cache) 427'00000000 (init)
DEFAULT_BUCKET_ID: WIN8_DRIVER_FAULT
BUGCHECK_STR: 0x7C
PROCESS_NAME: System
CURRENT_IRQL: 0
ANALYSIS_SESSION_TIME: 12-14-2020 12:28:48.0744
ANALYSIS_VERSION: 10.0.18362.1 amd64fre
STACK_TEXT:
ffff9f88
ad213c38 fffff805
05aba942 : 0000000000000025 00000000
00000003 ffff9f88ad213da0 fffff805
058709f0 : nt!DbgBreakPointWithStatusffff9f88
ad213c40 fffff805
05aba032 : 0000000000000003 ffff9f88
ad213da0 fffff805059e7a60 00000000
0000007c : nt!KiBugCheckDebugBreak+0x12ffff9f88
ad213ca0 fffff805
059d3487 : 0000000000000000 00000000
00000007 ffffd78e8a80c1a0 fffff805
05b3af6b : nt!KeBugCheck2+0x952ffff9f88
ad2143a0 fffff805
07c4e27e : 000000000000007c 00000000
00000025 0000000000000011 ffffd78e
90fb4fa8 : nt!KeBugCheckEx+0x107ffff9f88
ad2143e0 fffff805
07cf4121 : 0000000000000000 fffff805
0618b3f0 ffffd78e90fb4ee0 00000000
000000a8 : ndis!ndisBugCheckEx+0x1effff9f88
ad214420 fffff805
07cf3ff1 : 0000000003bfefbf ffffd78e
90fb4ee0 fffff80507cb6918 00000000
00000000 : ndis!ndisReportTimeoutWaitingForExternalDriver+0xd5ffff9f88
ad214460 fffff805
07cf43e9 : 0000000000040b28 ffffd78e
90fb4fa8 0000000000000011 ffff9f88
ad214558 : ndis!ndisFindSomeoneToBlame+0x125ffff9f88
ad2144d0 fffff805
07cf3e6e : ffffd78e90fb4ee0 ffff9f88
ad2145d9 ffffd78e8b6b2d30 00000000
00010286 : ndis!ndisWaitForExternalDriver+0x75ffff9f88
ad214500 fffff805
07cf4342 : ffffd78e90fb4ee0 fffff805
07cf4314 0000000000000010 00000000
00010246 : ndis!NdisWatchdogState::WaitSynchronously+0x6effff9f88
ad214540 fffff805
07d06a23 : ffffd78e90fb4ee0 ffff9f88
ad2145d9 ffffd78e8b6b2d30 ffffd78e
8b6b2ca0 : ndis!ndisWaitForEventThenDisarmWatchdog+0x2effff9f88
ad214580 fffff805
07cdb830 : ffffe78746c4efa0 ffffe787
46c4efa0 ffffd78e8a80d5a8 ffffd78e
8b6b2ca0 : ndis!ndisPauseFilterInner+0x573bffff9f88
ad214640 fffff805
07cd166a : 0000000000000000 ffff9f88
ad214790 ffffd78e8a80d590 00000000
00000000 : ndis!ndisPauseFilter+0xb4ffff9f88
ad214690 fffff805
07cd13c0 : ffffd78e8a80c1a0 ffffd78e
8a80c1a0 ffffd78e8a80d608 ffffd78e
8a80d590 : ndis!Ndis::BindEngine::Iterate+0x202ffff9f88
ad214810 fffff805
07ccc409 : ffffd78e8a80d590 00000000
00000000 0000000000000000 00000000
00000000 : ndis!Ndis::BindEngine::UpdateBindings+0x98ffff9f88
ad214860 fffff805
07ccc2c8 : ffffd78e8a80d590 00000000
00000000 ffffd78e8a80d590 fffff805
07ccc8e6 : ndis!Ndis::BindEngine::DispatchPendingWork+0x75ffff9f88
ad214890 fffff805
07c24728 : ffffd78e8a80c1a0 00000000
00000002 0000000000000020 00000000
00000000 : ndis!Ndis::BindEngine::ApplyBindChanges+0x54ffff9f88
ad2148e0 fffff805
07be280d : ffffd78e8a80c1a0 00000000
00000000 ffffd78e8a80cd48 ffffd78e
8a80c1a0 : ndis!ndisPrepForLowPowerCommon+0x41eecffff9f88
ad2149d0 fffff805
07be3246 : ffffd78e8a80c1a0 00000000
00000000 ffffd78e970f4e10 fffff805
07bd6755 : ndis!ndisPrepForLowPower+0x1dffff9f88
ad214a20 fffff805
07be3931 : 0000000000000000 ffffd78e
00000004 ffffd78e970f4e10 ffffd78e
8a80c1a0 : ndis!ndisSetSystemPower+0x19effff9f88
ad214aa0 fffff805
07be9e84 : ffffd78e970f4e10 ffffd78e
8690ed30 ffffd78e970f4f28 ffffd78e
8a80c1a0 : ndis!ndisSetPower+0x109ffff9f88
ad214b00 fffff805
0598b02f : ffffd78e8a80c050 ffff9f88
ad214be0 0000000000000000 ffffd78e
970f4e10 : ndis!ndisPowerDispatch+0x114ffff9f88
ad214b60 fffff805
0587cce5 : 0000000000000000 ffffd78e
86939080 fffff8050598ae50 00000000
00000000 : nt!PopIrpWorker+0x1dfffff9f88
ad214c10 fffff805
059da9ca : ffffa38117580180 ffffd78e
86939080 fffff8050587cc90 00000000
00000000 : nt!PspSystemThreadStartup+0x55ffff9f88
ad214c60 00000000
00000000 : ffff9f88ad215000 ffff9f88
ad20f000 0000000000000000 00000000
00000000 : nt!KiStartSystemThread+0x2aTHREAD_SHA1_HASH_MOD_FUNC: fb82d6835acc43782ce2d8cc87312c71a062da7a
THREAD_SHA1_HASH_MOD_FUNC_OFFSET: e9f541403998cd88a52fb202de8d71d9d54c78c0
THREAD_SHA1_HASH_MOD: ee7c730e4531afb6d09bc1abcea8a663b1fba34b
FOLLOWUP_IP:
wfplwfs!LwfLowerPause+0
fffff805`081a61f0 48895c2408 mov qword ptr [rsp+8],rbx
FAULT_INSTR_CODE: 245c8948
SYMBOL_NAME: wfplwfs!LwfLowerPause+0
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: wfplwfs.sys
DEBUG_FLR_IMAGE_TIMESTAMP: 60902cbb
STACK_COMMAND: .thread ; .cxr ; kb
BUCKET_ID_FUNC_OFFSET: 0
FAILURE_BUCKET_ID: 0x7C_VRF_FILT_Pause_wfplwfs!LwfLowerPause
BUCKET_ID: 0x7C_VRF_FILT_Pause_wfplwfs!LwfLowerPause
PRIMARY_PROBLEM_CLASS: 0x7C_VRF_FILT_Pause_wfplwfs!LwfLowerPause
TARGET_TIME: 2020-12-14T08:55:59.000Z
OSBUILD: 18362
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: unknown_date
BUILDDATESTAMP_STR: 190318-1202
BUILDLAB_STR: 19h1_release
BUILDOSVER_STR: 10.0.18362.1.amd64fre.19h1_release.190318-1202
ANALYSIS_SESSION_ELAPSED_TIME: d54
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x7c_vrf_filt_pause_wfplwfs!lwflowerpause
FAILURE_ID_HASH: {fef43b4d-fb67-4c46-c742-ecef5a38ee06}
Followup: MachineOwner
The text was updated successfully, but these errors were encountered: