Fatal DirectX Error 11000002 still there in Stormblood

For the folks that seem to mostly have an R9 380 that have been experiencing this issue, looks like they didn't bother to fix it in Stormblood. I'll be trying again when it dies down and isn't so incredibly crowded, but I'll bet it's still an issue regardless. I hate to make a post that's basically just whining, but if you search the forums you can already see countless posts on this issue so I don't think we need a 50th in-depth analysis of everything that's been attempted.

For the sake of being thorough though: tried multiple versions of old and new drivers with clean uninstalls via DDU and/or AMD cleanup utility, tweaking every graphics setting in game and in AMD settings, underclocking GPU, rolling back Windows updates, Dx9 "works", every other game works no issues, every other function of computer works no issues.

Not sure what else we can do here. I'm going to keep submitting stuff to AMD and I guess continue to complain here and just hope that at some point they care about us enough to fix it before I have to buy a new video card.

Yeah... It's really disheartening because I can hardly play the game in it's current state. I go to dx9 but the game does not perform well in dx9 and looks absolutely atrocious x.X

Yeah, also experiencing this, have been for a few months now. Tried everything you have, seems to especially affect 'Tonga' chipset GPUs (R9 285, R9 3xx). I have an R9 380, handles everything fine with any DirectX ver, just not this game on DX11. Was hoping it'd be addressed in SB but no dice. Not sure if it's an XIV issue or an AMD driver issue, but whichever it is, nobody seems to have a solution yet.

Same here. Playing with an R9 380. Still crashing in DX11. Still works with all other games with no issues. Still "works" in Dx9 (I get the strange bug where it fails to render mobs/npc/occasionally the floor). This is beyond frustrating.

So, did a search via Google and found this thread. I'm having the exact same issue with the R9 380. I've tried just about everything including rolling my drivers back to 16.11.5 with no luck. Seems to happen no matter what. Does anyone know what is causing the issue and any other potential fixes?

I'm all out of any hope that this can be resolved. If there is a fix, SE/AMD just don't care enough to implement it because I don't think there is a permanent fix on the client side (for an R9 380 at least). The only reliable resolution at this point as far as I can tell is to use Dx9 or buy a new video card and the former still isn't all that comfortable.

I too still have this problem and it sucks. The game looks beautiful on my pc in DX11 and I love that sexy FPS. But the crashes still happen and their severity and unpredictability makes it nearly unplayable. And even DX9 still occasionally hangs or even crashes rarely. I've been playing on my PS4 instead lately but it isn't nearly as satisfying and buying a new card just for a potential fix on a single game is not currently an option.

It is still happening for me too. I have emailed square tech about it and after trying all the steps they recommended (which i had already tried) they have now said they're escalating it. I have yet to hear back...

The game used to work for me until about a month ago, we have another PC in the house with the same hardware (R9 380) and the game works in DX11. >.<

R9 380 here too, same issue. I thought the latest drivers fixed it, but I guess I just a lucky streak of no crashes for an hour.

I'd love to be able to play this in its full glory instead of DX9!

This issue happened back in HW, and unfortunately it seems to be back for SB. Hope it gets fixed soon. Last time AMD had to release an update to fix it, but I think it's a SE issue.

I have R9 200 w/ crossfire. I never had this errors until stormblood. Used to play in directx9, but now game wont start at all unless 11.

Add me to the list, same DirectX issue, no surprise, have a R9 380

Same here I have a R9380, still getting an error with newest ATI drivers. Extremely frustrating.

I'am with you ! Got a R9 380 X ... Well i have to play on dx9 too but its really horrible. Guess we need to wait for SE or ATI to fix it , keep harrass them so they weill see there is a real problem for a lot of people

I got this error once and usually my screen goes black and my fans go up really fast/loud. I am running a GTX 1080 however. Not sure if this changes the reason/error. I never got the error and it only happened later today for me. The game was working like a charm as always.

(AMD r9 380)

Hello guys,
I've spent almost hours on end since the release of SB trying to fix this god damn DirectX error, and i think i might have done it.

A lot of forums suggest turning off power settings etc, which im sure everyone has done to no avail.

So today, i decided to search for a FFXIV specific driver, and turns out there was a fix from AMD back during HW.

Try to uninstall your current driver using DDU, and then search for driver 16.3.2.
You can find this on GURU's website.

Once that is installed, you will notice in the Global Settings, there is a power efficiency setting thats automatically turned on.
(I mentioned the power efficiency setting because for me, the majority of the time my screen goes blank but the sounds and game is still running, but the GPU decides it needs to restart)
Turn that off, Restart your computer and there you have.
At least, this fixed it for me.
Playing on DX11 now so smoothly and so far, without any crashes.


Please let me know if this fixes anyones issues!
:)

Quote:

---

Originally Posted by LexiWhitewind

(AMD r9 380)

Hello guys,
I've spent almost hours on end since the release of SB trying to fix this god damn DirectX error, and i think i might have done it.

A lot of forums suggest turning off power settings etc, which im sure everyone has done to no avail.

