Question Only one computer on network having ping spikes on ethernet despite fresh windows install, new cable, different ethernet port, ect.

[TheRustiestOne]

About a week and a half ago, while gaming, I noticed my computer starting to have ping spikes. These ping spikes have gotten worse and worse as this last week has gone on.

when I try and ping google I get this

Pinging google.com [2607:f8b0:4000:803::200e] with 32 bytes of data:
Reply from 2607:f8b0:4000:803::200e: time=21ms
Reply from 2607:f8b0:4000:803::200e: time=23ms
Reply from 2607:f8b0:4000:803::200e: time=22ms
Reply from 2607:f8b0:4000:803::200e: time=21ms
Reply from 2607:f8b0:4000:803::200e: time=22ms
Reply from 2607:f8b0:4000:803::200e: time=23ms
Reply from 2607:f8b0:4000:803::200e: time=22ms
Reply from 2607:f8b0:4000:803::200e: time=20ms
Reply from 2607:f8b0:4000:803::200e: time=881ms
Reply from 2607:f8b0:4000:803::200e: time=20ms
Reply from 2607:f8b0:4000:803::200e: time=21ms
Reply from 2607:f8b0:4000:803::200e: time=21ms
Reply from 2607:f8b0:4000:803::200e: time=20ms
Reply from 2607:f8b0:4000:803::200e: time=21ms
Reply from 2607:f8b0:4000:803::200e: time=23ms
Reply from 2607:f8b0:4000:803::200e: time=985ms
Reply from 2607:f8b0:4000:803::200e: time=21ms
Reply from 2607:f8b0:4000:803::200e: time=32ms
Reply from 2607:f8b0:4000:803::200e: time=19ms

As you can see every few seconds I get a huge ping spike which makes gaming unplayable. this happens for any game anytime, even with nothing running this happens. Now for the past week I've been trying to fix it and nothing has worked. I tried everything I could with windows setting but after nothing worked, I just decided to do a completely fresh install of windows and it still wouldn't work. I then tried a different ethernet cable and a different ethernet port but it still didnt work. my computer is custom and doesnt have a wifi card so I cant test anything but ethernet. I also went around to other computers on my network and none of them had this issue as well. At this point Im completely lost, should I buy new motherboard or anything? any ideas would really help

 

[Ralston18]

IPv6.

Can be problematic for some systems.

Try disabling IPv6 and use only IPv4.

 

[TheRustiestOne]

IPv6.

Can be problematic for some systems.

Try disabling IPv6 and use only IPv4.

I disabled IPv6 and now it is simply dropping the packets

Pinging google.com [142.251.35.206] with 32 bytes of data:
Reply from 142.251.35.206: bytes=32 time=20ms TTL=116
Reply from 142.251.35.206: bytes=32 time=18ms TTL=116
Request timed out.
Reply from 142.251.35.206: bytes=32 time=17ms TTL=116
Reply from 142.251.35.206: bytes=32 time=20ms TTL=116
Reply from 142.251.35.206: bytes=32 time=18ms TTL=116
Reply from 142.251.35.206: bytes=32 time=20ms TTL=116
Reply from 142.251.35.206: bytes=32 time=21ms TTL=116
Reply from 142.251.35.206: bytes=32 time=139ms TTL=116
Reply from 142.251.35.206: bytes=32 time=19ms TTL=116
Reply from 142.251.35.206: bytes=32 time=18ms TTL=116
Reply from 142.251.35.206: bytes=32 time=19ms TTL=116
Reply from 142.251.35.206: bytes=32 time=21ms TTL=116
Reply from 142.251.35.206: bytes=32 time=49ms TTL=116
Reply from 142.251.35.206: bytes=32 time=17ms TTL=116
Reply from 142.251.35.206: bytes=32 time=18ms TTL=116
Reply from 142.251.35.206: bytes=32 time=22ms TTL=116
Reply from 142.251.35.206: bytes=32 time=19ms TTL=116
Request timed out.

 

[plausible_deniability]

Do you have a Router or does your Modem have a Router built in?

 

[bill001g]

Ping the router IP instead. If the problem is actually the pc it should have the same issues. If not you have some strange error since it should affect all machines if it is in the internet.

I doubt it is a actual bad port that is very rare. Note if you have a 2.5g port there are issues with certain intel chipsets, that can't be fixed but is not the exact symptom you are having. Later hardware revisions seem to be fixed.

