I'm thinking about getting my subscription money back, I can't play the game like this. For a Pay to Play game I expected at least a reaction from SE on this issue. Please let us know what is going on.
I'm thinking about getting my subscription money back, I can't play the game like this. For a Pay to Play game I expected at least a reaction from SE on this issue. Please let us know what is going on.



			
			
				Unfortunately you won't be getting any sort of refund for your subscription. The only reason they would issue a refund is if there is criminal activity involved, as per the FFXIV User Agreement, Section 4.7 (Source)


			
			
				Alright, I still have yet to crash with the DirectX error. I did a clean reinstall of the 361.43 driver set without the GeForce Experience and have run the Void Ark without a crash. Will continue testing, but for me at least it seems uninstalling MSI Afterburner and the GeForce experience stopped the crashing. Now, to be clear, those are useful programs to some and I still think this is something Square-Enix and Nvidia (and ATI?) need to work together to fix. Keeping those programs uninstalled is a workaround, not a solution.
It's also clear there are multiple crashing bugs present. This thread revolves specifically around the bug wherein the DirectX 11 client either crashes with the message "A Fatal DirectX Error has occurred (11000002)" or the game seizes up completely, locking the PC as well. Normally the client itself will just freeze for a short period of time before the error message finally shows. This specific bug only occurs with the DX11 client, switching to DX9 will fix it. If your symptoms don't match these, you likely have a different crashing bug and this thread will not help you.
This has been a frustrating ride for a lot of us, and hopefully it will be resolved soon. I have a bit more testing to go before I can post something quite specific on the NVidia and SE forums. I want to be able to throw very specific data at them to speed up a fix. Hang in there one and all, and remember, aside from Steam, try completely uninstalling anything that may act as an overlay. It's more a band-aid then a fix, but at least I've been able to play crash-free for awhile now.
Some more info;
My game just crashed again (tried everything mentioned in this thread, without any luck). But I just noticed something weird, right before my game crashed, I saw a yellow/orange particle thingy showing up (flickering) that wasn't supposed to be there. Also, I'm using Dxtory to cap the framerate to 45 (yes without this program the game still crashes), right before the game crashed my framerate spiked and immediately went back to 45.
Also played the game yesterday for a few hours and it didn't crash at all. It's hard to really tell what the problem is if it happens so randomly.
There has to be a conflict with the engine and the NVidia drivers for some strange reason.
I haven't had a fatal error in several days, possibly a week now. However, now my game will randomly decide to enter a series of "lock ups" until I close firefox(64). An interesting turn of events!
Just happened again, Ramuh ex, on Arbiters + Thunderstorm
So... still nothing yet from SE?
Haven't played for a month now. Probably ending my 2 year long sub.![]()
Come on SE. Please fix.
Then why is there a "being addressed" section in the technical forums? I'm pretty positive that other customers don't move the threads themselves.
| 
            
               | 
          ![]()  | 
          ![]()  | 
          ![]()  | 
        
| 
            
               | 
          
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

			
.
						
  Reply With Quote

			
			
			
			
			

