Fatal DirectX Error 11000002

[PriestBelmondo]

Updated my driver chipset (no idea if that would help) so far i played about an hour then crashed. Restarted and no crash so far but its about to be an hour again so xD guess we'll see where it goes. It doesnt make any sense D= if i set it to dx9 there's more fps issues then when i play on dx11 which is why i must play it on 11. I can't stand it when the fps drops down to the 20's. With dx11 i have no such issues other than crashing ._.;;; Update: Just crashed lol

[PriestBelmondo]

There was a driver update a year back where AMD saw that dx11 crashed when playing heavensward that apparently fixed it. However obviously it still isn't, maybe with stormblood out they'll recognize the problem still exists and try to work on fixing the problem?

[Orlet]

It only fixed for some people (did work for me, until SB). But seriously, though, relying on a graphics card manufacturer to fix your bugs for you?

[PriestBelmondo]

Yea it sucks. What sucks more is that I'm looking to buy another GPU just to avoid a crash, other games play perfectly fine so it seems unnecessary to have to buy another card. Also why does my fps drop on dx9 however on dx11 the fps is stable at 50-60?

[GunksFoy]

This isn't only an AMD issue. I am running an Intel i5-7600k with a Gigabyte G1 Gaming GTX1070 and I get this error constantly. It always happens when I launch the game, and relaunching 4 or 5 times usually works, then no more errors. But I do indeed see the same errors.

EDIT: Additionally, I don't see these types of error with any game except FFXIV

[Velhart]

This isn't only an AMD issue. I am running an Intel i5-7600k with a Gigabyte G1 Gaming GTX1070 and I get this error constantly. It always happens when I launch the game, and relaunching 4 or 5 times usually works, then no more errors. But I do indeed see the same errors.

EDIT: Additionally, I don't see these types of error with any game except FFXIV

This. People saying this is a AMD related issue need to stop saying this. It is very clear this is also a problem with users using GTX cards also. Happening after a certain Windows update. There might of been a time it was an issue with AMD only but it is clearly spread among other types of setups. If SE can at least acknowledge this or at least try to pinpoint the issue, we could at least try to solve it on our end.

[misterwuggles]

I don't think it's EXCLUSIVE to AMD, but I also don't think it's a coincidence that there are such a huge number of reports of this coming from people with an R9 380. So while it's certainly possible for any card to get this or other errors I'm not sure they're the same exact thing under the hood. Either way it would be nice to get some communication or just plain old fixes.

[PriestBelmondo]

So any word yet?

[Epo]

Is it possible it has something to do with antivirus conflicting with anything? I know I have avast, what about everyone else

[SunnyKreolo]

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. ;-)