NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Netgear A6100 Wifi Adapter suddenly get lagspikes
I've had an A6100 wifi adapter for at least a year now with no problems at all. Last week i suddenly get lagspikes at 3k+ ms. Phones and laptops at the same network is working fine, i have also trie...
I solved it! Yesterday I stumbled upon a thread completely accidentally where somebody was experiencing the same problem. Granted, this solution won't work for you unless you have a Roccat product though.
The problem is the Roccat Swarm software! Upon uninstalling it, my connection becomes completely stable, the problem was not with Netgear at all! Hopefully this can at least raise awareness of this issue, as suspecting a gaming mouse's software does not seem logical at all for networking issues...
It's worth noting that I was able to achieve a stable connection with my A6100 on Windows 10 Home using current standalone drivers (Netgear Genie not installed).
So im not the only one, sorry to hear you have the same problem!
Unfortunately still no reply about why..
Hi All,
Do you have other devices that works fine or has a stable connection with the router? Try to uninstall and reinstall the driver of the adapter and use the standalone driver instead of the driver with Genie.
JamesGL
Community Team
Hi JamesGL,
I'm glad you have time to help us out :) So I have an Asus dongle that only works on the 2,4GHz band. I tried it out on my laptop a couple of weeks ago (I disabled the device's own wifi adapter using Device Manager) and I got a stable connection with a ping test.
I've also tried installing the standalone driver several times. On some occasions it worked fine for a while, but the connection becomes unstable again after a period of time and starts experiencing the 3k lagspikes. I'm not entirely sure but it seems like my driver keeps changing on every new reboot (currently I have Netgear Genie installed, gonna try uninstalling it now and doing the standalone installation one more time).
Furthermore, the adapter doesn't find any wifi signals after coming back from Sleep mode. I solve that by replugging the adapter and all of a sudden it magically finds wifi signals again. Not a big deal, only slightly annoying.
I'll definitely post it here if the new standalone installation works for me, otherwise assume that it didn't work.
Reply from 192.168.1.1: bytes=32 time=17ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3023ms TTL=64
Reply from 192.168.1.1: bytes=32 time=21ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3009ms TTL=64
Reply from 192.168.1.1: bytes=32 time=13ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3019ms TTL=64
Reply from 192.168.1.1: bytes=32 time=22ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3016ms TTL=64
Reply from 192.168.1.1: bytes=32 time=57ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Ping statistics for 192.168.1.1:
Packets: Sent = 284, Received = 284, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3202ms, Average = 285msThere's the result of my ping test after installing the standalone driver (I downloaded the newest one). This was on the 5 GHz band. Before you ask, yes I did uninstall the previous driver and Netgear Genie.
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=9ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3082ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=41ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=5ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3001ms TTL=64
Reply from 192.168.1.1: bytes=32 time=6ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=1ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=2ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3ms TTL=64
Reply from 192.168.1.1: bytes=32 time=3062ms TTL=64
Reply from 192.168.1.1: bytes=32 time=4ms TTL=64
Ping statistics for 192.168.1.1:
Packets: Sent = 129, Received = 119, Lost = 10 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3247ms, Average = 251msThat's the result on the 2,4 GHz band. Sorry for the spam :)
Hi All,
Is it possible to check the wired connection from the router and see if the same problem.
JamesGL
Community Team
Hi Glitch404,
We’d greatly appreciate hearing your feedback letting us know if you need further assistance.
JamesGL
Community Team
Well I've been testing my wifi a little bit more now and I don't think the problem is specifically with the Netgear adapter anymore.I've tested my wifi using the Netgear A6100 dongle AND a separate ASUS dongle that only has the 2,4GHz band. I tests using both dongles (also tested both bands on the A6100), both in my room and right next to the router. I ran these tests both on my desktop and my laptop. In addition, I ran a wired test on my desktop (laptop doesn't have a LAN port).
The conclusion is that I get the 3k ping spikes on my desktop, regardless of the used dongle nor the desktop's proximity to the router. However, my laptop does not get these lagspikes, even though the operating system is exactly the same (both have Win10 Anniversary update). I'm fairly certain that the problem isn't my router (Netgear R6100), as the wired test yielded a completely flawless connection in addition to a good wireless connection on the laptop.
I've tried upgrading the chipset on my motherboard, among other fixes, but I'm beginning to suspect that the problem is in my desktop's hardware setup, as I don't have a stock computer. I don't think this is Netgear's problem though, but I thought I'd post this for anyone experiencing the same problems expecting Netgear to solve it.