Network Adapter drivers
Wireless and wired network adapter drivers.
You might also need
Network Adapter drivers we cover
What does a network adapter driver do?
A network adapter driver is written to the Network Driver Interface Specification, so Windows always calls it as an NDIS miniport no matter what silicon is underneath. This is the abstraction that lets the same TCP/IP stack ride over a wired controller, a wireless card, a cellular modem, or a virtual switch. The miniport presents send and receive rings to the operating system and moves frames between those rings and the hardware's DMA buffers.
Much of the driver's value is in hardware offloads that keep the processor free. It advertises checksum offload so the adapter computes IP, TCP, and UDP checksums instead of the CPU, and large send offload, or TCP segmentation offload, so a big buffer is chopped into wire-sized segments by the hardware. Receive Side Scaling spreads incoming interrupts across processor cores so a fast link does not saturate a single core.
Why keeping it updated matters
Network adapters carry more logic in software than their small size suggests, so their drivers are revised to fix subtle data-path bugs. A common example is a broken large-send offload that works at idle but corrupts segments under sustained transfer, producing retransmissions that halve throughput. These regressions are fixed in driver updates, and running a current build is how the corrected offload logic reaches your adapter.
Stability is the second reason. Because the miniport runs in kernel space, a defect in its interrupt or DMA handling can bug-check the whole system, and disappearing-adapter faults where the device drops out under load are almost always driver issues rather than hardware failure. Updated builds tighten the interrupt-moderation and descriptor handling that cause those drop-outs.
Common warning signs of network adapter driver failure
- Throughput starts high then collapses during long transfers because a broken large-send offload corrupts TCP segments
- The network adapter vanishes from Device Manager under heavy load, then reappears after a disable and enable cycle
- Windows shows Code 31 after a feature update because the miniport was built against an older NDIS version
- Wake-on-LAN no longer wakes the machine, since the driver failed to arm the magic-packet pattern before sleep
- A VPN or virtual switch that binds above the adapter breaks all connectivity until the binding is removed
- High CPU usage on one core during downloads because Receive Side Scaling failed to spread interrupts across cores
How to fix network adapter driver problems
Cycle the adapter to clear a wedged data path
In Device Manager, expand Network adapters, right-click the adapter, choose Disable device, wait a moment, then Enable device. This re-initialises the miniport's descriptor rings and clears a state where the adapter has dropped out under load.
Disable a suspect hardware offload
On the adapter's Advanced tab, temporarily turn off Large Send Offload or TCP checksum offload, then re-test a long transfer. If throughput stops collapsing, the offload was corrupting segments and a driver update is the proper fix.
Reset the protocol stack above the miniport
Run netsh winsock reset and netsh int ip reset from an elevated prompt, then reboot. This rebuilds the Winsock catalogue and TCP/IP bindings that a misbehaving VPN or filter driver can leave in a broken state.
Reinstall the miniport driver cleanly
Right-click the adapter, choose Uninstall device, tick 'Attempt to remove the driver for this device', and reboot. Windows reinstalls a fresh miniport, clearing corrupted registry keys that trigger Code 31 or offload faults.
Error codes linked to this hardware
Helpful guides
Should You Use Driver Updater Software?
Driver updater tools promise one-click fixes but add risk. Here's what they really do, when they cause problems, and the safe way to check drivers yourself.
DCH vs Legacy Drivers in Windows 10/11
DCH drivers split hardware support from control-panel apps in Windows 10/11. Why the change happened and how to tell which type you have.
How to identify unknown devices with hardware IDs
A practical walkthrough for naming every mystery entry in Device Manager using hardware IDs, driver details, and Windows' built-in tools.
Frequently asked questions
Why does my network adapter start fast then slow to a crawl during long transfers?
That pattern is the classic signature of a broken large-send or checksum offload: the hardware corrupts segments under sustained load, forcing retransmissions that cripple throughput. Temporarily disabling the offload on the Advanced tab confirms it, and an updated miniport driver is the proper fix that lets you re-enable it.
Why does my network adapter disappear from Device Manager under heavy load?
A miniport that drops out under load has usually hit a fault in its interrupt or descriptor handling, or been switched off by aggressive power management. Disabling adapter power saving and installing a current driver both address it, since the drop-out is a driver defect rather than a failing chip.
Why does my network adapter show Code 31 after a Windows feature update?
Code 31 means Windows could not load the driver, and after a feature update it usually means the miniport was built against an older NDIS version. Reinstalling a driver made for the current Windows generation, or rolling back the feature update's driver change, restores the adapter.