TLDR: Try setting your GPU core voltage to 100% with Afterburner or another OC tool. Nvidia cards might be unstable under recent drivers when factory overclocked without increasing the voltage appropriately. The same applies to manual overclocking, of course, but there it's kinda obvious – you wouldn't think that the voltage might be too low on a factory OC.
Make sure you are on 4.4 Beta if you are using Afterburner and are on a 10 series card, otherwise you won't be able to change the voltage settings. Also, DO NOT install the RivaTuner Statistics Server when installing Afterburner since that is known to cause issues with game (as do other overlays like the optional Discord overlay).
Hey guys,
I've had crashing issues since I've returned to the game two weeks ago. Four different kinds of crashes actually:
- Fatal DirectX Error 11000002
- "An unexpected error has occured…"
- a Windows crash saying the game has stopped working
- and a single blue screen
I've basically tried everything at this point. Won't go into details, but it involved a lot of reinstalling the game, reinstalling Windows, hardware monitoring etc.
I guess my tinkering had some effect, because I haven't had a Windows crash since then and also no further blue screens since 1 1/2 weeks ago. But the other two errors still remained.
So today, after another 11000002 I looked over my Afterburner statistics (as I always do after a crash, trying to find something that looks wrong) and noticed that the GPU has been hitting the voltage limit all the time. I'm not actually sure if this isn't just normal behaviour anyway on Pascal cards (who boost themselves until they run into a limit), but it gave me the idea to just increase the voltage and see what happens – something I actually hadn't tried before.
Since Nvidia cards have a certain upper limit of voltage that you can't go over, I just went straight to 100% in Afterburner which brought up the voltage to ~1090mV (from around 1060mV) under load. I then started the Stormblood benchmark, set it to maximum settings and ran it in a loop – for seven hours straight now, without a single crash (Update: I let the benchmark running over night, 17 hours without issues). Normally, it would crash after a maximum of 10-15 minutes, sometimes even in the first run.
Two side effects I noticed: One, my card boosts even higher than before (up to 2075MHz (2025MHz before), which is pretty high for a 1080 Ti). Second, it's actually cooler than with lower voltage. I can't really explain it myself, but there are posts on hardware forums describing why too low voltage may actually run the card hotter when it's overclocked.
My guess is that the factory overclock of the GPU is too high for the voltage that is set – ZOTAC even advertises their 1080 Ti Amp Extreme as the fastest out of the box. They either forgot to increase the voltage accordingly or it may be a bug in the newer Nvidia drivers that causes the card to try and go beyond the voltage limit or something.
I've had no problems in other, more demanding games (like Witcher 3) before this change, but that doesn't really mean anything since it might just be the FFXIV engine being very susceptive to errors (even if they are corrected by Windows or the graphics driver instantly, otherwise we'd probably see more blue screens and not just crashes to the desktop).
Since I didn't run the game itself yet, I currently don't know if this also fixes the other remaining crash ("An unexpected error has occured…") for me since I used to get the 11000002 far more often than that one when running the benchmark (it's the other way around in the game, more "An unexpected error has occured…" crashes than 11000002). But my guess is that they are related or even the same with the message of the crash just depending on which part of the game notices the issue first (for the programmers: basically a race condition). I will certainly update this post and let you know in the coming days.
So, if you want, give it a go – just make sure to monitor your GPU temperature after increasing the voltage. Might actually go up a bit for you instead of going down, it's apparently pretty rare that it goes down and indicates that there was quite a lot of undervolting before.
My specs, just as additonal information:
OS: Windows 10 CU (with the latest updates)
CPU: i7-4790k (running on 4.5GHz/1.2V)
GPU: ZOTAC GeForce GTX 1080 Ti AMP Extreme (running on factory overclock/boost)
RAM: 32GB DDR3-2400 (using XMP)
SSD: Samsung 950 PRO 512GB NVMe M.2 (the OS and FF14 are both on that)
Display: Dell S2716DG (27 inches, 1440p, 144Hz, G-SYNC)
I'm currently running the driver version 382.53 since it has been stable everywhere (aside from FFXIV before this fix) and the newest one isn't well received on Reddit (many people report issues).
I've tried the following other things before I increased the voltage:
- Disabling any overlays (like Discord, RivaTuner Statistics Server (comes with Afterburner, so you might want to uninstall that if you just installed Afterburner to lower the voltage – sorry, forgot to mention that))
- Setting the card to "prefer maximum performance" in the Nvidia Control Panel (you can also do this via a profile just for FFXIV so it doesn't apply all the time)
- Running the game in fullscreen
- Disabling my CPU overclock
- Reinstalling Windows
- Disabling game mode, streaming and all the other stuff that came with the Windows 10 CU
- Reinstalling the game (copied over an installation from a friend who has no crashes so I can ascertain that I don't have any corrupted files)
- Turning down the graphics settings to the lowest possible
- Uninstalling Dropbox since the current version has an issue under Windows 10 where it floods the event viewer (see https://www.tenforums.com/software-a...0-entries.html)
- Running the game under admin mode and Windows 7 compatibiliy mode
- Checking my RAM with MemTest86
- Switching out my 32GB RAM with a 16GB kit
- Several different Nvidia drivers (basically all that officially support my 1080 Ti) with several different configurations
- Disabling G-SYNC
- Connecting my monitor over HDMI instead of DisplayPort
- Checking all my system temperatures under load (all way down in the green, I have very good cooling and even applied liquid metal to both my CPU and GPU die, so I wasn't expecting issues there anyway)
- Switching to my old GPU (a 980 Ti – had the same issues, although it was also quite heavily factory overclocked, so my voltage increase might have helped there too)
- Updating my Mainboard BIOS to the newest version
- Installing all the current Visual C++ runtimes (you could do it manually, but I used https://www.sereby.org/site/All%20in%20One%20Runtimes) and running the DirectX autoupdater
-
07-14-2017, 06:44 AMFromTheInternetz[POSSIBLE FIX] for Fatal DirectX Error 11000002 on Nvidia cards
-
07-14-2017, 09:05 AMMetatime
Everyone having nvidia card issues should really go to the nvidia forums and make awareness on this issue just like in the ati board. After enough players posted on the ati board, ati released drivers to fix the issue
-
07-14-2017, 05:12 PMFromTheInternetzI sent them a bug report instead (already did that a week ago), didn't think about posting on their boards – didn't get a reply yet though.Quote:
Originally Posted by Metatime
I might create a thread on their boards if I find the time. If I do, I'll link it here so everyone can contribute. -
07-15-2017, 12:03 AMVelhartI talked to a representative and sent as much information as I could regarding the issue. Suppose to hear back within 24 hours about their investigation. Hopefully it leads somewhere.Quote:
Originally Posted by Metatime
-
07-15-2017, 05:46 AMTalonWeaver
I've been having extremely similar issues but do not, as far as I know, have a factory overclocked card. I know my game has been causing some weird Dx11 errors lately, basically since downloading the latest Nvidia drivers. Very similar crashes to what you've explained, though more recently Windows will also give me a notification that the Nvidia driver kernel has crashed and restored itself, too.
-
07-15-2017, 06:01 AMVelhart
This is the response I get back....
Quote:
Hello ???,
Thank you for your patience and cooperation. I had this checked and issue is being going on for quite sometime and most commonly, this seems to be after Windows CU update: http://forum.square-enix.com/ffxiv/t...1000002/page11
You may have to contact the game developers and report the issue.
Best Regards,
NVIDIA Customer Care
-
07-15-2017, 08:17 AMDeclio
Thanks, i'll try this. The updated version of Precision XOC has a voltage slider (finally). I know pascal won't allow much, but maybe that little extra push will stabilize some of the offsets from the factory/manual overclocks.
I'm on a 1080ti/4770k using driver version 378.92 and crash with the DX11 error occasionally and CONSTANTLY in Susano specifically. I have to run in DX9 mode if we farm that fight. I will report back here in a few days to see if the voltage slider helped at all.
Has SE officially acknowledged this at all? I know AMD pushed an actual update out to address this specifically but it's clear Nvidia is going to shift the blame to SE.
edit: crashed quickly again after upping voltage. I'm going to have to play on DX9 until SE acknowledges/resolves the issue. -
07-16-2017, 05:58 AMXeon
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. -
07-16-2017, 06:17 AMXeon
And I know this information is accurate, because the guy above tried this and crashed even quicker...or quickly, or something.
Most of these DX11 issues are with the game. Some of them can be with the persons system, as I see alot of semi-old systems with 1080tis in them? Makes no sense to have a $70 cpu and a $500 GPU.
If you suspect that it is your GPU, before trying any of the advice above, download and run furmark. If you can run this for a half hour to an hour without it crashing, then the problem does not lie with your GPU. You can also try the same with prime95 with the CPU. if your system can survive these for an hour each, then you can count yourself clear of a hardware issue. -
07-19-2017, 10:02 PMVelhart
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.
Quote:
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
-
07-20-2017, 04:31 AMXeonRight 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.Quote:
Originally Posted by Velhart
-
07-20-2017, 06:07 AMGyroChulainn
Best news i've had all week. Hopefully this gets fixed soon.
-
07-20-2017, 10:28 PMZoserYou unquestionably made my day just now, Vel! :)Quote:
Originally Posted by Velhart
Here's hoping that Nvidia will solve this soon ...
Zos -
07-22-2017, 11:39 AMKadromAwesome 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.Quote:
Originally Posted by Velhart
-
07-22-2017, 11:48 AMGyroChulainn
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.
-
07-22-2017, 10:34 PMMetatimeQuote:
Originally Posted by FromTheInternetz
Yea I usually send a bug report but posting on forums I get a better response and it creates more awareness too on top of that -
07-23-2017, 09:03 PMFromTheInternetzHey, 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)?Quote:
Originally Posted by Xeon
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. :)
Awesome news! :)Quote:
Originally Posted by Velhart
-
07-24-2017, 01:08 PMDominicStone
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 -
07-24-2017, 05:45 PMZoser
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 -
07-25-2017, 06:07 AMVelhart
I have not received an update from them yet. I e-mailed them and asked how progress is proceeding on this.
-
07-25-2017, 11:37 AMVelhart
Unfortunately no update at the moment.
Quote:
Hi ???,
No updates on this issue at this time.
Josh
NVCC
-
07-25-2017, 02:33 PMDominicStone
I cannot recommend the nvidia driver released today (384.94). There is no mention of FFXIV in the release notes but I gave it a whirl anyways. These actually crash more often than ever. I hard crashed once, which is new, and then in a run of Dusk Vigil crashed before the first two bosses...as the healer. Rolled back to 384.76 (clean install, driver and physx only) and crash less, but still crash :(
-
07-26-2017, 02:33 AMZoser
I had a similar experience, three crashes during one dungeon as opposed to none with lowered settings and 384.76 ...
-
07-26-2017, 05:44 AMGyroChulainn
So, i used the launcher option to reset all configurations to default and for some reason it appears to have fixed it. I was crashing literally every 10 minutes and now i've played for 3 days straight with no crashes. Maybe it could also work for someone else.
-
07-26-2017, 08:48 PMRiardon
I'm getting random hard locks. It drives me nuts.
The game randomly just freezes and I can't do anything. The image freezes but Windows work normal in the background. CTRL+ALT-DEL does nothing when the image is frozen and I need to manually force reset my PC to get around it. This happens even when the game is running in thre background "minimized" (ALT+TAB). I don't get any error message or BSOD so there is no info to post. It just randomly freezes there. This started to happen after SB.
Tried clean Windows 10 format (CU) 2 time already. Tried 4 different Nvidia drivers including the newest and it keeps happening. Tried removing any OC and overlays nothing.
Tried uninstalling almost everything and run the game alone and yet it keeps happening. Tried disabling all power saving option in BIOS and set High Performance plan in Windows and still nada.
For reference my system is i5-2500k and GTX 970 G1 Gaming with 8 Gigs of 1600mhz RAM on SSD. Windows 10 x64 Pro Creators Update. -
07-27-2017, 01:36 AMDominicStoneMyself and others have tried these fixes, too. I really think it's game client, as that's really the only thing we all have in common. The chance that we all have cards with some niche fault that only happens in this game and no others is so small that it's laughable. If tech support tries to blame this on your PC, please point them to this and the umpteen other threads on DX9/11 errors.Quote:
Originally Posted by Riardon
-
07-27-2017, 08:42 AMSenlitenIt works to an extent, but for myself sadly, if I don't do exactly this each time I start the game up it ends up taking one nice big fatal directX nose dive at some point.Quote:
Originally Posted by GyroChulainn
-
07-28-2017, 05:37 AMLukahn
I started getting "An unexpected error has occured." crashes today. They just randomly started today and I've been playing the game a lot over the past couple of weeks. I do have a new system with an Auros GTX 1080ti, but to be honest most of the talk here is a bit technical for me. I haven't done any tinkering with fan settings or overclocking. The card is pretty much right out of the box. So am I waiting on a patch? I don't understand some of the solutions that have been recommended here. Any advice for a layman would be appreciated.
Edit: I'd like to add that some of the posts regarding power consumption make no sense to me, as the problem just started today after weeks of play. Why would the power consumption have just magically changed? -
07-29-2017, 05:20 AMVelhartIt isn't your power. There is some sort of bug that is telling your machine the power is going beyond the limit it is suppose when it is not when playing FFXIV. It crashes itself when this happens. Not saying this is what the issue is, but if hypothetically this is the case. Your power output is likely more than fine.Quote:
Originally Posted by Lukahn
-
07-29-2017, 03:31 PMDominicStone
I've had some success with resetting the settings in launcher config, setting the correct resolution and running in Borderless Window mode. I get some weird frame slow downs (mostly old ARR zones) but no crashes tonight. I really prefer to play Fullscreen but if I need to run it like this for now then I'm gonna have to deal with it :P. Anywho, hope that helps someone out there with the DirectX woes.
-
07-31-2017, 09:31 PMGalborion
My girlfriend cannot enter Chrysalis, she gets instant crash and cannot log back (I always have to log her character on my PC to get her out of there). I guess she is lucky because its the only place in game where it happens (100% of the time though). It was not that bad before, but now when Chrysalis is part of Trial roulette its bad. This issue started to appear after 3.5 patch. Its so long and there is still no fix from SE side. Its absolutely clear that is problem on client side and not on nVidia drivers because it did not happen before 3.5. I have no idea what they changed, but they changed something and they should fix it!:mad:
-
08-01-2017, 01:03 PMDominicStoneWell...after days with no crash, I crashed twice this evening over a 4 hour play session. Borderless Windowed mode, no setting changed, no different programs running, etc...Quote:
Originally Posted by DominicStone
-
08-02-2017, 12:26 AMaltathena
I get the 1100002 error all the time. I had thought it was because I am playing on an old laptop (and maybe that is the reason for me), but now I'm not so sure. I play on the absolute bare minimum graphics settings (15fps, windowed 1024, etc.) on a nvidia 540m. The 540m appears weaker than the 8800, which SE says is the minimum needed for FFXIV. DirectX 11 actually appears to catch the error and quit the program, whereas with DirectX 9 I have to hard reset my computer. Not really sure if I really belong in this thread since my computer is so old, but I thought I'd give my two cents...
-
08-02-2017, 02:23 AMDominicStoneThis post absolutely belongs here, sorry you've joined our ranks :( . I really don't think it's hardware specific as my machine specs are complete overkill and I'm suffering the same crashes. I'm convinced that this is a code problem in the client; as many have tested various Nvidia drivers with little-to-no success.Quote:
Originally Posted by altathena