The problem is never clear. From Most likely to least likely:
1. The PEBKAC, is trying to do something they aren't supposed to do.
2. The User's hardware is at fault(usually overclocking is the fault,) and only fails to run this software due to never running this software class before. Find another DX11 64bit game and try it. The only thing that comes to mind is Landmark. Consider the thermal conditions and climate. Are the fans kicking into high speed when the game runs? If they aren't, THAT is definitely a problem. I can't tell you how often people's systems will work just fine, and then suddenly some new thing comes along and now it crashes frequently. I've had TWO CPU's do this (PII, where MMX instructions would destabilize the system, and a QuadCore series Xeon which would likewise only fail if ANY game was running for 2 hours, on the dot. The latter changed behavior when I changed RAM, but ultimately I replaced everything in the system trying to resolve it.)
3. The User's operating environment is at fault, eg OS, Drivers and other conflicting software installed. The only way to verify this is to fresh-install the OS,all the OS updates, Video driver, and then run the game before installing anything else including antivirus software. Typically it will be antivirus software causing the problem. Some software hooks keyboard i/o (eg macro software, hotkey software), some hooks the video buffer. Some hook to the window context itself (eg Raptr) and it's their very presence that is destabilizing.
4. You only start blaming the software itself AFTER you've eliminated all the possibilities from your end, and damn near nobody does that or has the time to do it.
Hence "there is nothing to fix" unless everyone reporting the problem has exactly the same reproducible problem regardless of OS and Hardware. When it's confined to just one type of hardware, it's often a driver or hardware problem. Nobody seems to be able to reproduce the problem on other hardware.
The forum is not equipped with the ability to actually post crash dumps, but access violations are either:
1) Hooking utilities (in particular, two utilities trying to access the same memory, eg nVidia Experience + AMD Raptr)
2) Malware
3) Bad memory
Like if you go dig into the windows logs, it will tell you exactly what causes it, but that doesn't tell you much about the conditions that need to be true for it to do so.
Go to "View Event Logs" (just type this at the start menu in Win7)
Goto Application Error:
Find FFXIV's DX11 client
In this case the single crash I can find was this:
So what this tells me:Faulting application name: ffxiv_dx11.exe, version: 1.0.0.0, time stamp: 0x55997713
Faulting module name: DINPUT8.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdecf
Exception code: 0xc0000005
Fault offset: 0x000000000001b27f
Faulting process id: 0x316c
Faulting application start time: 0x01d0b8985038e4c4
Faulting application path: C:\Program Files (x86)\SquareEnix\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv_dx11.exe
Faulting module path: C:\Windows\system32\DINPUT8.dll
Report Id: 8f8b6d4b-248b-11e5-b1be-000c7646e994
The FFXIV_dx11.exe crashed, exactly once on 7/7/2015 due to something related to DINPUT8.dll. That means an input device, eg mouse or keyboard... or Joystick, was at fault. I have all three.
If I keep looking...
The next two crashes are on 6/20/2015 which crashed itself. THAT was when I downgraded and then reinstalled the MSVCRT100 files.
The last crash I can find in the log is 3/6/2015 in the ARR client, also for DINPUT8.DLL
So based on the crashes I DID get, rare as they are, they were all related specificly to DINPUT, and since they only happened while nVidia Experience AND AMD's Raptr were running, that's why I keep saying that, because these programs hook both the Video buffer AND the keyboard for recording. My Capture tool of choice is OBS and I actually activate it manually to avoid this very thing.
A BIOS update likely just adjusted the cooling fan curve or adjusted the voltage settings if the manufacturer was OC'ing the hardware to cheat benchmarks. MSI is known for doing crap like that. Note this:
While the most recent update only updates the USB Keyboard support. That's not a terribly likely thing to be crashing, but then again notice I mentioned DINPUT8 earlier in this post. The more interesting update is the 2014-11-12 one with the AGESA update. There are bugs in some AMD CPU's, which if you're also using the onboard GPU part in any capacity, can be tripped independently.http://ca.msi.com/support/mb/970-GAMING.html#down-bios
2015-05-13
Improved USB keyboard compatibility.
2014-11-12
Updated AGESA Code.
But this likely won't affect most users.
If you want SE to try and help (or just other people on the forum) you MUST do more than point fingers and go "make it work." That doesn't solve the problem and only earns non-serious answers like "throw PC out window"
Post the text of the crash report from the system log for starters. You may find that what people are assuming to be a video card problem is actually something else that other users have in common.