DX error 11000002

[Dynratygus]

Good afternoon and thank you for the reply.

I apologize for the delay in our response to your concern. Have you tried changing the size of the window to borderless fullscreen or fullscreen or windowed mode? Sometimes changing the window size can help with crashing. Have you tried disabling any of the monitors or doing a cleanboot? Open the task manager and select the 'Start up' Tab. Disable everything here and restart the PC.

Hope to see you online!

[LYagami]

So ive bit the bullet and completely redownloaded and installed the game from scratch........STILL PERSISTS
Ive literally reinstalled windows, all drivers, all programs and still this bloody problem persists. What else can it be??

[LYagami]

@Dynratygus
I have tried windowed, fullscreen borderless windowed (which is what i always play on) and fullscreen and crashes in all 3. I have done clean boots and still no change. Ive tried it on the other monitor and no change, the monitor i play on (primary) is only 6 months and is a 40" curved 4k monitor if it helps.
Im at my wits end here surely its going to be something small and silly but at this stage what HAVENT i tried? list is getting awfully small by now

[Madigari]

I just wanted to add in here that I'm having this exact same problem. I was able to play flawlessly with DirectX 11 and maximum settings for two hours before the most recent maintenance, no error 11000002 or anything. But once I tried it the next day, it started giving me this error in about 5-10 minutes after starting the game, and even forces my PC to reset at times. Tried it in DirectX 9, textures and models in game start freaking out and twitching green before the game shuts down, or my PC.

I've even done a full factory reset of my PC, including reinstalling the game fresh, and it's still giving me the same issue. Even attempted compatibility mode as suggested before.

[Einmimiria]

Thank you for the update LYagami.

I don't know all of the things you tried, so I apologize if you've tried some of the things I'm going to suggest.

First, when you updated your graphics card drivers, did you do a clean install of them? This is an option if you install them manually.

Try deleting the files in the 'My Documents' folder (My Documents > My Games > Final Fantasy XIV), then restarting the game. This is not deleted when you do a standard reinstall.

Try setting compatibility mode to Windows 7. Right-click on the ffxivboot.exe file and select ‘Properties.’ Then select the ‘Compatibility’ tab and choose Windows 7.

Are you overclocking any part of your PC?

You mentioned that you've experienced crashing in other games. Did this start happening around the same time as the crashing in XIV? Do they crash in a similar way?

We hope we can be of assistance in helping you enjoy the exciting world of Final Fantasy XIV!

[LYagami]

@Einmimiria
Yep i did clean installs of all my drivers. i WAS overclocking my PC but have since reverted back to factory however no changes. I had a stable clock on the CPU @ 5ghz with the GPU still being at standard factory OC, ram was also only bumped to 2666. Ive ran a few diagnostics over all the hardware to be safe and no problems have arisen.
I have however tinkered with a few settings in the nvidia panel and i may have found a solution, i havent crashed for a few hours so far but ill wait a few solid days before i call it...
For those who also have this same problem i have a few suggestions: disable ALL overlays. Exit completely out of steam, discord etc any third party program that stays open in the background even if not 'open'. I saw a lot of other people say it fixed problems for them while i was browsing the many other forum threads.
With regards to nvidia settings, open manage 3d settings and click program settings. Add in FF14 here if it isnt auto added in and for antialiasing mode select application controlled. I suspect that possibly FF14 and nvidia were having an argument over who chooses which antialiasing mode but now im forcing nvidia to let FF14 decide.
Ill post back here if i do encounter this still but its looking like im fixed. Hope this info helps others in the same boat.

[Ceilidh]

Alright, so I did a bunch (and I do mean A BUNCH) of tests, and it seems like the issue is with Chrome (or rather, part of Chromium).

Here's the big issue: Discord and Streamlabs also use Chromium, and WILL crash your computer if used while playing FFXIV, which also might indicate that the issue isn't with a Chrome Plug-in, but with a segment of the Chromium code itself.

Totally shutting down Chrome by right clicking on its icon in bottom right taskbar to close the process apparently fix the issue for me, but it means I can't run Streamlabs either.
Also, asking around to friend, I also have friend using Chrome who don't have that issue, so my guess is that it's not "just" Chrome, but chrome with another factor that I haven't been able to nail down.

Also salient: hardware acceleration isn't turned on in my Chrome browser.

I also have to run tests to see if the issue happens with Brave (which also uses Chromium), and other streaming software.

EDIT: a bit more details: I've been able to reduce the occurences of crash by running FFXIV in borderless fullscreen, and Windows 7 Compatibility mode.
It's not 100% perfect, and I still get a lot of issues if I run a video or a streaming app on my second screen, but at least I went from a number of crashes a day to one every other week.

[LYagami]

Spoke too soon unfortunately, has happened a couple of times now today. Is a little better if anything but i cant rule that out as a coincedance either.
Bugger

[LYagami]

Also @Einmimiria the only other game to crash was postal2, which did not behave in the same way. I only mentioned it on the off chance that it was related, but the more i think about it the less likely it is to be related in the way they happened and how they happened

[LYagami]

So last night i went probably 4-5 hours with only 1 crash, now i just logged in after booting up and straight away after 15 seconds i get a crash. Back to a broad range it seems. 'Escalated' ticket still sitting with SE with no reply for days now. ....