My internet connection briefly stops responding for about 2–3 seconds, then recovers. It happens several times a day and affects the entire computer, not just online games. I see the problem both over Wi‑Fi and when connecting Ethernet to a Wi‑Fi repeater, so it is not limited to one game or application. The same network worked normally for years, and this issue only started a few months ago. Could the problem be related to my PC hardware, network adapter, or drivers?
2 Answers
The repeater may still be part of the problem. Ethernet plugged into a repeater is usually only wired between your PC and the repeater—the repeater still uses Wi‑Fi for its connection back to the router. Single-band repeaters can add latency and briefly lose their link. If possible, test with a direct Ethernet cable to the main router, or test the PC right next to the router on its normal Wi‑Fi. A mesh system or a wired access point is generally more reliable than a basic repeater.
Run two continuous pings while the problem occurs: one to your router’s local address, such as 192.168.1.1, and another to a public address such as 1.1.1.1. If both fail, the issue is between the PC and router, which points toward the adapter, driver, signal, or repeater. If the router ping keeps working but the public ping fails, the problem is more likely the router or internet service. Also try updating or reinstalling the motherboard/network adapter drivers, disabling Wi‑Fi power saving, and checking whether the adapter disappears or resets in Event Viewer. Testing another computer on the same connection will help determine whether the PC is the only affected device.
The interruption only seems to affect this PC, whether I use direct Wi‑Fi or Ethernet through the repeater. I’ll compare the router and public-address pings and check the adapter drivers and power settings.
That makes sense for the repeater, but the dropouts also happen when the PC connects directly over Wi‑Fi. The same setup was stable for years, so I’m also wondering whether the PC’s network adapter or its drivers have started causing this.