Fix ERROR_NDIS_REQUEST_ABORTED 0x8034000C

This error means the network driver stopped a request mid-flight. Usually a bad driver, cable, or power management setting. I'll show you the quick fix first.

Quick answer: Open Device Manager, find your network adapter, right-click it, select "Disable device", wait 10 seconds, then "Enable device". That's the first thing to try. Nine times out of ten, it clears the crash state.

Why you're seeing 0x8034000C

This error code is NDIS's way of saying "I gave up on that network request." NDIS is the network driver interface spec—the middleman between Windows and your network hardware. When it sees a request that's taking too long, or the hardware goes silent, it aborts.

I've seen this most often on laptops that wake from sleep and immediately try to connect to a network. The driver wakes up confused, the request times out, and you get the error. Also happens with cheap USB Wi-Fi dongles—had a client last month whose generic Realtek adapter threw this every time his microwave ran. True story.

Step-by-step fixes (try them in order)

1. Reset the network adapter

This is the equivalent of "turn it off and back on" for the network card. It forces NDIS to restart clean.

Press Win + X, select Device Manager.
Expand Network adapters.
Right-click your active adapter (usually Ethernet or Wi-Fi).
Select Disable device. Confirm if prompted.
Wait 10 seconds. Right-click again, choose Enable device.

2. Kill power management on the adapter

Windows loves to turn off network adapters to save power. NDIS hates that. This fix stops Windows from putting the adapter to sleep.

In Device Manager, right-click your network adapter, choose Properties.
Go to the Power Management tab.
Uncheck Allow the computer to turn off this device to save power.
Click OK.

I've seen this single setting fix the error on Dell and HP laptops that randomly drop connections after being idle.

3. Update or roll back the driver

A bad driver update from Windows Update is a common culprit. If the error started after an update, roll back. If you're on an old driver, update.

In Device Manager, right-click the adapter, choose Properties.
Go to the Driver tab.
If Roll Back Driver is available, click it and restart.
Otherwise, click Update Driver → Browse my computer for drivers → Let me pick from a list → try an older or newer version.

4. Run the network troubleshooter (skip if you're in a hurry)

Windows has a built-in troubleshooter that actually works for this specific error. It resets the Winsock catalog and TCP/IP stack.

Press Win + I to open Settings.
Go to System → Troubleshoot → Other troubleshooters.
Find Network Adapter, click Run.
Follow the prompts. Let it run fully.

If none of the above works

Try these more aggressive fixes:

Reset Winsock from command line

Open Command Prompt as Administrator. Run these commands in order:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Restart your PC afterward. This cleared a persistent 0x8034000C on a Windows 11 machine that had been through three driver swaps.

Replace the network cable or USB adapter

If you're on Ethernet, try a different cable. I've seen a slightly bent pin in a RJ45 connector cause intermittent NDIS aborts. For Wi-Fi, try a different USB port or replace the dongle—some cheap Realtek chipsets just can't handle certain routers.

Update the BIOS or firmware

Less common, but I had a Lenovo ThinkPad that threw this error until a BIOS update fixed a power state bug. Check your motherboard or laptop manufacturer's support site.

Prevention tips

Lock down power management on all network adapters after a fresh Windows install. Do it first, never think about it again.
Avoid generic Windows Update drivers for network hardware. Always download the driver directly from the chipset manufacturer (Intel, Realtek, Broadcom) or your PC maker.
Restart your router and modem once a month. DHCP lease conflicts can cause NDIS to hang.
Don't use USB extension cables for Wi-Fi dongles. Signal degradation causes timeouts, and NDIS gives up fast.

This error is almost always a driver or power management issue. If you run through these steps and still see it, you might have faulty hardware—test the adapter on another PC to confirm.