Lag spike/90000 error DC victims -- Help gather data on the problem

[SionDurant]

tracert neolobby02.ffxiv.com

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 8 ms 10 ms 8 ms 10.50.192.1
3 13 ms 10 ms 9 ms ten0-0-0-7.ORLD02-ser1.bhn.net [72.31.239.224]
4 12 ms 14 ms 20 ms ten0-0-0-7.orld01-ser1.bhn.net [72.31.194.58]
5 23 ms 21 ms 26 ms ten0-8-0-0.tamp20-CAR1.bhn.net [71.44.1.210]
6 21 ms 16 ms 21 ms 71.44.3.92
7 17 ms 15 ms 23 ms 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com [66
.109.6.96]
8 41 ms 43 ms 42 ms ae-0-0.a1.pit75.tbone.rr.com [66.109.1.70]
9 40 ms 42 ms 41 ms ae-0-0.cr0.dfw10.tbone.rr.com [66.109.6.39]
10 41 ms 39 ms 41 ms ae0.pr1.dfw10.tbone.rr.com [107.14.17.232]
11 62 ms 66 ms 62 ms te0-4-0-17.ccr21.dfw03.atlas.cogentco.com [154.5
4.11.49]
12 62 ms 61 ms 69 ms be2032.ccr22.dfw01.atlas.cogentco.com [154.54.6.
53]
13 62 ms 60 ms 62 ms be2010.ccr22.mci01.atlas.cogentco.com [154.54.46
.217]
14 60 ms 58 ms 60 ms te0-7-0-4.ccr22.ord01.atlas.cogentco.com [154.54
.30.102]
15 75 ms * 81 ms be2080.ccr22.yyz02.atlas.cogentco.com [154.54.42
.6]
16 70 ms 70 ms 69 ms be2092.ccr21.ymq02.atlas.cogentco.com [154.54.25
.26]
17 67 ms 68 ms 67 ms 38.122.42.34
18 * * * Request timed out.
19 66 ms 68 ms 65 ms 192.34.76.2
20 70 ms 66 ms 79 ms 199.91.189.234
21 65 ms 82 ms 65 ms 199.91.189.74

Trace complete.

[waka_swag]

tracert neolobby02.ffxiv.com

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 8 ms 10 ms 8 ms 10.50.192.1
3 13 ms 10 ms 9 ms ten0-0-0-7.ORLD02-ser1.bhn.net [72.31.239.224]
4 12 ms 14 ms 20 ms ten0-0-0-7.orld01-ser1.bhn.net [72.31.194.58]
5 23 ms 21 ms 26 ms ten0-8-0-0.tamp20-CAR1.bhn.net [71.44.1.210]
6 21 ms 16 ms 21 ms 71.44.3.92

Are you on Bright House Networks? I noticed your bhn hops and I'm on Bright House and having lag issues as well.

