Crap Gaming Performance: VM + BF2 [Archive]

View Full Version : Crap Gaming Performance: VM + BF2

JoeBloggs

17-01-2009, 19:29

Really frustrated now with Virgin Media.

Last few weeks, I have been getting poor gaming performance on Battlefield 2. I have tried everything possible on my end. The problem is definately them.

Because earlier today BF2 was running sweet as a nut, on 20 man servers and 64 servers (full to the brim). Then tonight I log on and the spikes are there again... Even on the same servers where is was fine earlier.

So its runs smooth one day and the next day im back spiking again.

It's not a major spike. Like every 2-3 secs it will glitch slightly (especially when you run in bf2, you can see the gun is not swaying smoothly, plus everything around you freezes for a split second).

Really doing my head in now. I'm thinking about ending the contract.

Check out these videos I made...

As you can see the first video shows the spike (notice the gun twitching/hiccuping)

http://uk.youtube.com/watch?v=xhGSONbI6BE

And the second video shows everything is running fine...

http://uk.youtube.com/watch?v=RqmgnCwMv5g

Its an absolute joke.:mad:

Ignitionnet

17-01-2009, 19:33

When you are seeing the problems could you please do the following:

ping -n 100 bbc.co.uk

tracert bbc.co.uk

With the connection not being used for anything else.

JoeBloggs

17-01-2009, 19:38

Here's my signal levels btw:

Downstream Lock : Locked
Downstream Channel Id : 1
Downstream Frequency : 402750000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 5360.537 Ksym/sec
Downstream Interleave Depth : taps32Increment4
Downstream Receive Power Level : 5.6 dBmV
Downstream SNR : 41.2 dB

When you are seeing the problems could you please do the following:

ping -n 100 bbc.co.uk

tracert bbc.co.uk

With the connection not being used for anything else.

Will log on bf2 now and see if its still there... cheers

Ignitionnet

17-01-2009, 19:48

Signals on downstream are fine by the way, very good indeed.

Would be interesting to know if your download / upload speeds are affecting when it's glitching too.

JoeBloggs

17-01-2009, 20:11

Signals on downstream are fine by the way, very good indeed.

Would be interesting to know if your download / upload speeds are affecting when it's glitching too.

thanks for the help

yes, i have noticed the speed dropping on many occasions, like down to 300 kbps (which should be 2000kbps)

funny stuff this, just been playing bf2 now and its running smooth now - NO glitches whatsoever (on a full 64 server).

yeah recently exchanged the modem, but that didnt make a difference, was still getting smooth and glitched gameplay on the old ntl:200 modem (but still get the smooth/glitch gameplay on the new modem too!)

thanks for the help

deffo network problem here, not my end...

---------- Post added at 20:02 ---------- Previous post was at 19:54 ----------

Glitch back again (same server)

---------- Post added at 20:05 ---------- Previous post was at 20:02 ----------

Right then, I just left bf2 (when glitch appeared) and did the ping you mentioned...

