The huge DX11 crashing thread got moved to resolved issues?

[Nadirah]

I just wish I could figure out what error I'm even getting.

There's no log anywhere. No driver message, nothing. Just.. closes.

I'd like to reiterate that this is probably a separate issue from the black screen crashes.

This is specifically happening in combat, not when zoning or anything of the sort.

I ran the game just fine for 7 hours earlier in the day, and did the entire first part of Alex without issues but as soon as we got midway through that battle with the bombs and the mech you pull them away with.... crash.

Two pulls in a row.

Said F it and went back to DX9 so my group could kill it. Healer crashing midfight is a bitch.

[Callidor]

I just wish I could figure out what error I'm even getting.

There's no log anywhere. No driver message, nothing. Just.. closes.

I'd like to reiterate that this is probably a separate issue from the black screen crashes.

This is specifically happening in combat, not when zoning or anything of the sort.

I ran the game just fine for 7 hours earlier in the day, and did the entire first part of Alex without issues but as soon as we got midway through that battle with the bombs and the mech you pull them away with.... crash.

Two pulls in a row.

Said F it and went back to DX9 so my group could kill it. Healer crashing midfight is a bitch.

I think there are a lot of separate but related issues surrounding the dx11 client. My game doesn't even "crash" per se. It just minimizes itself and then can't be un-minimized. I think the fact that there are so many different ways this problem is manifesting for people mans it's going to be very difficult to research / solve =/

[Noxe]

I have an EVGA GTX 970. I used to have that exact same problem. I installed the hotfix driver 53.38. Hasn't happened since (its been a week or maybe more). No crashes of any kind either.

I also flashed my bios to the latest version.

[GunnarBerwerf]

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.

[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

[edenPiE]

So, I decided to maybe try going back to the dx9 client and that seriously won't even start up for me. I don't understand this game.

[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.

[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.