FFXIV DirectX Error 11000002

[Rhaervis]

Good afternoon and thank you for posting on the Final Fantasy XIV Technical Support Forums.

Unfortunately, we would be unable to state which hardware could be causing the issue nor could we recommend where to find out such information.

Thank you for posting on the Final Fantasy XIV Technical Support Forums.

[Packetdancer]

I just tried underclocking it again and it didn’t make any difference, it’s just crashed about 5 times in half an hour. It’s running at 65-75 degrees Celsius which from my limited knowledge I think is ok? I am totally out of ideas. Thanks for trying to help me.

Yeah, that should be absolutely fine; I'd say you can eliminate the graphics card as the cause. What I'd probably resort to next would be examining the system events log in painstaking detail in the moments after a crash (before too much has happened and you've lost the timestamp) and context.

Unfortunately, at this point I'm running low on other ideas, and troubleshooting remotely is difficult.

[JessBobbles]

Hi, sorry been a bit busy the last few days.

This is really strange. When Square said it was a hardware problem I raised a ticket with NVIDIA. They gave me a load of different tests and stuff to try but in the end said the card must be on its way out. I’d been reporting to them the errors out of the Event Log.

After this I though ‘oh well, I’ve tried all I can’ and ordered a new computer.

However....after 5.2 hit I haven’t had a single crash. I haven’t changed anything on the computer, Monday night crash crash crash, Tuesday morning fine.

@Support - was there something in the patch that would have fixed this? I don’t know whether to cancel the new computer order.

[Travithymia]

@Support - was there something in the patch that would have fixed this? I don’t know whether to cancel the new computer order.

From the 5.2 patch notes in the Resolved Issues section:

An issue wherein the game could not be run in DirectX® 11 mode with certain combinations of gamepads and drivers.

I reinstalled the entire game when the patch launched and have had less crashes too. However I still got a DX11 crash when trying to load into the Doman Enclave which caused me to replace the ex2 folder (which has all the Stormblood expansion data in it) with the ex2 folder that I backed up before I reinstalled the game and have not had a crash since then.

[Mautroniic]

+1 Same problem here after update 5.2 patch https://imgur.com/p8x3NuL

[Packetdancer]

@Support - was there something in the patch that would have fixed this? I don’t know whether to cancel the new computer order.

They fixed a weird driver conflict, yeah; it's in the patch notes.

I'd say whether to cancel the order or keep it going would depend on what Nvidia had you do and what those tests said. If they said "the card's on the way out because <results of various tests>", then I'd say the card's on the way out anyway—regardless of if the 5.2 fix temporarily addressed your problem—and you probably should keep the order open. If Nvidia was more like, "well, we're at a loss, can't see anything wrong; the card might just be on the way out." as sort of a shrug-and-fallback then maybe you're safe to cancel it.

[Meloncat]

Hi, sorry been a bit busy the last few days.

This is really strange. When Square said it was a hardware problem I raised a ticket with NVIDIA. They gave me a load of different tests and stuff to try but in the end said the card must be on its way out. I’d been reporting to them the errors out of the Event Log.

After this I though ‘oh well, I’ve tried all I can’ and ordered a new computer.

However....after 5.2 hit I haven’t had a single crash. I haven’t changed anything on the computer, Monday night crash crash crash, Tuesday morning fine.

@Support - was there something in the patch that would have fixed this? I don’t know whether to cancel the new computer order.

Unfortunately I am experiencing the reverse, not a single problem with XIV until 5.2 and now I am experiencing the direct X error incessantly. Most curious is the fact that if I do not click okay on the error, the game functions fine. Once I do, the game crashes. I've reinstalled it and the issue persisted.

I am going to open my own support ticket but I am worried they may have created a new error in fixing the older one.

[Travithymia]

Unfortunately I am experiencing the reverse, not a single problem with XIV until 5.2 and now I am experiencing the direct X error incessantly. Most curious is the fact that if I do not click okay on the error, the game functions fine. Once I do, the game crashes. I've reinstalled it and the issue persisted.

I am going to open my own support ticket but I am worried they may have created a new error in fixing the older one.

I wrote my reply before playing through the 5.2 MSQ and new Eden raids in which a lot of cutscenes caused crashes halfway through. Luckily I'm priveleged enough to also own the PS4 version so I've been able to use that to watch them and progress. The rest of my game is fine now but yeah I've still been having problems just like you and OP so the issue certainly isn't fixed.

In the past as long as the crashes haven't locked me into a loading screen I've been able to move around areas too once after the error message pops up but eventually the BGM stops and models/characters stop loading in. Maybe some smaller asset in your game is broken if that doesn't happen to you.

[Brightmore]

I began to have those errors again yesterday. Mining the internet I've found that the last version for win10 (directx 12) is bugging for lots of gamers. Unfortunately, there's nothing way to reverse it to 11. :'(

[Lucas_Angelini]

I began to have those errors again yesterday. Mining the internet I've found that the last version for win10 (directx 12) is bugging for lots of gamers. Unfortunately, there's nothing way to reverse it to 11. :'(

Perhaps it's time they need to work on a option to switch to DirectX 12 so we don't get crashes at DirectX 11 and lags at DirectX 9. The DirectX Error 11000002 needs to be fixed once and for all.