I would not go to the trouble of replacing a motherboard for a bad port. A add in pcie ethernet card is pretty cheap. You can also get usb3 devices that can run 1gbit. But before you consider spending any money I would load a linux USB image. This will let you test without disrupting your windows install. If linux has the same issue then you suspect a hardware issue otherwise it is some garbage in windows. I would try the drivers from the motherboard manufacture as well as the vendor that makes the ethernet chip. The ones you want to avoid are the microsoft generic drivers.

 

[Ralston18]

142.251.35.206 ?

What is the source of that IP address? How/why was that IP used?

Try 8.8.8.8 or 8.8.4.4

(142.251.35.206 seems to be an address associated with google (?) but I am not sure what the association is.

 

[TheRustiestOne]

142.251.35.206 ?

What is the source of that IP address? How/why was that IP used?

Try 8.8.8.8 or 8.8.4.4

(142.251.35.206 seems to be an address associated with google (?) but I am not sure what the association is.

that was pining google but the problem is also there when I ping 8.8.8.8

 

[TheRustiestOne]

Ping the router IP instead. If the problem is actually the pc it should have the same issues. If not you have some strange error since it should affect all machines if it is in the internet.

I doubt it is a actual bad port that is very rare. Note if you have a 2.5g port there are issues with certain intel chipsets, that can't be fixed but is not the exact symptom you are having. Later hardware revisions seem to be fixed.

I would not go to the trouble of replacing a motherboard for a bad port. A add in pcie ethernet card is pretty cheap. You can also get usb3 devices that can run 1gbit. But before you consider spending any money I would load a linux USB image. This will let you test without disrupting your windows install. If linux has the same issue then you suspect a hardware issue otherwise it is some garbage in windows. I would try the drivers from the motherboard manufacture as well as the vendor that makes the ethernet chip. The ones you want to avoid are the microsoft generic drivers.

when I ping 8.8.8.8 I get the same problem. Also after checking I do have a 2.5g port and a newer intel cpu so I'm a bit worried that could be my issue. I'm going to go ahead and pick up a ethernet pcie card tommorow and see if it works. If all else fails I might just strip some components and build a new computer.

 

[Nathkrul]

Ping your local ip, type ipconfig into a command prompt to get it, look for ipv4 address, then type ping (yourlocaliphere) -t and let it run for a few minutes, come back with the results please, thx.

Sorry I should have made it clear that you want your routers IP address in here to ping.

 

[Ralston18]

Regarding: "If all else fails I might just strip some components and build a new computer. ".

If a new ethernet pcie card does not resolve the problem, it is still not worth the immediate effort and trouble to build a new computer.

(In agreement with @bill001g.)

A bit more troubleshooting may identify the cause of the spikes.

Run "ipconfig /all" via the Command prompt and post the results. Just for the record.

[Note you can copy and past the 'ipconfig /all" results without needing to retype everything.]

Also, while gaming, open a window into either Task Manager or Resource Monitor. Use both tools but only one tool at a time.

The objective being to observe system performance (it may take some trial and error effort) to spot what, if anything, the system is doing or trying to do when spikes occur.

Especially if the problem is limited to just your computer on the network.

 

[johnbl]

what is your network chip name? ie look for a network driver update.
if the network interface in over a usb, be sure to update the bios/chipset and set the usb hub not to go to sleep.

you might ping your loopback driver to see if the problem is in the local network stack.

ie something like
ping -n 30 127.0.0.1

or ping your gateway address

I guess i would also look at what other network activity is going on with the local machine.
ie run cmd.exe as an admin then run
netstat.exe -b
to list the network processes .exes that are currently running

or maybe boot in safe mode and run your ping test or try a second network adapter

 

[TheRustiestOne]

Regarding: "If all else fails I might just strip some components and build a new computer. ".

If a new ethernet pcie card does not resolve the problem, it is still not worth the immediate effort and trouble to build a new computer.

(In agreement with @bill001g.)

A bit more troubleshooting may identify the cause of the spikes.

Run "ipconfig /all" via the Command prompt and post the results. Just for the record.

[Note you can copy and past the 'ipconfig /all" results without needing to retype everything.]

Also, while gaming, open a window into either Task Manager or Resource Monitor. Use both tools but only one tool at a time.

The objective being to observe system performance (it may take some trial and error effort) to spot what, if anything, the system is doing or trying to do when spikes occur.

Especially if the problem is limited to just your computer on the network.

Sorry for the late response I've been fairly busy this week. I got a new network card and that still hasnt fixed the issue. I've been testing everything suggested and I cant figure anything out. When I ran ipconfig netstat.exe -b, only normal network items showed up and none of them correlated with the spikes. Also in task manager there are no spikes in any of the different components even when lagging.

here is what I got when I ran ipconfig /all



Host Name . . . . . . . . . . . . : DESKTOP-6UT6EEA
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : hsd1.tx.comcast.net

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : hsd1.tx.comcast.net
Description . . . . . . . . . . . : Realtek PCIe 2.5GbE Family Controller
Physical Address. . . . . . . . . : 56-56-56-56-56-56
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . : hsd1.tx.comcast.net
Description . . . . . . . . . . . : Realtek PCIe 2.5GbE Family Controller #2
Physical Address. . . . . . . . . : 48-22-54-6F-F4-89
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv6 Address. . . . . . . . . . . : 2601:2c4:4300:a440::f5dd(Preferred)
Lease Obtained. . . . . . . . . . : Wednesday, March 29, 2023 9:00:10 PM
Lease Expires . . . . . . . . . . : Friday, March 31, 2023 10:07:27 PM
IPv6 Address. . . . . . . . . . . : 2601:2c4:4300:a440:ea71:adb:6689:dd5(Preferred)
Temporary IPv6 Address. . . . . . : 2601:2c4:4300:a440:cf8:bc2c:1d8f:e590(Preferred)
Link-local IPv6 Address . . . . . : fe80::cbc4:468a:f172:bdec%12(Preferred)
IPv4 Address. . . . . . . . . . . : 10.0.0.129(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : Wednesday, March 29, 2023 9:00:09 PM
Lease Expires . . . . . . . . . . : Friday, March 31, 2023 9:00:09 PM
Default Gateway . . . . . . . . . : fe80::9a9d:5dff:fe75:3ff7%12
10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DHCPv6 IAID . . . . . . . . . . . : 407380564
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-2B-B2-5E-4C-56-56-56-56-56-56
DNS Servers . . . . . . . . . . . : 2001:558:feed::1
2001:558:feed::2
75.75.75.75
75.75.76.76
2001:558:feed::1
2001:558:feed::2
NetBIOS over Tcpip. . . . . . . . : Enabled

 

[TheRustiestOne]

Ping your local ip, type ipconfig into a command prompt to get it, look for ipv4 address, then type ping (yourlocaliphere) -t and let it run for a few minutes, come back with the results please, thx.

Sorry I should have made it clear that you want your routers IP address in here to ping.

Just did this and there was no spikes in the response times, It stayed at a steady 1ms

 

[Ralston18]

IPv6 is still enabled. Did you re-enable it again after it began dropping packets?

On your computer try disabling IPv6. Often problematic for some systems. Disable, reboot, and try again.

Also:

Ethernet adapter Ethernet:

Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . : hsd1.tx.comcast.net
Description . . . . . . . . . . . : Realtek PCIe 2.5GbE Family Controller
Physical Address. . . . . . . . . : 56-56-56-56-56-56
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes

Did you edit or change that physical address? That is not a MAC that I would expect to see.....

Question: make and model router (or modem/router) if combined)?

The router (DHCP server) address is 10.0.0.1 and your computer is currently being provided an IPv4 DHCP IP address of 10.0.0.129.

Both are likely normal but best to confirm via the router make and model although end users can change the values.

Lastly: change the DNS servers to Google at 8.8.8.8 and 8.8.4.4

Versus Comcast's 75.75.75.75

Reference:

https://forums.xfinity.com/conversa...57676-revisited-2020/602dae29c5375f08cde06033

Older link. However, no harm in trying Google's addresses to determine if the spikes decrease.

 

[bill001g]

You are going to need to do better testing. You should have pinged the router IP before your spent the money on buying a nic card.
As mentioned above make sure IPv6 is disabled mostly so you are not running a mix of ipv6 and ipv4 when you test.

What is now inconsistent in what your previous testing shows is
You say no other devices is affected. Means internet/router should be good.
Your machine can ping the router with no loss, which means the device and cables are good.

These together eliminate all possibilities.

Since you have also replace the nic card that makes it much more likely this is a problem outside the machine and your other machine are actually being affected but you just did not find it.

The biggest issue you have is your ISP is not going to want to help you with latency issues. Packet loss is something they will fix.

Next step if we now assume there actually is something that affects all machines.
First run tracert 8.8.8.8. This will not likely show any errors it is mostly to get the IP addresses in the path.

Next try to run pings to hop 1 and hop 2 to start. Hop 1 is your router IP and again it should show no loss but let it run for a while. Hop 2 in most cases should be the ISP first router. Problems on hop 2 represent a issue with the cables coming to your house in most cases. Sometime the ISP will rig it so hop 2 will not respond to ping to you will need to try hop 3. Your goal is to see packet loss. Latency spikes are going be much harder to get the ISP to fix because they are being caused by a overloaded connection rather than defective equipment in most cases.