Windows 10: BUGCODE_NDIS_DRIVER 7c

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:

[COLOR=rgba30, 30, 30, 1]Microsoft R Windows Debugger Version 10.0.20153.1000 AMD64Copyright 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 LocationDeferred srv*Symbol search path is: srv*Executable search path is: Windows 10 Kernel Version 19041 MP 4 procs Free x64Product: WinNt, suite: TerminalServer SingleUserTS PersonalEdition build lab: 19041.1.amd64fre.vb_release.191206-1406Machine Name:Kernel base = 0xfffff802`29006000 PsLoadedModuleList = 0xfffff802`29c302f0Debug session time: Sun Jan 24 14:03:11.289 2021 UTC + 13:00System Uptime: 2 days 5:52:35.787Loading 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 SymbolsLoading unloaded module list......................................For analysis of this file, run [/COLOR][COLOR=rgba0, 0, 255, 1]!analyze -v[/COLOR][COLOR=rgba30, 30, 30, 1]nt!KeBugCheckEx:fffff802`293fb780 48894c2408 mov qword ptr [rsp+8],rcx ss:0018:ffffa304`10f60920=000000000000007c3: kd> !analyze -v******************************************************************************** ** Bugcheck Analysis ** ********************************************************************************BUGCODE_NDIS_DRIVER 7cThe 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 completelist of NDIS miniport drivers using !ndiskd.netadapter. You can get abig-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.sysKEY_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.1ADDITIONAL_XML: 1OS_BUILD_LAYERS: 1BUGCHECK_CODE: 7cBUGCHECK_P1: 25BUGCHECK_P2: 23BUGCHECK_P3: ffff9105e6e9cfa8BUGCHECK_P4: fd010101MODULE_NAME: [/COLOR][COLOR=rgba0, 0, 255, 1]wdiwifi[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXBSD: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxbsd[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXNTFS: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxntfs[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXPNP: 1 [/COLOR][COLOR=rgba0, 0, 255, 1]!blackboxpnp[/COLOR][COLOR=rgba30, 30, 30, 1]BLACKBOXWINLOGON: 1CUSTOMER_CRASH_COUNT: 1PROCESS_NAME: SystemSTACK_TEXT: ffffa304`10f60918 fffff802`2b7deabe : 00000000`0000007c 00000000`00000025 00000000`00000023 ffff9105`e6e9cfa8 : nt!KeBugCheckExffffa304`10f60920 fffff802`2b8a1eed : ffff9105`e6e9cee0 fffff802`299ddef0 ffff9105`f7a30ee0 00000000`00000027 : ndis!ndisBugCheckEx+0x1effffa304`10f60960 fffff802`2b8a1da5 : 00000000`033defbb ffff9105`f7a30ee0 fffff802`2b8649b0 ffff9105`e6e9cee0 : ndis!ndisReportTimeoutWaitingForExternalDriver+0xd5ffffa304`10f609a0 fffff802`2b8a1ba8 : ffff9105`ef852ee0 ffff9105`ef852fa8 fffff802`2b8a2220 00000000`00000018 : ndis!ndisFindSomeoneToBlame+0x111ffffa304`10f60a10 fffff802`2b8a2229 : 00000000`00000010 00000000`00050246 ffffa304`10f60a68 00000000`00000018 : ndis!NdisWatchdogState::ReportTimeout+0x68ffffa304`10f60a40 fffff802`2922b975 : ffff9106`56e6d080 fffff802`2b331d60 ffff9105`dd4c8c80 00000000`00000000 : ndis!ndisWatchdogTimeoutWorkerRoutine+0x9ffffa304`10f60a70 fffff802`2931de25 : ffff9106`56e6d080 00000000`00000080 ffff9105`dd505080 83838383`00000001 : nt!ExpWorkerThread+0x105ffffa304`10f60b10 fffff802`29402dd8 : fffff802`26ba1180 ffff9106`56e6d080 fffff802`2931ddd0 83838383`83838383 : nt!PspSystemThreadStartup+0x55ffffa304`10f60b60 00000000`00000000 : ffffa304`10f61000 ffffa304`10f5a000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28SYMBOL_NAME: wdiwifi!MPWrapperOidRequest+0IMAGE_NAME: wdiwifi.sysIMAGE_VERSION: 10.0.19041.1131STACK_COMMAND: .thread ; .cxr ; kbBUCKET_ID_FUNC_OFFSET: 0FAILURE_BUCKET_ID: 0x7C_VRF_MINI_StuckOID_FD010101_wdiwifi!MPWrapperOidRequestOS_VERSION: 10.0.19041.1BUILDLAB_STR: vb_releaseOSPLATFORM_TYPE: x64OSNAME: Windows 10FAILURE_ID_HASH: {7830f3c7-240a-5683-36bc-4b5efe5d5d35}Followup: MachineOwner---------[/COLOR]

:)

 

BUGCODE_NDIS_DRIVER

Since the issue is related to your network adapter driver, we suggest installing the latest network adapter driver from the device manufacturer's support page. If you're unable to connect to the Internet through Wi-Fi, try a wired connection using an Ethernet
cable. If you're still unable to connect, download the network adapter driver using a different device, and then install it to the device that is having the
BUGCODE_NDIS_DRIVER issue.

We'll be waiting for the results.

 

BUGCODE_NDIS_DRIVER

Hello,

BUGCODE_NDIS_DRIVER can be caused by a faulty or an incompatible device driver. It would be great if you can give us more information regarding your issue. Please answer the questions below.

• When did the issue start?
• Did you recently make any hardware changes to your PC?
• What troubleshooting steps have you done so far?
• Have you installed the latest update for Windows 10?
• What is the current version and build of your Windows 10 PC?

To check for the latest update for Windows 10, click the
Start button, go to Settings >
Update & security > Windows Update, and then select
Check for updates. Click the
Start button, type About your PC, and then press
Enter to find out the version and build number of your Windows 10 PC.

For now, we suggest running the Hardware and Devices Troubleshooter to diagnose and fix your PC for any driver issues. Make sure to temporarily disable your security software before running the troubleshooter to avoid software conflicts.
You can access the troubleshooter from this
link, under Find and fix problems with devices and hardware.

We're looking forward to your response.

 

My PC keeps crashing and giving me the code BUGCODE_NDIS_DRIVER

Hello,

This type of issue associated with the error code BUGCODE_NDIS_DRIVER can be related to driver failures. As a first troubleshooting step, we suggest checking the drivers and update it with the latest version. Feel free to check out
this link for steps on how to update drivers in Windows 10.

If the automatic update fails, or the issue is still unresolved, the next step that we can suggest is to uninstall and reinstall them manually, particularly the graphics card driver. Check out this
article from
JMH3143 for steps and more information.

Let us know the outcome.