Question Wi-Fi Packet loss on 1 laptop at hop 1

[Phocidae]

Hello,

I'm having packet loss to my router/modem on my MSI gaming laptop which is limiting my ability to play games online.
the only thing I can think of is maybe 2 weeks ago after a update on my network adapter driver these problems started but im not 100% sure about it.
I have already attempted to reset the modem multiple times which did not help.
the only thing that helps is to directly plug a ethernet cable into the modem but this is not a realistic fix.
thanks in advance for helping me

Specs for my laptop:

Micro-Star International Co., Ltd. GF65 Thin 10UE​

BIOS
Version
E16W2IMS.105
Date
5/14/2021

Motherboard
Manufacturer
Micro-Star International Co., Ltd.
Model
MS-16W2
Version
REV:1.0

Operating System
Edition
Microsoft Windows 10 Home (64 bits)
Version (Build)
22H2 (10.0.19045)

Processor

Intel® Core™ i7-10750H CPU @ 2.60GHz​

Graphics

NVIDIA GeForce RTX 3060 Laptop GPU​

Intel® UHD Graphics​

Audio

Intel® Display Audio​

NVIDIA High Definition Audio​

NVIDIA Virtual Audio Device (Wave Extensible) (WDM)​

Realtek High Definition Audio​

Nahimic mirroring device​

Networking and I/O

Bluetooth Device (Personal Area Network)​

Intel® Wi-Fi 6 AX201 160MHz​

Realtek PCIe GbE Family Controller​

Intel® Wireless Bluetooth®​

Memory

16 GB​

Storage

SAMSUNG MZVLQ1T0HALB-00000​

all drivers are up to date

Modem provided by isp
there are 14 devices connected to the modem
Model: FRITZ!Box 7560
FRITZ!OS: 07.30

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:
0 MSI.fritz.box [192.168.178.21]
1 fritz.box [192.168.178.1]
2 100.65.0.4
3 100.127.1.77
4 ve25.hil-redb-ipr02.tnoc.nl [45.145.109.92]
5 ve25.ams-nkhf-ipr02.tnoc.nl [45.145.109.86]
6 * * *
Computing statistics for 125 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 192.168.178.21
14/ 100 = 14% |
1 11ms 15/ 100 = 15% 1/ 100 = 1% fritz.box [192.168.178.1]
0/ 100 = 0% |
2 17ms 16/ 100 = 16% 2/ 100 = 2% 100.65.0.4
0/ 100 = 0% |
3 31ms 15/ 100 = 15% 1/ 100 = 1% 100.127.1.77
0/ 100 = 0% |
4 19ms 14/ 100 = 14% 0/ 100 = 0% ve25.hil-redb-ipr02.tnoc.nl [45.145.109.92]
2/ 100 = 2% |
5 21ms 16/ 100 = 16% 0/ 100 = 0% ve25.ams-nkhf-ipr02.tnoc.nl [45.145.109.86]

Trace complete.

and direct ping to modem:

Pinging 192.168.178.1 with 32 bytes of data:
Reply from 192.168.178.1: bytes=32 time=11ms TTL=64
Reply from 192.168.178.1: bytes=32 time=14ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=20ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=6ms TTL=64
Reply from 192.168.178.1: bytes=32 time=42ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=38ms TTL=64
Reply from 192.168.178.1: bytes=32 time=8ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=37ms TTL=64
Reply from 192.168.178.1: bytes=32 time=36ms TTL=64
Request timed out.
Reply from 192.168.178.1: bytes=32 time=18ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=158ms TTL=64
Reply from 192.168.178.1: bytes=32 time=395ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=752ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=325ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.178.1: bytes=32 time=1634ms TTL=64
Reply from 192.168.178.1: bytes=32 time=7ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=30ms TTL=64
Reply from 192.168.178.1: bytes=32 time=28ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=21ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=16ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=52ms TTL=64
Reply from 192.168.178.1: bytes=32 time=13ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=13ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=8ms TTL=64
Reply from 192.168.178.1: bytes=32 time=19ms TTL=64
Reply from 192.168.178.1: bytes=32 time=15ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=110ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=43ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=10ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=37ms TTL=64
Reply from 192.168.178.1: bytes=32 time=104ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=623ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1582ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1035ms TTL=64
Reply from 192.168.178.1: bytes=32 time=126ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=695ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=270ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=453ms TTL=64
Reply from 192.168.178.1: bytes=32 time=15ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=9ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=220ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=587ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=17ms TTL=64
Reply from 192.168.178.1: bytes=32 time=191ms TTL=64
Reply from 192.168.178.1: bytes=32 time=7ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=61ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=667ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=443ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Request timed out.
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Reply from 192.168.178.1: bytes=32 time=201ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=375ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=750ms TTL=64
Reply from 192.168.178.1: bytes=32 time=1ms TTL=64
Request timed out.
Reply from 192.168.178.1: bytes=32 time=10ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=10ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=21ms TTL=64
Reply from 192.168.178.1: bytes=32 time=15ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=8ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=17ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=7ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=13ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=8ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=18ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=7ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=13ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=46ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=18ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=6ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=20ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=12ms TTL=64
Reply from 192.168.178.1: bytes=32 time=6ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=6ms TTL=64
Reply from 192.168.178.1: bytes=32 time=32ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=6ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=23ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=24ms TTL=64
Reply from 192.168.178.1: bytes=32 time=6ms TTL=64
Reply from 192.168.178.1: bytes=32 time=7ms TTL=64
Reply from 192.168.178.1: bytes=32 time=77ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=13ms TTL=64
Reply from 192.168.178.1: bytes=32 time=26ms TTL=64
Reply from 192.168.178.1: bytes=32 time=6ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=10ms TTL=64
Reply from 192.168.178.1: bytes=32 time=10ms TTL=64
Reply from 192.168.178.1: bytes=32 time=6ms TTL=64
Reply from 192.168.178.1: bytes=32 time=13ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=6ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=11ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=18ms TTL=64
Reply from 192.168.178.1: bytes=32 time=14ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=5ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=129ms TTL=64
Request timed out.
Reply from 192.168.178.1: bytes=32 time=28ms TTL=64
Reply from 192.168.178.1: bytes=32 time=6ms TTL=64
Reply from 192.168.178.1: bytes=32 time=14ms TTL=64
Reply from 192.168.178.1: bytes=32 time=2ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=3ms TTL=64
Reply from 192.168.178.1: bytes=32 time=4ms TTL=64
Reply from 192.168.178.1: bytes=32 time=41ms TTL=64

