vista lag spikes (gamming is a no no :( )

Soldato
Joined
30 Nov 2005
Posts
13,916
i am running vista32 and pretty much got settled with it now, but i have had to start using a wifi connection now and i am getting lag spikes every 60 seconds or so now. I am on my 2nd wifi adapter now and the problem is the same. its wrecking my gamming enjoyment to be honest.


Is there a cure?

I have tried the antilag program- didn't work
I have tried to disable the wlan autoconfig in services and use the adpater software, but disbaling that stops all networks.


I am at my wits end.. Have I really got to install XP again??????



Please help network Gurus :D

:mad::mad:


Microsoft Windows [Version 6.0.6000]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\jamie>ping 10.0.0.2 /t

Pinging 10.0.0.2 with 32 bytes of data:

Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=2ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=783ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=1ms TTL=64
Reply from 10.0.0.2: bytes=32 time=726ms TTL=64
 
Last edited:
dont use wireless, give it ago then, i had this same problem, although not with vista, it was to do with the router and or USB, but when using a netgear 1 i didnt have it...

however i posted on 2 forums, no one knew anything.. because the problem i had was not logical.. try without wireless and see if that makes difference.

my findings were..

router seemed fine..
1 sec lag every 60 seconds (roughly), experienced this on 3 diff pc's with 7 different wireless usb's
for unknown reasons, the netgear WPN111 suffered no lag spikes..???//but made pc crash every day.. and so im using the CAT6 network cable now...

...
ps i know what u mean, gaming was real annoying.... good luck. i will check on this thread later
 
Sorry please can you specify the anti lag program?

I found this in a post on cable forums

There is a service called Base Filtering Engine, that when switched on slows look ups right down. It's not recommended to have this service switched off for security reasons, so after some more Googling led me to download Update for Windows Vista KB929547 (resolves an issue where after installing the Windows Filtering Platform (WFP) driver, applications and services appear to stop responding for approximately 15 seconds).

This has fixed the slow DNS problem, the only thing I'm angry about is that Vista told me I had all the relevant updates. Obviously not.....

Sorry if this is not relevant!
 
The answer is do not use wireless for gaming... use only wired. I had the same problem a year or two ago with XP and switched to wired and had no problems since.

Is there no chance at all that you can route cable through to your computer, or switch the router through to your room to use a wire and then make the other computer in the house wireless?
 
Switch to Homeplug technology for gaming. Thats what I did because I had the same issue with Wireless under Vista64
 
All those people who are suggesting that you can't use wireless for gaming really need to do some research on it first. I use wireless for my pc, 360 and PS3 and don't suffer from lag as my ping on the pc is 18ms which is perfectly fine.

I used to suffer these lag spikes until I found out what the problem was and it took about 1 minute to resolve. My situation is slightly different due to the fact I am using XP. All I had to do was disable the Wireless Zero Application in services and that stopped the wireless dongle from looking for new networks or whatever it does. So for me no more lag spikes and I am basically getting the same performance as wired.

Hope that helps
 
I had this problem under xp and fixed by disabling the zeroConfig application BUT vista you cant disable it without losing conectivity all together.
 
All those people who are suggesting that you can't use wireless for gaming really need to do some research on it first. I use wireless for my pc, 360 and PS3 and don't suffer from lag as my ping on the pc is 18ms which is perfectly fine.

I used to suffer these lag spikes until I found out what the problem was and it took about 1 minute to resolve. My situation is slightly different due to the fact I am using XP. All I had to do was disable the Wireless Zero Application in services and that stopped the wireless dongle from looking for new networks or whatever it does. So for me no more lag spikes and I am basically getting the same performance as wired.

Hope that helps

As said its a different situation under Vista......especially Vista 64 where in my experience Wireless drivers are still poor and older wireless hardware poorly supported.
 
i use wireless and had the lag/spike problems. I just did a bit of research and found a program that got rid of the spikes for my Vista32. If you need a link i'll send it via PM when i get home.
 
WLAN optimizer does the job, before that I used a batch file I had created which auto-enabled WLAN autoconfig on startup, then once I was connected I could press a key to disable it again.

Seems pretty shoddy that they still haven't fixed this.
 
used to use wireless when I was on XP, while there were the odd days where I'd get unexpected lag issues (high ping every minute or so) it was never a big deal. I then changed to Vista and started getting awful connection reliability, so I took the plunge and bought a 20 metre cable for my router, everything works fine now. Moral of the story, while wireless is ok for gaming, this cannot be garuanteed, particularly with windows vista.
 
Back
Top Bottom