If You're Having DirectX 11 Crash Issues, REPLY TO THIS!

[FizzyElf]

This is what fixed it for me on Windows 10 with updated nividia drivers:
1. Back up character data

2. Download the ffxiv setup https://www.finalfantasyxiv.com/playersdownload/na/

3.Uninstall the game through the ff14 setup

4. step1: go into windows settings > step2: go into update & security > step3: go to Windows Security > step4: go into virus and threat protection > step5: go into manage settings under virus & threat protection > step6: turn off real time protection.

5. reinstall ffxiv (When your done don't forget to turn anti virus back on).

[JheinaBae]

Don't remember quite when it started. 5.0 for sure. Always no-error crashes. Running in Dx9. Still crash. Crash faster in Dx11.

[Kewitt]

I will find out when I get him and update this thread but one of the bird EX trails mounts, 100% of the time with just that one mount, I crash about 30-60 seconds after using it I get a Direct X error. I didn't care much because I got 30 other mounts to choose from.
None of the other EX trial bird mounts crash on me.

[Snoogem]

Experiencing same issue as well, I can go for one day with no crashes then suddenly crash 5 times in a row within 30 minutes the next day.
I also experience a variant of the DX11 Error, all animations in game will freeze but I can still chat with other people. Then roughly 20 seconds later I get a DX11 Error.

What I have tried:

• Rollback on every major nvidia driver version (After using DDU)
• Uncap FPS in-game then cap FPS to 60 using RTSS
• Underclocking GPU Core Clock by 100 MHZ
• Reinstall FFXIV from scratch
• SFC /scannow
• Cap FPS in-game to 60 (Fullscreen), disable G-SYNC, set Refresh Rate to 60
• Use NVIDIA Control Panel to set GPU to Debug Mode to undo all factory OC

What I am trying now:

• Disable all forms of overlays + anything attaching onto the rendering pipeline
• Currently updated to latest NVIDIA driver 446.14
• Aggressive GPU Underclocking
• Switching to DX9 Client

What I haven't tried:

• Delete profile settings and redo my entire UI
• Update Motherboard BIOS
• Reinstall Windows

Success Condition: Not experiencing DX11 Error for 1 Week
Switching to DX9 client seems to have "fixed" it. The game is absurdly sensitive to any form of overlays like discord streams. I don't crash if I start the stream from character select menu.

[yotsuffy]

This issue? First time, and only time, it happened.

No idea what "2020-03-26_19:14" means, it happened 2020.05.24_17:56.

Most recent NVidia driver.
Non-OC CPU: AMD Ryzen 3 2200G
Non-OC GPU: EVGA RTX 2060
"display limit - characters and objects" at minimum.
1080p, all other graphic settings at "maximum".

[Koroem]

I use a 144hz Gsync monitor and globally cap my system fps at 141fps for all games.

Before 5.0 I would get random DX11 crashes from time to time. Rare, but they did happen. When 5.0 launched I got daily DX11 crashes. They removed that terrible broken 90fps cap at some point and the crashes got worse.

I then used RTSS to limit my game (FFXIV only) to 90fps, but left the frame rate setting in game at 144hz (Refresh Rate 1/1).

I have not had a single DX11 crash in months. I can't say it works for everyone, but cap the engine (properly), something isn't right.

[reallyfunnyname]

Was more or less crash free for the least 2-3 months, but they came back today with the Terms of Service update. Cant finish a single 24 man or go to half the areas without it crashing.

[EnigmaticDodo]

Can yall please fix your shi-. This is getting out of hand and going into the unplayable realm.

[Maeka]

No idea what "2020-03-26_19:14" means, it happened 2020.05.24_17:56.

That's the game version.

Anyhow, I switched to dx9.0c and..... no crashes yet.

It's been a week+ I think, and I've done quite a few several hour stints and have yet had any problems with crashing.

Sadly, a few features are not available in dx9 (like large inventory without tabs), but meh. That's better than crashes.

[Rizon]

Crashes started coming back for me with the latest updates to Windows. An update for my Nvidia also occurred. This still only occurs with the game. No problems with any of my other programs. Until someone from SE can convince me otherwise I firmly believe this is an incompatibility between Windows/DirectX and the game. Whether it's Microsoft's problem or SEs I cannot say. But they need to find out and take the appropriate steps.