Results 1 to 4 of 4
  1. #1
    Player
    MiNuN's Avatar
    Join Date
    Mar 2011
    Location
    Ul'Dah
    Posts
    1,546
    Character
    Azure Xanh
    World
    Hyperion
    Main Class
    Lancer Lv 70

    Hyperion, constant D/Cs

    Today I disconnected many times, in and out of instance, I also random my FC members disconnect many times and when I enter instances with shout parties, I watched many people disconnected many times.

    This started happening after maint, please fix it!
    (0)

  2. #2
    Player
    nabradia's Avatar
    Join Date
    Aug 2013
    Posts
    3
    Character
    Momo Saju
    World
    Hyperion
    Main Class
    Archer Lv 20
    Seconding this; was in Instance, d/c'd (all party members d/c'd, two during instance and one right after) and then was penalized and had to wait. Oops, SE.
    (0)

  3. #3
    Player
    Kurai's Avatar
    Join Date
    Mar 2011
    Location
    Limsa
    Posts
    109
    Character
    Kurai Kitsune
    World
    Raiden
    Main Class
    Dark Knight Lv 90
    I used to DC all the time (when i say all the time, i mean 7 or 8 DC's in an AK run) from 90k errors, but this fix worked for me.

    If you use a wireless connection give this a try.

    I was on a wireless connection using my desktop as I was far to lazy to run a cable through my house between the two devices, when I finally got around to wiring the home network a few weeks ago I noticed almost instantly that the 90k's stopped, since switching to a wired connection I have not had one single 90k error.

    I do still however get the odd client crash and the instant drop to desktop but v1 had that issue as well, and it might happen once ever couple of days which is tolerable in my opinion so not worth moaning about.


    I hope this helps your problem^^
    (0)

  4. #4
    Moderator Avurach's Avatar
    Join Date
    Sep 2013
    Posts
    288
    Greetings,

    We understand that you are experiencing difficulties with error code 90000. There is already an open discussion regarding this same concern here. Please browse through this thread for any possible solutions you may not have tried yet. In an effort to consolidate information on this error, we ask that any additional information you gather be added to that thread. As such, we will be closing this particular thread. We apologize for any inconvenience. Thank you!
    (0)