AMD GPU driver timeout CTD

[Trufret]

AMD GPU drive timeout Crash is random, anywhere between a few mins and a few hours into a flight.

I only play VR (Reverb G2) and MP so unsure if it also occurs on flat screen and SP

Notable messages in crash log include d3d11.dll C0000005 ACCESS_VIOLATION

System:

• 7800X3D
• MSI X670P
• 32GB DDR5
• XFX 7900XTX
• 2 TB Crucial NVME
• 64GB Page file

Windows 11 Pro updates current

Latest Mobo Bios

Latest AMD GPU driver 23.9.3

What I've tried so far:

• No OC on CPU
• No OC on GPU
• no EXPO on RAM
• SFC scan
• DCS updater repair
• Delete FSO/metashaders
• Disable Multi Plane Overlay
• Disable WMR virtual displays
• GPU driver reinstall (DDU and AMD system cleaner methods)
• running SingleThreaded exe
• Reduce desktop resolution from 4K to 1080P
• Disable 0 rpm fan mode

My cousin has an identical system (ordered 2 of everything and built together) and he is getting the same GPU driver timeouts as well but with an Oculus VR headset. This seems to suggest it's not simply faulty hardware on my end.

Crash reports submitted to ED and AMD.

Hoping someone might have a better idea of what's going on as it's pretty much unplayable now as I never know how long I'll be in a mission before the screen blacks out and I CTD with the driver timeout message.

dcs.log-20231016-225001.zip

[Trufret]

Updated DCS 2.9.0.47168 Open Beta

Updated AMD Driver 23.10.2

Crashing seems worse now, cant even start up and take off before crash occurs

Tried deleting entire saved games folder and letting DCS create a new one. No help either.  

dcs.log-20231027-194733.zip

[Flappie]

Hi. The first critical error that comes out of your first log is "XR_ERROR_RUNTIME_FAILURE".

Try this:

 

[Trufret]

On 10/27/2023 at 4:45 PM, Flappie said:

Hi. The first critical error that comes out of your first log is "XR_ERROR_RUNTIME_FAILURE".

Try this:

 

Interesting,

I was just about to update that I think I've found a different workaround but may be related.

I noticed in Event Viewer that before the game would crash there was an Application Error:
Faulting application name: dwm.exe, version: 10.0.22621.1635, time stamp: 0x6201aae6
Faulting module name: DHolographicDisplay.dll, version: 10.0.22621.2070, time stamp: 0x382b0255
Exception code: 0xc0000409
Fault offset: 0x0000000000045547
Faulting process id: 0x0x738
Faulting application start time: 0x0x1DA09B969FD2634
Faulting application path: C:\Windows\system32\dwm.exe
Faulting module path: C:\Windows\system32\DHolographicDisplay.dll
Report Id: 1489ad09-c297-4e0f-bcca-cd8e17ab5e67
Faulting package full name:
Faulting package-relative application ID:

Looks like the WMR VR environment was crashing which was taking down dwm.exe and then the game would crash with a d3d11.dll error after that.
After reinstalling the WMR components didn't fix the issue I switched from using the WMR OpenXR implementation to using Steam's OpenXR implementation.

Since then I've flown for several hours without a crash even with EXPO and GPU O.C enabled.

I do have open kneebaord installed v1.5.2+gha.1473 but haven't been using it recently.  i Will have to test and see if removing that registry key and updating to the latest version fixes the crashing on the WMR OpenXR version

[Trufret]

On 10/27/2023 at 4:45 PM, Flappie said:

Hi. The first critical error that comes out of your first log is "XR_ERROR_RUNTIME_FAILURE".

Try this:

 

I've tested switching back to WMR OpenXR after deleting the registry key in the linked thread and updating OpenKneeboard to latest build and was able to play for a few hours last night with CPU O.C, GPU O.C, EXPO and no crashes.

Performance between WMR OpenXR and Steam OpenXR seem comparable but since WMR OpenXR is working now I'll stick with that for the time being.

Thanks for the pointer.

[Flappie]

You're welcome. Thanks for your feedback.

[KoN]

Question do you have to run steamVR . Or can you run without it . 

[Trufret]

Looks like removing the registry key and updating openkneeboard was not the solution. Got the same crash the weekend with DHolographicDisplay.dll fault.

Switching back to Steam's OpenXR version to see if that helps long term as I haven't had a crash with that yet.

Sure seems to be an issue between AMD, Win 11, and WMR.

@KoNIn my current setup using Steam's OpenXR it does still launch SteamVR.

 

[KoN]

I'm using pico link DP mode . SteamVR  On AUTO .

DCS mt exe . 

No upscale MSAA x 2 . 

[Trufret]

SteamVR OpenXR is not the solution either.

Still getting DHolographicDisplay.dll crashing dwm.exe

I've picked up a Quest 3 to try and eliminate WMR entirely from the equation as trying to get other WMR headsets working to even test DSC was a nightmare of WMR errors.

So far its been stable with Quest 3 but needs more hours of flying to know for sure. 

[Trufret]

Quest 3 with Oculus OpenXR has also not corrected the problem.

PC has been wiped and clean install of Windows 10 (instead of 11) with only software required to run DCS installed.

no OpenXR toolkit or Openkneeboard at this time.

We'll see if this still crashes.

[Trufret]

I've got about 10-12 hours of flying in DCS since the clean install of windows 10 and haven't had a crash. Ram expo and GPU, CPU overclocks are back in place and still stable.

It seems like there is some issue with Windows 11 and AMD drivers that is just not stable in some situations at least with the 7900xtx or potentially all 7000 series cards.

My cousin, with the identical system, who's still on Windows 11 will be doing a clean install of Windows 10 as well as he's still getting regular timeouts in DCS and ARK so its not just VR that's timing out either.

Not the fix i was hoping for but I'll be sticking with Win 10 until 2025 and hopefully they have fixed Win 11/AMD drivers by then.

[Count von Altibar]

I have the exact same issues crashing/freezing and I'm AMD user with Windows 11. Appears to be that W10 users don't have this problem, it's making DCS pretty much unplayable for me now as it's happening so frequently and usually at critical moments in missions. All very frustrating indeed.