Confirmed driver issue with FFXIV Heavensward dx11 client on drivers 15.15 and 15.200. Game hangs due to the driver not responding and recovers causing the game to stop working and close. dx9 client works fine. Tested on 1920x1080 and 1920x1200 with maximum graphics settings. Issue also occurs on lower graphics settings. Crash occurs regardless of HBAO+ enabled or not. Crash occurs with vsync on or off.
This was tested with a brand new MSI R9 390X. Card was also swapped with a 2nd one to rule out hardware issues. Upon removing the drivers and the 390x, reverting to the previous system with powercolor 290x and omega drivers (14.12) the game runs flawlessly.
Duplicated on 2 different systems running Win7 64bit
Test system 1:
RAM: 16gb 1600mhz
Test system 2:
RAM 16gb 1866mhz
Compared against older r9 290x with omega drivers as well as an nvidia GTX 970. Only the 390x with the R9 300 series drivers is exhibiting this issue where the game hangs with black screen and eventually forcing windows to close the game client and recover to desktop.
This is a pretty serious issue as this game recently launched alongside the 300 series and the 380 / 390 cards should be an excellent choice for this type of game for 1080p/1440p; assuming driver reliability.
The game is an expansion to the 2013 MMO release which already has 4 million subscribed accounts as of May 2015. The DX11 game client is a much anticipated feature which will help drive sales of new graphics cards since several existing players as well as new ones interested in the game will be looking at upgrading graphics cards in the $200-400 price range.
The issue is also very easy to reproduce using the freely available FFXIV Heavensward Benchmark utility. Looping it in DX11 mode will eventually cause the crash.
Solved! Go to Solution.
Drivers 16.3.2 fixed the crashing for me on a R9 380 . Released a couple days ago I think March 28th.
Hi, I had the same problem as you, but I fixed it by
uninstalling any program that will cast an interface over dx11 games.
Take my case for example:
I simply uninstall raptr, which will have a small icon on the upper left corner when you play games.
Raptr comes with AMD driver package, ironically.
Hope this will help you too.
PS. It's according to this:
Is anyone from AMD going to respond to this? The game works with the 390x just fine running DX9. The problem is DX11. It also seems that when a youtube or twitch video is playing on the 2nd monitor any DX11 game, with the exception of the Unigine benchmarks, has the potential to freeze the game and cause one of those error messages saying the driver stopped responding and has recovered.
I submitted several bug reports to amd.com/report throughout the week and left my email address but no one has responded, nor has there been any statement from AMD acknowledging these problems with DX11 and the 300 series drivers.
Since no one is responding, I might have to return the 390x for a refund before the 15/30 day return policy is up.
I am not running any overlay programs. Also the issue isn't present with the 290x and the omega drivers. Not only does this game crash, but I've duplicated the problem with several other DX11 games.
The workaround you mentioned is still not considered a fix as the game should work in borderless windowed mode without having to disable other programs.
Actually I didn't play FFXIV at all.
Games I had these crash was Witcher 3, Toukiden Kiwami and GTA V in dx11.
These problem happened to me after installing 390X, the older one I had worked fine too.
Anyway, if you are not running any overlay program, maybe it's not the same cause, sorry about that.
Hope you problem can be fixed soon.
I have observed several DX11 games crashing in this same manner tested specifically with an MSI branded R9 390x. If anyone has observed this on other brands that would great. I've duplicated the issue on 2 different MSI 390x cards but I would like confirmation from owners of XFX, Sapphire, PowerColor, and other branded 390/390x are also seeing the same problem.
Though the factory overclocks differ, MSI does have the highest clocked 390x at 1080mhz.
Welp, I can confirm GIGABYTE 390X has the same problem, but now I'm using MSI, no issues after workaround though.
GIGABYTE has 1050mhz, I think.