D:\Documents and Settings\Administrator>ping -n 100 bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=208ms TTL=116
Reply from 212.58.224.138: bytes=32 time=193ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=193ms TTL=116
Reply from 212.58.224.138: bytes=32 time=195ms TTL=116
Reply from 212.58.224.138: bytes=32 time=200ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=194ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=227ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=204ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=190ms TTL=116
Reply from 212.58.224.138: bytes=32 time=219ms TTL=116
Reply from 212.58.224.138: bytes=32 time=19ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=193ms TTL=116
Reply from 212.58.224.138: bytes=32 time=214ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=194ms TTL=116
Reply from 212.58.224.138: bytes=32 time=194ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=209ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=222ms TTL=116
Reply from 212.58.224.138: bytes=32 time=194ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-136ms TTL=116
Reply from 212.58.224.138: bytes=32 time=42ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=213ms TTL=116
Reply from 212.58.224.138: bytes=32 time=205ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=193ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=222ms TTL=116
Reply from 212.58.224.138: bytes=32 time=201ms TTL=116
Reply from 212.58.224.138: bytes=32 time=195ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=198ms TTL=116
Reply from 212.58.224.138: bytes=32 time=196ms TTL=116
Reply from 212.58.224.138: bytes=32 time=196ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=202ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=194ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=211ms TTL=116
Reply from 212.58.224.138: bytes=32 time=190ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=202ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=195ms TTL=116
Reply from 212.58.224.138: bytes=32 time=202ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=27ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=194ms TTL=116
Reply from 212.58.224.138: bytes=32 time=194ms TTL=116
Reply from 212.58.224.138: bytes=32 time=22ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=27ms TTL=116
Reply from 212.58.224.138: bytes=32 time=194ms TTL=116
Reply from 212.58.224.138: bytes=32 time=200ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=201ms TTL=116
Reply from 212.58.224.138: bytes=32 time=222ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=201ms TTL=116
Reply from 212.58.224.138: bytes=32 time=195ms TTL=116
Reply from 212.58.224.138: bytes=32 time=193ms TTL=116
Reply from 212.58.224.138: bytes=32 time=203ms TTL=116
Reply from 212.58.224.138: bytes=32 time=203ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=213ms TTL=116
Reply from 212.58.224.138: bytes=32 time=194ms TTL=116
Reply from 212.58.224.138: bytes=32 time=202ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=206ms TTL=116
Reply from 212.58.224.138: bytes=32 time=192ms TTL=116
Reply from 212.58.224.138: bytes=32 time=191ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=195ms TTL=116
Reply from 212.58.224.138: bytes=32 time=194ms TTL=116
Reply from 212.58.224.138: bytes=32 time=195ms TTL=116
Reply from 212.58.224.138: bytes=32 time=197ms TTL=116
Reply from 212.58.224.138: bytes=32 time=193ms TTL=116
Reply from 212.58.224.138: bytes=32 time=193ms TTL=116
Reply from 212.58.224.138: bytes=32 time=193ms TTL=116

Ping statistics for 212.58.224.138:
Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = -136ms, Average = 174ms

---------- Post added at 20:08 ---------- Previous post was at 20:05 ----------

https://www.cableforum.co.uk/images/local/2009/01/16.png (http://www.speedtest.net)

---------- Post added at 20:11 ---------- Previous post was at 20:08 ----------

Seems to me the service is going up and down like a damn yo-yo.

I ain't paying for this crap anymore, f em now im sick of it

caph

17-01-2009, 20:31

Wow, those ping times are truly awful. I just got:-

Reply from 212.58.224.138: bytes=32 time=14ms TTL=118
Reply from 212.58.224.138: bytes=32 time=16ms TTL=118
Reply from 212.58.224.138: bytes=32 time=35ms TTL=118
Reply from 212.58.224.138: bytes=32 time=28ms TTL=118

which is more or less what it should be from the UK.

JoeBloggs

17-01-2009, 20:47

yeah I know mate, its unfair.

now...

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=217ms TTL=116
Reply from 212.58.224.138: bytes=32 time=19ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=216ms TTL=116

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 217ms, Average = 117ms

D:\Documents and Settings\Administrator>

Ignitionnet

17-01-2009, 21:38

General Maximus

17-01-2009, 22:22

tbh i havent played bf2 in a while now but i play bf2142 and left 4 dead all the time and i never have any lag issues unless it is a dodgy server and everyone suffers from the same problem. In the old days (last year) i used to suffer from jerkiness but that was because my graphics card couldnt handle all the explosions and people running around on screen. As soon as I replaced it with my new one I was everything was fine and ran as smooth as a babies bum.

cook1984

17-01-2009, 23:47

Do you have wifi? Check your network is secure, change the key just in case.

Have you run Spybot and/or a free BitDefender online scan recently? Make sure your PC is not part of a botnet.

To be honest though it's probably just that your area is oversubscribed.

AmAtoL

18-01-2009, 09:54

I used to have a similar thing as well, on BF2 and 2142 from time to time, in the end it got so bad that I left and got a separate BT line in for gaming. While it's not gaming nirvana as I still experience some warping and poor hit registration it's generally ok.
I may have to conduct some back to back tests with my cable connection now to see if things have improved any (yes..Cable and BT in same room :p)

Noggo

18-01-2009, 10:15

JoeBloggs,

As Broadbandings suggested get in contact with Virgin Media's newsgroup support:

