An internet connection that drops every few minutes, cuts out randomly, or disconnects and reconnects constantly is one of the most disruptive network problems — and one of the hardest to diagnose without a systematic approach, because the cause could be anywhere from Windows power settings to the cable modem hardware. This fits into the wider topic we cover in our Complete Guide to Fixing Windows, Browser, and Software Errors.
The first diagnostic question: does this affect all devices on the network, or just this one Windows machine? Check your phone or another computer on the same network during the next dropout. If everything drops simultaneously: the issue is in the router, modem, or ISP. If only the Windows machine drops while other devices stay connected: the problem is Windows-specific.
If only Windows disconnects: start here
Windows-specific dropouts are almost always caused by one of two things: power management suspending the network adapter, or a driver bug. These are the fixes to try first.
Power management — the most common cause of random disconnections on laptops:
- Device Manager → Network Adapters → right-click your Wi-Fi or Ethernet adapter → Properties
- Power Management tab → uncheck “Allow the computer to turn off this device to save power”
- Advanced tab → find “Power Save Mode,” “Power Management Mode,” or “Energy Efficient Ethernet” → set to Disabled or Maximum Performance
Also: Settings → System → Power → Power mode → change from “Best power efficiency” to “Balanced” — the efficiency mode is particularly aggressive at suspending network adapters.
Network adapter driver — try this next if power management didn’t fix it. Go to your laptop or motherboard manufacturer’s support page and download the specific driver for your network adapter model. Don’t rely on Windows Update for this — manufacturer drivers are tuned for the hardware and typically more stable.
If all devices drop: router and modem
When all devices lose connection simultaneously, work from the ISP equipment outward:
- Restart the modem (the device connected to the wall/coax) — unplug for 60 seconds → plug back in → wait for all lights to stabilise (2-3 minutes). Don’t press reset — that erases configuration
- Restart the router (separate from the modem if you have two devices) — same 60-second unplug cycle after the modem is stable
- Check ISP outage status — if it’s not just your house, checking the ISP’s status page or Twitter/X saves significant troubleshooting time
If rebooting helps temporarily but the problem returns after a few hours: the modem or router hardware is degrading. Routers running 24/7 for 3+ years commonly develop intermittent connection issues as their hardware ages.
Wi-Fi-specific dropout causes
Wi-Fi dropouts have additional causes beyond Ethernet:
- Channel congestion: if your 2.4 GHz Wi-Fi channel overlaps with neighbours’ networks, packet collisions cause random dropouts. Use a Wi-Fi analyser app (WiFi Analyzer on Windows Store) to find the least congested channel and set it manually in your router settings
- 5 GHz range limitations: 5 GHz Wi-Fi has shorter range than 2.4 GHz. If you’re at the edge of 5 GHz coverage, the connection becomes unstable. Force the device to use 2.4 GHz for better range at the cost of speed
- Band steering problems: routers with band steering automatically switch devices between 2.4 and 5 GHz bands. The switching process causes brief disconnections. Disable band steering in the router settings if you experience periodic 5-10 second drops
- Roaming aggressiveness: Device Manager → adapter → Advanced → “Roaming Aggressiveness” → set to Low or Medium. High roaming aggressiveness causes the adapter to frequently disconnect and reconnect searching for better access points
Network stack reset
Corrupted TCP/IP or Winsock configuration causes intermittent drops that look like hardware or ISP issues. Administrator Command Prompt:
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
Restart after running all three. If the dropouts reduce or stop: the network stack had accumulated corruption. This is a permanent fix — the stack stays reset until something re-corrupts it.
Ethernet cable and port
For Ethernet connections: intermittent dropouts that weren’t present before often indicate a failing cable or a loose connector. Test by:
- Replacing the Ethernet cable (try a Cat5e or Cat6 cable)
- Using a different Ethernet port on the router or switch
- Checking both connectors for bent pins or debris
Device Manager → your Ethernet adapter → Properties → Advanced → look for “Speed and Duplex” — if it’s set to a fixed speed (100Mbps) and the cable or switch expects auto-negotiation (or vice versa), the mismatch causes periodic link failures. Set to “Auto Negotiation” for most reliable operation.
ISP line issues and signal levels
For cable internet: the modem maintains a log of connection events. Access it by navigating to the modem’s admin page (typically 192.168.100.1 for cable modems) → Event Log. Look for “T3 timeout” or “T4 timeout” entries — these indicate the modem lost contact with the ISP’s cable plant. Multiple T3/T4 timeouts correlate exactly with the dropouts you experience and give you documented evidence for an ISP service call.
Signal levels matter: the downstream power level should be between -7 and +7 dBmV, and SNR (signal-to-noise ratio) should be above 33 dB. Values outside these ranges indicate line quality issues — loose splitter, corroded connector, or degraded cable from the street to your house — that the ISP needs to fix on their infrastructure.
Our guide on Wi-Fi dropping on Windows 11 covers the adapter-specific Wi-Fi dropout fixes in more depth, including driver rollback and the roaming settings. For the DNS and network stack issues that accompany connection drops, our connectivity troubleshooting guide covers the reset commands and DNS configuration. Microsoft’s network troubleshooting tools include the Network Adapter Diagnostic that specifically tests for intermittent adapter failures.
Using ping logging to document dropouts
When the connection drops intermittently and you need to document it (for ISP support, IT, or to confirm whether a fix worked), a continuous ping log captures exactly when dropouts occur and how long they last:
ping google.com -t > C:ping_log.txt
Run this in Command Prompt and leave it running. When you’re done, press Ctrl+C to stop. The text file shows every ping result with timing — “Request timed out” entries show when the internet was down, and the time gaps between them show the duration of each dropout.
Run a second simultaneous ping to your router (ping 192.168.1.1 -t) to separate local network drops from internet drops — if the router ping also times out, the local network failed; if only google.com times out, the internet connection itself dropped while local networking stayed up.
DHCP lease renewal causing apparent drops
DHCP automatically renews IP address leases periodically. If the DHCP renewal fails (router is briefly unresponsive, network congestion at renewal time), Windows loses its IP assignment and the connection drops for 10-30 seconds while it retries. This looks like a random dropout but happens at predictable intervals matching the DHCP lease time.
Workaround: Settings → Network → your connection → IP settings → Manual → assign a static IP in your router’s range. This eliminates DHCP renewal entirely. Alternative: increase the DHCP lease time in your router settings from the default (often 1 hour or 24 hours) — longer leases mean fewer renewal opportunities to fail.
VPN causing connection drops
If the connection drops happen when a VPN is connected: the VPN’s connection to its server is timing out. Every VPN dropout takes the internet with it (especially with a kill switch enabled). Causes:
- Overloaded VPN server — try a different server location in the VPN client
- UDP being blocked — switch protocol to TCP in VPN settings
- Network adapter power management suspending during VPN idle periods — disable power management on the adapter
- VPN session timeout — the VPN server has a maximum session length; configure auto-reconnect in the VPN client
NIC firmware and driver advanced settings
Several network adapter advanced settings can cause intermittent dropouts:
- Wake on LAN: some adapters wake from sleep incorrectly and cause brief drops. Device Manager → adapter → Advanced → “Wake on Magic Packet” and “Wake on Pattern Match” → Disabled
- ARP Offload / NS Offload: offloading ARP responses to hardware can fail on some adapters. Advanced → both offload settings → Disabled
- TCP/UDP Checksum Offload: if checksum errors are causing retransmissions that look like drops. Advanced → disable IPv4/IPv6 checksum offload → test
- Receive Side Scaling (RSS): distributes network load across CPU cores; can occasionally cause intermittent drops on certain CPU/NIC combinations. Try disabling and test
Interference sources for Wi-Fi
Radio frequency interference causes Wi-Fi dropouts that are hard to correlate to anything software-related:
- Microwave ovens emit 2.4 GHz interference that disrupts 2.4 GHz Wi-Fi during use — switch to 5 GHz or move the router away from the kitchen
- Cordless phones (older DECT phones) can interfere with 2.4 GHz
- Neighbouring Wi-Fi networks on the same channel (use the analyser to find a free channel)
- Bluetooth devices running simultaneously with Wi-Fi on 2.4 GHz — both use the 2.4 GHz band and can interfere; using 5 GHz Wi-Fi eliminates this entirely
Checking Windows Event Viewer for network events
Event Viewer → Windows Logs → System → filter for source “DHCP-Client,” “Netwtw04” (or your NIC driver name), “Tcpip,” or “Dhcp.” Events logged at the exact time of each dropout tell you what Windows saw when the connection dropped. Common findings:
- DHCP-Client “address X was declined” — DHCP conflict, IP was already in use
- Dhcp “Failed to obtain a lease” — DHCP server not responding
- NIC driver events showing “link lost” — physical connection interrupted (cable, signal)
- Tcpip “lost connection to DHCP server” — router briefly unreachable
Cross-referencing Event Viewer timestamps with your ping log shows whether Windows saw a specific event before or after the dropout, helping determine cause and effect.
Diagnosis summary: internet connection keeps dropping
| Who drops | Cause | Fix |
| Only this Windows machine | Power management or driver | Disable adapter power saving; reinstall driver |
| All devices simultaneously | Router, modem, or ISP | Restart modem and router; check ISP status |
| Every X minutes precisely | DHCP renewal failure | Static IP or longer lease time |
| During high-usage periods | ISP congestion or bandwidth saturation | QoS on router; check ISP capacity |
| Only on Wi-Fi, not Ethernet | Signal, channel congestion, or range | Change channel; reduce roaming aggressiveness |
| With VPN connected | VPN server overload or timeout | Switch VPN server; change protocol |
The two-ping test (router IP simultaneously with google.com) is the single most useful diagnostic technique here — it tells you in real time whether each dropout is losing the local network or just the internet, which immediately halves the number of possible causes to investigate. Combined with Event Viewer logs at the exact dropout timestamps, it’s usually possible to identify the cause within a few dropout cycles.
Windows network reset as a last resort
When individual settings changes haven’t resolved persistent dropping: Settings → Network and internet → Advanced network settings → Network reset → Reset now. This reinstalls all network adapters and resets all network settings to Windows defaults. It’s disruptive — you’ll need to re-enter Wi-Fi passwords, reconfigure VPN clients, and re-add mapped network drives — but it creates a completely clean network stack that eliminates accumulated configuration issues.
After the network reset, test the connection before re-adding any VPN clients or custom network settings. If dropping stops after the reset but returns after adding a specific setting or application: that application or setting was the cause.
Internet connection dropping is one of the more complex problems to solve because the cause can be at any layer from the physical cable to Windows configuration to the ISP’s infrastructure. The two-tier diagnostic at the start — does only this machine drop, or do all devices? — is the essential first step that directs everything else. Without that answer, you risk spending time fixing the wrong layer.
For ISP-side issues that you’ve documented with ping logs and modem event logs: when calling ISP support, be specific. “My internet keeps dropping” gets generic troubleshooting scripts. “My modem log shows 47 T3 timeout events between 6 PM and 10 PM daily, and my downstream power level is -12 dBmV” gets a line technician dispatched to check the physical cable plant. ISP support responds to specific technical evidence faster than to general complaints — the modem event log is your most powerful tool for getting line quality issues resolved quickly.
One more cause worth knowing: Windows Update downloading in the background can saturate the connection enough to cause apparent dropouts in games or video calls that interpret high latency as a disconnect. This isn’t a true connection drop — it’s bandwidth exhaustion. Settings → Windows Update → Advanced options → Delivery Optimization → limit the download bandwidth to a percentage that leaves room for other traffic. Or: pause updates manually when you need uninterrupted connectivity for meetings or gaming. You might also run into Internet Keeps Cutting Out.
