[SOLVED] Wired connection experiencing heavy packet loss whilst gaming ?

[nellisboomer]

Hi,

I've been plagued with network issues for a long period of time whilst gaming. These issues are persistent and extreme.

I mainly play Warzone. However i've experienced the same issues on CSGO.

The issue itself is a 10/20 second full disconnect whilst playing. During this time period I can move in game but time has practically stood still (I am usually on discord and my friends voices are lagging) It eventually catches up and I can get back to playing or I full disconnect from the server.
This happens quite often but doesn't seem to have a pattern.

For starters. I'll describe my setup to brief you with as much information as I can.

-My computer is connected to my modem directly using a Cat6 cable i've recently replaced.
-I'm from Australia and my ISP is Launtel.
-I've tried using ExitLag vpn using all three Sydney servers and have experienced the issue on all 3
-When lagging, everything is affected (including discord, google chrome etc)
-The packet loss only affects my computer, Wi-Fi still works perfectly fine.

I've completely reset my modem recently and the issue persists.

This link contains a session of pingplotter in which the issue has occurred:

https://imgur.com/KTh9kNA

View: https://i.imgur.com/KTh9kNA.jpg


I'm having a tough time interpreting my results and what I can do next.

Any help would be greatly appreciated.

Thank you all,

-Jack

 

[bill001g]

Pingplotter tell lots of lies so it takes a while to learn to use the tool. Way too many people go "red bad" ...must fix.

The hops late in the trace that show 100% loss can not be real data because if it was 100% loss then nothing could get past that point and the internet wouldn't work.

What you are looking for is more what you see in the first few hops. You see around 1% loss starting in the first hop and it continues to hops past there. Unfortunately the packet loss appears to be random so it actually stops happening before the test can complete to later nodes. In your cases it does not show any problems to the last hop,

If this consistently happens it means it is a issue with the testing tool and the routers in the path but does not show a actual problem.

You are better off testing to some local IP like 8.8.8.8 or maybe the game server.

Even very small packet loss is very noticeable in a game. Most other applications you will not even see 1% packet loss.

I will assume since you have wifi you actually have a router and just did this test plugged into the modem directly to show it was not the router. This is a good test and your data indicates that it is highly likely that the problem is the in the data circuit coming to your house.


The ISP though is going to try to blame your PC. What I would do is use simple ping commands rather than pingplotter. Pingplotter is to complex for most level 1 ISP techs. What you want to do is open a couple of cmd windows. Leave constant ping run to the router IP and to the first ISP IP....the 100.66.48.1. What you hope to show is that you get no loss at all to your router but you are seeing loss to the first ISP router. The no loss to your router show that the PC and the ethernet cables are good. You can show them with the router removed that you still get loss to the ISP router IP without your router in the path.

 

[nellisboomer]

Thank you so much for your response.

I will try your ping method as soon as I have the time.

 

[nellisboomer]

Pingplotter tell lots of lies so it takes a while to learn to use the tool. Way too many people go "red bad" ...must fix.

The hops late in the trace that show 100% loss can not be real data because if it was 100% loss then nothing could get past that point and the internet wouldn't work.

What you are looking for is more what you see in the first few hops. You see around 1% loss starting in the first hop and it continues to hops past there. Unfortunately the packet loss appears to be random so it actually stops happening before the test can complete to later nodes. In your cases it does not show any problems to the last hop,

If this consistently happens it means it is a issue with the testing tool and the routers in the path but does not show a actual problem.

You are better off testing to some local IP like 8.8.8.8 or maybe the game server.

Even very small packet loss is very noticeable in a game. Most other applications you will not even see 1% packet loss.

I will assume since you have wifi you actually have a router and just did this test plugged into the modem directly to show it was not the router. This is a good test and your data indicates that it is highly likely that the problem is the in the data circuit coming to your house.


The ISP though is going to try to blame your PC. What I would do is use simple ping commands rather than pingplotter. Pingplotter is to complex for most level 1 ISP techs. What you want to do is open a couple of cmd windows. Leave constant ping run to the router IP and to the first ISP IP....the 100.66.48.1. What you hope to show is that you get no loss at all to your router but you are seeing loss to the first ISP router. The no loss to your router show that the PC and the ethernet cables are good. You can show them with the router removed that you still get loss to the ISP router IP without your router in the path.

Ok, after trialing having 2 cmd's open with one pinging to my modem/router & the other pinging to my ISP. I've found that my modem/router receive no packet loss & my ISP ping does receive packet loss.

I was lucky enough to experience the main network disconnect that the original post was based around whilst experimenting.

I've posted two screenshots outlying what it looks like on my CMD

This first one shows the result from pinging my ISP launtel:

https://imgur.com/a/qAVSmwc

View: https://imgur.com/a/qAVSmwc


This second screenshot shows what it looks like in CMD when I time out:

https://imgur.com/a/gvwjhR7

View: https://imgur.com/a/gvwjhR7


What is my next plan of action?

Does this exempt my equipment from fault?

Does fault lay solely on my ISP?

Thanks for your support,
-Jack

 

[bill001g]

Not sure those look like the same IP address.

In any case if you get no loss to the router but loss to the ISP equipment then the problem is likely is the ISP equipment. Most likely wiring outside your house. There is a small possibility that it could be the wiring inside your house. Check for any obvious damaged wires.

I would call the ISP and see if you get lucky and their equipment also detect data loss. Most can run a test from the office that will detect issues. They can also use a ping command similar to what you did but it depends on what type of equipment they are using.

 

[nellisboomer]

Not sure those look like the same IP address.

In any case if you get no loss to the router but loss to the ISP equipment then the problem is likely is the ISP equipment. Most likely wiring outside your house. There is a small possibility that it could be the wiring inside your house. Check for any obvious damaged wires.

I would call the ISP and see if you get lucky and their equipment also detect data loss. Most can run a test from the office that will detect issues. They can also use a ping command similar to what you did but it depends on what type of equipment they are using.

So.

After more frustrating I decided to reset my BIOS settings to default.

This removed both my CPU overclock and RAM XMP.

Taking my cpu from 4.8ghz @ 1.38v back to 3.7 at 1.25.

Since than I haven't experienced the issue this post centres around.

I have no idea why.
Recently i've reenabled XMP and still no issue too.
My next step will be to slowly raise overclock and trial when issue returns.