Just post a message on VM newsgroup support, with details of your problem include tests like: (please make sure that no router is in place when you do the tests, otherwise tech support will just ask for them to be done again with direct PC to Modem connection)

Cable modem, down/up stream power levels
trace route to bbc.co.uk
ping bbc.co.uk -n 20

Outlook express setup can be found here (all the below links are at the bottom of the first link):
http://www.virginmedia.com/customers...ress-exntl.php

Subscribing to newsgroups and the newsgroup you to subscribe to is:
virginmedia.support.broadband.cable
http://www.virginmedia.com/customers...ss-exntl-2.php

Reading posts:
http://www.virginmedia.com/customers...ss.php#reading

How to post messages:
http://www.virginmedia.com/customers...ss.php#posting

Note: If you do post on Virgin Media's newsgroup support, please do not post any modem MAC or serial # info

JoeBloggs

18-01-2009, 13:21

I think you have an upstream SNR problem.

Pings should be closer to:

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=12ms TTL=119
Reply from 212.58.224.138: bytes=32 time=13ms TTL=119
Reply from 212.58.224.138: bytes=32 time=13ms TTL=119
Reply from 212.58.224.138: bytes=32 time=12ms TTL=119

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms

Have you posted on the VM newsgroups to see if those guys can assist and suggest what might be wrong? They can see upstream SNR with their tools, as well as test the performance of the network between the VM equipment and your modem.

Thanks - Will try the newsgroups.

tbh i havent played bf2 in a while now but i play bf2142 and left 4 dead all the time and i never have any lag issues unless it is a dodgy server and everyone suffers from the same problem. In the old days (last year) i used to suffer from jerkiness but that was because my graphics card couldnt handle all the explosions and people running around on screen. As soon as I replaced it with my new one I was everything was fine and ran as smooth as a babies bum.Hi mate, my pc is pretty good, don't think its a hardware problem...

4200 AM2 (EDIT, sorry - I have AMD 64 X2 dual core 3800+)
K9N Diamond
Kingston 1GB
7900GS

I thought my 7900 vc was overheating, as the spikes begin 2-3 mins after I joined the server.... But after I minimise bf2, I can see the high pings and network slowdown... So it doesn't seem to be my hardware.

cheers

Do you have wifi? Check your network is secure, change the key just in case.

Have you run Spybot and/or a free BitDefender online scan recently? Make sure your PC is not part of a botnet.

To be honest though it's probably just that your area is oversubscribed.I do use WiFi(WPA 2, TKIP) but I also use mac filter to stop anyone getting in and I disbable broadcasting. But it has been off for a while now, so that is definately not the problem.

Like i said, did a clean install many a times, so no again definately not virus/spyware!

Yeah oversubscribed is probably the cause. I'm get into this, start monitoring things and keep data, will post my findings. Cheers

I used to have a similar thing as well, on BF2 and 2142 from time to time, in the end it got so bad that I left and got a separate BT line in for gaming. While it's not gaming nirvana as I still experience some warping and poor hit registration it's generally ok.
I may have to conduct some back to back tests with my cable connection now to see if things have improved any (yes..Cable and BT in same room :p)Interesting, I might have to switch myself, if I cant have decent gaming performance, then personally I don't want to pay for it. Might have to start looking for an ADSL supplier that offers best gaming pings/connection.

Cheers

And finally, thanks Noggo - That's a great help, will get that done today now, thank you for the help.

Heres my ping results today...

D:\Documents and Settings\Administrator>ping -n 20 bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=-160ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-160ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-159ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-162ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-162ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-156ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-162ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-149ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-162ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-159ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-156ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-160ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-162ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-161ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-161ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-158ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-162ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-157ms TTL=116
Reply from 212.58.224.138: bytes=32 time=19ms TTL=116
Reply from 212.58.224.138: bytes=32 time=-143ms TTL=116

Ping statistics for 212.58.224.138:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 19ms, Maximum = -143ms, Average = 214748215ms

Turkey Machine

18-01-2009, 13:21

<snip>
Reply from 212.58.224.138: bytes=32 time=-136ms TTL=116
</snip>
Is that even legal? I didn't know you could have negative pings!

EDIT: From your most current post, you appear to have a rather large problem with negative pings. :D

JoeBloggs

18-01-2009, 13:38

