[SOLVED] Ethernet randomly drops to 0 kbps

[avengerbynight001]

Hi hello, I'm a bit new with my PC I guess but for some time now since I came into this apartment, I've had issues with my PC or something where my ethernet/internet speeds suddenly drop to 0 kbps and come back after either a few seconds or minutes. I've been in contact with my ISP but it seems like no matter what I or they do the problem persists which is weird because it feels like at times everything runs smoothly for a few days and then the issue is back. My isp's also mentioned that the issue/breaks I'm running into aren't on their end or in terms of high peak hour usage congestion either. I'm not sure what information is best to give regarding this so I'll just give what I know/have tried so far.

So far I've changed ethernet cables, updated the driver in my old router, updated my Killer E2600 Gigabit Ethernet Controller to one of its latest drivers (version 10.50.511.2021), and disabled my wifi network adapter since I only use ethernet, I then got a new router entirely (an Archer A7 v5.0), I've also disabled settings with my ethernet controller like the energy-efficient ethernet, the checksum offloads, green ethernet, and power-saving mode, etc since I might be forgetting something else, but still all to no avail.

My ipconfig:

Host Name . . . . . . . . . . . . : DESKTOP-79LB3CI
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Ethernet:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Killer E2600 Gigabit Ethernet Controller
Physical Address. . . . . . . . . : 5C-FF-35-E2-01-E0
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::f117:62f5:df1e:d25c%14(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.188(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, October 6, 2021 9:06:57 AM
Lease Expires . . . . . . . . . . : Wednesday, October 6, 2021 11:06:57 AM
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DHCPv6 IAID . . . . . . . . . . . : 442302261
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-27-33-31-BF-5C-FF-35-E2-01-E0
DNS Servers . . . . . . . . . . . : 192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled

This is what I got when I let winmtr run for a while whilst pinging one of the servers belonging to a game I play though I'm not sure how to interpret it
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 91 | 26723 | 2577 | 0 | 0 | 4 | 0 |
| 172.16.7.1 - 93 | 26530 | 1998 | 0 | 3 | 26 | 0 |
| 10.250.51.157 - 93 | 26405 | 1893 | 3 | 14 | 298 | 7 |
| 10.250.50.249 - 94 | 26407 | 1825 | 3 | 14 | 317 | 9 |
| 67.22.16.125 - 91 | 23054 | 2086 | 2 | 14 | 959 | 10 |
| 67.22.16.45 - 93 | 26192 | 2026 | 2 | 16 | 951 | 6 |
| 100.65.0.80 - 74 | 4559 | 1194 | 8 | 32 | 325 | 18 |
|r-equinix-isp-xe-7-0-4-3-2238.wiscnet.net - 95 | 22416 | 1276 | 29 | 51 | 378 | 42 |
| No response from host - 100 | 25065 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25049 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-0-pe04-eqch2.as57976.net - 74 | 4553 | 1187 | 35 | 58 | 328 | 35 |
| No response from host - 100 | 25046 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25050 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25050 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25054 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25045 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25045 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25044 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25026 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25035 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25035 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25049 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25038 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25039 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25021 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25039 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25044 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25035 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25046 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 25045 | 0 | 0 | 0 | 0 | 0 |
|____|__|__|__|__|__|__|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Any help at all would be greatly appreciated!

 

[Lutfij]

Welcome to the forums, newcomer!

Can you please mention the make and model of your motherboard? BIOS version for said motherboard?

 

[avengerbynight001]

Welcome to the forums, newcomer!

Can you please mention the make and model of your motherboard? BIOS version for said motherboard?

The specs for my motherboard are:
Manufacturer Product SerialNumber Version
Acer Predator PO3-620 DBE21110030370031D21B1 1.0

And for its BIOS version I got:
SMBIOSBIOSVersion
R01-A1

 

[bill001g]

You are getting packet loss between your computer and the router. Before you get real far try a simple ping command to the router IP and see if you also see loss.

Maybe you get lucky and it is a bad cable. Try a different one, do not use flat cables those are fake cables. Any cat5e or better should work unless you actually have a 2.5g port on your router.

Next issue is there are many strange issues with 2.5g ports. Not sure about the killer one and how different it is than the intel one. Intel had a bunch of problems and most patched them. I know people have tried older drivers and it sometimes works better.

I really dislike killer stuff. Now that intel bought them I don't know if they have the same issues. Killer loads some stupid "gamer" qos/priority software that causes all kinds of strange issues. I don't know if intel ships this garbage with these chips. You want to uninstall any software application that talks about favoring any kind of traffic.

 

[avengerbynight001]

You are getting packet loss between your computer and the router. Before you get real far try a simple ping command to the router IP and see if you also see loss.

Maybe you get lucky and it is a bad cable. Try a different one, do not use flat cables those are fake cables. Any cat5e or better should work unless you actually have a 2.5g port on your router.

Next issue is there are many strange issues with 2.5g ports. Not sure about the killer one and how different it is than the intel one. Intel had a bunch of problems and most patched them. I know people have tried older drivers and it sometimes works better.

I really dislike killer stuff. Now that intel bought them I don't know if they have the same issues. Killer loads some stupid "gamer" qos/priority software that causes all kinds of strange issues. I don't know if intel ships this garbage with these chips. You want to uninstall any software application that talks about favoring any kind of traffic.

I tried switching cables with an older one and now it definitely doesn't look like there's as much packet loss but I'm not sure. The ping times for the packets judging by the worst part still remain in the same state. As for the killer software, the only thing I have installed is the default performance suite, I've already removed the control center if they're supposedly separate things.

 

[avengerbynight001]

Here's an update with the winmtr but what can I do about the Worst delay/ping category? Because if I'm understanding this correctly are these more geared towards my isp? Or is due to one of the checksum offload settings in the ethernet adapter I turned off?

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.0.1 - 0 | 4734 | 4734 | 0 | 0 | 2 | 0 |
| 172.16.7.1 - 1 | 4710 | 4704 | 0 | 0 | 9 | 0 |
| 10.250.51.157 - 1 | 4711 | 4705 | 3 | 8 | 218 | 16 |
| 10.250.50.249 - 1 | 4708 | 4701 | 3 | 8 | 207 | 14 |
| 67.22.16.125 - 1 | 4711 | 4705 | 2 | 7 | 198 | 7 |
| 67.22.16.45 - 1 | 4726 | 4724 | 2 | 9 | 229 | 3 |
| 100.65.0.80 - 1 | 4656 | 4636 | 8 | 21 | 684 | 14 |
|r-equinix-isp-xe-7-0-4-3-2238.wiscnet.net - 1 | 4638 | 4613 | 29 | 41 | 741 | 32 |
| No response from host - 100 | 948 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 948 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-0-pe04-eqch2.as57976.net - 1 | 4644 | 4621 | 34 | 47 | 877 | 48 |
| No response from host - 100 | 948 | 0 | 0 | 0 | 0 | 0 |
|
| No response from host - 100 | 948 | 0 | 0 | 0 | 0 | 0 |
|____|__|__|__|__|__|__|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

 

[bill001g]

No ISP will give you any guarantee for delay.

Since it is farther into the network nothing you change in your house will have a impact. What is strange is this acts like you have 2 routers in your house. Both hop 1 and hop 2 have latency of zero. Maybe if you have fiber it might be that low.

First you can't read to much into the worst number. You best and average are very close so this means there are very few of those large spikes. It could also be testing errors. A router is set to favor passing traffic rather than responding to ping commands. So if it has data to pass it will delay responding to your ping command.

What you need to do is see what the results are to some end site like 8.8.8.8. You most times will not be able to detect small spikes in applications. It takes either packet loss or a bunch of delayed packets in a row not just a couple here and there.

In any case the only thing you can possibly think to fix is if for some reason you have other traffic in your house causing short overloads of your bandwidth. Almost all traffic delays are caused by data being buffered because of lack of capacity. There is nothing you can do if the problem is say between 2 ISP neither of which might be yours.