What's new

Fix for Erratic Windows 7 Ping

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

john9527

Part of the Furniture
I was setting up a new PC, and ran into problems with the wireless with very erratic ping times and slow transfer rates. After banging my head against the wall for a while, I realized I forgot to apply the change to force Windows to use a single system clock. Posted as a reminder...data and fix below.....

Before Fix
(C:\)
ping -n 10 ACER-E3FC0000

Pinging ACER-E3FC0000.lan [192.168.1.123] with 32 bytes of data:
Reply from 192.168.1.123: bytes=32 time=383ms TTL=64
Reply from 192.168.1.123: bytes=32 time=78ms TTL=64
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64
Reply from 192.168.1.123: bytes=32 time=203ms TTL=64
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64
Reply from 192.168.1.123: bytes=32 time=421ms TTL=64
Reply from 192.168.1.123: bytes=32 time=109ms TTL=64
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64
Reply from 192.168.1.123: bytes=32 time=202ms TTL=64
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.123:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 421ms, Average = 140ms

Apply Fix
Open cmd window with Run As Administrator

Enter:
bcdedit /set {default} useplatformclock true

Reboot Windows

After Fix
(C:\)
ping -n 10 ACER-E3FC0000

Pinging ACER-E3FC0000.lan [192.168.1.123] with 32 bytes of data:
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64
Reply from 192.168.1.123: bytes=32 time<1ms TTL=64
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64
Reply from 192.168.1.123: bytes=32 time=1ms TTL=64
Reply from 192.168.1.123: bytes=32 time=2ms TTL=64
Reply from 192.168.1.123: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.1.123:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 2ms, Average = 1ms
 
This tweak depends on the HW/BIOS supporting HPET - so for some folks this might have a negative impact - esp on older HW that is still supported by Win7 - for Win8/8.1 and Linux/*BSD this shouldn't be needed - sometimes Win7 doesn't enable HPET on install, falling back to LAPIC/ACPI...

Check BIOS to see if there is a switch for HPET, if so, make sure it's enabled, and Windows will use it (so will linux).
 
This tweak depends on the HW/BIOS supporting HPET - so for some folks this might have a negative impact - esp on older HW that is still supported by Win7 - for Win8/8.1 and Linux/*BSD this shouldn't be needed - sometimes Win7 doesn't enable HPET on install, falling back to LAPIC/ACPI...

Check BIOS to see if there is a switch for HPET, if so, make sure it's enabled, and Windows will use it (so will linux).

I think you need to go back quite a bit for a problem (the change makes a big difference for me down to a lowly Intel N450 Netbook).

Also, my experience (at least with Win 7) is that it's hit or miss being picked up. I had to set it manually on an ASUS 99FX board with HPET enabled.

If it does make things worse for you....it's easily disabled. From a Run as Administrator cmd window...

bcdedit /deletevalue {default} useplatformclock

and reboot.
 

Similar threads

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top