Quote Originally Posted by RocciaSolida View Post
Sometimes I get DX11 errors when closing the game so I don't really care much.
Still I pray every day that these issues won't suddenly get worse as I've already tried to reinstall my drivers with DDU, run multiple memtests, repair my DX11 install etc...
I'm certainly not gonna underclock my GPU because of some spaghetti code, I'd rather quit the game altogether
Downclocking dosen't help anyway, I've done that it just increase your time before the crash by around 20%, the longest I got it working on my old rig was to change the CPU affinity to high and lock the game to two CPU cores. And again, this is not a solution! The game still crashes! I've even went back to my old computer that worked 100% of the time and never had a single crash, even that computer crash now. From what I can see with my systems is that the issue is linked to the memory in some way, if I use an XMP profile at 3200mhz or higher, the game crashes on launch, even though the system is completely stable with every other game. If I go to XMP 1 at 3000mhz memory it crashes after 1 or 2 hours. If I go to 2999mhz but sill on the XMP1 profile the game doesn't crash at all. And if I turn off XMP the game crashes after 20min... something is funky with their shitty code, their implementation of DX in the game. This will never be fixed unless the developers get their hands on the issue, this is a hardware/software conflict and the DX11 error seems to be a "catch all" error, people who've had issues with the audio get DX11 errors even though it's a conflict with their wireless headsets.

Also a tip to everyone in this thread, open Run (windows key+R) and type "perfmon /rel". This will bring up the performance monitor, reliability monitor and I can guarantee that the error you get with FF14 crashes is a Hardware error with the problem event name "LiveKernelEvent". This goes to show that there's something that the game code is conflicting with. That's why some people have had some progress with removing USB devices. The error ID in the eventviewer is 1001. Or you can go the correlated time for the error and check if anything else show up in the eventviewer.