traceroute to neolobby02.ffxiv.com (199.91.189.74), 64 hops max, 52 byte packets
1 * * *
2 ten0-0-0-7.orld52-ser2.bhn.net (97.69.193.142) 12.663 ms 8.667 ms 11.015 ms
3 ten0-7-0-4.orld48-car2.bhn.net (71.44.60.128) 14.861 ms
ten0-1-0-2.orld48-car2.bhn.net (72.31.194.122) 19.236 ms
ten0-7-0-4.orld48-car2.bhn.net (71.44.60.128) 12.568 ms
4 ten0-3-0-12.orld71-car2.bhn.net (72.31.194.200) 15.826 ms
ten0-10-0-5.orld71-car2.bhn.net (71.44.61.44) 27.849 ms 25.906 ms
5 ten0-8-0-0.tamp20-car2.bhn.net (71.44.1.214) 31.207 ms
ten0-13-0-0.tamp20-car2.bhn.net (71.44.1.212) 21.795 ms
ten0-8-0-0.tamp20-car2.bhn.net (71.44.1.214) 29.612 ms
6 72.31.208.2 (72.31.208.2) 17.888 ms
hun0-7-0-0-tamp20-cbr1.bhn.net (72.31.117.164) 23.889 ms
hun0-6-0-0-tamp20-cbr1.bhn.net (72.31.117.160) 23.223 ms
7 10.bu-ether15.tamsflde20w-bcr00.tbone.rr.com (66.109.6.96) 19.647 ms 24.162 ms 22.549 ms
8 ae-0-0.a1.pit75.tbone.rr.com (66.109.1.70) 47.377 ms 49.622 ms 45.104 ms
9 ae-0-0.cr0.dfw10.tbone.rr.com (66.109.6.39) 47.413 ms 51.351 ms 46.413 ms
10 * ae1.pr1.dfw10.tbone.rr.com (107.14.17.234) 48.292 ms
ae0.pr1.dfw10.tbone.rr.com (107.14.17.232) 39.129 ms
11 te0-4-0-17.ccr21.dfw03.atlas.cogentco.com (154.54.11.49) 102.918 ms 109.304 ms 106.632 ms
12 be2031.ccr21.dfw01.atlas.cogentco.com (154.54.7.45) 100.700 ms *
be2032.ccr22.dfw01.atlas.cogentco.com (154.54.6.53) 109.501 ms
13 be2064.mpd21.mci01.atlas.cogentco.com (154.54.5.217) 104.667 ms
be2010.ccr22.mci01.atlas.cogentco.com (154.54.46.217) 96.724 ms
be2012.ccr21.mci01.atlas.cogentco.com (154.54.2.113) 107.456 ms
14 * te0-7-0-1.mpd22.ord01.atlas.cogentco.com (154.54.25.78) 104.025 ms
te0-4-0-3.mpd21.ord01.atlas.cogentco.com (154.54.30.169) 107.359 ms
15 be2079.ccr21.yyz02.atlas.cogentco.com (154.54.27.182) 317.816 ms
be2080.ccr22.yyz02.atlas.cogentco.com (154.54.42.6) 113.619 ms
be2081.ccr21.yyz02.atlas.cogentco.com (154.54.42.10) 122.979 ms
16 be2090.ccr21.ymq02.atlas.cogentco.com (154.54.30.206) 113.077 ms
be2092.ccr21.ymq02.atlas.cogentco.com (154.54.25.26) 106.778 ms 106.663 ms
17 38.122.42.34 (38.122.42.34) 68.650 ms 70.308 ms 70.026 ms
18 * * *
19 192.34.76.2 (192.34.76.2) 68.423 ms 69.165 ms 69.902 ms
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *

I'm assuming these in red are timeouts and if that has anything to do with the problem I'm having.

[KisaiTenshi]

I'm assuming these in red are timeouts and if that has anything to do with the problem I'm having.

Not necessarily. It just means that a router is refusing response to ICMP requests, therefor it's not passing any. Some data centers block ICMP on purpose.

Here's mine:

Tracing route to neolobby02.ffxiv.com [199.91.189.74]
over a maximum of 30 hops:

5 14 ms 15 ms 12 ms rc4wt-pos15-0-0.wa.shawcable.net [66.163.76.210]

6 18 ms 23 ms 15 ms rc2wt-ge6-2-1.wa.shawcable.net [66.163.68.21]
7 12 ms 15 ms 13 ms ix-1-2-1-0.tcore1.00S-Seattle.as6453.net [64.86.123.25]
8 203 ms 202 ms 204 ms if-1-0-0-3.core1.00S-Seattle.as6453.net [64.86.123.6]
9 91 ms 90 ms 81 ms if-8-2-3-0.tcore2.CT8-Chicago.as6453.net [64.86.124.30]
10 95 ms 91 ms 81 ms if-3-2.tcore1.W6C-Montreal.as6453.net [66.198.96.45]
11 97 ms 84 ms 84 ms 66.198.96.50 (TATA Montreal)
12 147 ms 84 ms 82 ms 192.34.76.2 (Ormuco Montreal)
13 83 ms 83 ms 84 ms 199.91.189.234 (Eidos Montreal (Ormuco))
14 82 ms 82 ms 82 ms 199.91.189.74 (Eidos Montreal (Ormuco))

Trace complete.

Kinda odd that it goes Vancouver-Seattle-Chicago-Montreal, my ISP is Shaw Communications.

I'm never getting the 90000 error, but the game is crashing after usually about 30 seconds of extreme lag (happens most often near zone edges)
I find if I let go of the mouse and keyboard, it will usually not crash, but it will remain lagged. If I minimize, ctrl-alt-del, or basically do anything to take focus away from it while it's lagging, it will result in a black screen, but the audio will resume working. If you punch esc, you can hear the menu come up, or at least I think it's the menu.

The game will work for anywhere between a few minutes and maybe 2 hours. Note that every crash sends a problem report to Microsoft. There's 27 reports of which 11 of them were on the 4th. The errors themselves are showing up as 0xc0000005 (Access Violation.) Note that I have DEP enabled on the CPU, and this may explain why the game client crashes and not simply throws itself back to the desktop.


Don't get me wrong, the game is playable enough, just the crashing/dc is unpredictable, that it would likely result in people not subscribing, who wants to pay for beta-quality... again.