Advertisement

PCIe Wi‑Fi card high ping on video calls: find the cause

High ping on calls can come from the Wi‑Fi link, the router, the ISP, or the app itself. This article shows how to test Ethernet, try other bands, and narrow down whether the PCIe Wi‑Fi card is really the problem.

Networking 9 min read
An open desktop PC showing an internal PCIe Wi‑Fi card installed in the motherboard slot.

High ping on a video call usually means one of three things: the Wi‑Fi link between your PC and router is adding delay, the internet path is congested or unstable, or the call app is buffering around packet loss and jitter. The fastest way to isolate it is to test the same call on Ethernet. Then try a different Wi‑Fi band. After that, test a different call app. If Ethernet is clean and only the PCIe Wi‑Fi card path fails, focus on signal quality, interference, driver and power settings, or a bad card installation.

What the high ping is really telling you

On a video call, “high ping” usually means the connection is seeing delay spikes, not just a higher average latency. That delay can come from the PC-to-router link, the wider internet path, or the app itself adding buffering when packets arrive late or out of order.

A browser speed test can look normal while a call still lags. Browsing is bursty. Calls care about steady latency, jitter, and upload stability. Weak Wi‑Fi often shows up as jitter before it turns into a full disconnect, so the call can feel choppy even when web pages load quickly.

A useful clue is where the problem shows up. If the lag happens only in Zoom, Microsoft Teams, or Google Meet, the app or its server path may be part of it. If it happens across apps, the Wi‑Fi path, router, or ISP is more likely.

Before you start

Use the same PC for every test so you do not confuse one device’s behavior with another’s. If you can, keep the PC in the same room as the router for the first pass. Distance, walls, and antenna placement can hide the real cause.

If you are going to change adapter settings, do one change at a time and keep track of what you changed. That makes it much easier to back out if a tweak makes the call worse instead of better.

The three quickest tests to isolate the cause

  1. Try Ethernet if you can.

If a wired connection makes the call smooth, the Wi‑Fi path is the likely bottleneck. That points you toward the adapter, signal quality, interference, band choice, or driver and power settings. If Ethernet still lags, the problem is probably upstream, such as upload saturation, the ISP path, or the app itself.

  1. Move the same PC to a different Wi‑Fi band.

If you are on 2.4 GHz, try 5 GHz or 6 GHz if your router and card support it. If you are already on 5 GHz, test 6 GHz only if both ends support it and the PC is close enough for a stable link. A better band can cut interference and lower jitter without changing anything else.

  1. Use a different call app or a different call type.

If one app lags and another behaves better on the same network, the problem may be app-specific. That can happen when one service handles packet loss, upload variation, or server selection better than another. If every app behaves the same way, focus back on the network path rather than the app.

If Ethernet is clean, look at the Wi‑Fi path

If wired testing is clean, the PCIe Wi‑Fi card path is where to focus. The most common causes are weak signal, interference, band choice, roaming behavior, driver issues, and power saving.

Start with signal quality. A weak signal does not always fail outright; it often creates jitter and short stalls first. If the PC is behind a desk, under a metal case, or tucked near a wall, antenna placement can matter more than people expect. Move the antennas to a clear spot and keep them upright if your card uses external antennas.

Then check the band. The 2.4 GHz band travels farther but is usually busier, so it is more prone to interference and latency swings. The 5 GHz band often gives better latency when signal is strong enough. The 6 GHz band can be even cleaner, but only if the router and adapter support it and the PC is close enough for a stable link.

Driver settings can matter more than people think. Windows or the adapter driver may allow the card to sleep too aggressively, which can add odd delay during sustained traffic. In practice, that can show up during a long call even when casual browsing looks fine. If your adapter vendor offers current drivers, use the latest driver from the official source for that exact card, and prefer the chipset vendor or PC maker when they differ. The Microsoft Q&A case in the retrieved material points in the same direction: the user suspected a Realtek RTL8821CE 802.11ac PCIe Adapter, said the issue continued on a hotspot, and said swapping to another adapter helped only briefly before the lag returned. That pattern can fit the adapter, its driver, or a flaky install rather than a bad internet path.

