Ethernet/LAN drivers
Wired LAN adapter drivers for stable gigabit connections.
You might also need
Ethernet/LAN drivers we cover
What does a ethernet/lan driver do?
An Ethernet LAN driver operates two closely linked blocks on your wired controller: the Media Access Control layer, which frames and schedules packets, and the physical-layer transceiver, or PHY, which turns those frames into the electrical signalling that travels down the twisted pairs of an RJ45 cable. The driver programs the MAC's descriptor rings for DMA and configures the PHY registers that decide how the link behaves.
Auto-negotiation is the first thing the driver arranges when a cable is plugged in. The PHY exchanges capability pages with the switch or router to agree the highest common speed, whether 10, 100, 1000, or on newer parts 2.5 gigabit, and the duplex mode. It also negotiates the MDI or MDI-X crossover so a straight cable works either way. If negotiation is forced to a fixed value on one end only, the result is a duplex mismatch that quietly wrecks throughput.
Why keeping it updated matters
A wired link feels simple, but the driver hides a surprising amount of negotiation and power logic that gets refined over time. A frequent fix concerns Energy-Efficient Ethernet: some driver builds enable it too aggressively for a given switch, and the low-power idle transitions cause brief drops or a link that flaps between speeds. Updated drivers ship better EEE defaults, and running one is how that improved behaviour reaches your controller.
Speed and duplex handling is the second reason. A stale driver can misread a switch's negotiation pages and train the link at 100 Mbps when the cabling supports gigabit, or settle on half duplex, which cripples throughput and floods the port with collisions. Refreshed builds correct the auto-negotiation state machine so the link reaches the speed the hardware and cable can actually sustain.
Common warning signs of ethernet/lan driver failure
- The wired link trains at 100 Mbps despite gigabit-capable cabling because auto-negotiation settled on the wrong speed
- Throughput is poor and the switch port logs collisions, a classic sign of a half-duplex mismatch on the link
- The connection flaps or drops briefly on a quiet network when Energy-Efficient Ethernet enters low-power idle
- Wake-on-LAN stopped waking the PC because the driver no longer arms the magic-packet pattern before sleep
- The Ethernet controller shows Code 10 and cannot start after a Windows feature update changed its power contract
- Large transfers stall under load as the controller drops out and only recovers after a disable and enable cycle
How to fix ethernet/lan driver problems
Force a clean re-negotiation of the link
In Device Manager, expand Network adapters, right-click the Ethernet controller, choose Disable device, wait a moment, then Enable device. This drops and re-trains the link so a stuck speed or duplex agreement is renegotiated from scratch.
Set speed and duplex explicitly if negotiation misbehaves
On the Advanced tab, find Speed & Duplex. Leave it on auto-negotiation normally, but if the link keeps training wrong, set it to match the switch port exactly, since a one-sided forced setting is what creates duplex mismatches.
Disable Energy-Efficient Ethernet to stop link flapping
On the Advanced tab, turn off Energy-Efficient Ethernet, and any Green Ethernet or EEE option, then re-test. If the drops on a quiet network stop, an aggressive low-power idle was the cause and a driver update usually restores it safely.
Reinstall the controller driver cleanly
Right-click the controller, choose Uninstall device, tick 'Attempt to remove the driver for this device', and reboot. Windows reinstalls a fresh driver, clearing corrupted registry keys behind a Code 10 or a controller that drops under load.
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 Ethernet link only train at 100 Mbps when my cable supports gigabit?
A gigabit-capable link that settles at 100 Mbps usually means auto-negotiation failed on one pair, or the cable or port cannot carry all four pairs cleanly. Re-negotiate by cycling the adapter, test a known-good Cat5e or Cat6 lead, and update the driver so its negotiation state machine reads the switch correctly.
Why does my wired connection have poor throughput and lots of collisions?
Collisions on a modern switch almost always mean a half-duplex mismatch, where one end auto-negotiates and the other is forced to a fixed setting. Set both ends to auto-negotiation, or match them explicitly, since a one-sided forced value is what drops the link to half duplex.
Why does my Ethernet link keep dropping briefly on a quiet network?
Brief drops on an idle link are the hallmark of Energy-Efficient Ethernet entering low-power idle when the switch handles the transition poorly. Disabling Energy-Efficient Ethernet on the Advanced tab confirms it, and a driver update with better EEE defaults usually lets you turn it back on safely.