Fatal DirectX Error 11000002

[Salt_Seafood]

Same here, Salt, except I have an nvidia card. As for today, I've gotten two fatal DirectX errors in Camp Bronzelake.

EDIT: FFXIV crashed a third time today at Camp Bronzelake. I don't know what is causing this.

Well, ladies and gentlemen, a fix might be upon us! Today Nivdia released the new drivers (Nvidia GeForce/Ion 361.43 WHQL). I have installed them and just ran FFXIV for 4 hours without a single crash! With the previous drivers this was impossible. Maybe its just luck, but maybe these new drivers fixed our problem!

[Tanama]

Well, ladies and gentlemen, a fix might be upon us! Today Nivdia released the new drivers (Nvidia GeForce/Ion 361.43 WHQL). I have installed them and just ran FFXIV for 4 hours without a single crash! With the previous drivers this was impossible. Maybe its just luck, but maybe these new drivers fixed our problem!

I'll give it a shot now. I hope this works!

EDIT: FFXIV encountered yet another Fatal DirectX Error while in Mor Dhona as I was riding back to town from the Tangle. So much for that fix.

[Urthdigger]

The new drivers want me to upgrade to windows 10. Whyyyyyy :/

[Tanama]

Yet another Fatal DirectX error just as I strike a tree.

EDIT: This is with the latest nvidia display drivers.

[Xerek]

Add me to the list. I had been getting this for maybe a week and none of the proposed setting changes or such fixed it. I initially crashed in FATEs and the Void Ark, though over time I crashed twice in private rooms and several times in dungeons (including Pharos Sirius - Hard). Most times were DirectX errors, though twice my system crashed outright, once with a horrific buzzing noise. This is on Win 10, NVidia 560Ti. This occurred with drivers 359.06 and 361.43. A couple days I uninstalled 361.43 and reinstalled the last one I used, 355.98. I've run that for several days now and so far, knock on wood, no crashes. The problem is, I missed a number of drivers between 355.98 and 359.06, four to be exact, so if it is a driver issue, I have no idea which driver actually broke it.

Hope this helps.

[outburstt]

Has anyone found a solution to this at all? I find it weird that my EVGA GTX 770 works perfectly fine on every single other video game, except this one.

[Souleater13]

Has anyone found a solution to this at all? I find it weird that my EVGA GTX 770 works perfectly fine on every single other video game, except this one.

It seems for Nvidia users its a matter of picking through driver releases and finding one that works.
For Amd users with tonga based chips there hasn't really been a solution besides the work around of running in DX9.

[outburstt]

It seems for Nvidia users its a matter of picking through driver releases and finding one that works.
For Amd users with tonga based chips there hasn't really been a solution besides the work around of running in DX9.

I think the bigger issue is that every other video game works perfectly, other than this one.

I also happen to rebuild and reformat my PC specifically for this game only to continue crashing like this. Then I tested my same exact setup using a number of other games and literally played for hours.

To me, sifting through the drivers to find one of the releases that works for me is not a solution.

[Souleater13]

I think the bigger issue is that every other video game works perfectly, other than this one.

I also happen to rebuild and reformat my PC specifically for this game only to continue crashing like this. Then I tested my same exact setup using a number of other games and literally played for hours.

To me, sifting through the drivers to find one of the releases that works for me is not a solution.

I do agree those aren't solutions but who knows when a real fix will be around. its been six months on AMD tonga's and Nvidia seems to be back and forth between various drivers as new FF14 patches are being implemented.

[Xerek]

Update: I still have yet to crash running 355.98. I've run multiple dungeons, Void Ark, roleplayed in Ul'dah, in personal housing...all ran perfectly fine.

So, that leads to a few thoughts. For Nvidia this seems to be a driver issue, but this error occurs on AMD as well. I'm wondering if the issue is with FF XIV. I'm wondering if FF XIV is making a DirectX video call that more current drivers don't like. If AMD and NVidia made some kind of universal change, or if there was a change to DirectX in how it interacts with the drivers. This still might be something SE needs to fix.

For Nvidia, sadly I skipped several driver revisions, and one of them started this error. So, we're just going to have to test them and see where it breaks.

361.43: *DirectX Error*
359.06: *DirectX Error*
359.00: ???
358.91: ???
358.87: ???
358.50: ???
355.98: Works!

There is obviously an issue here, and since it spans NVidia and AMD, I hope SE will take a look at it. Hope this at least helps.