Roaming can also hurt one machine even when other devices seem fine. If the card keeps trying to switch between access points or mesh nodes, the call may hitch while the connection is technically still alive. That is a router-side behavior, but it only shows up on the device that roams badly.

If Wi‑Fi is fine, check the router and your upload

If Ethernet is clean and the Wi‑Fi link itself looks stable, the router and upload path move to the top of the list. A video call can fall apart when upload is saturated, even if downloads and browsing seem normal.

This is where bufferbloat matters. Bufferbloat is what happens when the router or modem queues too much traffic, so small packets for your call wait behind bigger uploads. The result is ping spikes during activity, not necessarily during idle use. A browser test may still look fine because it does not keep the uplink busy the way a call does.

Check whether someone or something on the same network is uploading, syncing, or backing up while you call. Cloud backups, game uploads, photo sync, and large file transfers can all crowd out call traffic. Some routers have QoS, traffic prioritization, or device prioritization settings that can help. The exact path depends on the model, so use the router’s current manual or admin UI for the current settings.

A router can also treat one PC badly even when other devices seem okay. That can happen with a weak mesh backhaul, a bad access point handoff, a firmware bug, or a band-steering rule that keeps pushing one device around. If the problem appears on only one desktop with a PCIe Wi‑Fi card, the router may still be part of the story, even though phones and laptops look normal.

The YouTube repair walkthrough that was retrieved for this topic showed netsh wlan show settings and netsh wlan set autoconfig enabled=yes interface="WIFI NAME" as troubleshooting commands, but that material is just a tutorial, not proof that those commands fix every adapter issue. Treat them as examples of where people start, not as a guaranteed cure.

What to try first, and when to suspect hardware

  1. Test Ethernet, then a different Wi‑Fi band.

If Ethernet fixes the call, focus on Wi‑Fi. If 5 GHz or 6 GHz is stable while 2.4 GHz is not, the card is probably fine and the problem is signal quality or interference.

  1. Update the Wi‑Fi driver from the correct source.

Use the card maker, motherboard maker, or PC maker’s current driver package for that exact adapter family. If the problem started after a driver change, roll back only if you know the previous version was more stable on your system.

  1. Reposition the antennas and check the installation.

A loose PCIe card, a poorly seated antenna lead, or antennas hidden behind the case can create exactly the kind of random call lag you’re seeing. Power down before touching the card or its antennas, then reseat it if your system design allows that safely.

  1. Reduce power saving on the adapter if your system exposes that option.

This is one of the few settings that can help latency without changing your network gear. If the lag gets worse after a sleep, wake, or long call, power management is a strong suspect.

Those signs point to a bad adapter, bad antenna connection, or a mounting problem rather than a setting you can polish away. I would replace the card, or test it in another known-good system if you have that option, before spending more time on router tweaks.

What usually does not help much is random “speed optimization” advice that ignores the call path. Changing DNS, chasing browser cache tips, or toggling unrelated Windows settings rarely fixes a Wi‑Fi latency spike during a live call. Focus on the link, the band, the driver, and the upload path first.

How to verify the fix worked

Run the same call test that was failing before, on the same desk and with the same PC, after each change. If the call stays smooth for the whole session instead of only for the first minute, that tells you the fix addressed the real bottleneck.

If you changed only one thing and the problem stopped, keep that change and do not pile on more tweaks. If the symptom moved but did not disappear, the remaining issue is probably in a different layer, such as router upload handling or a stubborn driver problem.

If the PC still lags on Ethernet, the Wi‑Fi card is probably not the main cause. At that point, look harder at the ISP path, router behavior, or the call app itself.

Conclusion

If the call only lags on the PCIe Wi‑Fi connection, start with Ethernet, then a better Wi‑Fi band, then a second call app. If those tests point back to the adapter, fix the driver, antenna placement, power settings, or the install itself. If they do not, move your attention to the router, upload saturation, or the app.

Sources