Fatal DirectX error 11000002

[misterwuggles]

I'm getting this issue as well WITHOUT the Creator's Update--I'm still on the Anniversary Update with all the bullshit like the Xbox app and game mode completely removed rather than just disabled. The only thing that changed when this begun happening for me was an FFXIV update (3.3 or 3.4--don't remember which exactly since I was winding down to unsub for a break). I don't update my drivers or Windows unless I have a need based on the change logs so the ONLY thing that changed at the time I started getting this error was an FFXIV update. I have an R9 380 so in my case I believe a patch broke some sort of compatibility between the game and my card (many people getting this have an R9 380) and it hasn't been fixed by SE or AMD. I'm sure both have the capability to fix it, but neither have. AMD doesn't have a great track record with drivers but I feel like this is more on SE since I had no issues from launch until 3.3/3.4.

Every other game and function on my computer performs perfectly. I've tried everything the OP mentioned aside from a full format because it's just not worth the effort for an incredibly low chance that it'll do anything. From everything I've read from all the threads here and on Reddit and all the Googling combined with my own experience with the issue I really think the only way this is going to be fixed is if SE or AMD fixes it. I'm really hoping Stormblood fixes it because as many people have said using Dx9 is not a solution. I get that we're a small percentage but everything I've seen points to them breaking something and it would be nice if they unbroke it--or even if they didn't break it they can certainly fix it--considering an expansion is on the horizon.

[Epo]

I'm really nervous that because of this Stormblood will be unplayable... Gonna be super bummed if that's the case.

[Aladire]

I know this may sound weird, but I have these installed on my computer from my IDEs for programming. Yet, I do know that graphic drivers and DirectX can refer to them as well.

If you do not have these install, please make sure do to so:
Microsoft .NET Framework 3.5 and the latest (I believe it is 4.6.1)
Latest version of Vulkan (For those using Nvidia)

Please visit https://www.microsoft.com/en-us/down...ils.aspx?id=35 and make sure you have the latest DirectX 9 and 11. This will run on any windows 7 and later. (Note: DirectX 12 can only be downloaded and updated through windows update on windows 10.)

[Yusuke_Yang]

I reinstall everything on my computer, even reinstall windows. Nothing seems to help. I play other games at max setting for at least 3-5 hours and they give me no issues. I lower the settings on ff14 just in case to see if that would help but nothing. I really hope is a patch issue with ff14 and not windows because stormblood is around the corner =/

[Chained_Icarus]

Stormblood is here now and problem still persists. I have a Radeon R9 380 like a few others around here. FF only game ever giving me errors. At my wits end. It is basically unplayable.

[zXr]

I want to just troll you can blame Win10, but there is a reason and a fix.

I would check this out:
http://www.dependencywalker.com/

I actually had help from the Marvel Heroes tech team years back, most game with a launcher will auto-select 32 or 64 bit based on your system's compatibility, if for whatever reason the 64-bit one fails to start it will default to 32-bit. The link is to a dependency checker, basically identifies and displays all files/DLL's that are needed to run the selected program. This was extremely useful to me in fixing my inability to run 64-bit clients at all, while not realizing there was in issue until I tried playing a game that had separate 32-bit and 64-bit clients for download and the 64-bit one would not load up and just crash.

Basically run the program from the link that matches your system (x64 one) and select the dx11 client from the game folder to test and any results that show up in red text are the culprits. The most common reason for these fatal errors is the x64 version is either missing or corrupted, this can be caused by OS updates, DX updates from installing other programs (where in a 64-bit client was added later and the devs never updated the DX version included) and malware/viruses.

To Fix: Delete the culprit DLL files completely, then go to the Microsoft website and download and install their latest comprehensive DX update. (This will take some time to run, as it will check and add any missing ones, complete deletion is required to break the associations so they can be properly replaced.)

[FaerRow]

Bumping, still occurs with Stormblood.

Edit: I may have jumped the gun there, I updated my AMD drivers to the optional 17.6.2 drivers and it seems to have worked. Before it would crash between 1-20mins in, and I just finished playing for over an hour with no issues! Fingers crossed it stays that way...

[Kamiako]

Same problem. Windows 10 64bit, AMD 380. Tried what you just suggested and updated to the optional 17.6.2 drivers, saw some improvement but still getting crashes.

EDIT: Did a little bit of an experiment. Using the current AMD drivers, I was crashing at the exact same point in the first Red Mage job quest instance, three times in a row. When I updated to the optional AMD drivers, I was able to get past that point, but then crashed twice at the very end of the instance. When I moved the client to DirectX 9 there was no crashing and I was able to finally finish the quest. I would call the optional drivers an improvement, but this is still a serious issue that has been going on for months and only seems to have gotten worst with Stormblood.

[Chained_Icarus]

I want to just troll you can blame Win10, but there is a reason and a fix.

I would check this out:
http://www.dependencywalker.com/

I actually had help from the Marvel Heroes tech team years back, most game with a launcher will auto-select 32 or 64 bit based on your system's compatibility, if for whatever reason the 64-bit one fails to start it will default to 32-bit. The link is to a dependency checker, basically identifies and displays all files/DLL's that are needed to run the selected program. This was extremely useful to me in fixing my inability to run 64-bit clients at all, while not realizing there was in issue until I tried playing a game that had separate 32-bit and 64-bit clients for download and the 64-bit one would not load up and just crash.

Basically run the program from the link that matches your system (x64 one) and select the dx11 client from the game folder to test and any results that show up in red text are the culprits. The most common reason for these fatal errors is the x64 version is either missing or corrupted, this can be caused by OS updates, DX updates from installing other programs (where in a 64-bit client was added later and the devs never updated the DX version included) and malware/viruses.

To Fix: Delete the culprit DLL files completely, then go to the Microsoft website and download and install their latest comprehensive DX update. (This will take some time to run, as it will check and add any missing ones, complete deletion is required to break the associations so they can be properly replaced.)

I tried this but it seems like the program has been long discontinued and flags a ton of false negatives. =/

I really am at my wits end with this problem. It's rendered the game unplayable even in DX9 mode with no real solutions. Could someone from SE please acknowledge they're even aware of the problem and make some suggestions?

[Zetaemu]

I've spent the past 2 days trying to fix this problem and I cant find any solution.
Fresh OS install - No Fix
Old/Current/Beta Drivers - No fix
Clean FF14 Install -No Fix
Change PCI Express Link in Power Options settings -No Fix
Lower GPU clock speeds - No Fix
Clean out GFX card and installed new cables -No Fix
Change AA settings - No Fix
Reinstall DX drivers - No Fix
Change to Dx9 - No fix

I get no problems in other games that I play. Just FF.