BobTheVeg
join:2004-09-05
Montreal, QC | reply to vithos
Re: [XP] Getting negative ping times
MSI K8N NEO4-F NFORCE4 SATA PCI-X
Athlon64 X2 3800+
2x 1024mo PC3200 Major
Asus AX800XL 256mo
Antec Sonata 450W
HD IDE : 15GB Maxtor, 2x160GB Maxtor
no CD/DVD/floppy/extra PCI card.
Exact same problem. |
|
vithos
join:2003-07-31
Fayetteville, AR
| reply to Todd222
let's see how much hardware we all have in common.
I suspect it's the nForce4 chipset.
ASUS A8N-SLI Premium
Athlon64 X2 4400+
2GB (4 * 512MB) Corsair XMS DDR 400MHz 2-2-2-5 SDRAM
ASUS 256MB nVidia 7800 GTX
PC Power & Cooling 510 SLI
2 * 400GB Seagate sATA disks
74GB 10,000rpm Raptor sATA disk
Plextor sATA PX-716SA
Creative X-Fi XtremeMusic
notes: I have tried Kingston ram, a 6800 video card, no sound card, a different power supply, even a gigabyte motherboard (same nForce4 chipset) and they all have the same problem. I also have a friend with almost exactly the same hardware as I (he has a 4800+) and he has the same problem. |
|
Todd222
join:2006-02-22
Riverside, CA
| reply to vithos
I have been getting the same issue with my ASUS AN8-SLI Premium MB and X2 4800+ (new gaming rig). At first I thought it was my D-Link DGL-4300 but ran ping from a different machine to the inside interface and one of our DNS server all night and didn't have any issues. I even tried the other NIC on the MB and it made no difference. It acts so bad from my gaming rig I can't even play online  . Any solutions would be greatly appreicated. |
|
vithos
join:2003-07-31
Fayetteville, AR
| reply to hse
I get this as well. It seems to be an issue with dual core processors on windows xp (seemed fixed in vista, but i didn't test extensively). If you set the process affinity of ping.exe to only one core or the other, you will get different results. It doesn't occur immediately after rebooting, and seems to slowly get worse. Game engines especially do not like this problem, so if you game you should set the process affinity of the game every time you launch it. I've been in contact with ASUS about this and they won't help me at all -- in fact they now hang up on me and tell me they're going to have someone call me back but it never happens (4 or 5 times they've done this). Sounds like they're trying to avoid extremely expensive recalls perhaps? If anyone has a REAL solution, I'm very interested. By the way, setting the process affinity doesn't completely fix it. Pinging localhost with the first core sometimes gives negative results, the other core sometimes always positive but still not correct, like 10ms instead of 1ms. |
|
