Fatal DirectX Error 11000002

[draconene]

I'm running with a Amd radeon R9 380 too and the same processor as the OP. I keep getting this error like every hour when I play, and instantly when I open google Chrome while playing.
I'l try SunnyKreolo's solution then :/

[FaerRow]

Gonna try this tomorrow, in the meantime... Should we cut out the middle man and try AMD direct?

http://support.amd.com/en-us/contact/email-form

[Zetaemu]

So the night before I decided to chance it again, I fresh installed windows and manually update my system/OS to the current build. (15063) I was able to play for 4 hours straight 0 Crashes. Last Night another 2 with no problems. This morning it's all good as well. This is coming from either crashing after load - to up to 20mins before it would crash - showing Directx Error 11000002 Window.

Not sure what the problem is myself, but IMO it's with windows. I knew my card would run fine as I had it running in another computer just to check, and I assure you I've try all the fixes.
Updating GFX Drivers.
Clean Installing GFX Drivers.
Setting PCI Express Link Power Manager in Power Options to OFF.
Removing the overclock on my GFX Card.
Changed GFX cards.
Changed AA and AF to application controlled.
Clean installed FFXIV and updates.
Clean installed Windows 10.
Use DX9 - still crashed

After all that as I said I am currently running fine with the following-
Windows 10 build 15063
Amd Drivers 17.4.4
CPU AMD 1700 8 Core
GPU AMD 270x
Ram 16gb ddr4 3000 LPX Memory
MOBO MSI B350 PC Mate

[Basso]

the se support is so useless, after telling them my problem they said should clean install graphic drivers and so on.
after i said i did that and that i doesn't work and also send them a huge list of links where people are complaining about this problem the said do a forum post and make a bug report.

[Memoir]

I have started having this issue of late as well also. I have Nvidia drivers though and use Geforce GTX 980 for my card(s) . I have updated to my latest drivers and did a clean install for it and still this occurs. I am using DirectX11 to play the game. Also as a side note, if you google this error, you will see this has been going on for some time.

[WonderPeter]

I have a AMD Radeon HD 7870 never had problems in the last 2 years. Been very rarely having this exact error message when I come back to the game after having minimized for a while. I'm using the latest drivers and updates for Windows 10 x64 ( I have the creators update installed).
I have a friend that also had a lot of crashes with his AMD RX 480 and was only able to reduce them by tuning down the graphics quality.

[Hawkwing]

Using a GTX 780 and I get this at least once a day. Started happening after upgrading to Windows 10. Not only an AMD problem.

[PriestBelmondo]

I'm also running a R9 380 and I encountered crashes since 2 weeks before the Stormblood launch or so.
Before, I never had any problems at all. Always had the latest drivers installed.

So in a last desperate effort, I decided to roll back to the 17.1.1 drivers. I've never had a single crash since then. Maybe I'm just lucky. But maybe some of you might want to try the same thing and become lucky, too. ;-)

So I tried this out just for the heck of it. It was one of the few Driver patches I haven't tried yet. Yesterday night... and today all day I played about 12 hours straight not a single crash. Didnt get off at all and the game ran smooth. Maybe I'm lucky too? or that driver version really works.

[misterwuggles]

So I tried this out just for the heck of it. It was one of the few Driver patches I haven't tried yet. Yesterday night... and today all day I played about 12 hours straight not a single crash. Didnt get off at all and the game ran smooth. Maybe I'm lucky too? or that driver version really works.

I think it's just random unfortunately. I tried at least a dozen different drivers with clean installs--one of them being 17.1.1--and while some appeared to be good at first I ultimately did crash no matter what. Could certainly be different for you guys and I hope it is, but I didn't experience the same thing.

[WonderPeter]

I had this error today if its any help: