Crash every 10-20 minutes...

[Epedemic_Optikz]

Alright, first and foremost, I've been playing since closed beta. I never had any crashing issues or anything that caused the game to fail and shut down on itself whatsoever. Perhaps it happened once but then never again. Come open beta, I can only play every 10-20 minutes and all of a sudden, the game would crash and give me an "unable to detect directx device." error. I figured ok whatever, I'll try back later.

The problem didn't go away for the entire open beta. So now, I'm here in the retail version and the problem still exists except this time when the game crashes, I have a windows notifier box on the lower left that says "display driver stopped responding and has recovered" and when i click on the minimized FFXIV tab, it'll show the unable to detect directx error. The funny thing is though, the game is still running, it's just a black screen. I can run and walk and I know this because I can hear the footstep sound but I don't see anything.

Everytime I crash with FFXIV, my GPU temp were never any higher than 60C. I have an XFX Radeon 5850 max OC, Q9550 @ 3.8 Ghz, 4GB Ram, Win 7 64, 750W thermaltake psu. I'm using 10.9 drivers atm, used 10.8 in closed beta and open beta. I even ran the game at the near lowest settings and it'd last maybe 10 minutes longer but it'd still crash. Anyone else have any similar issues and were able to work them out?

[aru]

I've also been having this issue. I made a thread here back during open beta and it seems like a fairly common problem without a solution. The only thing that's worked to reduce the frequency for me is to close everything but what is required to run the game. I don't think I'll be buying the game until they fix this because it is pretty much unplayable.

[sruon]

Well the error message is pretty clear... your driver is crashing, tried updating? Had this happen to me last month and the card was in fact dieing.

[Epedemic_Optikz]

5850s are fairly new, not to mention i bought mine a couple months ago. I tried wiping and updating the drivers to different stable versions like 10.5, 10.8. I believe some people still retain this error even when switching to another card.