Multi-Threading Multiplayer Crashes

[AdrianL]

4 minutes ago, bravobuller said:

can anyone help me here

You are getting fatal 'out of memory' errors.

Increase your page file from its current 9 gig to 32 gig

Edited September 15, 2023 by AdrianL

[bravobuller]

16 hours ago, AdrianL said:

You are getting fatal 'out of memory' errors.

Increase your page file from its current 9 gig to 32 gig

 

will try do that.

my dcs is installed on my d-drive, with close 1.5tb free space. 32GB RAM in system.

is the d-drive the only drive, that i need to set up the page file? still got my saved games on c-drive

null

[Flappie]

We can see you have two pagefiles in the picture above, one on C and one on D. You only need one. You can choose whichever you like. It will make no difference if you choose the DCS drive or the system drive.

The only things that matter are the free space on the drive and its speed. You want to choose the fastest, with enough free space.

[lester]

Just got interesting OOM error on MP Syria server flying Viper, there was a dialog notifying that game crashed (and suggested to send report, which I did later), but the DCS process continued to run until I left the server.

dcs.log-20230917-062313.zip dcs.log

[Flappie]

At the risk of repeating myself, now that you have 64GB of RAM, you have too much pagefile:

2023-09-17 04:21:50.677 INFO    APP (Main): CPU cores: 8, threads: 16, System RAM: 65456 MB, Pagefile: 51200 MB

 And this below looks like a crash caused by an issue with the pagefile ("mmfMemoryBlockPrefetch"):

2023-09-17 06:23:12.302 INFO    ASYNCNET (Main): Current ping: 40.2ms
2023-09-17 06:23:13.676 INFO    EDCORE (27344): try to write dump information
2023-09-17 06:23:13.683 INFO    EDCORE (27344): # -------------- 20230917-062313 --------------
2023-09-17 06:23:13.684 INFO    EDCORE (27344): DCS/2.8.8.43704 (x86_64; MT; Windows NT 10.0.19045)
2023-09-17 06:23:13.685 INFO    EDCORE (27344): D:\games\dcs_world_open_beta\bin-mt\edCore.dll
2023-09-17 06:23:13.685 INFO    EDCORE (27344): # C0000005 ACCESS_VIOLATION at 00007ffe5349e4a5 00:00000000
2023-09-17 06:23:13.687 INFO    EDCORE (27344): SymInit: Symbol-SearchPath: 'D:\games\dcs_world_open_beta\bin-mt;', symOptions: 532, UserName: 'iv_ma'
2023-09-17 06:23:13.687 INFO    EDCORE (27344): OS-Version: 10.0.19045 () 0x300-0x1
2023-09-17 06:23:13.690 INFO    EDCORE (27344): 0x000000000006e4a5 (edCore): mmfMemoryBlockPrefetch + 0x95
2023-09-17 06:23:13.691 INFO    EDCORE (27344): 0x000000000006d47f (edCore): mmfMemoryBlockPreload + 0x2F
2023-09-17 06:23:13.692 INFO    EDCORE (27344): 0x0000000000253993 (edterrain4): landscape5::Surface5File::Square::preload + 0x233
2023-09-17 06:23:13.692 INFO    EDCORE (27344): 0x000000000006be9d (edterrainGraphics41): edtg41::TerrainRenderable::dumpRenderItem + 0x56AFD
2023-09-17 06:23:13.692 INFO    EDCORE (27344): 0x0000000000033c39 (edCore): ed::this_thread::yield + 0xB59
2023-09-17 06:23:13.692 INFO    EDCORE (27344): 0x0000000000049228 (edCore): ed::this_thread::yield + 0x16148
2023-09-17 06:23:13.692 INFO    EDCORE (27344): 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71
2023-09-17 06:23:13.693 INFO    EDCORE (27344): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
2023-09-17 06:23:13.693 INFO    EDCORE (27344): 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14

Since you now have 64GB of RAM, DCS don't need a big pagefile anymore. Let Windows handle the pagefile size automatically, as explained here:

Windows will probably give you the default 4GB pagefile. Once this is done, I think your DCS won't get the "mmfMemoryBlockPrefetch" crash anymore.

Edited September 17, 2023 by Flappie

[lester]

Shoot, I did change the pagefile settings back to default as you suggested, but it looks like they haven't not been actually applied until the OS restart (which I thought I did at the time of error, but it obviously didn't happen looking at the logs). My apologies and thank you for your time @Flappie !

[Flappie]

You're welcome.

Tell us whether that solves the problem or not.

[lester]

Hey @Flappie. Now with pagefile settings set to default for sure, I got crash in 2.9 MT while flying in a Viper on a multiplayer server. Looks like it's familiar ACCESS_VIOLATION memory error. Please find the logs attached (also sent crash report), hope it might help.

dcs.log dcs.log-20231031-061115.zip

[Flappie]

Hey. The "ACCESS_VIOLATION" keyword doesn't say much unfortunately.

