Fatal Direct X error for almost an entire year

[Adavon]

Turned Game Mode Off and lasted about 10 minutes before getting the error:

Unexpected error has occurred
ffxiv_dx11.exe+14A8EB3
ffxiv_dx11.exe+14A6B0F
ffxiv_dx11.exe+1497960
ffxiv_dx11.exe+1494247
ffxiv_dx11.exe+1498BC8
ffxiv_dx11.exe+14D533D
ffxiv_dx11.exe+14D7BF2
ffxiv_dx11.exe+14D7B40

the game visuals froze, error message came up on top of the game window, and audio still played
was in Limsa, at the market board with crafters nearby, and could still hear the sound effects of them crafting things, and the footsteps of other players walking by

[Arrhin]

Everyone make sure their .Net Framework and C++ Runtime are the latest versions. These are typically done through Windows Update but can be missed or corrupted. Googling some of the errors listed some of them relate to one or the other of those things. I also do recall an instance where I moved my client et al over to a new laptop and it would not run, citing a C++ runtime error. Just a thought, if no one has tried yet!

[Adavon]

went through and installed (was missing 2010 runtime) or repaired (reinstalled) each C++ Runtime (2008, 2012, 2013, 2015-2019)

crashed to desktop twice, both times with no error message

and once with:
Unexpected error has occurred
???+7FF63D088889
ffxiv_dx11.exe+14D533D
ffxiv_dx11.exe+14D7BF2
ffxiv_dx11.exe+14D7B40
ffxiv_dx11.exe+14D7A96
KERNEL32.DLL+17034
ntdll.dll+52651

These errors all in a matter of less then an hour, and were in order: no error message, no error message, with message

edit: the first 2 errors were inside the Carpenter's Guild building, and third error with message was in the Leatherworker's Guild Building

[Arrhin]

went through and installed (was missing 2010 runtime) or repaired (reinstalled) each C++ Runtime (2008, 2012, 2013, 2015-2019)

crashed to desktop twice, both times with no error message

and once with:
Unexpected error has occurred
???+7FF63D088889
ffxiv_dx11.exe+14D533D
ffxiv_dx11.exe+14D7BF2
ffxiv_dx11.exe+14D7B40
ffxiv_dx11.exe+14D7A96
KERNEL32.DLL+17034
ntdll.dll+52651

These errors all in a matter of less then an hour, and were in order: no error message, no error message, with message

edit: the first 2 errors were inside the Carpenter's Guild building, and third error with message was in the Leatherworker's Guild Building

Sorry to hear that. Was hoping something would help. I read some CTD's are caused by corrupt textures when I was researching my crashes. But you already reinstalled so I'm not sure anymore. If I see anything else I'll post it. All the best luck

[Adavon]

still not able to play, it's been months of constant crashes, two responses from a mod that was of no help and has yet to check back or leave any kind of update

this is a known issue, and has been for a long time

my 8 year old computer can play without issue and yet my new computer is not, due to constant crashing

[Larirawiel]

Do you overclock or something? If so then revert it please. And it can help when you disable the quickstart in Windows. If you have a SSD then the quickstart is basically useless because it does only slightly speed up the boot times. You can disable it with following steps:

1. Start cmd.exe with Administrator priviliges
2. Type following into the command line: powercfg /h off
3. Press Enter
4. Reboot the computer

Cheers

[Kyrushi]

Do you overclock or something? If so then revert it please. And it can help when you disable the quickstart in Windows. If you have a SSD then the quickstart is basically useless because it does only slightly speed up the boot times. You can disable it with following steps:

1. Start cmd.exe with Administrator priviliges
2. Type following into the command line: powercfg /h off
3. Press Enter
4. Reboot the computer

Cheers

I do not overclock no. I tried it at one point and even underclocked since a forum post I read said it helped but neither did the trick.
I followed instructions to turn off quick start the other night and I had no crashes for about 2 days but had a crash last night unfortunately.

[Kyrushi]

Bumping just so the thread doesn't get locked. It's been nearly 2 weeks since support has responded and I even directly responded to them. Why does this happen to nearly every damn post regarding this error? It's ridiculous.

[Adavon]

Bumping just so the thread doesn't get locked. It's been nearly 2 weeks since support has responded and I even directly responded to them. Why does this happen to nearly every damn post regarding this error? It's ridiculous.

I've noticed that as well with support closing threads that never did say the issue was ever resolved,

I will note that I have been able to see some stability after going through and uninstalling a redundant C++ 2008 visual runtime
windows had installed an update a while back without removing an older version, so there was 4 of the C++ 2008 (an older set of 32bit and 64bit, and a newer 32bit and 64bit versions) i uninstalled the 2 that had a lower version number

I did this after I had went through and updated all the other versions or installed any that were missing, I think it was the 64bit version of the 2010 runtime that was missing

That said the stability is only somewhat better as I still have some crashing, just not within 10 minutes of logging into the game like before, I was able to actually get in like 2 hours of playtime before a crash the last 2 days each after work

[Fufusi]

I've been getting "A fatal DirectX error occurred.(11000002)" every now and then since I got a new PC.
Can someone explain how/why the audio enhancements might be causing these issues? I think in my case it's an issue with my overclock because in event viewer there's a bunch of Nvidia-related errors when it happens. But I do use audio enhancements as well so...

It happens so infrequently it's hard to nail down any specific details, but one thing in common is usually it's when I am on a safe zone map for around 10 minutes just chatting. So far it happened in 2 different houses and in Old Gridania.

Edit: Yesterday also happened during an alliance raid, just to make it even harder to pin down the problem.