Second to last Update, I have being plagued by error 90000

[Dorwar]

I updated my nvidia Geforce GTX 670 drivers hoping that it would solve the problem, but no. It's still there. My computer is all updated as well. Double

[Raist]

I updated my nvidia Geforce GTX 670 drivers hoping that it would solve the problem, but no. It's still there. My computer is all updated as well. Double

Think 90k is basically a generic "connection lost" type of message. Graphics card drivers shouldn't have any affect on it unless it's something tripping a GPU reset and loss of DirectX focus (in which case you should also get a message to that effect, as it is a driver crashing issue and not connectivity). Driver updates in general shouldn't address connectivity problems (unless it's something going on with your network card or security software/devices).

Barring something security/virus/malware related, these are often tripped by issues in route or at the endpoint (ie: their server). More often than not, it simply boils down to a capacity problem. Either a portion of your route to the SE server or the server itself is highly congested or flat out overloaded, so your connection either expires from a lack of timely response (lag too high or device went offline), or you get denied access (server overloaded, logins get clamped down, etc.).

Note that SE once again acknowledged server-side stability and connectivity issues back on March 5th that they have been investigating and trying to remedy (Lodestone and Status forums have several announcements from the 5th through the 12th). They have scheduled another maintenance this week in an attempt to address those issues they have been able to identify.

Just in case, you may want to double check the stability of your route to the SE server you play on. Not your local connectivity to the web, but the specific route to the server you actually connect to for the game. You can get that by watching connections through resmon or netstat while you are logging in or fully logged into the game (resmon can be run from the start/search line, netstat can be run periodically from a command prompt window). The Canada based servers start with 199, and the Japan ones start with 124.

If you run a tracert from a CMD prompt window (ie. tracert 199.91.189.25) and see hops with either time outs (*) or highly erratic response times (one or two stars but less than 3, or really low then really high (like 30ms than 200ms) and demonstrating a variance of 2x or higher of another value for that hop), then there is likely a problem with congestion and possibly even packet loss along your routing that the ISP's need to investigate and address. Take some more traces to some more common sites lke google/youtube or yahoo (tracert www.google.com) to see if you get similar results. If so, contact your ISP so you can forward the results to them (right-click a spot in the command window, select all, and press the <enter> key to copy all text into notepad so you can then paste it into a text file or email). This gives them a lot of information for conducting a further investigation, as well as backing up your claim of an issue that should hopefully convince them to get involved.