Akula108

I am happy to share that after disabling the in-game overlay of GeForce Experience, I have been able to play DCS on Multithreading for the past two days in single-player and multi-player without any crash issues.

Hi, I haven't had any stability issues after disabling the in-game overlay in GeForce Experience, I was able to play for about four hours last night without issues. I can't say for sure whether its a reliable fix as I have only about one day of stable gameplay on multiplayer using the multi-threaded build. One note, I read a comment from a forum user long ago saying each time you change your in-game graphics, to delete and and rebuild the files inside fxo and metashaders. I also suggest taking a look at this article provided by another forum user that has some additional possible solutions if you find DXGI_ERROR_DEVICE_REMOVED in your dcs.log. https://thegeekpage.com/dxgi-error-device-removed/

Update: I seem to have isolated the crashing to the GeForce experience app but only with the in-game overlay enabled, quite unfortunate as I wanted to use that as my main source of recording and measuring performance metrics. I don't really know what causes the app to conflict with DCS.

Hello SpecialK, I ran the registry fix and uninstalled geforce experience and one of the two seems to have fixed the issue. Thank you for the registry suggestion as I would not have thought of it myself. I will keep monitoring gameplay for the next day or two before marking an answer and closing the thread. So far, I have been able to play two multiplayer lives with almost all graphics turned up.

I've ran DDU already but I have not tried modifying my registry, I will try these and post here again.

Update: Rebuilt C drive files and still crashes, at this point I'm just considering waiting for the next openbeta patch to see if the issue is resolved. I could run the last multithreaded patch just fine.

Hello Killferus, you and I seem to be having a similar issue. I also just recently built a new PC for sim gaming and I also crash non-stop using the normal build and the multithreaded build. DCS is also the only game that acts up on my PC. The contents/output of your crash log are almost identical to mine. Would you be so kind to check the thread I have created a few days ago to see if your issue is similar to mine?

I just tried playing the MT client after patching to the latest hotfix deployed this morning. Game crashed instantly once I loaded into the cockpit of the F/A-18C. Crash log output is the same, attached below. # -------------- 20230505-082722 -------------- DCS/2.8.4.39731 (x86_64; MT; Windows NT 10.0.22621) C:\Windows\SYSTEM32\d3d11.dll # C0000005 ACCESS_VIOLATION at 00007ff9cf4059b5 00:00000000 SymInit: Symbol-SearchPath: 'D:\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'David' OS-Version: 10.0.22621 () 0x100-0x1 0x00000000001059b5 (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0x10535 0x000000000002db61 (dx11backend): createRenderer + 0x15C51 0x000000000007edcb (edterrainGraphics41): edtg41::TerrainRenderable::dumpRenderItem + 0x69A2B 0x00000000000d630c (edterrainGraphics41): createInstancerRenderable + 0x3885C 0x0000000000033678 (edCore): ed::this_thread::yield + 0x598 0x000000000002448a (edCore): ed::make_render_thread_tasks + 0x1A 0x0000000000107106 (Visualizer): smCamera_Implement::getClipRegion + 0x16996 0x00000000000f6a16 (Visualizer): smCamera_Implement::getClipRegion + 0x62A6 0x000000000010a0f2 (Visualizer): smSceneManager::DestroySceneManager + 0x1542 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71 0x0000000000029363 (ucrtbase): _recalloc + 0xA3 0x00000000000126ad (KERNEL32): BaseThreadInitThunk + 0x1D dcs.20230505-082722.crash

Update to this thread, the crashing persists after a ~15 minute session yesterday. I have not tested the new openbeta hotfix (will try later this evening) and update this thread again. The crash log output was identical to the most recent one I posted two days ago. "0x00000000001059b5 (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0x10535"

I have ran both files, indeed the file named "vc_redist.x64" fails to run properly, and the file named "vcredist_x64" allows me to uninstall or repair, I checked repair and I will post my findings in game soon.