2023-10-31 06:11:14.793 INFO    EDCORE (18536): try to write dump information
2023-10-31 06:11:14.809 INFO    EDCORE (18536): # -------------- 20231031-061115 --------------
2023-10-31 06:11:14.809 INFO    EDCORE (18536): DCS/2.9.0.47168 (x86_64; MT; Windows NT 10.0.19045)
2023-10-31 06:11:14.810 INFO    EDCORE (18536): C:\Windows\SYSTEM32\d3d11.dll
2023-10-31 06:11:14.811 INFO    EDCORE (18536): # C0000005 ACCESS_VIOLATION at 00007ff9a13007fb 00:00000000
2023-10-31 06:11:14.812 INFO    EDCORE (18536): SymInit: Symbol-SearchPath: 'D:\games\dcs_world_open_beta\bin-mt;', symOptions: 532, UserName: 'iv_ma'
2023-10-31 06:11:14.813 INFO    EDCORE (18536): OS-Version: 10.0.19045 () 0x300-0x1
2023-10-31 06:11:14.815 INFO    EDCORE (18536): 0x00000000001307fb (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0x1735B
2023-10-31 06:11:14.815 INFO    EDCORE (18536): 0x000000000012874d (d3d11): CreateDirect3D11SurfaceFromDXGISurface + 0xF2AD
2023-10-31 06:11:14.817 INFO    EDCORE (18536): 0x0000000000018e9c (dx11backend): RenderAPI::DX11Renderer::setShaderResources + 0xCC
2023-10-31 06:11:14.817 INFO    EDCORE (18536): 0x0000000000065b8d (dx11backend): createRenderer + 0x4C45D
2023-10-31 06:11:14.817 INFO    EDCORE (18536): 0x0000000000065449 (dx11backend): createRenderer + 0x4BD19
2023-10-31 06:11:14.817 INFO    EDCORE (18536): 0x0000000000062ba9 (dx11backend): createRenderer + 0x49479
2023-10-31 06:11:14.817 INFO    EDCORE (18536): 0x000000000001300b (dx11backend): RenderAPI::DX11Renderer::draw + 0x36B
2023-10-31 06:11:14.817 INFO    EDCORE (18536): 0x000000000000dfd5 (NGModel): cloth::FlagModel::getCollisionShellId + 0x1E15
2023-10-31 06:11:14.817 INFO    EDCORE (18536): 0x000000000000e4b8 (NGModel): model::DeckMaterialMT::draw + 0x4B8
2023-10-31 06:11:14.818 INFO    EDCORE (18536): 0x000000000003c839 (NGModel): model::NGModelLodsMT::testWithSegment + 0x7D9
2023-10-31 06:11:14.818 INFO    EDCORE (18536): 0x00000000000a0d6c (GraphicsCore): render::ShadowMapModule::queryCasters + 0xA0C
2023-10-31 06:11:14.818 INFO    EDCORE (18536): 0x0000000000053bef (GraphicsCore): render::BaseRenderingPass::execute + 0x1F
2023-10-31 06:11:14.818 INFO    EDCORE (18536): 0x00000000000542fc (GraphicsCore): render::BaseRenderingPass::execute + 0x72C
2023-10-31 06:11:14.818 INFO    EDCORE (18536): 0x0000000000058b3d (GraphicsCore): render::RenderGraph::render + 0x11D
2023-10-31 06:11:14.818 INFO    EDCORE (18536): 0x000000000001b7f2 (SceneRenderer): DCSSceneRenderer::renderBakedRenderGraph + 0x42
2023-10-31 06:11:14.818 INFO    EDCORE (18536): 0x0000000000150d31 (Visualizer): smSceneManager::regLua + 0x12A1
2023-10-31 06:11:14.818 INFO    EDCORE (18536): 0x000000000013c7d9 (Visualizer): smCamera_Implement::getClipRegion + 0x19459
2023-10-31 06:11:14.819 INFO    EDCORE (18536): 0x0000000000128736 (Visualizer): smCamera_Implement::getClipRegion + 0x53B6
2023-10-31 06:11:14.819 INFO    EDCORE (18536): 0x000000000013fbd2 (Visualizer): smSceneManager::DestroySceneManager + 0x13D2
2023-10-31 06:11:14.819 INFO    EDCORE (18536): 0x00000000000335b1 (edCore): ed::thread::_get_current_thread_id + 0x71
2023-10-31 06:11:14.819 INFO    EDCORE (18536): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
2023-10-31 06:11:14.819 INFO    EDCORE (18536): 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14
2023-10-31 06:11:15.040 INFO    EDCORE (18536): Minidump created.

The crash was seemingly caused by a problem during 3D rendering of the scene.

Try this:

1. Uninstall your graphic driver using DDU.
2. Reboot your PC.
3. Install a fresh GPU driver.
4. If crashes keep happening, try NVIDIA control panel "Debug" mode (Help > Debug).