Fatal DirectX Error 11000002

[Xerek]

Update: I still have yet to crash running 355.98. I've run multiple dungeons, Void Ark, roleplayed in Ul'dah, in personal housing...all ran perfectly fine.

So, that leads to a few thoughts. For Nvidia this seems to be a driver issue, but this error occurs on AMD as well. I'm wondering if the issue is with FF XIV. I'm wondering if FF XIV is making a DirectX video call that more current drivers don't like. If AMD and NVidia made some kind of universal change, or if there was a change to DirectX in how it interacts with the drivers. This still might be something SE needs to fix.

For Nvidia, sadly I skipped several driver revisions, and one of them started this error. So, we're just going to have to test them and see where it breaks.

361.43: *DirectX Error*
359.06: *DirectX Error*
359.00: ???
358.91: ???
358.87: ???
358.50: ???
355.98: Works!

There is obviously an issue here, and since it spans NVidia and AMD, I hope SE will take a look at it. Hope this at least helps.

[Xerek]

Oh, and here is a screencap of one of the crashes I got way back when this started...

[outburstt]

Personally, I'd like to see SE respond to this thread to see if some of us can gather some sort of logs for them to try and resolve this issue.

[Monsalvato]

Having the same issues with 361.43 on Windows 10 64bit with a GeForce 670.
Gonna try with 355.98 now and see what happens.

Have you guys tried to open a similar thread on the nvidia forums? I remember in the past a similar issue plagued FFXI, SE never gave us an official reply but Nvidia did (even though it took them quite a long time to do so!) and it turned out it was an issue with their drivers an they finally fixed. Took them ages but they did, even if FFXI back then was already a very old game.
So yeah, if someone has experience with this things, I warmly suggest to open a similar thread on Nvidia forums as well.

[HakaseNyan]

For Nvidia, sadly I skipped several driver revisions, and one of them started this error. So, we're just going to have to test them and see where it breaks.

361.43: *DirectX Error*
359.06: *DirectX Error*
359.00: ???
358.91: ???
358.87: ???
358.50: ???
355.98: Works!

358.87: *DirectX Error* - Win10_64
358.50: *DirectX Error* - Win10_64
355.98: *DirectX Error* - Win10_64

I think the 358.50 lasted the longest for me. I got an error with 355.98 within ten minutes.

[Monsalvato]

Gonna try with 355.98 now and see what happens.

Over 1 hour of gameplay and no crash with 355.98 in DX11 mode.

[Xerek]

Still no crash with 355.98. Going to finish up my weeklies then try 359.00. Given revision numbers and past results, I have a bad feeling 355.98 might be the last stable one. Once I finish testing all the drivers, I'll put a post up on the NVidia forums. I want to be able to tell them exactly where things went wrong.

@HakaseNyan, when you're trying the other drivers, are you performing a clean install each time? I'm surprised 355.98 crashed on you.

[Monsalvato]

Over 12 hours of gameplay and no crash on Windows 10 64 with 355.98 using DX11.
Kinda makes you wonder why this issue happens only with DX11 and not DX9 though, and why it only affects some systems and not all of them. (I could name a long list of people with up-to-date drivers who are experiencing no issues with DX11 using an nVidia card)

[RPGKing4]

(Original) Set up - Pre-Error
ASRock 870 EXTREME3 Motherboard
AMD Athlon II X4 640 Propus Quad-Core 3.0 GHz Socket AM3
Nvidia GForce 9800 GTX+
2x 2GB DDR3 1333
Windows 10

Been playing for about a month now without issues. Back on Thursday, 12/31/15, I got a new gpu. It is a used AMD R9 200 / HD 7900 Series. I played close to 30 hours over the weekend without issues.

Fast forward to today. I get a new stick of ram in, taking out my old ones. It is an 8GB DDR3 1600 stick. Install it without issues. Everything seems to run fine. I know my Motherboard won't run it 1600 by default, so i OC'd it to 1600 from 1333. Load FF14 and it started giving me this error every 5 mins or so. (I'm running on D11 Max settings, btw.)

I went back and changed the RAM speed back to 1333 and the errors went away. Don't know if this helps anyone, but if your RAM is DDR3, 1600, try changing it to 1333 and see if that works? Or if your RAM is overclocked, try without?

Figured I'd post just to see if my solution helps anyone. Hope Square or AMD can fix the issues.

[HakaseNyan]

Still no crash with 355.98. Going to finish up my weeklies then try 359.00. Given revision numbers and past results, I have a bad feeling 355.98 might be the last stable one. Once I finish testing all the drivers, I'll put a post up on the NVidia forums. I want to be able to tell them exactly where things went wrong.

@HakaseNyan, when you're trying the other drivers, are you performing a clean install each time? I'm surprised 355.98 crashed on you.

Yes, I always do clean install of drivers and then I reboot just to be safe. All of the drivers posted lead to crashes for me on win10_64. Interestingly enough, the most recent drivers will actually cause the entire system to hang until finally crashing the game with the error pop-up. 358.50 and earlier will freeze the system for a very short moment and then the error pops.