Test the connection to your router and the wider Internet separately while Minecraft is running; this will show whether the failure is inside the PC/Wi‑Fi link, upstream of the router, or limited to Minecraft.
1. Run two separate ping tests
- Open Command Prompt.
- Run
ipconfigand find Default Gateway under the active Wi‑Fi or Ethernet adapter. It commonly resembles[IP Address]. - Open two Command Prompt windows.
- In the first window, ping your actual Default Gateway. In the second, ping a public Internet address:
:: Window 1 — replace this example with your Default Gateway
ping -t [IP Address]
:: Window 2 — Internet-path test
ping -t [IP Address]
Do not type angle or square brackets. Play Minecraft until the problem occurs, then press Ctrl+C in each window to display packet-loss and latency statistics. Microsoft documents the gateway ping as a way to check the PC-to-router connection.^1^
Interpret the results:
- Gateway ping spikes or times out: the problem is between this PC and the router—usually the Wi‑Fi link, network adapter, cable, or router.
- Gateway stays stable, but the public ping spikes or times out: the fault is beyond the PC-to-router link, potentially the modem, router’s Internet side, ISP, or wider route.
- Both tests remain stable while only Minecraft disconnects: test another Minecraft server. If only one server is affected, its performance or the route to it is the likely area to investigate.
- The public ping fails on this PC only: continue with the Windows adapter steps below.
- It fails on multiple devices, including over Ethernet: restart the modem/router, retest, and then contact the ISP with the packet-loss results. If
[IP Address]never responds at all, use another public target because some destinations may decline ping traffic.
Also note whether Windows itself shows No Internet, or whether only Minecraft disconnects. Those are different failures.
2. Compare Wi‑Fi, Ethernet, and another device
If possible, connect the PC directly to the router with Ethernet and repeat both tests.
- Ethernet works but Wi‑Fi fails: focus on Wi‑Fi signal, interference, frequency band, or the wireless adapter.
- Both fail on this PC, but another device works: focus on Windows or this PC’s adapter.
- Multiple devices fail: focus on the router, modem, or ISP.
For Wi‑Fi, try the router’s other band—2.4 GHz versus 5 GHz—if both appear as separate networks. Microsoft also recommends testing the same network on another device to distinguish a device problem from a network problem.^1^
Restarting the modem/router temporarily disconnects everyone:
- Unplug the router and modem.
- Wait at least 30 seconds.
- Reconnect the modem and wait for its lights to stabilize.
- Reconnect the router and retest.^2^
3. If only this Windows 11 PC fails
Run Get Help → Network and Internet troubleshooter first. Then open Command Prompt as administrator and run:
netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns
Restart Windows afterward. These commands reset Winsock/TCP-IP, obtain a new address, and clear the DNS resolver cache.^1^
If that fails, download the correct adapter driver from the PC manufacturer before removing anything. Then use Device Manager → Network adapters → your adapter → Uninstall device, restart, and let Windows reinstall it.^1^
Use Settings → Network & internet → Advanced network settings → Network reset → Reset now only as the last step. It removes and reinstalls network adapters and resets their settings; VPN clients or virtual switches may need reconfiguration afterward.^2^
Ping, FPS, and TPS are different
- FPS measures graphics rendering, so 80 FPS does not establish that the network is healthy.
- Ping measures network latency. Sustained values of 1,000–9,000 ms indicate severe delay or congestion.
- TPS measures game simulation speed. In multiplayer, low TPS is generally a server-performance issue and cannot be fixed with a Windows network reset. In single-player, Minecraft runs an integrated server locally, so low TPS can instead reflect CPU or mod workload.
The fact that different modpacks behave differently does not by itself establish that mod count is controlling the connection; the two simultaneous ping tests will show whether the underlying network actually drops when each pack runs.
References