STATUS_NDIS_DEVICE_FAILED 0XC0230008 Fix (Windows)

You're mid-Zoom call, or halfway through a 40GB Steam download, and Windows drops the connection. Event Viewer logs STATUS_NDIS_DEVICE_FAILED (0XC0230008) and Device Manager shows a yellow bang on your NIC. Sometimes it recovers on its own after 30 seconds. Usually it doesn't. I've seen this hit Intel AX200 and AX201 Wi-Fi cards on Dell XPS 15s after a driver auto-update, and Realtek RTL8168 gigabit NICs on custom builds after Windows Update pushes a newer driver than the hardware likes. USB Wi-Fi dongles get it too when they brown out on a weak hub.

I know this error is infuriating because it looks like hardware death. It usually isn't.

What STATUS_NDIS_DEVICE_FAILED actually means

NDIS is the Network Driver Interface Specification — the layer between Windows and your network card's miniport driver. When the miniport detects something it can't recover from (a ring buffer overrun, a DMA fault, or a watchdog timeout), it signals NDIS that the device is toast. NDIS then surfaces 0XC0230008 to anything waiting on that adapter. The catch: the adapter often isn't physically dead. The driver just stopped trusting it.

Three things trigger it most often:

Driver mismatch after an update. Windows Update pushes 22.x.x.x over an OEM 21.x.x.x and the firmware handshake breaks.
Power management quirks. The NIC enters D3 low-power and can't get back to D0. Common on laptops with Modern Standby.
Failing USB or PCIe link. A cheap USB hub, a riser cable, or a dusty PCIe slot causes signal errors the driver reads as fatal.

The fix, in order

Work top to bottom. Don't skip ahead — step 1 solves it about 60% of the time.

Disable and re-enable the adapter. Open Device Manager (devmgmt.msc), expand Network adapters, right-click yours, Disable device, wait 5 seconds, Enable device. This forces NDIS to reinitialize the miniport without a full reset.
Roll the driver back. Right-click the adapter, Properties, Driver tab, Roll Back Driver. If it's greyed out, Windows replaced the OEM driver less than one cycle ago or you already rolled back once. Note the driver version and date before you do this.
Kill power management on the NIC. Same Properties dialog, Power Management tab. Uncheck "Allow the computer to turn off this device to save power." On laptops this single checkbox prevents most 0XC0230008 events during sleep/wake cycles.
Reset the network stack. Open an elevated Command Prompt or PowerShell and run:
```
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
shutdown /r /t 0
```
The reboot is mandatory — winsock reset doesn't take effect until you do.
Reinstall the driver cleanly. If the above didn't stick, remove every trace and install OEM drivers fresh (Intel, Realtek, or your laptop maker's build — not the generic Windows one). From an elevated prompt:
```
pnputil /enum-drivers
pnputil /delete-driver oem##.inf /uninstall /force
```
Swap oem##.inf for the actual published name of your NIC driver from the first command. Then reboot and install the OEM package. Grab it directly from Intel's site (Wireless drivers) or Realtek's download page — not the Microsoft Update Catalog.
Check physical layer. Desktop: reseat the card, blow out the slot, try a different PCIe slot. Laptop: reseat the M.2 Wi-Fi card if you're comfortable opening it. USB dongle: plug directly into the motherboard, not a hub, not a front-panel port.

If it still fails after all that

Check these, in this order:

Event Viewer details. Filter System log for source Netwtw10 (Intel), rtwlanu, or NDIS. The event payload sometimes names the specific fault — DMA error, firmware timeout, or wake failure.
BIOS/firmware. Dell, Lenovo, and HP have all shipped BIOS updates that fix Wi-Fi card enumeration bugs. Check your model's release notes for "network" or "WLAN" fixes.
Fast Startup. Disable it. Control Panel → Power Options → Choose what the power buttons do → Change settings that are currently unavailable. Uncheck "Turn on fast startup." This alone fixes a stubborn subset of NIC wake failures on Windows 10 22H2 and Windows 11 23H2.
Try a different adapter entirely. A $15 USB Wi-Fi dongle or a $25 PCIe NIC tells you fast whether the problem is Windows or the hardware. If the new card works fine, the old one is dying — replace it.

One last thing: if this error only shows up when you're on a docking station or specific USB hub, the problem is the dock, not your NIC. That trips up a lot of people who spend an afternoon reinstalling drivers for nothing.