The huge DX11 crashing thread got moved to resolved issues?

did anyone try catalyst 15.7.1 ?

BUMP x.x I havent bothered to try direct x 11 in a while.if others here with the same gpu still got crashes i probably will still have crashes too i got amd R9 380. i went back to direct x 9 since i upgraded my gpu no crashing there was supposed to be a upgrade but with direct x 11 crashing thats a downgrade for this game >>

970 g1 GIGABYTE here, still having random crashes when teleporting. That really sucks, we've got a new patch and stuff... and again, SE didn't even say something about DX11 problems, i'm getting tired of this sh***. Being forced to play on DX9 when there's (only in theory, in my case) a dx11 available with a lot of game improvements. I'm a new player (like many who've got tired of the lack of content on WoW) but this indifference about a serious problem is really annoying. I'd expected more from SE's getting this sh** serious. =/ sad...

Quote:

---

Originally Posted by Brytor

I tried to 15.7.1 drivers but I still have the name corruption if I try to run in full-screen with crossfire

---

https://community.amd.com/thread/183429

I somehow found a fix for the name corruption/name display bug. Give it a try and see if it work for you. Still testing on some more setting see if i can found better one. See if anyone else use what I did and see what the respond, may not work for everyone. (only posted up about 20mins from this post)

Quote:

---

Originally Posted by PhallOiD

did anyone try catalyst 15.7.1 ?

---

Still doesn't work.

Quote:

---

Originally Posted by Ardna

I have 2 GTX 970s and a single 2560x1080 display
i7-4790K, 16GB RAM, Windows 8.1 Pro

Tried playing with DX11 and DX9, had crashes with driver version 353.62
Moved to driver version 353.06, after another player's advice, still crashes on 11 and 9.

No overlays whatsoever have been on. DX9 also acts flaky, not even playable with lowest settings.

Only seems to play well when SLI is turned off.

Although I swear I ran through a dungeon a week ago on DX11 with SLI on and had no problems until I spoke with a Levemete afterwards. That was with 353.3X driver (can't quite remember).

I just built this rig and it bums me out that I have $300 just sitting in the case not doing anything while I play FFXIV.

I plan on getting Win 10, and some are saying they haven't had any problems since upgrading. Any more news on that front?
EDIT: Just did a quick 10 load. Nothing fixed. So the question for the 10 users is: Did things work for you after doing a clean load or just the normal upgrade?

---

I play with a single GTX 980 and the only way I stopped the fatal errors was to revert my drivers to 350.12. I haven't changed them since, and I haven't crashed since.

Quote:

---

Originally Posted by Syx

I play with a single GTX 980 and the only way I stopped the fatal errors was to revert my drivers to 350.12. I haven't changed them since, and I haven't crashed since.

---

The only driver that I know of that doesn't cause this issue doesn't support my card.

The other 280 series cards that *can* use this driver can roll back to it and have no problems, but it won't work with my 390.

Quote:

---

Originally Posted by Nadirah

The only driver that I know of that doesn't cause this issue doesn't support my card.

The other 280 series cards that *can* use this driver can roll back to it and have no problems, but it won't work with my 390.

---

Sorry, that was for Nvidia cards, not AMD.

Quote:

---

Originally Posted by SaderX

https://community.amd.com/thread/183429

I somehow found a fix for the name corruption/name display bug. Give it a try and see if it work for you. Still testing on some more setting see if i can found better one. See if anyone else use what I did and see what the respond, may not work for everyone. (only posted up about 20mins from this post)

---

This seems to be working for me also. I did have to also check "Enable Crossfire for games that do not support it"

There's a new beta driver for AMD users if they want to try their luck with that.