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

[Jubern]

It got fixed for me! Played all day yesterday without any problem. Did FATEs, a dungeon, traveled around: no problem at all.

[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.

[DreXxiN]

Is anyone with Time Warner Cable having issues? Just started having 90000 disconnect issues. Did a traceroute and didn't notice anything in particular that was odd but this has been an issue all day today for me and only today.

[Huynh]

Is anyone with Time Warner Cable having issues? Just started having 90000 disconnect issues. Did a traceroute and didn't notice anything in particular that was odd but this has been an issue all day today for me and only today.

I am, everyone freezes for me every like 5 seconds and they just start teleporting. I get 90000 numerous times a day compared to my friends without TWC

[PennBlackacre]

Not seeing tiscali but I'm constantly getting a time out at #11 out of 14.

[Yuengling]

I'm not an RCN customer, but Verizon FiOS.

The problem for me is the TINET hops.

8 41 ms 39 ms 37 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 41 ms 37 ms 40 ms ormuco-gw.ip4.tinet.net [216.221.156.110]

Reply from 216.221.156.110: bytes=64 time=39ms TTL=250
Reply from 216.221.156.110: bytes=64 time=37ms TTL=250
Request timed out.
Request timed out.
Reply from 216.221.156.110: bytes=64 time=40ms TTL=250
Reply from 216.221.156.110: bytes=64 time=34ms TTL=250
Reply from 216.221.156.110: bytes=64 time=33ms TTL=250
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=32ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Request timed out.
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=38ms TTL=250
Reply from 216.221.156.110: bytes=64 time=39ms TTL=250

[n1MB1s]

From Cox Communications in Las Vegas, NV. Both at home and at the office I have lag with TINET hops as well then again with Eidos Montreal.

3 1 ms 1 ms 1 ms wsip-24-120-105-81.lv.lv.cox.net [24.120.105.81]
4 8 ms 7 ms 7 ms 10.90.64.1
5 9 ms 9 ms 7 ms 24-234-16-105.ptp.lvcm.net [24.234.16.105]
6 9 ms 10 ms 13 ms 24-234-6-233.ptp.lvcm.net [24.234.6.233]
7 9 ms 9 ms 9 ms 24-234-6-250.ptp.lvcm.net [24.234.6.250]
8 24 ms 21 ms 27 ms langbprj02-ae2.rd.la.cox.net [68.1.1.19]
9 22 ms 15 ms 80 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
10 101 ms 107 ms 100 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
11 110 ms 101 ms 101 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
12 106 ms 102 ms 92 ms 192.34.76.2
13 96 ms 95 ms 95 ms 199.91.189.234
14 113 ms 107 ms 111 ms 199.91.189.74

[KMarsara]

im in washington dc and it takes me 13 hops to get to the server

[desertw0lf]

From Cox Communications in Las Vegas, NV. Both at home and at the office I have lag with TINET hops as well then again with Eidos Montreal.

Also in Las Vegas here with Cox Communications. Mine is similar:

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

1 1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms 10.89.0.1
3 11 ms 9 ms 8 ms 24-234-16-101.ptp.lvcm.net [24.234.16.101]
4 10 ms 8 ms 8 ms 24-234-6-245.ptp.lvcm.net [24.234.6.245]
5 8 ms 8 ms 8 ms 24-234-6-222.ptp.lvcm.net [24.234.6.222]
6 21 ms 20 ms 21 ms langbbrj01-ae2.rd.la.cox.net [68.1.1.14]
7 20 ms 14 ms 14 ms ae2-223.lax20.ip4.tinet.net [173.241.128.81]
8 102 ms 94 ms 101 ms xe-1-0-0.mtl10.ip4.tinet.net [89.149.185.41]
9 106 ms 99 ms 108 ms ormuco-gw.ip4.tinet.net [216.221.156.110]
10 106 ms 105 ms 109 ms 192.34.76.2
11 100 ms 101 ms 101 ms 199.91.189.234
12 94 ms 93 ms 102 ms 199.91.189.74

Trace complete.

[dspguy]

Is anyone with Time Warner Cable having issues? Just started having 90000 disconnect issues. Did a traceroute and didn't notice anything in particular that was odd but this has been an issue all day today for me and only today.

TWC here. 90000 sometimes every 5 minutes. I don't know if it is related to FFXIV though. Honestly, I do a tracert and if I ping the first IP past my gateway (so a TWC/RoadRunner IP) and it times out there - about 1.5% packet loss over 24 hours.

That seems like a TWC problem... I had TWC put a modem watch on my modem. Supposedly they see it "dropping off" every 5-10 minutes for 10 seconds. This is with or without FFXIV running.