Sporadically crashes (graphics driver issues)

Ithronwise · October 30, 2020

Hi ED team,

for almost two weeks I am facing with sporadically crashes in DCS. The first one was after a long mission with the A-10C II at the NTTR map ten days ago, the second one in a Su-33 at the Syria map about one hour ago.

After the first mission I checked the dcs.log and crash.log and found some issues with the graphics driver (access violation by atidxx64.dll). At this time i still used the old 19.12.1 AMD driver. So I changed to the new recommended driver (20.9.1). But also with this I had a crash for the same cause.

Attached you can find the dcs.log and .trk file of this newest CTD.

Hope you have some hints for solving this problem.

Best Regards,

Rene

dcs.log

dcs.20201030-153723.trk

Flappie · October 30, 2020

Hi. Your crash log indicates an issue wih compiled shaders. Try emptying your "fxo" and "metashaders2" folders in "C:\Users\your_names\Saved Games\DCS".

2020-10-30 15:37:03.378 ERROR GRAPHICSVISTA: Can't open model F-16C_oblomok_wing_L.
2020-10-30 15:37:03.378 ERROR GRAPHICSVISTA: Can't open model F-16C_oblomok_wing_R.
2020-10-30 15:37:19.862 ERROR GRAPHICSVISTA: Can't open model F-16C_oblomok_wing_L.
2020-10-30 15:37:23.345 INFO EDCORE: try to write dump information
2020-10-30 15:37:23.418 INFO EDCORE: # -------------- 20201030-153723 --------------
2020-10-30 15:37:23.461 INFO EDCORE: DCS/2.5.6.55960 (x86_64; Windows NT 10.0.18363)
2020-10-30 15:37:23.511 INFO EDCORE: C:\WINDOWS\System32\DriverStore\FileRepository\u0359160.inf_amd64_2abe2598d9a3141f\B358802\atidxx64.dll
2020-10-30 15:37:23.553 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 2FE0DF58 00:00000000
2020-10-30 15:37:23.603 INFO EDCORE: SymInit: Symbol-SearchPath: '.;F:\DCS World;F:\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'René'
2020-10-30 15:37:23.644 INFO EDCORE: OS-Version: 10.0.18363 () 0x100-0x1
2020-10-30 15:37:24.160 INFO EDCORE: 0x000000000004DF58 (atidxx64): XdxQueryTlsLookupTable + 0x313A8
2020-10-30 15:37:24.203 INFO EDCORE: 0x00000000008DABBF (atidxx64): AmdDxGsaFreeCompiledShader + 0x850CFF
2020-10-30 15:37:24.253 INFO EDCORE: 0x00000000008CEFC9 (atidxx64): AmdDxGsaFreeCompiledShader + 0x845109
2020-10-30 15:37:24.254 INFO EDCORE: 0x0000000000A80424 (atidxx64): AmdLiquidVrD3D11WrapDeviceContext + 0xA97A4
2020-10-30 15:37:24.254 INFO EDCORE: 0x0000000000017C24 (KERNEL32): BaseThreadInitThunk + 0x14
2020-10-30 15:37:24.255 INFO EDCORE: 0x000000000006D4D1 (ntdll): RtlUserThreadStart + 0x21
2020-10-30 15:37:24.456 INFO EDCORE: Minidump created.

Your Windows is a bit outdated by the way (November 2019). You should consider updating it.

Ithronwise · October 30, 2020

Hi Flappie,

I will try. But normally I clean these both folders everytime I change something in the DCS or Radeon settings (also when I install a new graphics driver). Windows 10, yeah I know, I am a little paranoid with these upgrades because there is a lot of issue reports every time Microsoft is "blessing" us with one of these upgrades, so I do it so rarely as possible. But I also will do it and hopefully it will resolve this problem. Thank you very much for your fast help.

Best regards,

Rene

Ithronwise · October 30, 2020