Cable Modem Upstream
Upstream Lock : Locked
Upstream Channel ID : 3
Upstream Frequency : 34000000 Hz
Upstream Modulation : QPSK
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 39.0 dBmV
Upstream Mini-Slot Size : 2

---------- Post added at 13:29 ---------- Previous post was at 13:27 ----------

Is that even legal? I didn't know you could have negative pings!

EDIT: From your most current post, you appear to have a rather large problem with negative pings. :D

Oh yeah! Just noticed the minus sign

What the hell ??? :shocked:

---------- Post added at 13:32 ---------- Previous post was at 13:29 ----------

I've just read somewhere that negative pings are caused by AMD Dual-Core Processors??

About the negative pings, I'm not a genius computer user, but I noticed the negative pings and connectivity issues as well. I therefore referred my problem to the great technical support in the wire- aka, the Internet.

Seems that AMD has some issues with their Dual-core processors. I found this, and variations of it on several sites: [my thanks to "Stanley" who postd this]

"I am guessing all or most of those experiencing negative ping times are using the new dual core AMD cpu line. There appears to be a bug in the CPU, which AMD will not directly admit to or identify publicly. Being a big fan of AMD for years I find this very unfortunate since this has been affecting the AMD based servers I manage at work and the home machines of myself and many other people I know.

After narrowing it down to the processor itself I started to put pressure on AMD for answers and was finally told to update the processor driver for all systems experiencing the problem. I did this at home last weekend and at work to almost a dozen servers and it has fixed the problem on ALL workstations and servers.

From my discussions with AMD I have pieced together the following likely issue with the dual core processors. It seems there is a timing issue between the two cores that slowly causes the timing to drift further and further apart between the two cores. This is why rebooting the machine temporarily fixes the syptoms; atleast for a couple of hours. The longer the system is up the worse the problem appears to get until simple tasks such as web browsing and copying files becomes untolerable.

Below is a link to AMD to get the latest processor driver which appears to correct the issue with the dual core processor.

www . amd . com/us-en/Processors/TechnicalResources/0,,30_182_871_13118,00.html
(sorry for the broken URL, the borad will not let me post a URL with less than 15 posts here under my belt)

For those that may feel this problem still resides on the network side I can only say in the past two months I have tried 5 different brand NICs (netgear, HP, linksys, d-link, and an older Compaq server NIC), 4 different switchs (Cisco 6513, Cisco 2950, Netgear, and D-Link), and tried a straight crossover cable between two computers and non had any affect on the problem. I have also experienced the problem on 3 different system boards (Compaq DL385, MSI K8N Neo4, and an Asus board. I have flashed the BIOS repeatedly on all these boards and the Neo4 ensured I was running the latest nForce4 drives. None of this troubleshooting has any affect on the problem.

In the past two or so months I have read about a lot of people having this problem but have not seen a fix for this posted anywhere so I am hoping this email can help at least one person save the months of meaningless troubleshooting I have to go through.

If you find this to be help full at solving your problem please take a minute to spread the word.

Stanley
Network Administrator"---------- Post added at 13:38 ---------- Previous post was at 13:32 ----------

bbc pings 5 mins later...

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=21ms TTL=116
Reply from 212.58.224.138: bytes=32 time=27ms TTL=116
Reply from 212.58.224.138: bytes=32 time=30ms TTL=116
Reply from 212.58.224.138: bytes=32 time=22ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=46ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=34ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=26ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116

Ping statistics for 212.58.224.138:
Packets: Sent = 20, Received = 20, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 46ms, Average = 22ms

Going to try that AMD cpu driver now...

chickendippers

18-01-2009, 14:03

Support will ask you to remove the router from the equation, so connect direct to the modem via ethernet.

JoeBloggs

18-01-2009, 14:31

Will do chicken :)

Right then, I've installed the AMD Processor Driver.

And just been playing bf2 for 30 mins with no problems, really smooth gameplay, no gun twitching!

Will try again later on tonight...

bbc pings after driver install...

