[POSSIBLE FIX] for Fatal DirectX Error 11000002 on Nvidia cards

[Velhart]

Alright good news everyone. I have been working with a representative at Nvidia who has been working with folks who have been communicating with me attempting to find the issue. Through the benchmark, the group at Nvidia were able to create the error and now are investigating exactly what is causing it and fix the issue. I will keep posted in here the progress that happens.

Response By Email (Josh) (07/18/2017 04:11 PM)
Thanks ???,

Looks like we got a crash on the benchmark app for this game, so I think we are making progress on this now.

Josh
NVCC

[Xeon]

Alright good news everyone. I have been working with a representative at Nvidia who has been working with folks who have been communicating with me attempting to find the issue. Through the benchmark, the group at Nvidia were able to create the error and now are investigating exactly what is causing it and fix the issue. I will keep posted in here the progress that happens.

Right on. Thats awesome news. I wish that the users with AMD cards could get them involved, but NVIDIA traditionally has had much better customer service.

[GyroChulainn]

Best news i've had all week. Hopefully this gets fixed soon.

[Zoser]

Alright good news everyone. I have been working with a representative at Nvidia who has been working with folks who have been communicating with me attempting to find the issue. Through the benchmark, the group at Nvidia were able to create the error and now are investigating exactly what is causing it and fix the issue. I will keep posted in here the progress that happens.

You unquestionably made my day just now, Vel!
Here's hoping that Nvidia will solve this soon ...

Zos

[Kadrom]

Alright good news everyone. I have been working with a representative at Nvidia who has been working with folks who have been communicating with me attempting to find the issue. Through the benchmark, the group at Nvidia were able to create the error and now are investigating exactly what is causing it and fix the issue. I will keep posted in here the progress that happens.

Awesome news. Please keep us posted. I've been dealing with this bug since late last year and every time any thread gets long enough it just gets archived as "resolved." Would love to finally be able to play this game without holding my breath again.

[FromTheInternetz]

Sorry but drivers do not control the voltage or the clock speed of the card. Speed and voltage settings are manufacturor specific on their O/C models and these features are controlled and can be edited directly through the BIOS. Sure, you can control clock speed and voltages with MSI afterburner, but the base values are set in the BIOS code and are not affected by drivers outside of throttling.

Slapping your GPU to use 100% vcore at all times can cause hardware failures. I did this on an AMD card with no overclocking. Just a lift to 100% voltage and it blew up one of the VRM chips on the card. It can also essentially "break your fans" too as they're running harder than intended. The only cards currently available that are built to run at 100% vcore and fan operation are the newly released mining cards, using lower voltage, fluid bearing fans that can sustain 100% speed 24/7.

If you suffer damage by applying 100% voltage at all times in afterburner, and it malfunctions, and you do not have a mining specific card, you have essentially voided your warranty. The mining cards share the same core and memory as the gaming cards, and in part, were brought to market because miners are blowing up their standard version GPUs due to running them at 100% voltage and higher fan speeds, and the obvious market shortage aswell.

If you need to "up your voltage" in this way to run a game, especialy this game, which doesn't seem to utilize over 40% of GPU power on a modern GPU, you need to be in contact of the manufacturer of your card if you've got things like adequate case cooling.

A safer alternative would to just up your fan speed in afterburner, or to set up a tighter speed curve. This should help you if running at 100% voltage does. If you need more voltage to run at stock or factory overclocked speed, usually this is because of a heat issue, because greater temperature usually equates into more needed voltage to run at said speed.

You also don't have to have a 10 series card to adjust your voltage. This is also manufacturer specific, and the higher tier manufacturers like ASUS, eVGA, ect have put in hardware that allowed the voltages to be tweaked on many older cards.

Hey, thank you for the input. I know that the drivers aren't able to change the clock or voltage but my assumption was that the issue may be with throttling. E.g., if the driver throttles the card, both frequency and voltage, but doesn't do so at the exact same time, wouldn't that likely cause problems (when the card runs at a frequency slightly too high for the voltage, even if only for a split second – see typical crashes when overclocking a CPU)?