I have just experienced another crash in MP using the MT build, this time I crashed within minutes of joining the 4YA PVE servers. Crash log output was different this time. Text pasted below and log attached. # -------------- 20230503-093428 -------------- DCS/2.8.4.39313 (x86_64; MT; Windows NT 10.0.22621) C:\Windows\SYSTEM32\d3d11.dll # C0000005 ACCESS_VIOLATION at 00007fff304859b5 00:00000000 SymInit: Symbol-SearchPath: 'D:\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'David' OS-Version: 10.0.22621 () 0x100-0x1 0x00000000001059b5 (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0x10535 0x0000000000042270 (dx11backend): createRenderer + 0x2A360 0x0000000000005422 (dxgui_edge_render): (function-name not available) + 0x0 0x00000000000054b5 (dxgui_edge_render): (function-name not available) + 0x0 0x0000000000019a68 (dxgui): gui::getWidgetCallbackType + 0x4D8 0x000000000001d09e (dxgui): gui::GUI::doRedraw + 0x2E 0x000000000011de90 (Visualizer): smSceneManager::regLua + 0x46D0 0x0000000000107121 (Visualizer): smCamera_Implement::getClipRegion + 0x16A31 0x00000000000f6996 (Visualizer): smCamera_Implement::getClipRegion + 0x62A6 0x000000000010a072 (Visualizer): smSceneManager::DestroySceneManager + 0x1542 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71 0x0000000000029363 (ucrtbase): _recalloc + 0xA3 0x00000000000126ad (KERNEL32): BaseThreadInitThunk + 0x1D dcs.20230503-093428.crash

CPU and GPU both remain under 55C.

Update: After a one hour session, the crashes have returned. However I have noticed that once the first crash happens, any time I relaunch and play the game, I can only stay in single player or multiplayer for around 10 minutes before another crash appears. Latest crash log attached, output is basically the same. "ComputeOptimalBarriers" still present. # -------------- 20230503-014114 -------------- DCS/2.8.4.39313 (x86_64; MT; Windows NT 10.0.22621) D:\Eagle Dynamics\DCS World OpenBeta\bin-mt\GraphicsCore.dll # C0000005 ACCESS_VIOLATION at 00007ffa173de168 00:00000000 SymInit: Symbol-SearchPath: 'D:\Eagle Dynamics\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'David' OS-Version: 10.0.22621 () 0x100-0x1 0x000000000003e168 (GraphicsCore): render::RenderGraph::~RenderGraph + 0x2E48 0x0000000000041fd3 (GraphicsCore): render::RenderGraph::computeOptimalBarriers + 0x403 0x0000000000041ace (GraphicsCore): render::RenderGraph::bakeGraph + 0x18FE 0x000000000000e20f (SceneRenderer): DCSSceneRenderer::bakeRenderGraph + 0x3F 0x0000000000107f27 (Visualizer): smCamera_Implement::getClipRegion + 0x17837 0x00000000000483fb (edCore): ed::this_thread::yield + 0x1531B 0x00000000000476d2 (edCore): ed::this_thread::yield + 0x145F2 0x0000000000048f73 (edCore): ed::this_thread::yield + 0x15E93 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71 0x0000000000029363 (ucrtbase): _recalloc + 0xA3 0x00000000000126ad (KERNEL32): BaseThreadInitThunk + 0x1D dcs.20230503-014114.crash

Update to this thread, I may have what was causing the persistent crashes. First off, my windows power plan was set to "Balanced" though I do remember picking the "High Performance" option, a windows update may have reverted this change. Secondly, I uninstalled all additional terrains only leaving Caucasus and Marianas, One of these two changes has allowed me to play multiplayer on MT build for a 35 minute session (before being pulled away by work)without crashing. I will continue to monitor later this evening.

Unfortunately I have submitted a ticket but it seemed like support was unable to get anywhere either so created this post afterwards. However, I was able to find another thread mentioning "RenderGraph::computeOptimalBarriers", supposedly it was fixed in a patch but it seems like users are still experiencing the issue, however the thread leads to a dead end as there are no suggested fixes. The Crash log's output in that thread are basically identical to the output of my own crash log. I am still crashing on MT and ST after testing this morning.