DCS Open Beta Crashes to desktop when loading into Multiplayer

[VIGIT12]

Evening all,

Had an issue surface today where I select a server from the multiplayer server list. Loads as normal. get's to Post net mission start and then crashes to desktop. I am currently using this with an Oculus Quest 2.

I've never had a problem with DCS and nothing has really changed with my computer. All mods removed and a repair done as well. 

System Specs: Ryzen 7 5700x, RTX 3070, 16GB RAM, should meet all the specs!

 

 

dcs.log dcs.log.old

[Flappie]

Hi, the sim could not communicate with your GPU anymore (''DXGI_ERROR_DEVICE_REMOVED"):

2022-11-12 17:22:15.936 INFO    EDCORE (14136): try to write dump information
2022-11-12 17:22:15.941 INFO    EDCORE (14136): # -------------- 20221112-172216 --------------
2022-11-12 17:22:15.941 INFO    EDCORE (14136): DCS/2.8.0.32235 (x86_64; Windows NT 10.0.19044)
2022-11-12 17:22:15.942 INFO    EDCORE (14136): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\edCore.dll
2022-11-12 17:22:15.943 INFO    EDCORE (14136): # C0000005 ACCESS_VIOLATION at 88591749 00:00000000
2022-11-12 17:22:15.947 INFO    EDCORE (14300): try to write dump information
2022-11-12 17:22:15.949 INFO    EDCORE (14300): # -------------- 20221112-172216 --------------
2022-11-12 17:22:15.949 INFO    EDCORE (14300): DCS/2.8.0.32235 (x86_64; Windows NT 10.0.19044)
2022-11-12 17:22:15.949 INFO    EDCORE (14300): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\edCore.dll
2022-11-12 17:22:15.949 INFO    EDCORE (14300): # C0000005 ACCESS_VIOLATION at 88591749 00:00000000
2022-11-12 17:22:15.966 INFO    EDCORE (14300): SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'cmtur'
2022-11-12 17:22:15.967 WARNING LOG (6200): 1 duplicate message(s) skipped.
2022-11-12 17:22:15.967 INFO    EDCORE (14300): OS-Version: 10.0.19044 () 0x300-0x1
2022-11-12 17:22:15.997 WARNING LOG (6200): 1 duplicate message(s) skipped.
2022-11-12 17:22:15.997 INFO    EDCORE (10636): try to write dump information
2022-11-12 17:22:15.998 INFO    EDCORE (10636): # -------------- 20221112-172216 --------------
2022-11-12 17:22:15.998 INFO    EDCORE (10636): DCS/2.8.0.32235 (x86_64; Windows NT 10.0.19044)
2022-11-12 17:22:15.998 INFO    EDCORE (10636): C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\edCore.dll
2022-11-12 17:22:15.998 INFO    EDCORE (10636): # C0000005 ACCESS_VIOLATION at 88591749 00:00000000
2022-11-12 17:22:15.998 INFO    EDCORE (10636): SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'cmtur'
2022-11-12 17:22:15.998 INFO    EDCORE (10636): OS-Version: 10.0.19044 () 0x300-0x1
2022-11-12 17:22:16.213 ERROR   DX11BACKEND (3660): failed to create vertex buffer. Reason: E_OUTOFMEMORY
2022-11-12 17:22:16.213 ERROR   DX11BACKEND (3660): Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183
2022-11-12 17:22:16.214 ERROR   DX11BACKEND (9256): failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2022-11-12 17:22:16.214 ERROR   DX11BACKEND (9256): Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183
2022-11-12 17:22:16.213 ERROR   DX11BACKEND (15872): failed to create vertex buffer. Reason: E_OUTOFMEMORY
2022-11-12 17:22:16.215 ERROR   DX11BACKEND (15872): Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183
2022-11-12 17:22:16.215 ERROR   DX11BACKEND (3660): failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED
2022-11-12 17:22:16.215 ERROR   DX11BACKEND (3660): Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183

 

Seeing as you only have 8 GB of RAM, that could be the reason of the crash, say, if your memory was saturated at the moment of the crash.

Do you see any useful message in the Windows Event Viewer at the time of the crash?

[VIGIT12]

I think i may have figured the issue.... one of my RAM sticks was unseated so i was trying to run it with 8GB RAM. i will connect up and try again.

 

Thank you for taking the time to look into my issue.

Edited November 12, 2022 by VIGIT12

[VIGIT12]

Issue solved! RAM was seated incorrectly.

[Flappie]

Great, thanks for your feedback.