F5F Stay Refreshed Power Users Networks Unusual notification problem on Windows 10 Issue with pings or alerts not functioning properly

Unusual notification problem on Windows 10 Issue with pings or alerts not functioning properly

Unusual notification problem on Windows 10 Issue with pings or alerts not functioning properly

A
Azastias
Member
223
05-22-2016, 07:33 AM
#1
Hey, I see something odd here. You might want to try this with me. It becomes more obvious when using AMD's 3000 series CPU. - Connect directly to your router - don’t run other programs on your PC. Open the command prompt (press Start > type "cmd"). Type "ping <your local router IP> -t" unless you have a complicated network or powerline setup, then it should be under 1ms. While pinging, launch a game or application. You don’t need to join any server—just open the main menu of the game. Notice a sudden increase in ping. See below Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=19ms TTL=64 Reply from 192.168.1.1: bytes=32 time=20ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 I’ve asked over six people from different countries to test this. Those who don’t see the issue consistently are using Windows 1909. The rest are running Windows 2004 or 20H2. I’ve checked my router, cables, ports, drivers… etc. Plus others are facing the same problem as me (the six international participants). I’m pretty sure it’s not a hardware problem. In Windows XP, 7, this issue doesn’t appear. Someone also mentioned that Windows 10 might now include processing delay in ping. Not entirely sure.
A
Azastias
05-22-2016, 07:33 AM #1

Hey, I see something odd here. You might want to try this with me. It becomes more obvious when using AMD's 3000 series CPU. - Connect directly to your router - don’t run other programs on your PC. Open the command prompt (press Start > type "cmd"). Type "ping <your local router IP> -t" unless you have a complicated network or powerline setup, then it should be under 1ms. While pinging, launch a game or application. You don’t need to join any server—just open the main menu of the game. Notice a sudden increase in ping. See below Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 Reply from 192.168.1.1: bytes=32 time=5ms TTL=64 Reply from 192.168.1.1: bytes=32 time=19ms TTL=64 Reply from 192.168.1.1: bytes=32 time=20ms TTL=64 Reply from 192.168.1.1: bytes=32 time<1ms TTL=64 I’ve asked over six people from different countries to test this. Those who don’t see the issue consistently are using Windows 1909. The rest are running Windows 2004 or 20H2. I’ve checked my router, cables, ports, drivers… etc. Plus others are facing the same problem as me (the six international participants). I’m pretty sure it’s not a hardware problem. In Windows XP, 7, this issue doesn’t appear. Someone also mentioned that Windows 10 might now include processing delay in ping. Not entirely sure.

I
imTri
Posting Freak
786
05-22-2016, 09:14 AM
#2
It could simply be that starting a game causes a brief lag during the first boot, which might temporarily affect performance. The pinging stops when you press Ctrl+C, as the -t flag continues until you interrupt it.
I
imTri
05-22-2016, 09:14 AM #2

It could simply be that starting a game causes a brief lag during the first boot, which might temporarily affect performance. The pinging stops when you press Ctrl+C, as the -t flag continues until you interrupt it.

H
145
05-25-2016, 09:57 PM
#3
This problem didn’t occur on my older Windows XP PC, though I suspect the latest updates might be the cause.
H
hamsterdance00
05-25-2016, 09:57 PM #3

This problem didn’t occur on my older Windows XP PC, though I suspect the latest updates might be the cause.

P
perssonTA
Member
118
06-01-2016, 06:56 PM
#4
I tested it and everything worked fine. Launched Minecraft and Outlook 2016. Wireless ping stayed under 1 ms without using Windows 10, but on Windows 9 (Win8.1 with industry embedded pro and a Win7 skin).
P
perssonTA
06-01-2016, 06:56 PM #4

I tested it and everything worked fine. Launched Minecraft and Outlook 2016. Wireless ping stayed under 1 ms without using Windows 10, but on Windows 9 (Win8.1 with industry embedded pro and a Win7 skin).

M
Mexassassin07
Member
50
06-04-2016, 05:54 PM
#5
It appears to run on Windows 2004 or 20H2 and is impacted by non-network dependent programs such as AMD Ryzen Master. Opening it directly triggers a significant increase in activity.
M
Mexassassin07
06-04-2016, 05:54 PM #5

It appears to run on Windows 2004 or 20H2 and is impacted by non-network dependent programs such as AMD Ryzen Master. Opening it directly triggers a significant increase in activity.

I
Ice3Boy
Member
230
06-22-2016, 08:27 AM
#6
Yes, someone with networking expertise can test this on Windows 10. The feedback you received suggests there may be an issue or bug related to the connection.
I
Ice3Boy
06-22-2016, 08:27 AM #6

Yes, someone with networking expertise can test this on Windows 10. The feedback you received suggests there may be an issue or bug related to the connection.

T
Towny_
Junior Member
4
06-22-2016, 12:46 PM
#7
I just tested it on my computer and it happens too. Probably similar to what @flashiling mentioned—starting a game causes the system to briefly slow down (temporarily uses a lot of CPU) and slightly delays the pings. Or maybe the game you and I started has heavy network connections right from the beginning, which affects the packet timing a bit. We're only talking about a few milliseconds for a couple of packets, which isn't noticeable at all.
T
Towny_
06-22-2016, 12:46 PM #7

I just tested it on my computer and it happens too. Probably similar to what @flashiling mentioned—starting a game causes the system to briefly slow down (temporarily uses a lot of CPU) and slightly delays the pings. Or maybe the game you and I started has heavy network connections right from the beginning, which affects the packet timing a bit. We're only talking about a few milliseconds for a couple of packets, which isn't noticeable at all.

F
FearCZ__Ever
Member
56
06-23-2016, 10:48 AM
#8
I really can't recall this occurring on Windows 7 or XP with an older PC, to be honest. Thanks for your feedback!
F
FearCZ__Ever
06-23-2016, 10:48 AM #8

I really can't recall this occurring on Windows 7 or XP with an older PC, to be honest. Thanks for your feedback!

J
justxtamara
Junior Member
11
06-25-2016, 12:14 AM
#9
I believe I identified the reason; it was released on February 9, 2021 - KB4601050 Cumulative Update for .NET Framework 3.5 and 4.8 targeting Windows 10, version 2004, Windows Server 2004, Windows 10 20H2, and Windows Server 2004 20H2. This update follows the one released after uninstalling it on January 12, 2021 - KB4586876 Cumulative Update Preview for the same versions. Installing it on another machine triggered the spike. Removing it resolved my problem. An update (KB4578968) also seems to impact this and appears after KB4586876.
J
justxtamara
06-25-2016, 12:14 AM #9

I believe I identified the reason; it was released on February 9, 2021 - KB4601050 Cumulative Update for .NET Framework 3.5 and 4.8 targeting Windows 10, version 2004, Windows Server 2004, Windows 10 20H2, and Windows Server 2004 20H2. This update follows the one released after uninstalling it on January 12, 2021 - KB4586876 Cumulative Update Preview for the same versions. Installing it on another machine triggered the spike. Removing it resolved my problem. An update (KB4578968) also seems to impact this and appears after KB4586876.

I
inderkiller24
Member
136
07-01-2016, 10:59 AM
#10
For those curious, the latest cumulative update appears to resolve this problem, and the ping issue is now quite minor.
I
inderkiller24
07-01-2016, 10:59 AM #10

For those curious, the latest cumulative update appears to resolve this problem, and the ping issue is now quite minor.