The huge DX11 crashing thread got moved to resolved issues?

[Nadirah]

That's because there is no issue. It has nothing to do with the game client and everything to do with what is installed on the players system or they have a defective GPU.

There are 3 main causes:
1) Software hooked into the game client (eg MSI Afterburner, Ratr, nVidia Experience)
2) Microsoft Visual C++ runtimes are out of date (which means you haven't been running Windows Update like you are supposed to)
3) Drivers are out of date (particularly you haven't updated -ALL- your GPU drivers, this includes the iGPU in Intel i3/i5/i7 chips)
4) Bad GPU hardware (factory overclocked parts)

If it's not the first 3, which are entirely within your control, it must be the 4th option.

Otherwise absolutely everyone would have the problem, which is not the case.

My problem, being an access violation, can most certainly be the client.

[MisterRuseman]

ok so strange thing, I got off work today turn on my pc. My auto update bios app thing pop ups and says theres a bios update for my msi gaming 970 mobo. I Updated my bios. Restart PC. Start playing dx11.. Boo yah. It didnt crash for 3 hrs until the client crashed.
Normally i get a crash within 10 mins "display error stopped responding" or something like that. So it seems my bios update did something. i also played an hour after the crash and everything seemed to be working well

[Noxe]

ok so strange thing, I got off work today turn on my pc. My auto update bios app thing pop ups and says theres a bios update for my msi gaming 970 mobo. I Updated my bios. Restart PC. Start playing dx11.. Boo yah. It didnt crash for 3 hrs until the client crashed.
Normally i get a crash within 10 mins "display error stopped responding" or something like that. So it seems my bios update did something. i also played an hour after the crash and everything seemed to be working well

Yep, pretty sure I've mentioned this in a couple of the threads on a GTX 970. I also used to get the crashes/BSOD's. But it all went away as soon as I flashed my motherboard bios to the latest version.

[KisaiTenshi]

1) Nothing of those software installed. (because i don't need them, as i am not overclocking and stuff like that)
2) it's all up to date.
3) it's all up to date. (if you have a dedicated GFX then you disable the iGPU in the bios anyway, at least me, and even with the dedicated GFX removed and trying with my iGPU the game wont start after clicking the button on the launcher in dx11 mode, its the same with the dedicated GFX))
4) everything is ok, (besides if hardware was faulty then other games would give me the same error or something similar)

the problem is clearly on nvidia, ati, Square or microsoft's side.

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.

My problem, being an access violation, can most certainly be the client.

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:

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

So what this tells me:
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.

ok so strange thing, I got off work today turn on my pc. My auto update bios app thing pop ups and says theres a bios update for my msi gaming 970 mobo. I Updated my bios. Restart PC. Start playing dx11.. Boo yah. It didnt crash for 3 hrs until the client crashed.

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:

http://ca.msi.com/support/mb/970-GAMING.html#down-bios
2015-05-13
Improved USB keyboard compatibility.

2014-11-12
Updated AGESA Code.

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.

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.

[sucht]

...

what i wrote was after a fresh install, and just the stuff i need to play(drivers, vc++ redists), and the only thing i install from Nvidia are the Drivers+Physx(no 3d and no experience)

Event Viewer error:

Faulting application name: ffxiv_dx11.exe, version: 1.0.0.0, time stamp: 0x55a68eb2
Faulting module name: ffxiv_dx11.exe, version: 1.0.0.0, time stamp: 0x55a68eb2
Exception code: 0xc0000005
Fault offset: 0x00000000000089d4
Faulting process id: 0x15cc
Faulting application start time: 0x01d0c4e8ee380521
Faulting application path: X:\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv_dx11.exe
Faulting module path: X:\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv_dx11.exe
Report Id: 2c1d3edb-30dc-11e5-825d-74d435b2da53

it's more or less the same as posted by MrBinary, only difference "fault offset", "process id", "application start time" and "report id", and that i cant even start the game if i have directx11 activated.

and i have other games that use directx11 and some of them come with a x64 binary(exe), the newest of it is Witcher 3, and i have no problems what so ever with these games.


edit: my GFX is a Nvidia GTX 560Ti

[MrBinary]

what i wrote was after a fresh install, and just the stuff i need to play(drivers, vc++ redists), and the only thing i install from Nvidia are the Drivers+Physx(no 3d and no experience)

Event Viewer error:


it's more or less the same as posted by MrBinary, only difference "fault offset", "process id", "application start time" and "report id", and that i cant even start the game if i have directx11 activated.

and i have other games that use directx11 and some of them come with a x64 binary(exe), the newest of it is Witcher 3, and i have no problems what so ever with these games.

I'm curious if anyone is still having this issue, as it appears people have grown quiet about it. For myself the crashes have stopped for the most part. They only seem to happen upon transitioning areas ina dungeon now.

[Saffina]

Just gonna add my crash to the pile

Faulting application name: ffxiv_dx11.exe, version: 1.0.0.0, time stamp: 0x55ae90ad
Faulting module name: ffxiv_dx11.exe, version: 1.0.0.0, time stamp: 0x55ae90ad
Exception code: 0xc0000005
Fault offset: 0x0000000000145691
Faulting process id: 0x14b8
Faulting application start time: 0x01d0c6c8a978b90e
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv_dx11.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv_dx11.exe
Report Id: 92773f90-32bd-11e5-8fa0-d8cb8a7730fd

[MrBinary]

Just gonna add my crash to the pile

Faulting application name: ffxiv_dx11.exe, version: 1.0.0.0, time stamp: 0x55ae90ad
Faulting module name: ffxiv_dx11.exe, version: 1.0.0.0, time stamp: 0x55ae90ad
Exception code: 0xc0000005
Fault offset: 0x0000000000145691
Faulting process id: 0x14b8
Faulting application start time: 0x01d0c6c8a978b90e
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv_dx11.exe
Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FINAL FANTASY XIV - A Realm Reborn\game\ffxiv_dx11.exe
Report Id: 92773f90-32bd-11e5-8fa0-d8cb8a7730fd

Yeah, the same exact error everyone appears to be having. This one just happened to me less than a minute ago upon pressing 'Play' in the launcer:

Problem signature:
Problem Event Name: APPCRASH
Application Name: ffxiv_dx11.exe
Application Version: 1.0.0.0
Application Timestamp: 55ae90ad
Fault Module Name: ffxiv_dx11.exe
Fault Module Version: 1.0.0.0
Fault Module Timestamp: 55ae90ad
Exception Code: c0000005
Exception Offset: 0000000000d9e659
OS Version: 6.1.7601.2.1.0.768.3
Locale ID: 4105
Additional Information 1: faf4
Additional Information 2: faf47e036330d690387c6fbd24f2db66
Additional Information 3: 5f56
Additional Information 4: 5f5675faeae776855b84672422123d6f

[sucht]

I'm curious if anyone is still having this issue, as it appears people have grown quiet about it. For myself the crashes have stopped for the most part. They only seem to happen upon transitioning areas ina dungeon now.

still crashing when i try to start the game
oh and right after the last update it worked for some time, but now it doesn't anymore.



edit: my GFX is a Nvidia GTX 560Ti