Originally posted by DaveG
Seytra: This is news to me. When did this crash start appearing? Do you know of any way to induce it?
Hmm, I have seen several people getting this one so I assumed it was a really common thing, as it is pretty common for me.
As for ways to induce it: As I said, click around a lot in the client before you join (like creating a char and going back and forth in the creation)
Also, a previous crash tends to trigger it, I am not sure if killing PS does the same.
Another thing that likely creates crashes for me is tasking away PS before inside the loading screen unless at the login screen. (I didn\'t check the error codes recently, I\'ll take note next time).
Task it away during the initial splash screen (i.e., when the game doesn\'t come from the cache but is actually loaded from the hdd), or during login will likely result in a crash, even if you task back and continue to another page. Mostly you crash with this error at either the char selection (even after a while sitting at it) or when entering the game (at no fixed time, so you\'re safe only when you actually are ingame).
Sadly, these are only things that make it more likely to happen, I know of no way to have it happen reliably.
Most often I get this when loading into Hydlaa, though that is where I am most often. Maybe also because due to the larger map, there is more chance for it to occur.
As for how long it has been there: at least since the last big update, possibly before that. I have submitted two dumps of it with a temporal distance of some weeks to the dump site before the service was suspended, since I didn\'t want to resubmit every time I got one to not clog the server.
Edit: The constant part is the error always ending in \"161\" (Maybe even \"F161\" ).
Edited to add in response to DaveG below:
This isn\'t just a problem that can be fixed by rebooting. This
also happens when after a crash I don\'t log back in but instead shut down the computer, turn it off and only turn it back on the next day, by which time clearly any residue would be gone. Still I had this happening.
This is why I assumed something in the account or char being left in a state that can confuse the client when getting sent the information from the server.
