Fatal DirectX Error 11000002 still there in Stormblood

[LexiWhitewind]

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

[Chipipie]

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.

[Aladire]

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

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

[LexiWhitewind]

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

[Ceryni]

I getting the same problem myself.

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

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

[misterwuggles]

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

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.

[LexiWhitewind]

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.

[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.

[Dee64]

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.

[ElazulHP]

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!