Ran into a weird network issue this week that took me a few days to pin down. Here’s the scenario: I’d leave my computer running overnight with my online game and IM still active. In the morning, the game and IM would still be connected, but my web browsers (Opera, Firefox, Edge) couldn’t load anything. The wireless connection showed “Excellent” signal, and restarting the wireless card didn’t help—only a full reboot would fix it.
After testing different combinations, I noticed a pattern: IM worked if left running, but browsers never did unless restarted. My MMO game stayed connected regardless. This pointed to something selectively blocking traffic.
I found a potential culprit in my Atheros wireless adapter settings: Power Save Mode. By default it was set to “Normal” which can throttle the card when idle. I switched it to Off. This morning, my browser connected fine after the game had been running all night—first success. However, my antivirus (Avira) had also crashed overnight, so I need to run another test to isolate the cause.
My Hypothesis
Power Save Mode restricts the adapter’s activity to only the most active programs, which would explain why high-traffic apps like games and IM kept working while browsers (which only send small keep-alive packets) got deprioritized or cut off.
Action Taken
- Disabled Power Save Mode on the wireless adapter in Device Manager
- Verified no malware or spyware (scanned with Malwarebytes and Windows Defender)
- Checked firewall (ZoneAlarm) logs—no blocks
Next Steps
- Test with antivirus disabled to rule out interference
- Check Windows Power Management settings for USB selective suspend or similar
- Update drivers from manufacturer (Atheros/Qualcomm)
If anyone else has encountered this, I’d appreciate your thoughts. Will update after a few more overnight tests.
Topic Summary: Intermittent internet connectivity often traced to wireless adapter power saving features. This thread covers troubleshooting steps, driver settings, and modern Windows power management to resolve browser-only drops.
YouTube Video:
---
title: Intermittent Connectivity Troubleshooting
---
flowchart TD
A[Start: Intermittent Browser Issues] --> B{Check Wireless Adapter Settings}
B --> C[Power Save Mode Enabled?]
C -- Yes --> D[Disable Power Save Mode]
C -- No --> E[Check Other Power Settings]
D --> F[Check Windows Power Management]
E --> F
F --> G[Allow computer to turn off device unchecked?]
G -- Unchecked --> H[Test Connectivity]
G -- Checked --> I[Uncheck and Test]
H --> J{Browsers Working?}
I --> J
J -- Yes --> K[Issue Resolved]
J -- No --> L[Check Security Software Logs]
L --> M[Disable Security Temporarily]
M --> N[Test Again]
N --> O{Stable?}
O -- Yes --> P[Update Security Software/Driver]
O -- No --> Q[Check Event Viewer for Adapter Resets]
Q --> R[Update or Replace Adapter Driver]
Interesting issue. Power Save Mode on wireless adapters has been a known troublemaker for years, especially with modern OS power management. The way it works: when the adapter enters a low-power state, it can miss beacon frames or fail to keep the TCP connection alive for idle applications. Games and IM clients often use persistent connections with frequent keep-alives, so they stay active. Browsers, on the other hand, rely on short-lived HTTP connections that may not trigger the adapter to wake up in time.
You should also check Windows Power Management for the adapter under Device Manager → Network adapters → your adapter → Power Management tab. Uncheck “Allow the computer to turn off this device to save power.” That can override your driver-level setting.
Also, consider disabling 802.11 power saving in the adapter’s advanced settings—look for “Preferred Band” or “Roaming Aggressiveness” options that might interfere.
If you’re on Windows 10/11, run powercfg /energy from an admin command prompt to generate an energy report that highlights devices preventing sleep or causing wake issues.
Glad the first test worked. Keep us posted on the antivirus theory—some security suites have aggressive network filtering that kicks in during idle hours.
This thread touches on a classic yet often overlooked culprit in intermittent connectivity. Power save mode on wireless adapters has been a known issue for years, but modern hardware and software add new layers.
Beyond the Basics
While disabling power saving in the adapter’s advanced settings is the first step, there are additional modern considerations:
- Windows 10/11 Modern Standby: This new sleep state can cause adapter power transitions even when the system appears active. Use
powercfg /availablesleepstates to check if your system supports it.
- Wi-Fi 6/6E (802.11ax) Target Wake Time: Newer adapters may use TWT to schedule wake intervals, which can cause similar symptoms if misconfigured. Check for “Wake on Magic Packet” or “Wake on Pattern Match” settings.
- Driver Version: Many Atheros/Qualcomm adapters have later drivers that expose more power options. Updating to the latest driver from the manufacturer (not just Windows Update) can provide a “Power Save Mode” set to “Disable” explicitly.
- Event Viewer Clues: Look under System logs for warnings from
e1rexpress or Netwtw10 about adapter reset or power transitions. This helps confirm power saving as the cause.
Modern Troubleshooting Workflow
- Check Adapter Power Management (Device Manager → Power Management tab) – uncheck “Allow computer to turn off this device”.
- Disable Power Saving in Advanced Properties: Look for “Power Save Mode” or “802.11 Power Save” and set to Off.
- Review Windows Power Plan: Set the wireless adapter behavior to “Maximum Performance” under Advanced power settings.
- Test with Security Software Temporarily Disabled: As the OP noted, Avira crashing suggests possible interference. Modern suites often have network monitoring that may drop idle connections.
- Use PowerShell to Generate Energy Report:
powercfg /energy outputs an HTML report showing devices that prevent sleep or cause wake failures.
On the Antivirus Angle
Many modern security programs (Avira, Norton, etc.) include intelligent firewall or behavior blocking that can suspend network traffic for applications deemed idle. Checking logs for blocked packets or processes during the overnight period is worthwhile. Some suites also have a “Gaming Mode” that may alter network filtering.
Final Thoughts
The fact that browsers failed while games/IM remained connected strongly points to a connection idle timeout issue. Power save mode is the prime suspect, but driver/OS interaction with security software should not be dismissed. Running a clean boot test (disabling all third-party services) can help isolate the root cause. This type of intermittent problem can be frustrating because it’s hard to reproduce on demand, but systematic elimination usually narrows it down.
YouTube Video:
