GTX680 And Losing DirectX Device

[OrionInerghem]

I just finished my brand new computer, i73930k, asus ROG, EVGA GTX 680 SC, I tried to do United We Stand tonight and I got the "ffxiv has stopped working" error about 12 times in 2 hrs. The game was completely unplayable. Not impressed.. Eventually i d/c while dead, came back and d/c again and gave up.. The game looks amazing but can't play... Ive tried high settings, low settings, settings off, everything...

Before this it was the directx error only but now it's switched to "ffxiv has stopped working"

[Sajittarius]

yea i havent gotten directx error lately but since patch 1.23a i get the FFXIV has stopped working once or twice a day. Looks like they changed something in the last patch.

I'm just waiting for 2.0 to fix everything at this point...

[Goddhand]

Count me amongst those with an issue. This is imo the same problem that was affecting nvidia users back in 2010. A google search on both the nvidia and the square enix side reveals several false solutions, the most laughable of which is nvidia claiming they can't recreate the issue. This despite hundreds of youtube videos and complaints clearly illustrating the issue, of which the ONLY COMMON THREAD is nvidia users playing ffxiv.

Its not the overclock, its not other programs being open, its not ambient occlusion or depth of field. The best nvidia cards are still not loading up heavy textures properly even under the lightest settings and someone needs to tell us why.

I am trying to get all the achievments and content done before 2.0 that I can right now, but how can I get any help? You can't even get in a linkshell without shouting in Ul'Dah, and sitting there makes the game crash. Not to sound snarky, but its been 2 years.

[Blane]

I am disappointed. I got my Lancer to 24 earlier this summer/year and I tried playing again today. At first, I was able to log in and make it to the first loading screen, then it would crash. I fidgeted with the Multisampling settings and now I can play for about 10 minutes or so and it will crash again, mentioning the DirectX issue.

I'm assuming that it's something in the latest patch (as previously stated) that's messing with something connected to the multisampling setting. As it is now, I don't even feel like trying to get it to work anymore today (and I really wanted to hear the lore behind Meteor, as the Meteor wasn't in the sky when I stopped playing before. I logged on and was like "WHAT IS THAT!?!"). Ah well. Here's to version 2.0.

[Drewbie]

Heu SE pls fix so we can play and be happy ty do it just do it lol

[Miiu]

Played the game on a GTX580 until yesterday and no real problems with it. Now I switched to a GTX690 and like other people I get "ffxiv has stopped working" quite frequently. (306.2 driver version)

[zzapp]

AMD 5870 GC, playing in windowed mode, since patch 1.23a I get the 'Windows has stopped working' error alot more than I ever did. Also, the 'unble to detect directx message is now very common, mostly @ sign-in. My friend with a brand new Alienware and different graphics card is having the same issues. Prior to this patch I think i only got the directx error once in almost 2 years of play ;/

[zaknefein]

Ive got a GeForce GTX 675M with the latest driver (304.79) installed and I get both the DirectX crash and the "Final Fantasy XIV has stopped working" crash. Usually a few times each day, unpredictable time periods. I'm running it on Samsung series 7 gamer system, so it should be powerful enough to run it. Cmon SE -.-

[VoltaAsura]

please read prior postings in this thread. It is a newer gpu, newer architecture, and apparently the drivers for the 600 series cards have compatibility issues with ffxiv. Not se's fault.

[zaknefein]

please read prior postings in this thread. It is a newer gpu, newer architecture, and apparently the drivers for the 600 series cards have compatibility issues with ffxiv. Not se's fault.

honestly, i dont care if its SE's fault or not. the issue remains that this is a common problem that many people are having for a long period of time. after reading about 7 pages on this forum i gave up trying to figure out who is at fault or why; the fact remains that this is a persistent problem that should be worked out. especially given the fact that theyre releasing a 2.0 version; which seems absurd when the current version has common crashes.
SE needs to know that people are having this problem in order to either fix it on their end, or put pressure on the card's manufacturers to fix it on their end. this post started in March ffs.