So today, i decided to search for a FFXIV specific driver, and turns out there was a fix from AMD back during HW.

Try to uninstall your current driver using DDU, and then search for driver 16.3.2.
You can find this on GURU's website.

Once that is installed, you will notice in the Global Settings, there is a power efficiency setting thats automatically turned on.
(I mentioned the power efficiency setting because for me, the majority of the time my screen goes blank but the sounds and game is still running, but the GPU decides it needs to restart)
Turn that off, Restart your computer and there you have.
At least, this fixed it for me.
Playing on DX11 now so smoothly and so far, without any crashes.


Please let me know if this fixes anyones issues!
:)

---

Fixed it for how long so far? I've tried probably a dozen drivers and some were more stable than others, often tricking me into thinking it was fixed. At least a couple of them seemed to work for a day or so before it continued to happen. Not sure if I've tried this particular driver so I'll give it a try when I get home, but I'd just caution against folks getting their hopes up.

I haven't seen that on my end for a while now. Make sure your highest Direct X , 12 right now. I had that issue when I was using HDMI , I switched to Display port and have had no issues. I don't think it's a game issue, more of a performance setting on our systems.

Quote:

---

Originally Posted by ManuelBravo

I haven't seen that on my end for a while now. Make sure your highest Direct X , 12 right now. I had that issue when I was using HDMI , I switched to Display port and have had no issues. I don't think it's a game issue, more of a performance setting on our systems.

---

I've tried at least a dozen different drivers--old and new--with clean uninstalls via DDU and/or AMD Cleanup Utility. I've tried various combinations of settings in-game and in AMD Settings. I've underclocked the GPU and I've overclocked the GPU. I've rolled back/updated Windows (which with Windows 10 also updates Dx12). I've re-installed the game. I've re-installed Windows. I've moved the card to another identical computer (built my computer and GF's computer at the same time with an R9 270--only difference being my 270 died and was RMA'ed to an R9 380) and the issue moved with the card. Absolutely zero issues with other games and functions on my PC.

I can pretty confidently say this almost certainly isn't something on the user side. FFXIV wants the card to do something it doesn't like and it crashes the drivers and therefore the game. An update to FFXIV or to the drivers could likely fix it but neither SE nor AMD has deemed us important enough to look into this or communicate with us about it.

I'll continue to try every single fix people recommend and say ha worked for them because I'd love to be wrong and finally be able to play the game properly, but that hasn't happened yet and Stormblood has been a markedly less amazing experience because of it. If I wasn't already so invested in FFXIV I'd drop it in a heartbeat over this. I shouldn't have to buy a new video card to fix an error in a single game.

Actually, earlier today there was a response by the AMD engineer team member that they have replicated the issue and are working on a fix. So there is hope.

it has been on all day so far, without crashes.
I only assume its fixed because i would stutter here and there.
Especially in areas such as kugane or Rahlgrs reach with high population.

I might just be being hasty with the smoothness, but so far, so good.
I will keep updating you though with my progress.

Please try it, and let me know your progress too :)

well for me i tested dx11 again yesterday it was ok , i where fishing all the day so np when i dont move to much apparently. Then i moved a little and traveled to peak area and i crashed on my mount alone in the desert so i dont think its only on crowded areas.

Sorry that so many are still having these problems. My solutions I posted in the other forums would have resolved if it was a hardware problem since settings changes effects that. But, if you do not have drivers that will even work, then nothing will help till the graphic card company fixes it. Props to Orlet for contacting ATI directly!

For those on Nvidia, the most recent drivers have resolved issues for the windows 10 latest updates, including the creator update.

For those on ATI cards, the other thread that has more replies has this: http://forum.square-enix.com/ffxiv/t...1000002/page14

Quote:

---

Originally Posted by Orlet

Unlike the "super helpful" SE support, AMD support has been nothing but helpful. Earlier today user amdmatt has posted a reply that they have managed to recreate the issue with their internal engineer team, and will start working on a fix. So hang in there guys, it's coming (hopefully).

For the nVidia product users I highly recommend posting this on their support boards as well. You never know, they might fix it as well.

It's still sad that game bugs have to be patched out by the graphics drivers engineers, not the original developers of the game...

---

Can someone please link me to the support forum on AMD where this was said?

I getting the same problem myself. :mad:

Quote:

---

Originally Posted by LexiWhitewind

Can someone please link me to the support forum on AMD where this was said?

---

https://community.amd.com/thread/196446

Have this in the other larger/older thread about this issue but just wanted to put it here as well to be safe:

Quote:

---

Originally Posted by HeavensHell

I have an R9 380x in my old build that suffered the same error and I fixed it by doing a clean uninstall of drivers with DDU and reverting to the 16.11.5 driver and turning off windows automatic driver update and my old build has no issue running FFXIV in DX11 until they sort the problem in an updated drivers.

---