I have deleted the fxo and metashaders2 folder, upgraded my Windows 10 to version 20H2 (2004 wasn't offered anymore) but it crashed again, Su-33, Syria map, same mission.This time neither a .trk file nor a .crash file was written, only the dcs.log file (attached). It crashed to desktop without any error message.

dcs.log

Flappie · October 30, 2020

There's a more recent AMD driver available (not WHQL, though) if you want to give it a try: https://www.amd.com/en/support/graphics/amd-radeon-5700-series/amd-radeon-rx-5700-series/amd-radeon-rx-5700-xt

Can you please share screenshots of both your AMD and DCS graphical settings?

Ithronwise · October 30, 2020

Here they are (the Radeon settings are in german, sorry for that). I will try the newest AMD driver tomorrow. Thanks for your help.

Flappie · October 30, 2020

Please try disabling "AMD Enhanced Sync". A user has reported it made his game crash back in 2019. It's my only lead so far.

Ithronwise · October 31, 2020

Hi Flappie,

I disabled "Enhanced Sync" both at Global and DCS profile within the Radeon settings, deleted the fxo and the metashaders2 folders again, started the game, flew the same mission as before (Syria map, Su-33). More than 1 hour later I finished the mission by landing on the Kuznetsov with the last drop of fuel, folded the wings, rolled to the parking position and ... crash! Very frustrating.

Attached you can find the dcs.log and the dxdiag.txt (the .trk file is to large for upload).

Best regards,

René

dcs.20201031-100926.log

dxdiag.txt

Flappie · October 31, 2020

I understand your frustration. The error is different this time:

2020-10-31 10:06:06.041 INFO TACVIEW.DLL: Tacview recorder is taking 0.0% of CPU
2020-10-31 10:09:25.836 INFO EDCORE: try to write dump information
2020-10-31 10:09:26.067 INFO EDCORE: # -------------- 20201031-100926 --------------
2020-10-31 10:09:26.108 INFO EDCORE: DCS/2.5.6.55960 (x86_64; Windows NT 10.0.19042)
2020-10-31 10:09:26.150 INFO EDCORE: F:\DCS World\bin\DCS.exe
2020-10-31 10:09:26.191 INFO EDCORE: # C0000005 ACCESS_VIOLATION at 4C2819CF 00:00000000
2020-10-31 10:09:26.233 INFO EDCORE: SymInit: Symbol-SearchPath: '.;F:\DCS World;F:\DCS World\bin;C:\WINDOWS;C:\WINDOWS\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'René'
2020-10-31 10:09:26.275 INFO EDCORE: OS-Version: 10.0.19042 () 0x100-0x1
2020-10-31 10:09:26.792 INFO EDCORE: 0x00000000005819CF (DCS): CoreUtils::TempFilesManager::operator= + 0x213D9F
2020-10-31 10:09:26.833 INFO EDCORE: 0x000000000056EF8C (DCS): CoreUtils::TempFilesManager::operator= + 0x20135C
2020-10-31 10:09:26.875 INFO EDCORE: 0x000000000056F572 (DCS): CoreUtils::TempFilesManager::operator= + 0x201942
2020-10-31 10:09:26.876 INFO EDCORE: 0x000000000053AD28 (DCS): CoreUtils::TempFilesManager::operator= + 0x1CD0F8
2020-10-31 10:09:26.877 INFO EDCORE: 0x0000000000003B94 (World): wSimTrace::CommandsTraceDiscreteIsOn + 0x504
2020-10-31 10:09:26.877 INFO EDCORE: 0x000000000000403D (World): wSimCalendar: DoActionsUntil + 0x1FD
2020-10-31 10:09:26.878 INFO EDCORE: 0x0000000000711B7F (DCS): CoreUtils::TempFilesManager::operator= + 0x3A3F4F
2020-10-31 10:09:26.878 INFO EDCORE: 0x00000000007243D3 (DCS): CoreUtils::TempFilesManager::operator= + 0x3B67A3
2020-10-31 10:09:26.879 INFO EDCORE: 0x00000000006F6604 (DCS): CoreUtils::TempFilesManager::operator= + 0x3889D4
2020-10-31 10:09:26.879 INFO EDCORE: 0x00000000006F69C9 (DCS): CoreUtils::TempFilesManager::operator= + 0x388D99
2020-10-31 10:09:26.880 INFO EDCORE: 0x00000000016E8CEB (DCS): AmdPowerXpressRequestHighPerformance + 0xB1ACE7
2020-10-31 10:09:26.880 INFO EDCORE: 0x00000000008E261E (DCS): CoreUtils::TempFilesManager::operator= + 0x5749EE
2020-10-31 10:09:26.881 INFO EDCORE: 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
2020-10-31 10:09:26.881 INFO EDCORE: 0x000000000004CEC1 (ntdll): RtlUserThreadStart + 0x21
2020-10-31 10:09:27.029 INFO EDCORE: Minidump created.

If you keep experiencing these crashes, try each of the following steps separately (if 1 doesn't work, try 2, then 3):

1/ Disable mods (except Tacview, SRS and LotATC - these usually don't make DCS crash).

2/ Rename your "C:\Users\your_name\Saved Games\DCS" folder as "DCS_backup".

3/ Try the cleanup and repair procedure.

Ithronwise · November 1, 2020

Hi Flappie,

yesterday I deactivated all third party mods (these were A-4E-C by Heclak, Su-57 by Cubanace and some liveries for different aircraft types), then I flew the syria mission and had no crash. Today I activated the mods again (except Su-57 because I had installed it only for testing), flew the Syria mission and also had no crash. But in both cases the mission duration was a little shorter than one hour. Not sure whether duration time could be a factor.

What I did also yesterday was to increase the DRAM voltage from 1.2V (it was the auto setting in the BIOS) to 1.35V (the max. recommended voltage for my DRAM). I don't know whether to less DRAM voltage can cause such kind of crashes. I will keep it watching and testing. If this has solved my issue I will report to you. Thanks again for your help!

Best regards,

Rene

Flappie · November 1, 2020

Good. I hope it will be OK.

Before you changed the DRAM voltage, was your PC overclocked? (RAM, CPU or GPU)

Ithronwise · November 1, 2020

No it wasn't. My DRAM has a factory clock of 3000MHz. Before I upgraded it from 32GB to 64GB it ran with 3200MHz and 1.2V without any issues (all above 2666MHz is overclocking speed for my mainboard). After the upgrade it wasn't stable with this RAM clock and also with lower overclocking speed settings, even with 1.35V (Windows didn't start or crashed with bluescreens). I read that Ryzen processors don't like DRAM overclocking when all RAM banks are full, not sure if it's true. So I set the RAM to non-overclocking speed of 2666MHz with 1.2V. With this it was stable so it seemed. But maybe 1.2V is not enough for four 16GB DIMMs in some cases with high load.

The GPU runs with undervolting.

Ithronwise · November 15, 2020

Hi Flappie,

just for your information. The last two weeks I flew several missions in different aircrafts (A-10C-II, AV-8B, F-15C, F-16C, F/A-18C, Su-33) with mission durations between 45 and 90 minutes without any further CTDs. It seems the solution for my issue was a mix of graphic drivers update and DRAM voltage increasing.

Best regards,

Rene

Flappie · November 15, 2020

OK, thanks very much for your feedback! :thumbup:

Kevstosmart · November 16, 2020

Hey, OP what AMD drivers did you end up reverting back to, i uninstalled all my mods/ fresh install. and sometimes ill get a crash as well in relation to my gpu drivers

Ithronwise · December 3, 2020

Hi Kevstosmart,

sorry for my late answer. I didn't change back to an older driver. I used the 19.12.1 Radeon driver for a long time. After I ran into the described issue I tried the 20.9.1 WHQL driver but with the old Radeon GUI (not these Adrenalin GUI crap) because I need the Frame Rate Target Control setting, which isn't present in the Adrenalin GUI anymore although the function is still existing within the drivers. With the 20.9.1 driver and the increasing of the DRAM voltage the crashes are completely gone. I didn't try the newest WHQL driver (20.11.2) yet, You know, never change a running system.

Best regards,
Rene

Sign In

Sporadically crashes (graphics driver issues)

Recommended Posts

Ithronwise

Flappie

Ithronwise

Ithronwise

Flappie

Ithronwise

Flappie

Ithronwise

Flappie

Ithronwise

Flappie

Ithronwise

Ithronwise

Flappie

Kevstosmart

Ithronwise

Recently Browsing 0 members