Intermittent packet loss on PC
By Ryan Mercer Updated 8 min read
Some links on Gaming Past are affiliate links: if you sign up or buy through them we may earn a commission, at no extra cost to you. We recommend a tool only where it fits the problem, and say who should skip it.
On this page (8 sections)
- The short version
- How to log jitter and frame times for PC games
- Testing packet loss with Windows CMD
- Broadcom WiFi driver causing packet loss test
- Intermittent packet loss on PC: how to log jitter, frames, and spot Broadcom WiFi issues
- Common mistakes and myths about lag and packet loss testing
- How GearUP Booster helps with intermittent packet loss on PC
- Questions people still ask
In short: To lag test PC for intermittent packet loss, log jitter and frame times during gameplay using built-in and free tools, test packet loss via Windows CMD ping commands, and check Broadcom WiFi drivers by comparing with wired or alternative adapters.
Part of our guide on interpreting udp packet tests
Prove intermittent packet loss on PC with detailed jitter and frame logging plus test Broadcom WiFi driver faults before fixing lag.
| Normal jitter | Under 20 ms |
|---|---|
| Acceptable packet loss | Below 1% |
| WiFi unstable if loss >5% | Broadcom drivers often culprit |
| Ping test length | 3-5 minutes |
| GearUP trial | Free PC app |
The short version
- Log jitter and frame times with free PC tools to quantify lag.
- Use Windows CMD ping for packet loss tests over time.
- Broadcom WiFi drivers often cause intermittent packet loss.
- Compare WiFi with wired tests to isolate driver issues.
- GearUP Booster can test and improve server route lag.
How to log jitter and frame times for PC games
Jitter is the variation in packet delay, measured in milliseconds. Tracking jitter during gameplay helps prove intermittent lag. Frame times reveal stutters caused by PC performance or network issues.
Use free tools like MSI Afterburner or Rivatuner Statistics Server to log frame times. Both run alongside your game, recording frame intervals. Look for spikes or irregular intervals over 16 ms indicating stutter.
For jitter, tools like PingPlotter or in-game net graphs can log latency changes. Run them for at least 3 minutes during normal gameplay. A jitter above 20 ms usually causes noticeable lag spikes.
Save logs and examine patterns. Frequent jitter spikes combined with frame time irregularities suggest your PC or network causes lag. Solid frame times but jitter spikes point to network issues. We go through packet loss on WiFi 6 MT7921 reproducible test step by step elsewhere on the site.
Jitter logging also helps spot if your ISP’s network is unstable. If jitter spikes align with packet loss in ping tests, the ISP’s route or infrastructure could be the culprit.
Frame time irregularities over 25 ms typically cause visible stutter or choppy gameplay. For example, if one frame takes 40 ms and the next 10 ms, the uneven pacing feels laggy even if average FPS is high.
You can cross-check frame time spikes with network jitter spikes by comparing timestamps in logs. If frame time spikes coincide with jitter spikes, network lag causes the stutter. If no jitter spikes appear, local PC issues like CPU or GPU bottlenecks are likely. It helps to understand high ping on ethernet before going further.
Testing packet loss with Windows CMD
Windows CMD can test packet loss using continuous ping commands. Run ping [game server IP] -t for 3 to 5 minutes to check packet delivery.
A healthy connection shows 0% packet loss. Packet loss above 1% may cause rubber-banding and lag spikes. Sporadic packet loss indicates intermittent network problems.
Use tracert [game server IP] to identify problematic hops en route. High loss or latency at specific hops suggests your ISP or server route issues. The other half of this decision is udp packet loss detection methods.
Combine CMD tests with jitter logs to confirm if lag comes from network or PC performance. CMD tests need the correct server IP; you can find this via game console commands or community forums.
If you notice packet loss above 1%, try running ping tests at different times of day. Network congestion can cause intermittent loss, showing lower loss during off-peak hours and higher during peak times.
To check packet loss more precisely, use the command ping -n 100 [game server IP]. This sends 100 pings and gives a percentage of lost packets at the end. For example, if 5 packets are lost, packet loss is 5%. We cover does ethernet fix packet loss in its own article.
Intermittent packet loss might not show as continuous 'Request timed out' messages. Instead, you could see occasional timeouts or delayed replies, signaling brief drops or slow responses. Watch for irregular reply times as well as lost packets.
- Open CMD (type cmd in Windows search).
- Enter: ping [game server IP] -t and press Enter.
- Let it run for 3-5 minutes during gameplay.
- Watch for 'Request timed out' messages or packet loss percentage.
- Press Ctrl+C to stop and see statistics.
Broadcom WiFi driver causing packet loss test
Broadcom WiFi adapters often cause intermittent packet loss due to driver issues. Many gamers report lag spikes even with a strong signal.
Test by switching from WiFi to a wired Ethernet connection. If packet loss disappears, the WiFi adapter or driver is suspect. It helps to understand 1% packet loss for gaming before going further.
Update Broadcom drivers to the latest version from the PC maker’s site, not just Windows Update. If problems persist, consider disabling Broadcom WiFi and using a USB WiFi adapter or Ethernet.
Broadcom issues may not show in signal strength metrics but cause packet drops. Tools like Wireshark can confirm dropped packets on the wireless interface.
Some Broadcom WiFi adapters also have power management settings causing packet drops when the device sleeps or lowers power. Check your adapter’s power settings in Device Manager and disable any power-saving modes to improve stability. The other half of this decision is measuring ping under real conditions.
Testing on different WiFi channels can also help. Broadcom adapters may perform poorly on crowded 2.4 GHz channels. Switching to a 5 GHz channel or less congested frequency can reduce packet loss and jitter.
In rare cases, Broadcom driver issues affect only certain Windows versions. If you updated Windows recently and began seeing packet loss, try rolling back the WiFi driver or Windows update to identify the cause.
Intermittent packet loss on PC: how to log jitter, frames, and spot Broadcom WiFi issues
Start by logging jitter and frame times using MSI Afterburner and PingPlotter during your usual gaming session. Check for spikes over 20 ms jitter and frame time irregularities over 16 ms.
Next, run a continuous ping test using Windows CMD for 3 to 5 minutes targeting your game server’s IP. Look for packet loss above 1% or timed out packets.
If you use Broadcom WiFi, test with a wired connection to compare. Persistent packet loss on WiFi but none on wired indicates driver or adapter faults.
Once you confirm route-related packet loss, try GearUP Booster. It reroutes your gaming traffic along better pathways to reduce packet loss and jitter, without changing your PC’s frame rate.
Common mistakes and myths about lag and packet loss testing
Myth: High ping always means packet loss. Fact: Ping measures latency, not packet drops. You can have high ping with no packet loss and vice versa.
Myth: WiFi signal bars guarantee good network quality. Fact: Even with full bars, Broadcom WiFi drivers can cause packet loss.
Mistake: Testing network only once. Packet loss and jitter are intermittent; test multiple times under varying conditions.
Mistake: Using generic ping tests to random websites instead of your game’s server IP. This misses game-specific lag issues.
- Ping ≠ packet loss – test both separately.
- WiFi bars don’t show packet loss.
- Test lag repeatedly, not just once.
- Use game server IP, not random IPs.
How GearUP Booster helps with intermittent packet loss on PC
GearUP Booster routes your game traffic via optimized internet paths to cut packet loss, jitter, and lag spikes caused by ISP or server route issues.
It works with over 3,000 games including Valorant, Fortnite, Apex Legends, CS2, and PUBG. The PC app offers a free trial to test improvements on your route.
GearUP does not increase your PC’s frame rate or fix weak WiFi. It’s best used after confirming your network route causes lag, not local hardware issues.
Using GearUP is a practical next step after manual logging and CMD tests show route-related packet loss. The app’s adaptive routing can stabilize your connection where ISP congestion or cross-region routing spike lag.
Questions people still ask
How long should I log jitter and packet loss during gameplay?
Log jitter and packet loss for at least 3 to 5 minutes during typical gameplay to catch intermittent spikes. Short tests miss occasional lag bursts.
Can I use any ping command to test packet loss?
Use ping to your game server’s IP, not a website or generic IP. This targets the actual route your game traffic takes.
How do I find my game server’s IP address?
Check your game’s network debug console, official forums, or community tools. Some games show it in logs or via server info commands.
What if I don’t have a wired Ethernet port?
Try a USB to Ethernet adapter for a wired test. Alternatively, use a different WiFi adapter to compare with your Broadcom device.
Does GearUP fix local PC performance issues or WiFi signal problems?
No. GearUP only improves internet routing. Fix local hardware or WiFi issues first to benefit from it.
Ready to try it? It reroutes game traffic to reduce lag and packet loss caused by bad server routes or ISP congestion.
Run the free ping test