Yeah I did the same recently and I've been okay for 3 solid days and counting. I expect it to still crash at some point, but it's probably stable enough to play. My issue was I underestimated just how persistent Windows 10 is with updating your drivers in the background so that's KEY. If you're trying to use an old AMD driver like 16.3.2--which is the version in which they fixed this issue back during HW--Windows is going to apply a newer version if it has it. You might be able to cut out some steps but this is basically what I did:

1. Delete your Windows store driver. Mine was from April 2017 so anything older was being replaced with this without any notification or restart required.
2. Set Windows to not include drivers with Windows Update in group policy.
3. Switch Device Installation Settings to not update stuff automatically.
4. Do a clean uninstall of existing drivers with DDU/AMD Cleanup in safe mode.
5. Re-install 16.3.2 drivers (or something else from this era if you think something is going to be more stable) and restart.
6. Give it some time and restart again just to make sure Windows 10 isn't installing a newer driver.

I included all the details of what I experienced in my ticket with AMD so hopefully that'll help get the fix into a newer driver. AMD's support while they didn't actually fix anything actually seemed to have read my email and had a good suggestion (to try 16.3.2 which specifically fixed this issue in HW). SE's support on the other hand gave me a list of generic things to try that I already tried and specifically detailed in my original email then closed the ticket. I'm going to say if you can't get it working with old drivers you're just going to have to wait for the fix to make it into a new one because SE doesn't really give a hoot.

thank you for sending me the link ;)

I can confirm as well, that the automatic windows driver update is indeed the cause of these errors.
I have rolled bck my driver and the issue has been gone, at least for the past 2 days.

If any of you are unsure on how to do this, follow my instructions below :)

Right click Start Menu > Device Manager
Display Adapter > (GPU Card)
Right click > Driver
Rollback

it SHOULD stick to the old driver, but best to check it every now and then to make sure windows doesnt update it again.

I am currently using AMD driver - 16.150.2211.0 via Device Manager NOT Radeon Settings.

Hmmm...my wife has the same Errors.
- New Win10 Pro x64 installation
- no AMD components
- only intel and Nvidia

But we can reproduce the error. It happens very frequently when TeamSpeak or Discord client is opened. We testet more days with and without the voice programs, and here we can say - 100% stable without and many Direct X errors when in Teamspeak or Discord is started.

I play on Sargatanas. Tonight was the first time I've gotten this Fatal DirectX Error 11000002, since SB, even with NVIDIA. I usually get booted, frequently, with 90001, 90002, and since SB 90006. Players have been DC'ing from our server all day and night. It hasn't improved. It is probably worse.

There are notes in the new AMD 17.7.1 driver saying the crashing issue in FFXIV is resolved for all 3xx series cards and so far I am inclined to agree. I've yet to crash after installing the new driver in DX11. I'm running a R9 380. YAY! FINALLY!

I started having the same issues as everyone else when Stormblood came out and I have not been able to find a solution yet. I've done everything everyone on every forum has suggested and nothing has worked. If anyone can suggest anything, I'm willing to give it a shot if I haven't tried it already. I really don't want to be forced to stop playing the game over something like this. =(

I'm running an Nvidia GeForce GTX 675M on an Alienware M17 RX. I know the vast majority of people use AMD so maybe someone can suggest something specifically for Nvidia users that might work?

Quote:

---

Originally Posted by Barkit

I started having the same issues as everyone else when Stormblood came out and I have not been able to find a solution yet. I've done everything everyone on every forum has suggested and nothing has worked. If anyone can suggest anything, I'm willing to give it a shot if I haven't tried it already. I really don't want to be forced to stop playing the game over something like this. =(

I'm running an Nvidia GeForce GTX 675M on an Alienware M17 RX. I know the vast majority of people use AMD so maybe someone can suggest something specifically for Nvidia users that might work?

---

I would try contacting the Nvidia support. AMD released a driver for the 3xx series cards the other day that fixed the issue for us. Nvidia will probably need to do something like that as well for you guys.

So I found a solution that works for me and I'm a little upset that it's such a simple solution and that it took me this long to discover it. I turned my graphic settings in-game down. I had just about everything running on maximum until now but I went down to standard and I haven't gotten the error since. We'll see if this will last but so far, it's been working. I know toning down the graphics isn't ideal for most folks when you consider how much you spent on your GPUs and what you expect from them but honestly, there isn't much difference in the visuals at all between the settings at all.

Edit: So an update, lowering the graphic settings in the game hasn't actually stopped the error from happening but at least it doesn't happen as often as it did before. It's an improvement but not a solution to this problem.

Quote:

---

Originally Posted by CyberWuff

Hmmm...my wife has the same Errors.
- New Win10 Pro x64 installation
- no AMD components
- only intel and Nvidia

But we can reproduce the error. It happens very frequently when TeamSpeak or Discord client is opened. We testet more days with and without the voice programs, and here we can say - 100% stable without and many Direct X errors when in Teamspeak or Discord is started

---

I noticed that too and it's when I'm just afk fast crafting
I don't use ts right now but discord yes. Sometimes I forget to turn off discord and voila! Mr fatal error