A Windows 11 Wi‑Fi driver that “keeps crashing” rarely looks dramatic. The network icon flips to a globe, the adapter vanishes from Settings, and a minute later it’s back—until it isn’t. On laptops it often happens on battery, after sleep, or the moment you start a Teams call. On desktops it can show up as random disconnects that only happen on 5GHz.
The awkward part is that Windows will happily reconnect and make it feel like a router problem. Then you open Event Viewer and see the adapter resetting, a Netwtw* or Realtek driver fault, or a “device stopped responding” entry. I’ve also seen machines that only crash when Bluetooth is active, which points straight at radio coexistence and power management rather than “bad Wi‑Fi”.
If you’ve got a Mac available, it’s useful as a control device: if macOS stays stable on the same network while Windows 11 drops, you can stop chasing the router and focus on the Windows driver stack. If both drop, you’re looking at RF interference, router firmware, or a failing access point.
What’s actually crashing when Wi‑Fi dies on Windows 11
When people say “the Wi‑Fi driver crashes”, they’re usually seeing one of three failure modes:
- NDIS reset loop: Windows detects the adapter isn’t responding and resets it. You’ll see brief disconnects, then reconnection. This often correlates with power state changes (sleep/Modern Standby) or aggressive power saving.
- Driver service fault: The vendor driver (Intel/Realtek/Qualcomm) throws an error and Windows unloads/reloads it. Device Manager may show Code 10/Code 43 temporarily.
- Network stack corruption: The adapter is fine, but Winsock/TCP/IP components are in a bad state after updates, VPN clients, or security software. The adapter stays “on”, but traffic stalls.
Windows 11 adds two complicating factors. First, Modern Standby (S0) keeps the machine semi-awake and can expose flaky power transitions. Second, Windows Update can push a “newer” driver that’s technically compatible but unstable on a specific laptop SKU. This is the most common issue I see on UK devices sold before 2024, especially when the OEM shipped a customised driver branch.
Before changing anything, it helps to identify the chipset. Intel AX200/AX201/AX210 behave differently to Realtek 8822/8852 families, and Qualcomm adapters have their own quirks. The fix path is similar, but the best driver source differs.
A failure-first checklist that narrows it down fast
Start by catching the failure in logs. Guessing wastes time.
- Event Viewer: Windows Logs > System. Filter for sources like Netwtw* (Intel), rtwlane* (Realtek), WLAN-AutoConfig, NDIS, and Kernel-PnP.
- Reliability Monitor: Search “Reliability” > View reliability history. Look for “Windows stopped working” entries tied to network components.
- Device Manager: Check whether the adapter disappears entirely (hardware/driver crash) or stays present but loses connectivity (stack/router/interference).
If you see repeated adapter resets around sleep/wake, treat it as a power management problem first. If it crashes during heavy throughput (downloads, cloud sync, game updates), suspect driver version, channel width, or router features like OFDMA/802.11ax compatibility.
Step-by-step: stabilise the driver without breaking everything else
Work through these in order. Stop when the crashes stop; piling changes on top of each other makes it hard to know what actually fixed it.
1) Roll back the Wi‑Fi driver (or install the OEM one)
Windows Update drivers are convenient, not always stable. If the issue started after an update, rolling back is often the cleanest win.
- Right-click Start > Device Manager.
- Expand Network adapters > double-click your Wi‑Fi adapter.
- Go to Driver tab.
- If Roll Back Driver is available, use it and reboot.
If rollback is greyed out, install the driver from your laptop maker’s support page (HP/Dell/Lenovo/Acer/ASUS). For Intel adapters, you can also use Intel’s Wi‑Fi driver packages—but on some OEM laptops the OEM build is less crash-prone because it’s tuned for that power profile.
Seen most often on HP, Dell and Lenovo laptops: the “newest” Intel driver works, but only until the machine sleeps twice, then the adapter starts resetting. The OEM package fixes it because it includes a matching Bluetooth component and power settings.
2) Do a clean driver reinstall (the non-obvious part)
A normal reinstall can leave old components behind. You want Windows to forget the driver package.
- Disconnect from the internet (turn off Wi‑Fi, unplug Ethernet if you can).
- Device Manager > right-click the Wi‑Fi adapter > Uninstall device.
- Tick Attempt to remove the driver for this device (wording varies) and confirm.
- Reboot.
- Install the known-good driver package (OEM or vendor).
- Reconnect to the internet.
If Windows immediately reinstalls the problematic driver via Windows Update, pause updates temporarily or use Device Installation Settings to prevent automatic driver downloads while you test stability.
3) Turn off the power features that trigger resets
Power management is a frequent trigger because the adapter is asked to enter low-power states repeatedly. On some machines it never wakes cleanly.
- Device Manager > Wi‑Fi adapter > Power Management.
- Untick Allow the computer to turn off this device to save power.
- Open Control Panel > Power Options > Change plan settings > Advanced.
- Under Wireless Adapter Settings > Power Saving Mode, set Maximum Performance on battery and plugged in.
In practice, this step fixes the problem in about half of cases where the crash happens after sleep or when the lid is closed and reopened. The trade-off is slightly worse battery life, but it’s usually worth it if the machine is dropping off calls.
4) Disable Fast Startup (it can preserve a broken state)
Fast Startup isn’t a full shutdown. If the Wi‑Fi stack is in a bad state, it can come back exactly the same way.
- Control Panel > Power Options.
- Choose what the power buttons do.
- Click Change settings that are currently unavailable.
- Untick Turn on fast startup.
- Shut down fully, then power on.
5) Reset the network stack (when the adapter stays “alive” but traffic dies)
If the adapter doesn’t disappear, but DNS fails, pages half-load, or VPN toggling triggers the issue, reset the stack.
- Settings > Network & internet > Advanced network settings.
- Network reset > Reset now.
- Reboot and rejoin Wi‑Fi networks.
For Microsoft’s own steps and what gets removed, use Microsoft’s network reset guidance.
6) Change two adapter settings that commonly destabilise Wi‑Fi 6/6E
These are not universal fixes. They’re targeted at “works for a bit, then collapses under load” behaviour.
- Device Manager > Wi‑Fi adapter > Advanced tab.
- Try setting 802.11ax to Disabled (or “Wi‑Fi 6 mode” off) as a test.
- Set Channel Width for 5GHz to 20 MHz or Auto (avoid 160MHz while testing).
If stability returns with 802.11ax disabled, the router and adapter are negotiating features badly (often OFDMA/TWT related). You can then update router firmware or keep ax off until a driver update lands.
7) Prove whether it’s the router or the Windows machine (macOS helps here)
Use a simple A/B test rather than swapping settings blindly.
- Test 1: Mac on the same SSID. If macOS stays stable for an hour while Windows drops repeatedly, it’s probably Windows driver/power/stack.
- Test 2: Windows on a phone hotspot. If Windows is stable on a hotspot but crashes on your home Wi‑Fi, suspect router firmware, channel congestion, or a specific band (5GHz/6GHz).
- Test 3: Force 2.4GHz. If 2.4GHz is stable but 5GHz isn’t, look at channel width, DFS channels, and interference.
I’ve had a Windows 11 laptop that crashed only on a particular mesh system’s 5GHz backhaul channel. The same laptop ran for days on a basic ISP router. That’s not “bad Wi‑Fi”; it’s a compatibility edge case.
When it happens: patterns that point to the real cause
Crashes are rarely random. The trigger tells you where to look.
- Only after sleep/closing the lid: power management, Modern Standby, Fast Startup, or an OEM hotkey/utility interfering.
- Only during video calls: driver instability under sustained low-latency traffic, Bluetooth coexistence, or USB audio devices causing DPC latency spikes that look like network drops.
- Only on battery: wireless power saving mode, OEM battery profiles, or “intelligent” network switching utilities.
- Only on 5GHz/6GHz: channel width, DFS, router firmware, or a noisy RF environment (flats with dense networks are brutal).
- Only on one network: router features (WPA3 transition mode, 802.11r fast roaming, band steering) or a misbehaving mesh node.
Common mistakes that keep the crash loop going
- Updating everything at once: BIOS, chipset, Wi‑Fi, Bluetooth, VPN, and Windows updates in one evening makes it impossible to isolate the regression.
- Assuming “latest driver” means “best driver”: for Wi‑Fi, stability beats new features. A slightly older OEM driver can be the correct answer.
- Ignoring Bluetooth: many Wi‑Fi cards share antennas and coexistence logic. If the crash happens when a Bluetooth headset connects, update Bluetooth drivers alongside Wi‑Fi.
- Leaving VPN/security filters installed: uninstalling a VPN app doesn’t always remove its network filter driver. If crashes started after a VPN trial, remove it cleanly and reset the network stack.
- Chasing DNS settings: DNS tweaks don’t fix a driver reset. They can mask symptoms and waste time.
If you’re also seeing general instability after Windows updates (not just Wi‑Fi), it’s worth checking Windows 11 freezing randomly after updates because a broader driver or system file issue can present as “network crashes”.
Hardware and software factors people miss
Once the obvious driver steps are done, the remaining causes tend to be physical, firmware, or environmental.
Router features that can trip Windows 11 drivers
- WPA3 transition mode: some adapters behave better on WPA2-only while testing.
- 802.11r fast roaming: great for enterprise, occasionally messy at home with mixed clients.
- Band steering: can look like “driver crashes” when the client is pushed between 2.4/5GHz aggressively.
- 160MHz channels: fast on paper, unstable in crowded areas. Try 80MHz or 40MHz.
If you change router settings, change one thing, then test for long enough to catch the original failure. Five minutes isn’t a test if the crash normally happens every hour.
BIOS, chipset and OEM utilities
Wi‑Fi stability isn’t only the Wi‑Fi driver. The PCIe power management and platform firmware matter.
- BIOS updates can fix sleep/wake power issues that present as adapter resets.
- Chipset drivers (Intel/AMD) influence power states and device enumeration.
- OEM network utilities sometimes “optimise” networks by switching profiles or prioritising traffic; I remove them when diagnosing.
I’ve seen a Lenovo utility repeatedly rewrite adapter advanced settings on reboot. You’d set 802.11ax off, it would come back on, and the crashes would return. If settings don’t stick, suspect OEM tooling.
When it’s actually the Wi‑Fi card
A failing adapter is less common than a bad driver, but it happens—especially after liquid exposure, a drop, or years of heat cycling.
- Adapter disappears from Device Manager entirely until a cold boot.
- Crashes happen across multiple OS installs and multiple networks.
- Bluetooth also becomes unreliable (shared module).
On desktops, a cheap USB Wi‑Fi dongle can be the culprit too. They overheat, especially when plugged into a rear port with poor airflow. If the dongle is hot to the touch when it drops, that’s not subtle.
Closing notes: what I’d do on a stubborn case
If the driver still crashes after a clean reinstall and power tweaks, I stop treating it as a “Windows networking” problem and start treating it as a compatibility problem between a specific adapter and a specific environment. I’ll lock the router to a conservative 5GHz setup (80MHz, non-DFS channel), disable WPA3 transition temporarily, and test. If that stabilises it, I bring features back one by one.
If you need a quick workaround while you diagnose, Ethernet via a USB‑C adapter is boring but reliable. And if you’re seeing odd performance differences between wired and wireless, Ethernet slower than Wi‑Fi on Windows 11 is worth a look—sometimes the “Wi‑Fi crash” report is actually a wired driver or power issue pushing you back onto Wi‑Fi.
FAQ
Why does my Windows 11 Wi‑Fi driver crash only after the laptop wakes from sleep overnight?
That pattern points to power state transitions: Modern Standby, adapter power saving, or Fast Startup preserving a broken state. Disable “Allow the computer to turn off this device”, set Wireless Adapter power saving to Maximum Performance, and turn off Fast Startup. If it persists, install the OEM Wi‑Fi driver rather than the Windows Update one.
Why does Wi‑Fi work for 10 minutes then keeps disconnecting when I start a Teams or Zoom call on Windows 11?
Calls create sustained low-latency traffic and often bring Bluetooth audio into the mix. Update Wi‑Fi and Bluetooth drivers together, then test with Bluetooth off. If the router is using Wi‑Fi 6 features aggressively, temporarily disable 802.11ax on the adapter or reduce 5GHz channel width to rule out an ax/OFDMA compatibility issue.
Why is my Windows 11 laptop stable on a phone hotspot but the Wi‑Fi driver crashes on my home router?
That usually means the adapter is fine and the crash is triggered by something specific to the home network: WPA3 transition mode, band steering, 160MHz channels, DFS channels, or router firmware. Make the home setup conservative while testing (WPA2, 80MHz, fixed 5GHz channel) and update router firmware if available.
Does Windows 11 Wi‑Fi still work properly if I disable 802.11ax (Wi‑Fi 6) to stop driver crashes?
Yes. Disabling 802.11ax forces the adapter to use 802.11ac/n modes, which are often more stable on older routers or mixed-client networks. You’ll lose some peak throughput and efficiency features, but for most UK broadband connections it won’t be noticeable day to day, and it’s a useful diagnostic step.
Why does my Wi‑Fi driver crash when I connect Bluetooth headphones, but it’s fine with Bluetooth off?
Many laptop radios share antennas and coexistence logic, so a buggy driver pair (Wi‑Fi + Bluetooth) can destabilise the whole module. Install the OEM wireless package (not just Wi‑Fi), then retest. If it still happens, try moving to 5GHz (or away from congested 2.4GHz) because Bluetooth lives in the 2.4GHz band and can worsen interference.
Recommended gear on Amazon UK
- Gives you a stable wired connection while you isolate whether the Wi‑Fi crashes are driver-related or triggered by your router’s 5GHz/6GHz settings. Relevant examples
- Useful as a quick A/B test: if a different adapter stays stable on the same network, the internal card or its driver branch is the weak link. Comparable items
- Helps in cases where the wireless module becomes unstable under heat, which can look like random driver resets during long downloads or calls. See suitable options
- Makes it easier to spot crowded channels and wide channel widths that can trigger disconnect loops, especially in flats with dense 5GHz networks. Comparable items
