Runtime Error

[Rahal]

I get this daily, combined with 1017 and the Lobby Server errors it is ridiculous. It took me 6 hours to hand in a single quest because of the game crashing every time I finally got in.

[Ubermann]

And again....

[Ubermann]

Managed to get back in, crashed on my first zone transition.

[Ubermann]

Le bump....

[Raist]

No problems here... yet. Granted, I've only got maybe 40 hours of playtime combined the last 2 1/2 weeks because of the log in clamping.

Something I've been wondering... are you guys running on the high end of the quality settings and such? I've been running the Standard Desktop profile with a few things like shadows and such toned down or disabled.

Just wondering if maybe it's not tied to something funky like fetching components for specific effects/texture maps or something that is tripping things up. Otherwise, maybe an issue with something not getting downloaded properly with all the congestion?

[Korinth]

I'd been having this, but I downloaded all the C++ redistributables from Microsoft, and haven't had it since. Not sure if it's a fix for everyone, but worked for me.

[Juriva]

Just got this error randomly killing stuff in La Noscea.

[Dev]

Still getting this error.. If I'm mining, questing, or crafting I'm just fine.. The moment I start running with a pack of people to a FATE or I'm near a FATE my chances of getting this error seem to go up 100%..

This is a programming error and needs to be addressed by someone from SE.. The tech forums have had zero responses!

[Evilbob]

get same thing and started another thread posting screen shots of where and when ingame
http://forum.square-enix.com/ffxiv/t...-Runtime-Error

[Evilbob]

Found a page that explains why this is happening and it is a programming error.
http://support.microsoft.com/kb/125749

Cause:
This error occurs when your application indirectly calls a pure virtual member function in a context where a call to the function is not valid. In most cases, the compiler detects this and reports the error when building the application. But depending on how your code is written, sometimes the problem is detected only at run-time.

The error occurs when you indirectly call a pure virtual function within the context of a call to the constructor or destructor of an abstract base class.

So basically one or more of their programmers derped some code.