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

Add me to this list. I started receiving DirectX Fatal Error 110000002 today. Similar to Raiya I can only get into the game if I force default values.

se just needs to fix there end its sure not my end
they prolly shouldnt even added the patch i tested this on 2 pc's running different hardware and nothing i do for both fixes the problem

hmm really odd pulled out my hp laptop with a intel cpu and hour in no crash yet my other ones i was using had amd 2nd gen and a 3rd gen

Ok, I couldn't see the error when my game would crash on fullscreen. I switched to borderless windowed though and now I can see it is in fact the directx 110000002 error. I had never gotten it before patch 5.3, now I'm getting it multiple times a day.

Started getting it yesterday specifically when around the Quicksand so my initial thought is my issue is related to player density somehow. But it does it even on other worlds and other capitals so I doubt that.

Tried changing border type, turned all my video options to their lowest, deleted (actually just moved to a different folder) my My Documents files, disabled Game Mode, Steam Overlay and Discord Overlay. So far nothing seems to help except getting lucky, and even then it only seems to work for a few minutes.

Weirdly enough these crashes don't generate any entries in my Event Viewer so I can't even trace the cause. Only thing I have to go on is it's an error in ffxiv_dx11.exe, KERNEL32.DLL, and ntdll.dll

Having this issue in all of sudden lately. Not sure why but it just happened.

https://cdn.discordapp.com/attachmen...9_02_54_PM.png

Quote:

---

Originally Posted by SynValdyn

I had these crashes nearly everyday, sometimes several times a day, for months now and finally seemed to have fixed it (*fingerscrossed*). I'd tried a ton of different things and nothing was working but the last thing I did where it finally stopped crashing was I went into my BIOS. I'd had it set to automatically detect my memory frequency and changed that to put the actual frequency instead of auto. While I was in there I also saw that I had a setting enabled that allowed my CPU to auto overclock and I disabled that (I didn't even realize I had that sort of setting). I did all of that two weeks ago and haven't had a single crash since then. I'm not sure which one fixed the issue but one of them seems to have fixed it as before this the longest I went without a crash was a day. Hopefully that helps someone else!

---

Started getting the crashes again after the 5.3 patch, can confirm this worked for me though I just disabled auto CPU overclocking in my BIOS settings and didn't fiddle with memory. Haven't crashed a single time since.

I had the same issue however... I don't understand how I apparently fixed it?

My game would do the same error stuff you all are experiencing but I had the game installed on a Samsung T7 external SSD. Moving it to either the internal HDD I have or internal SSD I have apparently made it not crash anymore. Makes NO sense. Maybe someone else can explain. Should note that I have only tested it out for an hour. But before, I couldn't go 15 minutes without a crash.

Quote:

---

Originally Posted by SPHENiO

Having this issue in all of sudden lately. Not sure why but it just happened.

https://cdn.discordapp.com/attachmen...9_02_54_PM.png

---

Add me to the list with this same issue.

Well I was able to get the error count cut down to two by updating my Visual C++ install.

Then I made the mistake of switching jobs to Machinist and now I can't even reach character select without getting 5 error boxes.