What this driver does
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. The driver also governs how interrupts and buffers are managed. Interrupt moderation batches completions so the adapter raises fewer, larger interrupts under load, trading a little latency for far less CPU overhead. Receive and transmit descriptor counts, jumbo-frame support, and flow control are all knobs the driver exposes so the adapter matches the demands placed on it. Binding is the last piece. Above the miniport, Windows binds protocol drivers, filter drivers, and services: the TCP/IP stack, the QoS packet scheduler, and any VPN or virtualisation filters. The network adapter driver reports its capabilities upward so these layers negotiate what they can use. A stale or mismatched driver often shows up not as a dead link but as an offload negotiated wrongly, so packets are silently corrupted or dropped under load.
Observable states associated with this device class
These states describe how hardware, firmware, operating-system services, and a driver can interact. They do not identify a cause on their own.
- 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 it works in a real system
Drivers operate in the background as translators. This setup shows the software, connection, and physical hardware that the Network adapter driver supports.
Compatibility model
Driver compatibility is defined by the device hardware identifier, the operating-system driver model, processor architecture, and the interfaces implemented by the hardware or firmware. A shared device class does not imply that packages from different manufacturers are interchangeable.