Fix NDIS Bad Characteristics Error 0x80340005 on Windows

You're staring at a blue screen with 0x80340005 and the message ERROR_NDIS_BAD_CHARACTERISTICS — an invalid characteristics table was used. This usually hits right after you install a new network adapter driver, update Windows, or plug in a USB Wi-Fi dongle that claims to be 'plug and play'. It's not random. It's a driver that NDIS.sys can't parse because the table describing its features is missing a field, has a wrong version number, or points to garbage memory.

Root Cause: What's Actually Wrong

NDIS (Network Driver Interface Specification) expects every driver to register with a proper NDIS_MINIPORT_CHARACTERISTICS structure. That structure contains pointers to functions like MiniportInitialize and MiniportSendNetBufferLists. If the driver's version doesn't match what NDIS.sys expects — for example, you installed a Win8.1 driver on Windows 10 22H2 — the structure version check fails. Or the driver might be half-baked: corrupted download, incompatible chipset, or a beta release that didn't fill in all required fields. The result is that NDIS refuses to load the driver and throws 0x80340005.

I've seen this most often with Realtek gigabit NICs, Intel PRO/1000 adapters, and cheap USB Wi-Fi adapters from brands you've never heard of. The culprit is almost always a mismatched driver version or a Windows Update that shoved a generic driver over your OEM vendor's specific one.

Fix: Step-by-Step

Step 1: Identify the offending driver

Open Device Manager (right-click Start -> Device Manager). Expand Network adapters. Look for any device with a yellow exclamation mark. That's your problem. Right-click it, select Properties, go to the Details tab, and choose Hardware IDs from the dropdown. Copy the value (something like PCI\VEN_10EC&DEV_8168). This helps you find the right driver later.

Step 2: Remove the current driver completely

Don't just uninstall the device. That leaves the .inf files behind. Instead:

1. In Device Manager, right-click the problem adapter and select Uninstall device.
2. Check the box Delete the driver software for this device if it appears. If it's grayed out, proceed to step 3.
3. Now use a tool like DriverStore Explorer (free, open source) to scan for leftover driver packages matching that hardware ID. Delete them. Or do it manually: run pnputil /enum-drivers in an admin command prompt, find the published name (e.g., oem123.inf), then run pnputil /delete-driver oem123.inf.

This ensures no old, broken driver files remain.

Step 3: Get the correct driver from the vendor

Do not let Windows Update decide. Go to the network adapter manufacturer's support site. For Realtek, download directly from Realtek's site, not a third-party driver updater. For Intel, use the Intel Driver & Support Assistant. For a USB dongle, check the chipset maker (like Ralink, Mediatek, or Atheros) and grab the latest WHQL driver for your exact Windows version (10, 11, 64-bit or 32-bit).

Step 4: Install the driver offline

Disconnect from the internet (disable Wi-Fi, unplug Ethernet). Then run the installer. If the installer fails, use Device Manager's Update driver -> Browse my computer for drivers -> point to the folder where you extracted the driver files. Make sure to check Include subfolders.

Step 5: Reboot and test

Restart the machine. If you get the error again, you've got a different problem.

What to Check If It Still Fails

• BIOS settings: Some OEMs disable built-in NICs when a PCIe card is installed. In BIOS, make sure the onboard LAN is enabled.
• Windows version mismatch: If you're on Windows 11 24H2, a driver meant for Windows 10 2004 may fail. Check the driver's inf file for LayoutFile version — you can open it with Notepad.
• Corrupted NDIS.sys: Run sfc /scannow and dism /online /cleanup-image /restorehealth from an admin command prompt. Rarely needed, but it's free.
• Bad hardware: If none of the above works, try a different PCIe slot or a known-good USB Wi-Fi adapter. I've seen NICs that went bad after a power surge and threw this exact error.
• Third-party firewall or VPN: Uninstall any antivirus with network filtering (like Norton, McAfee, or Webroot) or VPN client that hooks into NDIS. Reboot and test. If that fixes it, reinstall the latest version of that software.

That's it. Nine times out of ten, a clean driver install with full removal of the old driver resolves 0x80340005. Don't waste time with registry hacks or sfc alone — they rarely fix a bad characteristics table.