Windows 7 Forums

Welcome to Windows 7 Forums. Our forum is dedicated to helping you find support and solutions for any problems regarding your Windows 7 PC be it Dell, HP, Acer, Asus or a custom build. We also provide an extensive Windows 7 tutorial section that covers a wide range of tips and tricks.


Windows 7: Ping spikes

11 Jul 2014   #1
keyboardface

Windows 7 Ultimate x64
 
 
Ping spikes

Recently I've started getting these big ping spikes whilst online gaming making them kinda pointless to play cos I'd get temporary 'Connection Interrupted' errors and such. My setup hasn't changed and I've never had this problem before so I'm hoping it's a software issue or some pretty well hidden malware.

Code:
Pinging google.com [173.194.34.169] with 32 bytes of data:
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=36ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=39ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=36ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=34ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=32ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=32ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=39ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=34ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=32ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=97ms TTL=58
Reply from 173.194.34.169: bytes=32 time=206ms TTL=58
Reply from 173.194.34.169: bytes=32 time=251ms TTL=58
Reply from 173.194.34.169: bytes=32 time=56ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=1192ms TTL=58
Reply from 173.194.34.169: bytes=32 time=112ms TTL=58
Reply from 173.194.34.169: bytes=32 time=1362ms TTL=58
Reply from 173.194.34.169: bytes=32 time=185ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=78ms TTL=58

Ping statistics for 173.194.34.169:
    Packets: Sent = 93, Received = 93, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 1362ms, Average = 65ms
I've restarted in Safe Mode with Networking and tried the same thing and the ping spikes still occur.
I've tested the ping to Google on another machine on the network and there were no spikes at all, ~30ms straight across the board.

Any ideas to help me work out what's causing them? Any help would be much appreciated.


My System SpecsSystem Spec
.
11 Jul 2014   #2
carwiz

Windows 7 Pro-x64
 
 

If you're not pinging Google, perhaps Google is pinging because you have some com blocked. Do you run Chrome or the Tool Bar? They both "phone home" and report everything you do on your PC, basically.
My System SpecsSystem Spec
11 Jul 2014   #3
keyboardface

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by carwiz View Post
If you're not pinging Google, perhaps Google is pinging because you have some com blocked. Do you run Chrome or the Tool Bar? They both "phone home" and report everything you do on your PC, basically.
I'm not sure what you mean sorry? I just used Google as an example to demonstrate the ping spikes. If you scroll down you'll see the spikes in bold.

I use Firefox.
My System SpecsSystem Spec
.

11 Jul 2014   #4
carwiz

Windows 7 Pro-x64
 
 

So you did the pinging. So what's the problem?

It's not unusual for pings to be all over the place unless you have exclusive use of the routers from your location to the site. What did you use for the ping test?

I just ran one and it's showing packet losses. Could be a router problem somewhere.


Attached Thumbnails
Ping spikes-ping-google.com.png  
My System SpecsSystem Spec
11 Jul 2014   #5
keyboardface

Windows 7 Ultimate x64
 
 

Quote   Quote: Originally Posted by carwiz View Post
So you did the pinging. So what's the problem?

It's not unusual for pings to be all over the place unless you have exclusive use of the routers from your location to the site. What did you use for the ping test?

I just ran one and it's showing packet losses. Could be a router problem somewhere.
I just used Command Prompt. I'm not convinced that random ping spikes of +1000ms are normal, and the problems I've been having with online gaming would prove that. There's only one other machine on this network and I still get the spikes when nobody is using it.
My System SpecsSystem Spec
11 Jul 2014   #6
carwiz

Windows 7 Pro-x64
 
 

Let me get this straight--Your network is connected directly to Google servers? Are you inside the Google building?

Run a ping plot and you'll get a better idea of where your traffic is going. It returns a ping from each server in the message route. You'll should note that network traffic can get bounced all over the world just to get next door. It just depends on network load. There's a lot of load on the network now. MS just released a ton of updates.
My System SpecsSystem Spec
11 Jul 2014   #7
Layback Bear

Windows 7 Pro. 64/SP-1
 
 

I didn't know that 1 or 2 ms difference was considered a spike.
My System SpecsSystem Spec
12 Jul 2014   #8
Alejandro85

Windows 7 Ultimate x64
 
 

Also consider that this kind of pinging with a significant amount of packets is not normal for an extended period. No idea if that's your case, but the server may be applying to your connection as a defensive measure against DDOS.
My System SpecsSystem Spec
13 Jul 2014   #9
Shadowjk

Windows 7 Professional x64 SP1 ; Windows Server 2012 R2 Standard
 
 

Quote   Quote: Originally Posted by keyboardface View Post
Recently I've started getting these big ping spikes whilst online gaming making them kinda pointless to play cos I'd get temporary 'Connection Interrupted' errors and such. My setup hasn't changed and I've never had this problem before so I'm hoping it's a software issue or some pretty well hidden malware.

Code:
Pinging google.com [173.194.34.169] with 32 bytes of data:
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=36ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=39ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=36ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=34ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=32ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=32ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=39ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=34ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=32ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=97ms TTL=58
Reply from 173.194.34.169: bytes=32 time=206ms TTL=58
Reply from 173.194.34.169: bytes=32 time=251ms TTL=58
Reply from 173.194.34.169: bytes=32 time=56ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=30ms TTL=58
Reply from 173.194.34.169: bytes=32 time=1192ms TTL=58
Reply from 173.194.34.169: bytes=32 time=112ms TTL=58
Reply from 173.194.34.169: bytes=32 time=1362ms TTL=58
Reply from 173.194.34.169: bytes=32 time=185ms TTL=58
Reply from 173.194.34.169: bytes=32 time=29ms TTL=58
Reply from 173.194.34.169: bytes=32 time=31ms TTL=58
Reply from 173.194.34.169: bytes=32 time=78ms TTL=58

