The huge DX11 crashing thread got moved to resolved issues?

[Sartori]

Pretty sad that the community has to help each other fix their issues and SE doesn't respond to any of the tech threads to help, sad indeed

[Casanters]

If you're running an Nvidia card and drivers past 350.12(And even this version, albeit less so) and are suffering from the "Displayer Driver has stopped responding and recovered..." error, you're not alone.

In fact, it's a massively widespread issue among many nvidia users. https://forums.geforce.com/default/t...dmkm-stopped-/
Figuring out what's causing it is a very painful and drawn out process, and your mileage will vary in any kind of attempt to fix it.
In my case, I was having HD audio device conflicts and had to disable the HD audio drivers for nvidia entirely. I only ended up on that particular solution after hours of benchmarking, burn testing, fiddling with overclocks, and even going through the hassle of trying to sort out WMI errors.

Seriously. It's a major issue for nvidia and has been for a while, due to the really poor quality of their drivers as of late.
The best place to start in dealing with that particular error is to get Display Driver Uninstaller from https://forums.geforce.com/default/t...d-07-10-2015-/

Use it after booting into safemode. Restart, and then install driver version 347.88 with a clean install, selecting only the Driver and PhysX. Nothing else. Make sure to go into the nvidia control panel and set your power management mode to "Prefer Maximum."
If that resolves your issue, you're good to go.

If it doesn't, then you've got a long, long journey of sorting out what's causing it. Could be anything from bad DRAM, PCI-E bus going out, or even a file corruption in windows.

Despite that issue, though, I still get the DX11 crashes on loads, though. That generally appears to be entirely unrelated to hardware, and something client-side. It's definitely not my video card if 4 hours of Furmark and Heaven/Valley are stable at a core clock boosted to 1400mhz.
Running an MSI GTX 970 Gaming 100me.

[PhallOiD]

Let's make this thread huge again, F5 on technical assistance and amd forums everyday are making me crazy. I don't think either square or amd or nvidia really cares about that.

[sucht]

If you guys are crashing at loading or at the launch of the game try reinstalling/installing Visual C++ Redistributable Packages for Visual Studio 2013 (both x86 and x64)

https://www.microsoft.com/en-us/down....aspx?id=40784

It helped me especially when i was having lauch crashes.

i have that crashing at Launch i did try all of that, heck i even reinstalled Windows 8.1 completely and its not working.
it works every now and then, but 99% of the time it does not.

i never overclock my hardware, never ever, and i checked system memory(Ram), i even disable the TurboBoost thing in the bios for my i7.

directx11 also means 64bit, maybe the problem is with that.


edit: my GFX is a Nvidia GTX 560Ti

[Nadirah]

Seems my problem is Exception code: 0xc0000005 access violation.

Good luck figuring this one out. Completely new build and I can't run memtest until bf gets home so I can borrow his flash drive. I can't run it from CD.

It's *only* the DX11 version causing it.

[Bentozzi]

Still SE pretend to not see this thread.

[Xoriam]

If you're running an Nvidia card and drivers past 350.12(And even this version, albeit less so) and are suffering from the "Displayer Driver has stopped responding and recovered..." error, you're not alone.

In fact, it's a massively widespread issue among many nvidia users. https://forums.geforce.com/default/t...dmkm-stopped-/
Figuring out what's causing it is a very painful and drawn out process, and your mileage will vary in any kind of attempt to fix it.
In my case, I was having HD audio device conflicts and had to disable the HD audio drivers for nvidia entirely. I only ended up on that particular solution after hours of benchmarking, burn testing, fiddling with overclocks, and even going through the hassle of trying to sort out WMI errors.

Seriously. It's a major issue for nvidia and has been for a while, due to the really poor quality of their drivers as of late.
The best place to start in dealing with that particular error is to get Display Driver Uninstaller from https://forums.geforce.com/default/t...d-07-10-2015-/

Use it after booting into safemode. Restart, and then install driver version 347.88 with a clean install, selecting only the Driver and PhysX. Nothing else. Make sure to go into the nvidia control panel and set your power management mode to "Prefer Maximum."
If that resolves your issue, you're good to go.

If it doesn't, then you've got a long, long journey of sorting out what's causing it. Could be anything from bad DRAM, PCI-E bus going out, or even a file corruption in windows.

Despite that issue, though, I still get the DX11 crashes on loads, though. That generally appears to be entirely unrelated to hardware, and something client-side. It's definitely not my video card if 4 hours of Furmark and Heaven/Valley are stable at a core clock boosted to 1400mhz.
Running an MSI GTX 970 Gaming 100me.

347.88 doesn't support SLI for the dx11 client though.

[Nadirah]

347.88 doesn't support SLI for the dx11 client though.

Let me see here...

SLI or no crashing.

I'll take no crashing.

[Xoriam]

Let me see here...

SLI or no crashing.

I'll take no crashing.

No idea what this has to do with anything since you're not the one using my computer.

I also don't play at 1080 so no SLI = no go for me.

[KingStyles1]

I am throwing in my problem with dx11. I am having problems with running ff14 in surround in full screen mode with dx11 enabled.

I can run 1 screen with dx11 enabled in sli or from any 1 of my 3 980ti's. As soon as I try to run surround with all 3 screens in fullscreen or windowless mode with dx11 enabled, it crashes back to the desktop.

Never have a problem at all if it is in windowed mode or I can run it any way I want if I am in dx9. So the only time it crashes is When I am in fullscreen or windowless mode in surround with dx11 enabled.

Running 3 1440 rog swift moniters with 5930k chipset and 3 or 2 (tried it both ways) 980ti in sli. Worked for about a day when it came out and worked for another day with a clean driver install, but after that, no matter what I try cant get it working.