[Extinction18]

Well, about a week and a half ago I started to encounter issues with my WoW latency spiking to 500+, when it usually sit around 50-150, but my frame rate staying exactly the same. There was simply a 1-2 second pause between me doing something and it actually happening (text, abilities, etc).

So, I started doing a few registry fixes (Nagles, etc), then ran a few utilities to optimize my connection, but nothing stuck. So, I stumbled across a solution previously posted about this where it was the ISP having interleaving enabled and therefore creating the issue. (thread is at: http://forums.techguy.org/games/6888...tency-wow.html) Well, that thread had a guy tracert'ing the WoW server at 12.129.232.115, which is the login server. I did so on my desktop, where I play primarily, and here are the results:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Tracing route to 12.129.232.115 over a maximum of 30 hops

1 2 ms <1 ms <1 ms 10.0.0.1
2 1076 ms 656 ms 706 ms 10.225.128.1
3 571 ms 810 ms 758 ms gig6-2.vstlny11-rtr002.nyroc.rr.com [24.94.32.10
1]
4 800 ms 1069 ms 1094 ms ge-0-1-0.rochnyei-rtr001.nyroc.rr.com [24.92.224
.185]
5 670 ms 761 ms 805 ms ae10-0.syrcnycsr-rtr03.nyroc.rr.com [24.24.21.22
0]
6 740 ms 848 ms 949 ms xe-9-1-0.bar2.Cleveland1.Level3.net [64.156.66.4
1]
7 1026 ms 1034 ms 996 ms ae-0-11.bar1.Cleveland1.Level3.net [4.69.136.185
]
8 826 ms 816 ms 988 ms ae-6-6.ebr1.Washington1.Level3.net [4.69.136.190
]
9 944 ms 1082 ms 1084 ms ae-81-81.csw3.Washington1.Level3.net [4.69.134.1
38]
10 520 ms 540 ms 883 ms ae-3-89.edge1.Washington4.Level3.net [4.68.17.14
6]
11 1086 ms 938 ms 528 ms 4.68.62.30
12 1113 ms 1050 ms 994 ms cr1.wswdc.ip.att.net [12.122.88.174]
13 987 ms 942 ms 597 ms cr2.phlpa.ip.att.net [12.122.4.53]
14 803 ms 856 ms 927 ms cr2.cl2oh.ip.att.net [12.122.2.209]
15 856 ms 821 ms 738 ms cr1.cl2oh.ip.att.net [12.122.2.125]
16 838 ms 1045 ms * cr1.cgcil.ip.att.net [12.122.2.205]
17 570 ms 611 ms 605 ms cr2.dvmco.ip.att.net [12.122.31.85]
18 795 ms 582 ms 725 ms cr1.slkut.ip.att.net [12.122.30.25]
19 802 ms 794 ms 941 ms cr2.la2ca.ip.att.net [12.122.30.30]
20 1001 ms 677 ms 390 ms cr84.la2ca.ip.att.net [12.123.30.249]
21 560 ms 745 ms 818 ms gar5.la2ca.ip.att.net [12.122.129.25]
22 887 ms 948 ms 952 ms 12.122.255.74
23 720 ms 797 ms 707 ms 12.129.193.246
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Obviously, these values are very high. Well, I then tried it on my laptop, which is connected to the same network, and here are the results:

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Tracing route to 12.129.232.115 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 13 ms 2 ms 4 ms 10.225.128.1
3 9 ms 11 ms 27 ms gig6-2.vstlny11-rtr002.nyroc.rr.com [24.94.32.10
1]
4 6 ms 14 ms 6 ms ge-0-1-0.rochnyei-rtr001.nyroc.rr.com [24.92.224
.185]
5 4 ms 5 ms 5 ms ae10-0.syrcnycsr-rtr03.nyroc.rr.com [24.24.21.22
0]
6 6 ms 15 ms 17 ms xe-9-2-0.bar2.Cleveland1.Level3.net [64.156.67.1
3]
7 6 ms 7 ms 7 ms ae-0-11.bar1.Cleveland1.Level3.net [4.69.136.185
]
8 29 ms * 175 ms ae-6-6.ebr1.Washington1.Level3.net [4.69.136.190
]
9 26 ms 25 ms 15 ms ae-81-81.csw3.Washington1.Level3.net [4.69.134.1
38]
10 161 ms * 24 ms ae-3-89.edge1.Washington4.Level3.net [4.68.17.14
6]
11 11 ms 10 ms 11 ms 4.68.62.30
12 31 ms 32 ms 43 ms cr1.wswdc.ip.att.net [12.122.88.174]
13 77 ms 53 ms 48 ms cr2.phlpa.ip.att.net [12.122.4.53]
14 37 ms 78 ms 41 ms cr2.cl2oh.ip.att.net [12.122.2.209]
15 82 ms 52 ms 33 ms cr1.cl2oh.ip.att.net [12.122.2.125]
16 50 ms 38 ms 31 ms cr1.cgcil.ip.att.net [12.122.2.205]
17 32 ms 32 ms 31 ms cr2.dvmco.ip.att.net [12.122.31.85]
18 48 ms 45 ms 73 ms cr1.slkut.ip.att.net [12.122.30.25]
19 40 ms 77 ms 44 ms cr2.la2ca.ip.att.net [12.122.30.30]
20 59 ms 63 ms 73 ms cr84.la2ca.ip.att.net [12.123.30.249]
21 43 ms 57 ms 73 ms gar5.la2ca.ip.att.net [12.122.129.25]
22 47 ms 76 ms 33 ms 12.122.255.74
23 134 ms 148 ms 144 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Now, these values are exactly what I'm looking for, and what I'm used to.

So, computer issue or ISP issue?

Here's my suspicion: It's a computer issue via operating system. The laptop is running windows XP, the desktop is on 7. But don't take my opinion to be fact - I'm a hardware junkie, not a connection guy.

So, any thoughts?

[computerguy1990]

I would say its probably malware or a virus of some kind on your desktop I to run a desktop and a laptop and I have never had such an issue where the connection only slows for one computer and not the other. If I have a connection problem it affects both machines. Try checking for ad-ware and malware and viruses and the usual or an out of control process causing the lag spike. If that doesnt work call your ISP and ensure they are not throttling your connection

[Extinction18]

If it were an ISP issue, then both computers would be effected.

And the desktop has anti-spyware, adware, and virus software installed that are run every day.

[Extinction18]

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert 12.129.232.115

Tracing route to 12.129.232.115 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 10.0.0.1
2 165 ms 9 ms 13 ms 10.225.128.1
3 162 ms 139 ms 149 ms gig6-2.vstlny11-rtr002.nyroc.rr.com [24.94.32.10
1]
4 167 ms 115 ms 123 ms ge-0-1-0.rochnyei-rtr001.nyroc.rr.com [24.92.224
.185]
5 362 ms 229 ms 104 ms ae10-0.syrcnycsr-rtr03.nyroc.rr.com [24.24.21.22
0]
6 26 ms 21 ms 21 ms xe-9-0-0.bar2.Cleveland1.Level3.net [4.78.59.45]

7 293 ms 199 ms 209 ms ae-0-11.bar1.Cleveland1.Level3.net [4.69.136.185
]
8 385 ms 416 ms 682 ms ae-6-6.ebr1.Washington1.Level3.net [4.69.136.190
]
9 621 ms 395 ms 234 ms ae-81-81.csw3.Washington1.Level3.net [4.69.134.1
38]
10 113 ms 177 ms 228 ms ae-3-89.edge1.Washington4.Level3.net [4.68.17.14
6]
11 200 ms 449 ms 294 ms 4.68.62.30
12 502 ms 504 ms 381 ms cr1.wswdc.ip.att.net [12.122.88.174]
13 98 ms 109 ms 97 ms cr2.phlpa.ip.att.net [12.122.4.53]
14 98 ms 98 ms 105 ms cr2.cl2oh.ip.att.net [12.122.2.209]
15 98 ms 155 ms 123 ms cr1.cl2oh.ip.att.net [12.122.2.125]
16 100 ms 97 ms 101 ms cr1.cgcil.ip.att.net [12.122.2.205]
17 260 ms 257 ms 170 ms cr2.dvmco.ip.att.net [12.122.31.85]
18 235 ms 258 ms 144 ms cr1.slkut.ip.att.net [12.122.30.25]
19 397 ms 109 ms 115 ms cr2.la2ca.ip.att.net [12.122.30.30]
20 98 ms 100 ms 154 ms cr84.la2ca.ip.att.net [12.123.30.249]
21 140 ms 139 ms 97 ms gar5.la2ca.ip.att.net [12.122.129.25]
22 502 ms 575 ms 671 ms 12.122.255.74
23 183 ms 133 ms 97 ms 12.129.193.246

That as done just now, and it seems to have cut down a little but it's still not optimal. The only thing I did was a small registry tweak that I know of.

Any other suggestions to bring it into line with the laptop's numbers?

Note, ingame latency has not changed.

[Tanis]

Well, as you have said you can confirm with about 100% certainty that the problem is with your desktop somewhere.

My immediate thought would be a possible driver problem! I am still using XP myself having not even upgraded to Vista, but are all your desktop drivers Win 7 certified?