D:\Documents and Settings\Administrator>ping -n 50 bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:

Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=22ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=37ms TTL=116
Reply from 212.58.224.138: bytes=32 time=44ms TTL=116
Reply from 212.58.224.138: bytes=32 time=19ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=26ms TTL=116
Reply from 212.58.224.138: bytes=32 time=19ms TTL=116
Reply from 212.58.224.138: bytes=32 time=29ms TTL=116
Reply from 212.58.224.138: bytes=32 time=21ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=21ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=19ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=32ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=20ms TTL=116
Reply from 212.58.224.138: bytes=32 time=32ms TTL=116
Reply from 212.58.224.138: bytes=32 time=19ms TTL=116
Reply from 212.58.224.138: bytes=32 time=17ms TTL=116
Reply from 212.58.224.138: bytes=32 time=27ms TTL=116
Reply from 212.58.224.138: bytes=32 time=43ms TTL=116
Reply from 212.58.224.138: bytes=32 time=21ms TTL=116
Reply from 212.58.224.138: bytes=32 time=19ms TTL=116
Reply from 212.58.224.138: bytes=32 time=18ms TTL=116
Reply from 212.58.224.138: bytes=32 time=22ms TTL=116

Ping statistics for 212.58.224.138:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 44ms, Average = 20ms

---------- Post added at 14:31 ---------- Previous post was at 14:29 ----------

I am hoping it was the CPU problem. All will be revealed, time will tell.

JoeBloggs

19-01-2009, 11:02

Well folks, played Battlefield 2 last night and it was sweet as a nut. Not once did it stutter/spike.

Might be a coincidence, but after installing the CPU driver it seems to run better, but I will keep a close on it.

Noggo

19-01-2009, 12:22

Always helps having the correct drivers for hardware.

Eye :)
but I will keep a close on it.

JoeBloggs

19-01-2009, 13:06

Always helps having the correct drivers for hardware.

Eye :)

Thing is though, I have played fine without the driver for at least 6 months, just recently started to get these spikes.

Hopefully it is solved

Will report back whichever way it goes...

Cheers

AntiSilence

19-01-2009, 13:12

I've got an AMD dual core CPU running XP 64 and BF2 and not had any lag spike issues at all with my VM 10mb connection. CPU driver may be up to date though.

General Maximus

19-01-2009, 14:09

:confused: i didn't even know you could get cpu drivers. I always keep my drivers for my graphica card up to date (gpu) and my motherboard to a certain extent but never my processor.

JoeBloggs

19-01-2009, 17:06

lol

well today I have been capped to 256kB/s download

cheers vm
much appreciated

and I haven't gone over the limits!!!

---------- Post added at 17:06 ---------- Previous post was at 17:02 ----------

:confused: i didn't even know you could get cpu drivers. I always keep my drivers for my graphica card up to date (gpu) and my motherboard to a certain extent but never my processor.

I knew they existed, but I always knew they weren't necessary, because windoze has its own cpu driver and I did fine with that for ages (I dont like installing "extra" software if I can help it).

But has it fixed my bf2 problems? Who Knows.
I'll give you the answer to this soon when I format again back to win 32 bit.

Stabhappy

19-01-2009, 17:08

It's not so much a CPU driver than it is a CPU hotfix.

JoeBloggs

19-01-2009, 18:36

It's not so much a CPU driver than it is a CPU hotfix.

yeah i suppose it is

about my speed dropping earlier to 256kB/s, rang virgin and they said I have not been STM'd - Just there is maintenance ongoing in my area.

apparently...

cook1984

19-01-2009, 18:42

Just there is maintenance ongoing in my area.

That's code for "we suck but won't do anything about it, now please go away"

keyholder

19-01-2009, 18:45

yeah i suppose it is

about my speed dropping earlier to 256kB/s, rang virgin and they said I have not been STM'd - Just there is maintenance ongoing in my area.

apparently...

Ha same excuse i get, HA ha.

If your close the the exchange and can get o2/ be etc then do yaself a favour ditch the cable and go elsewhere :) save yourself the hasle and stress :D

Noggo

19-01-2009, 22:27

Ha same excuse i get, HA ha.

If your close the the exchange and can get o2/ be etc then do yaself a favour ditch the cable and go elsewhere :) save yourself the hasle and stress :D

If you're thinking of going down that route go for Bethere not O2, as Be* has fastpath as an option and O2 doesn't.