I don't think that running the card at 100% voltage at all times is likely to cause any damage if the temperature stays at appropriate levels. If you were able to blow one of the VRMs by running around 30mV more than normal then I'd assume faulty hardware. The Vcore is hardcapped anyway so it should be safe. See https://www.reddit.com/r/nvidia/comm..._core_voltage/ for more information.

What kind of GPU only goes to 40% power when running this game? Maybe if you are not playing on max settings at a resolution higher than 1080p, but I can assure you that the load goes to 90%+ regularly when it's pushing 140+ FPS on 1440p. And not only on my system. The game is very much GPU-bound. Also, setting a tighter fan speed curve doesn't help at all (yes, I also tried that). My card stays at 60° Celsius at all times under full load, even with the stock settings. It's not a heat issue whatsoever (for me, at least).

You are of course right that you don't need a 10 series card to adjust the voltage. However, you need the current Beta of Afterburner to adjust the voltage for 10 series cards – it doesn't work with older versions of Afterburner. I'm sorry if that came across the wrong way.

I can only say that I've had no further crashes after increasing the voltage. Might not work for everyone and might be hardware-specific, but after trying almost everything else and having no problems anywhere else (whether in any other game or benchmark – and I usually bench my hardware for 16+ hours straight) I was very happy to finally find a fix. :P

Oh and I fully agree with you that most of the issues are with the game, especially since Nvidia was able to reproduce them (I assume we can disregard any hardware issues in their test systems). But it's not DX11 specific as people have been reporting crashes running DX9 as well.

One last thing: where did you see any systems with a $70 CPU and a $500 GPU (aside from the fact that the 1080 Ti is more like $700+)? The lowest I've seen is a 4770k. And cards like a 4770k or 4790k (like I have myself) are still regarded as high-end when it comes to gaming, especially if they are overclocked. You currently pay about the same for a 4790k as a 7700k and it's not much slower than that. And aside from Intel's new (and hilarious) Skylake-X stuff there isn't much that is faster in gaming than a 7700k. Hardware age doesn't equal speed, especially when it comes to CPUs where they have been unable to develop meaningful upgrades for years.

EDIT: I just reread my post and realized that it might come across as slightly arrogant. Please be assured that this was not my intention, I really appreciate your input here. I just wanted to answer to offer my point of view because I think any discussion on this issue is useful, especially if any Nvidia tech comes across this topic when they are looking for a solution.

Alright good news everyone. I have been working with a representative at Nvidia who has been working with folks who have been communicating with me attempting to find the issue. Through the benchmark, the group at Nvidia were able to create the error and now are investigating exactly what is causing it and fix the issue. I will keep posted in here the progress that happens.

Awesome news!

[GyroChulainn]

I really hope Nvidea does something soon because my game has just reached a point where it's no longer playable. I get an "unexpected error" crash every minute or so when in an instance.

[DominicStone]

I did not experience any crashing until the 4.0.5 Omega raid patch. I went to 70, did Primals, Roulettes, etc with no trouble...then the woes began.

I tried the up-voltage but crashes were just a little less frequent.

What I've done is this:
1. Use DDU to disable Windows driver updates and totally remove Nvidia software.
2. Install the latest Nvidia driver and Physx only (no HD audio, geforce experience, etc).

I crash way less often, but I still do about every 3 hours. I've tried that in combination with the up-voltage, removing overclock and every other thing. No other game I play crashes like this so I'm going to say that it's either the FFXIV client, the drivers or (more likely) the combination of the two. I've rolled back to various other drivers pre-Stormblood with the same result. So, my money is on some code in the client itself that is the culprit.

The unpredictable and non-reproducible nature of this error makes me think that it's some sort of memory leak. I'm too timid to run a process monitor or debugger against the executable as that is definitely against the ToS, but if Nvidia is aware of it then that's probably what they are doing to trace the full nature of the error anyways.

We can try whatever voodoo combination of fixes we might dream up but until the code is fixed we gotta live with this crashfest :/

edit: words

[Zoser]

Thank you for the idea of removing the HD audio. Before doing this, I crashed after less than a minute, now I could play for a couple of hours.
Anyway, here's hoping for a fix soon, it is rather irritating having to worry about crashing out all the time ... O.o

[Velhart]

I have not received an update from them yet. I e-mailed them and asked how progress is proceeding on this.