Fatal Direct X error for almost an entire year

[Adavon]

Has anyone tried turning off both Windows Game Mode and Game Bar? Used to crash for me randomly untill i turned both those off, lowered my FPS to 60 and set to Fullscreen.

Had tried all those you recommended, and was still getting crashes

[Adavon]

Most recent attempt to fix this issue so far has been a motherboard change, I went from a X570 AORUS PRO WIFI (rev. 1.0) to an ASUS ROG Strix B550-F Gaming (WiFi)
kept everything else the same in my build, and has had the most stable performance so far
Ryzen 3600X / 32GB RAM (4x8GB HyperX FURY) / RTX3060 With the same Windows install on my SSD

I don't know what the the 2 boards have that make them run differently with FFXIV, one theory I have is how the ram trace topology is on the 2 boards, but I do not have the ability to test to confirm this at all

Edit: After changing out the motherboard was able to play on Tuesday (Sept. 14) for up to 8 hours with only a 90k disconnect error, that I am able to account for a possible router that needs to be replaced

[Pribo]

I've been also suffering from the directx error for 5-6 months now, but unlike for most other people I always get it as I launch the game, making it literally impossible to play.

I've tried clean installing drivers, I've tried running it both borderless windowed and fullscreen, reinstalled windows, underclocked/overclocked and tried many other things that are posted on different forums, but nothing works. It's extremely annoying and disappointing at this point that the issue has been around for such a long time and seemingly there is no clear solution to it and everyone is just guessing what might work. I love the game so much, but it's starting to get very exhausting that I have to spend so much time with trying to fix this...

[AvelosFloof]

I have been playing this game since the start of 2016. Love it of course. But started having this very same issue pretty much the entire past year. Sometimes it's on and off, other times it'll do it a few times in an hour and I just quit the game. I have tried everything under the sun in OPs opening post same as they have, and nothing works. I have search high and low for solutions and seen threads as far back as patch 3.5 where this persists and I bet it's been going on before that also. I have switched my PC hardware as well. I don't recall it happening on my oldest system which packed an i7 4790K, Rog Maximus Z87, 32GB G.Skill Trident X 2400mhz, Samsung 850 Evo raid 0 and two GTX 1080s in SLI. Ran great on that system.
Later upgraded to intel i9 9900K, Gigabyte Aorus Xtreme Z390, 32 GB G.Skill Trident Z/R 4000 mhz, Samsung 970 Evo Plus, and the same GTX 1080s. Didn't happen with the 1080s but I picked up two preowned 1080 TIs and it happened from time to time.
I don't think it's hardware related because I've read about it happening plenty with AMD users. I upgraded to an RTX 3090 in April and it didn't do it at all for a month and a half but immediately started happening again when I did a fresh install of Windows to try and sort out something else. It happened infrequently then.
Now just this past week, I have changed my system to Ryzen 9 5950X, Gigabyte Aorus X570 Xtreme, and Samsung 980 Pro and same RTX 3090, same ram, it's happened twice in the past 20 minutes as of writing this.
This ongoing issue isn't the reason I upgraded my PC as much as I have, but I was low-key hoping that it would address the issue on the side. Nope. I run a pretty light version of windows 10 also and it's been new as of this weekend.

I know of someone else who was having this issue briefly and it was happening so much to the point the game was unplayable. When diagnosing the issue, they found that the system DRAM voltage was too high so they tuned it down a little bit. It may or may not have fixed it entirely but as far as I am aware, it has not happened since. Something I'm looking into as well with my own Ryzen system.

It's frustrating to say the least and I've since resolved to hoping that it finally gets addressed with the release of 6.0. Probably not.

[Adavon]

Most recent attempt to fix this issue so far has been a motherboard change, I went from a X570 AORUS PRO WIFI (rev. 1.0) to an ASUS ROG Strix B550-F Gaming (WiFi)
kept everything else the same in my build, and has had the most stable performance so far
Ryzen 3600X / 32GB RAM (4x8GB HyperX FURY) / RTX3060 With the same Windows install on my SSD

I don't know what the the 2 boards have that make them run differently with FFXIV, one theory I have is how the ram trace topology is on the 2 boards, but I do not have the ability to test to confirm this at all

Edit: After changing out the motherboard was able to play on Tuesday (Sept. 14) for up to 8 hours with only a 90k disconnect error, that I am able to account for a possible router that needs to be replaced

as of my last post I've not had a crash since changing out the motherboard, as for me it seems to have been an incompatibility with the game and that board, or a setting that board had that FF did not play well with
it's sad that it's the players that have to respond so much to each other to get anywhere with diagnosing a problem, or just so much self diagnosing
with only ever getting one or two responses from a mod, that never seem to get anywhere, due to being the most basic of troubleshooting tips or a copy paste response about supplying a system report

[Fufusi]

Haven't had the issue since my last post. Seems this game is very sensitive to system stability. Even though other games have no issues and all stress tests succeeded, FF14 simply doesn't like my GPU overclock it seems.

[Brandter]

It's always the same response, it's always been the same response looking years back with this issue. Most of the time it seems like AMD is the issue, I've seen a few players with intel CPUs:s but mainly it seems like an issue with AMD. I've also tried everything, last time I reinstalled my OS and ONLY installed steam and FF14 and it still crashed. It's hardware related, windows warn for hardware error, it's not because of broken parts but some compatibility issue with certain hardware, and as long as Square doesn't actually let the devs look at this issue it will never be fixed, forum mods respond with at most 2 responses and then they don't answer anymore. This game works better with old hardware and clearly is a lot more stable with Intel.

[Korrawito]

To be honest I've tried every those moderators always post by same suggestion on this forum it change nothing, it still crash. this is my first subscription service game I ever play sure I need something difference from F2P game, more responsibility from dev for bug or crash fixing as worth as I've paid.

I would unsub until endwalker release and I hope dev could fix something about it.

[Brandter]

Don't know if this works for anyone else, it's been working for me for the past days.

I changed the CPU affinity for FFXIV. It might be worth testing.

For me, I set Priority to High and Affinity to only six cores.

For people who don't know how you do this.

1: Start the game normally.
2: Open task manager, go to details and look for FFXIV_DX11.
3: Right-click and change the priority to High and set affinity to 4-6 cores, or rather 4-6 threads. For me, I chose CPU 10 through 15.

The problem is that you have to do this every time you start the game, I made a script that does this for me but you can test it manually and see if it works for you.

I can help you make a script if this works for you, my is a powershell script that looks like this.

Get-Process ffxiv_dx11 | ForEach-Object {
$_.ProcessorAffinity=64512
$_.PriorityClass='High'
}

Save it as a .ps1 file and you can right click it and run with powershell.

What you have to figure out is the correct number for the Affinity, you can do this by following the first steps of the guide, open powershell and run...

"get-process ffxiv_dx11 | select ProcessorAffinity"

And you will get the correct number for your script file.

Also, if you have problems running the script you might have to start PowerShell as admin and change the execution policy by running the command.

"Set-ExecutionPolicy Unrestricted"

Hope it works for other people as well.

Still, THIS IS A WORKAROUND, SQUARE! This is not a solution!