Fatal DirectX Error 11000002

Quote:

---

Originally Posted by Salt_Seafood

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. :(

Quote:

---

Originally Posted by Tanama

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. :(

---

I am sorry to hear this. I have played for another 2 hours just now and still no crash. I will keep you all updated here.

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

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

EDIT: This is with the latest nvidia display drivers.

http://i.imgur.com/J1MKm9H.jpg?1

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.

Any new info out there on this issue?
R9 285 and R9 380 still have this issue(since July), can someone confirm R9 390(x) is now fixed?
Is it possible that tonga series gpus will just never work correctly in dx11 with this game? Someone made a comment that tonga has major issues with this gaming engine and unreal engine when it comes to dx11

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.

Quote:

---

Originally Posted by 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.

---

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.

Quote:

---

Originally Posted by Souleater13

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.

Quote:

---

Originally Posted by outburstt

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.

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.

Oh, and here is a screencap of one of the crashes I got way back when this started...

http://i.imgur.com/39x49e1.jpg

Personally, I'd like to see SE respond to this thread to see if some of us can gather some sort of logs for them to try and resolve this issue. :(

Having the same issues with 361.43 on Windows 10 64bit with a GeForce 670.
Gonna try with 355.98 now and see what happens.

Have you guys tried to open a similar thread on the nvidia forums? I remember in the past a similar issue plagued FFXI, SE never gave us an official reply but Nvidia did (even though it took them quite a long time to do so!) and it turned out it was an issue with their drivers an they finally fixed. Took them ages but they did, even if FFXI back then was already a very old game.
So yeah, if someone has experience with this things, I warmly suggest to open a similar thread on Nvidia forums as well.

Quote:

---

Originally Posted by Xerek

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!

---

358.87: *DirectX Error* - Win10_64
358.50: *DirectX Error* - Win10_64
355.98: *DirectX Error* - Win10_64

I think the 358.50 lasted the longest for me. I got an error with 355.98 within ten minutes.

Quote:

---

Originally Posted by Monsalvato

Gonna try with 355.98 now and see what happens.

---

Over 1 hour of gameplay and no crash with 355.98 in DX11 mode.

Still no crash with 355.98. Going to finish up my weeklies then try 359.00. Given revision numbers and past results, I have a bad feeling 355.98 might be the last stable one. Once I finish testing all the drivers, I'll put a post up on the NVidia forums. I want to be able to tell them exactly where things went wrong.

@HakaseNyan, when you're trying the other drivers, are you performing a clean install each time? I'm surprised 355.98 crashed on you.

Over 12 hours of gameplay and no crash on Windows 10 64 with 355.98 using DX11.
Kinda makes you wonder why this issue happens only with DX11 and not DX9 though, and why it only affects some systems and not all of them. (I could name a long list of people with up-to-date drivers who are experiencing no issues with DX11 using an nVidia card)

(Original) Set up - Pre-Error
ASRock 870 EXTREME3 Motherboard
AMD Athlon II X4 640 Propus Quad-Core 3.0 GHz Socket AM3
Nvidia GForce 9800 GTX+
2x 2GB DDR3 1333
Windows 10

Been playing for about a month now without issues. Back on Thursday, 12/31/15, I got a new gpu. It is a used AMD R9 200 / HD 7900 Series. I played close to 30 hours over the weekend without issues.

Fast forward to today. I get a new stick of ram in, taking out my old ones. It is an 8GB DDR3 1600 stick. Install it without issues. Everything seems to run fine. I know my Motherboard won't run it 1600 by default, so i OC'd it to 1600 from 1333. Load FF14 and it started giving me this error every 5 mins or so. (I'm running on D11 Max settings, btw.)

I went back and changed the RAM speed back to 1333 and the errors went away. Don't know if this helps anyone, but if your RAM is DDR3, 1600, try changing it to 1333 and see if that works? Or if your RAM is overclocked, try without?

Figured I'd post just to see if my solution helps anyone. Hope Square or AMD can fix the issues.

Quote:

---

Originally Posted by Xerek

Still no crash with 355.98. Going to finish up my weeklies then try 359.00. Given revision numbers and past results, I have a bad feeling 355.98 might be the last stable one. Once I finish testing all the drivers, I'll put a post up on the NVidia forums. I want to be able to tell them exactly where things went wrong.

@HakaseNyan, when you're trying the other drivers, are you performing a clean install each time? I'm surprised 355.98 crashed on you.

---

Yes, I always do clean install of drivers and then I reboot just to be safe. All of the drivers posted lead to crashes for me on win10_64. Interestingly enough, the most recent drivers will actually cause the entire system to hang until finally crashing the game with the error pop-up. 358.50 and earlier will freeze the system for a very short moment and then the error pops.

Whelp, 359.00 crashed twice in under 24 hours. Once in Wanderer's Palace (Hard) at first boss. The next in Private Chambers after a half hour or so of RP. Time to test 358.91.

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

About the DirectX Error issue, I encountered it too, but it happened only when I had Occlusion Culling enabled.

Quote:

---

Originally Posted by Gunty

About the DirectX Error issue, I encountered it too, but it happened only when I had Occlusion Culling enabled.

---

what gpu and windows version are you using?

Quote:

---

Originally Posted by Gunty

About the DirectX Error issue, I encountered it too, but it happened only when I had Occlusion Culling enabled.

---

I wish this were the fix for me, but unfortunately I run with Occlusion Culling disabled and just had my game crash. I had gone without any fatal errors for a few weeks, too lol. :(

Still no update on this? Honestly, I haven't touched the game in almost 2 weeks because the crashes are so frequent for me, even when downgrading to different drivers.. Till today.

The crazy thing? I just built a new computer. Completely brand new components. Only installed FFXIV and nothing else. Two hours in? Crash. Nvidia driver 355.98

So I'm very, very, very, very upset.

I may have a workaround. After doing a *lot* of web scouring I have found something that has worked for me so far. I am still using the 359.00 drivers, which crashed twice in 24 hours before.

I've read that overlays might cause this issue. Three specifically mentioned were Fraps, MSI Afterburner and the NVidia Experience. I don't run Fraps while I'm playing most of the time, but I did have the other two apps. I uninstalled MSI Afterburner and Nvidia Experience. I've now gone a few days (and a lot of dungeons) and have yet to crash. Note that I do have Steam installed, so it doesn't look like the Steam overlay is an issue. I'll continue to test. If this works I'll install the latest driver, remove NVidia Experience, and give that a try.

Hope this helps.

Well, just started playing FFXIV and this error really makes it hard to enjoy it at the moment. Latest drivers installed, latest Windows 10 updates installed, game still crashes randomly (sometimes it runs fine for hours, sometimes it crashes within minutes).

To be clear, I don't have Fraps, MSI Afterburner or NVidea Experience installed, it still crashes. Disabling Steam Overlay doesn't work either. I really hurts the experience for me, hopefully this will be fixed as soon as possible.

EDIT:
Some more information:

My System: OS:Windows 10 64-Bit, GPU:EVGA GeForce GTX 570 Superclocked, RAM: 12GB, CPU: i7 920

Using the DirectX 11 Client of the game.

If I run the game in Borderless Windowed mode and this error occurs, my whole system freezes and I need to reset my PC.

I don't have any problems with running other games.

Quote:

---

Originally Posted by M4gicFe4ther

Well, just started playing FFXIV and this error really makes it hard to enjoy it at the moment. Latest drivers installed, latest Windows 10 updates installed, game still crashes randomly (sometimes it runs fine for hours, sometimes it crashes within minutes).

To be clear, I don't have Fraps, MSI Afterburner or NVidea Experience installed, it still crashes. Disabling Steam Overlay doesn't work either. I really hurts the experience for me, hopefully this will be fixed as soon as possible.

EDIT:
Some more information:

My System: OS:Windows 10 64-Bit, GPU:EVGA GeForce GTX 570 Superclocked, RAM: 12GB, CPU: i7 920

Using the DirectX 11 Client of the game.

If I run the game in Borderless Windowed mode and this error occurs, my whole system freezes and I need to reset my PC.

I don't have any problems with running other games.

---

Are you sure you don't have the NVidia Experience installed? It's installed by default with the driver. From what I found it's not enough to disable it, it has to be uninstalled completely through the Control Panel.

Quote:

---

Originally Posted by Xerek

Are you sure you don't have the NVidia Experience installed? It's installed by default with the driver. From what I found it's not enough to disable it, it has to be uninstalled completely through the Control Panel.

---

Yep, I always select "Custom" and only install the Display Driver and PhysX components. Also, it seems to be crashing more frequently after or while changing the graphics options. I'm 99% sure something is wrong with the XIV client. Other games run hours on end without any problems, I checked and updated several things on my PC and most people seem to only have this issue with the latest patch of the game. When I played the free trail a few months back I had no problems with running the game at all.

EDIT: Just had to restart Windows because the game kept crashing while loading the main menu, it's so random :S.

I also have no MSI afterburner and NVidia experience. still crashing. Literally the only thing that's installed is FFXIV, teamspeak and OBS. TeamSpeak has yet to be used and OBS is used only when streaming for Xbox/WiiU. This is on a completely brand new built computer, only a week old.

as a test, I downloaded unigine valley and it ran fine.

I still believe there is something wrong with the game itself, and I think SE not commenting on this very long thread [at least compared to others found here] is either proving that there is something wrong and they don't know how to fix it, or them not acknowledging there's something wrong.

I'm thinking about getting my subscription money back, I can't play the game like this. For a Pay to Play game I expected at least a reaction from SE on this issue. Please let us know what is going on :(.

Quote:

---

Originally Posted by M4gicFe4ther

I'm thinking about getting my subscription money back, I can't play the game like this. For a Pay to Play game I expected at least a reaction from SE on this issue. Please let us know what is going on :(.

---

Unfortunately you won't be getting any sort of refund for your subscription. The only reason they would issue a refund is if there is criminal activity involved, as per the FFXIV User Agreement, Section 4.7 (Source)

Alright, I still have yet to crash with the DirectX error. I did a clean reinstall of the 361.43 driver set without the GeForce Experience and have run the Void Ark without a crash. Will continue testing, but for me at least it seems uninstalling MSI Afterburner and the GeForce experience stopped the crashing. Now, to be clear, those are useful programs to some and I still think this is something Square-Enix and Nvidia (and ATI?) need to work together to fix. Keeping those programs uninstalled is a workaround, not a solution.

It's also clear there are multiple crashing bugs present. This thread revolves specifically around the bug wherein the DirectX 11 client either crashes with the message "A Fatal DirectX Error has occurred (11000002)" or the game seizes up completely, locking the PC as well. Normally the client itself will just freeze for a short period of time before the error message finally shows. This specific bug only occurs with the DX11 client, switching to DX9 will fix it. If your symptoms don't match these, you likely have a different crashing bug and this thread will not help you.

This has been a frustrating ride for a lot of us, and hopefully it will be resolved soon. I have a bit more testing to go before I can post something quite specific on the NVidia and SE forums. I want to be able to throw very specific data at them to speed up a fix. Hang in there one and all, and remember, aside from Steam, try completely uninstalling anything that may act as an overlay. It's more a band-aid then a fix, but at least I've been able to play crash-free for awhile now.

Some more info;

My game just crashed again (tried everything mentioned in this thread, without any luck). But I just noticed something weird, right before my game crashed, I saw a yellow/orange particle thingy showing up (flickering) that wasn't supposed to be there. Also, I'm using Dxtory to cap the framerate to 45 (yes without this program the game still crashes), right before the game crashed my framerate spiked and immediately went back to 45.

Also played the game yesterday for a few hours and it didn't crash at all. It's hard to really tell what the problem is if it happens so randomly.

There has to be a conflict with the engine and the NVidia drivers for some strange reason.

I haven't had a fatal error in several days, possibly a week now. However, now my game will randomly decide to enter a series of "lock ups" until I close firefox(64). An interesting turn of events!

Just happened again, Ramuh ex, on Arbiters + Thunderstorm

So... still nothing yet from SE?
Haven't played for a month now. Probably ending my 2 year long sub. :(

Come on SE. Please fix.

Quote:

---

Originally Posted by outburstt

So... still nothing yet from SE?

---

Sorry, but SE don't reply to technical support requests on these forums. They are more for customers to help other customers. To contact SE directly you need to open a ticket from their support site or ring them.

Quote:

---

Originally Posted by worldofneil

Sorry, but SE don't reply to technical support requests on these forums. They are more for customers to help other customers. To contact SE directly you need to open a ticket from their support site or ring them.

---

Then why is there a "being addressed" section in the technical forums? I'm pretty positive that other customers don't move the threads themselves.