BUGCODE_NDIS_DRIVER (7c)

Question

Upon opening my laptop from sleep I was given this error.

I'm wondering if there's any way to fix it.

Heres the dump:

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

Loading Dump File [C:\Windows\Minidump\012421-78718-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 19041 MP (4 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS Personal
Edition build lab: 19041.1.amd64fre.vb_release.191206-1406
Machine Name:
Kernel base = 0xfffff802`29006000 PsLoadedModuleList = 0xfffff802`29c302f0
Debug session time: Sun Jan 24 14:03:11.289 2021 (UTC + 13:00)
System Uptime: 2 days 5:52:35.787
Loading Kernel Symbols
..

Press ctrl-c (cdb, kd, ntsd) or ctrl-break (windbg) to abort symbol loads that take too long.
Run !sym noisy before .reload to track down problems loading symbols.

.............................................................
................................................................
................................................................
............................
Loading User Symbols
Loading unloaded module list
......................................
For analysis of this file, run !analyze -v
nt!KeBugCheckEx:
fffff802`293fb780 48894c2408      mov     qword ptr [rsp+8],rcx ss:0018:ffffa304`10f60920=000000000000007c
3: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

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: 0000000000000023, NDIS_BUGCHECK_WATCHDOG_MINIPORT_OID
There was a timeout while delivering an OID request to a
miniport adapter.
Arg3: ffff9105e6e9cfa8, 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: 00000000fd010101, The OID code of the stuck request. Use !ndiskd.help
or look in a header file to decode it.

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

*** WARNING: Unable to verify checksum for win32k.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 13999

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on PAB

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.mSec
    Value: 48244

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

    Key  : Analysis.System
    Value: CreateObject

    Key  : WER.OS.Branch
    Value: vb_release

    Key  : WER.OS.Timestamp
    Value: 2019-12-06T14:06:00Z

    Key  : WER.OS.Version
    Value: 10.0.19041.1

ADDITIONAL_XML: 1

OS_BUILD_LAYERS: 1

BUGCHECK_CODE:  7c

BUGCHECK_P1: 25

BUGCHECK_P2: 23

BUGCHECK_P3: ffff9105e6e9cfa8

BUGCHECK_P4: fd010101

MODULE_NAME: wdiwifi

BLACKBOXBSD: 1 (!blackboxbsd)

BLACKBOXNTFS: 1 (!blackboxntfs)

BLACKBOXPNP: 1 (!blackboxpnp)

BLACKBOXWINLOGON: 1

CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffa304`10f60918 fffff802`2b7deabe     : 00000000`0000007c 00000000`00000025 00000000`00000023 ffff9105`e6e9cfa8 : nt!KeBugCheckEx
ffffa304`10f60920 fffff802`2b8a1eed     : ffff9105`e6e9cee0 fffff802`299ddef0 ffff9105`f7a30ee0 00000000`00000027 : ndis!ndisBugCheckEx+0x1e
ffffa304`10f60960 fffff802`2b8a1da5     : 00000000`033defbb ffff9105`f7a30ee0 fffff802`2b8649b0 ffff9105`e6e9cee0 : ndis!ndisReportTimeoutWaitingForExternalDriver+0xd5
ffffa304`10f609a0 fffff802`2b8a1ba8     : ffff9105`ef852ee0 ffff9105`ef852fa8 fffff802`2b8a2220 00000000`00000018 : ndis!ndisFindSomeoneToBlame+0x111
ffffa304`10f60a10 fffff802`2b8a2229     : 00000000`00000010 00000000`00050246 ffffa304`10f60a68 00000000`00000018 : ndis!NdisWatchdogState::ReportTimeout+0x68
ffffa304`10f60a40 fffff802`2922b975     : ffff9106`56e6d080 fffff802`2b331d60 ffff9105`dd4c8c80 00000000`00000000 : ndis!ndisWatchdogTimeoutWorkerRoutine+0x9
ffffa304`10f60a70 fffff802`2931de25     : ffff9106`56e6d080 00000000`00000080 ffff9105`dd505080 83838383`00000001 : nt!ExpWorkerThread+0x105
ffffa304`10f60b10 fffff802`29402dd8     : fffff802`26ba1180 ffff9106`56e6d080 fffff802`2931ddd0 83838383`83838383 : nt!PspSystemThreadStartup+0x55
ffffa304`10f60b60 00000000`00000000     : ffffa304`10f61000 ffffa304`10f5a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28

SYMBOL_NAME:  wdiwifi!MPWrapperOidRequest+0

IMAGE_NAME:  wdiwifi.sys

IMAGE_VERSION:  10.0.19041.1131

STACK_COMMAND:  .thread ; .cxr ; kb

BUCKET_ID_FUNC_OFFSET:  0

FAILURE_BUCKET_ID:  0x7C_VRF_MINI_StuckOID_FD010101_wdiwifi!MPWrapperOidRequest

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7830f3c7-240a-5683-36bc-4b5efe5d5d35}

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

Answer 1

Hi Liam

Most likely, one of those drivers is causing the device to not power up, or even powering up in a corrupted state after sleep and the best option is to re-install those drivers . . .

Answer 2

No, not at all. 

I would doubt I need to consider it considering it makes no sense that the Touchpad and WiFi card drivers manage to have my laptop bluescreen upon being awoken from sleep.