FFXIV Crash

"An unexpected error has occurred. Exiting FINAL FANTASY XIV: A Realm Reborn. (2) (17)"

I just completed the quest to get into the Ifrit Cavern and skipped the cut scene since I had watched it before and it crashed and I have yet to get back into the game to continue.

My characters name is Melyia Epona from the Coeurl server.

After the server maintenance and a good nights rest I have come to try and log back into the game. I am still getting the same area and it appears it says I am in South Thanalan.. which is a mistake since the Ifrit Cavern is suppose to be in the same area as Drybone.

I am either awaiting a response or a fix.

Only other option I have is to contact the Support Center.

This game crash error message comes in a OS-type window or is it a game-type window?
Because, well, some players are experiencing game client crashes since P4.

Quote:

---

Originally Posted by Lexiel

This game crash error message comes in a OS-type window or is it a game-type window?
Because, well, some players are experiencing game client crashes since P4.

---

It is a EDIT: It's a OS-window. Although I really hope this emergency world maintenance is going to fix my problem. I guess I'll see at 7:30CT

Still experiencing the same error even after the emergency maintenance.

I don't understand that they say the know about the problem do maintenance and still achieve nothing on said problems.

They close ticket in question saying Emergency Maintenance will fix my problem like they fixed it. Their technical support is a little on the -2 side.

my game crash also dosent matter what do have tested all change grafic option turning cf and so on but it still crash to winows time to time using w8

7:00AM CT and Emergency Maintenance still has not fixed my problem. I am starting to get really angry now.

Having the same problem here. Had none of these problems in beta 3 and 4.

crashing continually when i try to run game, phenom x4955 and 7970 gpu so not a lack of power issue no idea what causes it they really need to fix this

Now getting error 10102 so I don't know if my problem is fixed or not. If it's not one it's another... sigh.

@Irisa: I haven't had the problems in neither betas either. A little fucked up.

Current error fixed. More to come I'm sure, though.