Coming soon - Get a detailed view of why an account is flagged as spam!
view details

This post has been de-listed

It is no longer included in search results and normal feeds (front page, hot posts, subreddit posts, etc). It remains visible only via the author's post history.

3
Ping spikes just to router over wireless, [probably] caused by the PC
Author Summary
zetka is in probably
Post Body

I've just started using wireless again after being on wired for about 3 months and I am having some severe ping troubles. As far as I'm aware nothing in my computer has significantly changed that could affect my wireless connection.

Issue: Ping spikes of over 1000ms to my router at random intervals

Pinging to my router:

    Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=587ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1362ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=4ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1421ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1181ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=1ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=42ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=3ms TTL=64
    Reply from 192.168.1.254: bytes=32 time=2ms TTL=64

Attempted Solutions:

  • Reinstalled Drivers
  • Trying different Wifi settings (channel, wireless interface type)
  • Switching between 2 and 5 GHz bands
  • Factory Resetting Router
  • Installing WLAN Optimizer
  • Disconnecting all other wireless devices from the network
  • Virus/Malware scan
  • Using older drivers
  • Disabling a number of process and services and preventing them from starting up
  • Booting in Safe mode

So far none of the above have worked

OS: Windows 8.1 64 Bit

My NIC is an http://www.asus.com/uk/Networking/PCEAC68/ , I spent a lot of money on it to make sure I would have no wireless issues but apparently that is not the case.

This is not occurring on any other wireless device I use with this router which leads me to believe something on my PC is causing it.

Any help would be appreciated

Author
Account Strength
100%
Account Age
13 years
Verified Email
Yes
Verified Flair
No
Total Karma
16,761
Link Karma
5,110
Comment Karma
11,552
Profile updated: 4 days ago
Posts updated: 8 months ago

Subreddit

Post Details

Location
We try to extract some basic information from the post title. This is not always successful or accurate, please use your best judgement and compare these values to the post title and body for confirmation.
Posted
9 years ago