DX11 Issue

[Yurien]

Add me to the list. Ugh.

[Alex_the_Cat]

So, this issue has been plaguing me for the past week at least. Started manifesting itself during dungeons. Thought it might be overwolf. Problem actually got worse.

Saw this in another thread on here, but someone mentioned overclocked RAM. I've only had the issue since upgrading my PC components. Went into BIOS, reset my CPU overclock, RAM overclock, and set MSI afterburner to default - happy to say no problems so far.

[Kisama]

Incredibly annoying. This is happening multiple times per hour.

[BohnMi]

Oh my god, similar but not same issue here. Twice last night during PotD runs my screen went black, usic kept playing, but I had to force myself out of the client. I received an error saying DX11 was unresponsive. If anyone finds anything please post it here!

[Khanscott]

DX11 Client has been completely incompatible with Eyefinity + Crossfire since day 1 of its release. Pretty clear that S-E has little intention of doing any sort of significant fixes to the DX11 client for those having issues.

[Combat]

Hey fam!

I run a r9 380 in my rig, and was having the same problems pretty much everyone was having while using dx11 and windows 10. After some searching and experimenting, I finally settled on uninstalling the latest drivers and installing the 16.3.2 drivers, as they claimed to fix the issue in the patch notes http://support.amd.com/en-us/kb-arti...on-16-3-2.aspx

Not running any overlays (all steam / discord overlays turned off) and it's been two days since I've 11000002'd. Worth a shot. Good luck!

[Geminias]

Video Card: Radeon R9 380 (4 GB VRAM)
Driver Version: 17.4.3 (cleaned up)
OS: Windows 10

Having issues since one of the recent patches (I think it was 3.5), I did a clean install of the drivers yesterday, but to no avail: Just had another crash in Idyllshire. PC freezes for a moment, then boots me out of the game with the 11000002 error code. Too my knowledge it's the only game where this is happening, but at the same time I don't play that many Direct X 11 enabled games at the moment.

EDIT: Oh yeah, I also forgot to mention that I also experienced a crash for the same reason during the Stormblood Benchmark

[Mizudes]

Hi all!,

I just wanted to chime in as well and past few days have been unplayable.. I have uninstalled and reinstalled FFXIV a bunch of times.. and done driver rollbacks and updated to the latest drivers doing clean installs..

Graphics card: GTX 1060 6gb
OS: Windows 10
Driver version: 22.21.13.8205

[ShadoShryke]

I just wanted to chime in here on a specific point.

I noticed a lot of people post the video card version (GTX 1060), but not the manufacturer. Please note that not all videocards with the same version (GTX 970 or GTX 1060 for instance) are the same. It is like comparing different types of grapes or different types of apples. Same family, but different entities when you go between manufacturers. See, each manufacturer tends to put their own approach into the design of their cards/chipsets. An ASUS GTX 970 and a MSI GTX 970 are not truly the same animal, in more than just manufacturer name. One single variance in chipset can make the difference between core drivers or DX11 cooperating completely with the software. This use to be a regular thing back in the early days of PC gaming, but in the modern day it is a more commonly unrecognized factor.

This also goes for Windows versions. Windows 8.1, with out certain updates that may be optional, may have issues with certain hardware setups in certain schemes. Remember that Windows is made for general compatibility, and fine details can create issues if certain factors are not known.

This applies to laptops as well, since most things are on the motherboards. For instance, the gaming computers for Cyberpowerpc and Ibuypower for a while are built on MSI gaming cores. They are just "rebranded" MSI machines. Though the motherboards and core are MSI, they have different chipsets added (or subtracted/replaced) between the different companies. This means that the core firmware for the same GE62 machine may be different by the manufacturer you buy it from, and the core MSI firmware released for their direct machines may be more compliant than a rebranded with the apparent exact same specs.

Though companies have gotten far better about this, sometimes their "special twist" causes an unseen error in DirectX handling. This is why three people with the exact same systems specs can have a different experience only because one had a motherboard and videocard from MSI, one had a ASUS/Gigabyte combination, and one had a Sapphire and EVGA build.

So, listing the specific manufacturer of the video card (and even motherboard) can be a big difference it tracking down the exact issues.

Just a though from a tech of 20 years. I do more support for companies and small businesses than I do gaming, but I have seen this cause issues in lots of different software.

[Ephemeris]

Have there been any updates on this issue?

It will make a large chunk of the player base unable to play when Stormblood launches, and there doesn't seem to be a single official comment about it.

Forcing people to switch to DX9 just to play longer than 5-10 minutes is not acceptable.

Asking people to roll back drivers that could cause compatibility issues with other games is not acceptable.

Expecting people to switch to Nvidia cards is not acceptable either.

This has been a problem with FFXIV and AMD cards for years. It's pretty safe to say that none of these crashes are the user's fault.

With DX11 the game just randomly crashes in very populated areas. With DX9 it "hangs on" for a while longer and the first few times when it's about the crash it re-renders the entire screen. This happens a few times before it finally crashes as well, but in the way that the screen freezes and it won't re-render anymore without restarting the game.