Ping statistics for 192.168.178.1:
Packets: Sent = 224, Received = 219, Lost = 5 (2% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1634ms, Average = 61ms

 

[Phocidae]

also other devices in the network do not experience these issues

 

[JohnMGotts]

First thing I’d try is backing out that driver for the old one first, just to be sure.
Does it do it on both the 5 & 2.4 bands?

 

[Phocidae]

First thing I’d try is backing out that driver for the old one first, just to be sure.
Does it do it on both the 5 & 2.4 bands?

it's slightly better on 5 band

 

[JohnMGotts]

Roll back the driver via device manager & retest just to verify your suspicion.
I assume prior to this you had no issue.

 

[Phocidae]

Roll back the driver via device manager & retest just to verify your suspicion.
I assume prior to this you had no issue.

I did this and this has made it a lot better but still some packet loss
atleast i can play online without it being unbearable.
thanks

 

[JohnMGotts]

Likely your antenna placement or interference of other equipment. Is it the same when you’re closer to the router?

 

[Phocidae]

Likely your antenna placement or interference of other equipment. Is it the same when you’re closer to the router?

there is only a wall inbetween nothing else

 

[JohnMGotts]

If you can, try it on the other side of the wall. If it resolves, it’s likely the shortcoming of the laptop wifi antenna. You can check signal strength easily via https://www.howtogeek.com/719669/how-to-check-your-wi-fi-signal-strength-on-windows-10/

 

[Phocidae]

If you can, try it on the other side of the wall. If it resolves, it’s likely the shortcoming of the laptop wifi antenna. You can check signal strength easily via https://www.howtogeek.com/719669/how-to-check-your-wi-fi-signal-strength-on-windows-10/

it's 80% and up where i normally sit and 99% close to the router

 

[JohnMGotts]

And what about packet loss when up close?

 

[Phocidae]

And what about packet loss when up close?

I tried this for an hour 0% packet loss on cmd and 0.1% on pingplotter

 

[Phocidae]

And what about packet loss when up close?

do you think i should buy a tp-link archer t3u.
if it doesn't work I can return it within 30 days for free

 

[JohnMGotts]

You could try the T3U plus. I’d get a usb extender too so you can move the antenna away from the laptop. BTW, it doesn’t have bluetooth (if you even use it.) Additionally, you have to consider the router capability to support that (and your current) wifi adapters. Make sure the router isn’t tucked away somewhere (like behind a couch, etc.)

 

[Phocidae]

You could try the T3U plus. I’d get a usb extender too so you can move the antenna away from the laptop. BTW, it doesn’t have bluetooth (if you even use it.) Additionally, you have to consider the router capability to support that (and your current) wifi adapters. Make sure the router isn’t tucked away somewhere (like behind a couch, etc.)

it didn't work as I had hoped still getting packet loss.
but atleast I now know it's probably not my laptop that is the issue but the router/modem
what do you think is better a wi-fi extender, wi-fi repeater or an additional router?

 

[bill001g]

Likely only going to make it worse with any kind or repeater/extender.

Any kind of repeater must still receive a good signal from the main router. It then must retransmit it to your pc. You now have 2 signals that can cause you issues and unless you buy high end mesh units these 2 signals directly interfere. BUT even the mesh units must receive a good signal from the main router. If you think the main router is the problem then the mesh/repeater will get the same data loss. Many of these devices are using the same wifi chips as end devices use.

Now I guess your current router could be defective but it would be rare that both the 2.4 and 5 radio chips are affected. You can either just replace the router completely or you can buy a inexpensive router and use it as a AP. You would connect the AP to a LAN port and then turn off the radios in the main router. You are in effect replacing the radio chips in the main router.

Will it make any difference I doubt it but you have tried all the other more common things to try to fix wifi packet loss.

You maybe better off spending any money on a non wifi solution. MoCA if you have coax cables tends to be almost as good as ethernet and you can use powerline networks. Powerline device many times are slower than wifi but you seldom get data loss or latency spikes. If you find the download speeds unacceptable you could always switch over to wifi to download and then switch back to powerline to play.

 

[Phocidae]

Likely only going to make it worse with any kind or repeater/extender.

Any kind of repeater must still receive a good signal from the main router. It then must retransmit it to your pc. You now have 2 signals that can cause you issues and unless you buy high end mesh units these 2 signals directly interfere. BUT even the mesh units must receive a good signal from the main router. If you think the main router is the problem then the mesh/repeater will get the same data loss. Many of these devices are using the same wifi chips as end devices use.

Now I guess your current router could be defective but it would be rare that both the 2.4 and 5 radio chips are affected. You can either just replace the router completely or you can buy a inexpensive router and use it as a AP. You would connect the AP to a LAN port and then turn off the radios in the main router. You are in effect replacing the radio chips in the main router.

Will it make any difference I doubt it but you have tried all the other more common things to try to fix wifi packet loss.

You maybe better off spending any money on a non wifi solution. MoCA if you have coax cables tends to be almost as good as ethernet and you can use powerline networks. Powerline device many times are slower than wifi but you seldom get data loss or latency spikes. If you find the download speeds unacceptable you could always switch over to wifi to download and then switch back to powerline to play.

yeah it's disheartening but i know playing with a powerline adapter + ethernet cable works so maybe i will just do that from now on and hope something changes with a driver update or something

 

[bill001g]

Just be happy you have a solution that lets you play the game itself. It is the strange need to download things fast that I like others have trouble resisting. Everytime the ISP tries to get me to upgrade to 5gbit I have to talk myself out of spending another $80/month just to save a couple minutes of total download time a month.