Ping statistics for 173.194.34.169:
    Packets: Sent = 93, Received = 93, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 29ms, Maximum = 1362ms, Average = 65ms
I've restarted in Safe Mode with Networking and tried the same thing and the ping spikes still occur.
I've tested the ping to Google on another machine on the network and there were no spikes at all, ~30ms straight across the board.

Any ideas to help me work out what's causing them? Any help would be much appreciated.
With times like that I am suspecting that this is a wireless based connection? Wireless can suffer from various interferences that could affect latency. Test your latency when using a wired connection to see if the Wireless connectivity is the cause of this.

If the latency is still irregular on a wired connection and other devices do not experience any issues then it could be software based.

I would begin to look into drivers for your NIC. What is the make/model of your NIC?

There was a case awhile back that had a similar symptom and the issue was the result of a bad driver.

Ping (ICMP) is a connection-less protocol therefore the ping spikes wouldn't be a result of his server-client connection as there is none. Equally, if it was traffic engineering then it would affect anyone who pings Google and for me I do not receive lag spikes.

Code:
C:\Users\Josh>ping www.google.com -t

Pinging www.google.com [2.127.252.221] with 32 bytes of dat
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=19ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=19ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=22ms TTL=60
Reply from 2.127.252.221: bytes=32 time=16ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=21ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=22ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=16ms TTL=60
Reply from 2.127.252.221: bytes=32 time=20ms TTL=60
Reply from 2.127.252.221: bytes=32 time=21ms TTL=60
Reply from 2.127.252.221: bytes=32 time=35ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=20ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=16ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=16ms TTL=60
Reply from 2.127.252.221: bytes=32 time=16ms TTL=60
Reply from 2.127.252.221: bytes=32 time=19ms TTL=60
Reply from 2.127.252.221: bytes=32 time=16ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=17ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=21ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60
Reply from 2.127.252.221: bytes=32 time=16ms TTL=60
Reply from 2.127.252.221: bytes=32 time=18ms TTL=60

Ping statistics for 2.127.252.221:
    Packets: Sent = 42, Received = 42, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 16ms, Maximum = 70ms, Average = 19ms
Control-C
^C
C:\Users\Josh>
With a wireless connection like mine a Jitter (Variance in latency) of 1 to 5 ms is average.

Josh
My System SpecsSystem Spec
13 Jul 2014   #10
carwiz

Windows 7 Pro-x64
 
 

Oh there is indeed a connection; Otherwise, the server(s) wouldn't respond. While the ICMP special message is handled differently, it's still a message. The option to respond is server based. The Ping doesn't really mean much if you're looking for why a delay is occurring. You certainly can't say it's local software simply because there is a delay. All a ping tells you is end-to-end time. A routing trace (Tracert) is more meaningful in determining where the delay is occurring since you get a "ping" return from each server that handles the message to the end-point. If you see an elevated response from a server in the route, the problem is there, not local.

The route servers I see may not be the same as the servers you see. More often than not, they won't be the same until the message reaches the end point. So comparing two pings from different clients to the same end point doesn't tell you anything. The OP experienced delays and that's for sure but given the data above, blaming a driver is a shot in the dark.
My System SpecsSystem Spec
Reply

 Ping spikes




Thread Tools Search this Thread
Search this Thread:

Advanced Search




Similar help and support threads
Thread Forum
Ping Spikes At Random Times
Hey SevenForums, My internet at home keeps spiking at random intervals and it seems that when I use speedtest the meter would be running at full speed but then drop really slowly as if there was no "gas" being put into the meter. During these times my ping spikes to 300+ and I really can't do...
Network & Sharing
Evening Random ping spikes.
I`m gettin random ping spikes around 18:00-23:00. At night or morning everything is ok. I can easily watch videos or smth like that,but it`s unplayable at this time. I`m using wired connection to a wireless router(Linksys wrt54g) When i`m pinging google i`m gettin few timeouts and sometimes my...
Network & Sharing
Random Ping Spikes
Hey guys, I recently reformated my computer and unfortunately, I have been reminded of the wireless problem I had in the past that I fixed. The ping on my computer randomly spikes as you can see here: ping I have went on google and tried basically everything. People have suggested to disable...
Network & Sharing
Internett ping spikes/ DCs
So afew months back i started having small ping spikes here and there, nothing major so i just ignored it, after awhile it got worse. First i thought that it was the router or modem, but when no one else connected to the internett is having this problem. I have tried with two different...
Network & Sharing
Call of Duty 2 ping spikes
Hi there, I recently installed Windows 7 Professional 64bit. Since doing so, when I play on a CoD2 server, my ping will randomly spike up and I'll get CI. These are the same servers I played on when I ran XP and I had no issues with ping. On top of that, my spouse also plays on the same...
Gaming


Our Sites

Site Links

About Us

Find Us

Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd

All times are GMT -5. The time now is 13:30.

Twitter Facebook Google+



Windows 7 Forums

Seven Forums Android App Seven Forums IOS App