Associate
Decided that it was time to reinstall Windows 10. Everything went well but then I am playing PUBG for the first time and find my ping is spiking to 400ms in game briefly. Whilst game running I switch to desktop and run a ping and see the same thing - every 30secs or so my ping goes through the roof for 1 ping only like this:
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=505ms TTL=64 <<<---
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=8ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
It ranges from 500ms up to 1.5s. I am running a wired ethernet connect so no Wifi. Same thing just pinging my local router GW IP so its not ISP related and never happened before the reinstall. So far I have done the following:
1) Installed latest Intel NIC drivers
2) Rebooted router (even though another laptop connected via same switch has no such issues when running a ping at the same time)
3) Used different port on Router
4) Reseated & replaced ethernet cables as a precaution
5) Updated Win 10 - was 1903 now 1909
6) Watched via resource mgr and seeing no CPU, GPU, Memory surge at or around time of ping
7) Changed NIC from autoneg to 1gig Full Duplex hard coded
8) Disabled windows update via other PC's (as googling this seemed to be a first suggestion for similar such issues).
If I run a parallel ping to my own IP the spikes dont happen (all <1ms) so it definitely seems to be NIC related rather than resource related (CPU, mem etc).
My mobo doesnt have WIFI to test if I have the same issue over wireless but I would expect not.
Any ideas on what else it might be?
Thanks
Simon
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
Reply from 192.168.1.254: bytes=32 time=505ms TTL=64 <<<---
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
Reply from 192.168.1.254: bytes=32 time=8ms TTL=64
Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
It ranges from 500ms up to 1.5s. I am running a wired ethernet connect so no Wifi. Same thing just pinging my local router GW IP so its not ISP related and never happened before the reinstall. So far I have done the following:
1) Installed latest Intel NIC drivers
2) Rebooted router (even though another laptop connected via same switch has no such issues when running a ping at the same time)
3) Used different port on Router
4) Reseated & replaced ethernet cables as a precaution
5) Updated Win 10 - was 1903 now 1909
6) Watched via resource mgr and seeing no CPU, GPU, Memory surge at or around time of ping
7) Changed NIC from autoneg to 1gig Full Duplex hard coded
8) Disabled windows update via other PC's (as googling this seemed to be a first suggestion for similar such issues).
If I run a parallel ping to my own IP the spikes dont happen (all <1ms) so it definitely seems to be NIC related rather than resource related (CPU, mem etc).
My mobo doesnt have WIFI to test if I have the same issue over wireless but I would expect not.
Any ideas on what else it might be?
Thanks
Simon