Jump to content

Recommended Posts

Posted

I am playing fine with the single thread. But when i open the game from bin-mt folder after a while game crashes without error code or anything. I am not using vr.

Posted

I am not using any PCI risers and i didnt changed any priority settings. Also how can i find my dcs log file it could could help

Posted
40 minutes ago, =BK=Chekist [39] said:

 The game crashes after a few hours of play MT (This log on Mi-24). Can you help me?
dcs.log-20230605-201743.zip

It looks like you encountered Petrovich crash bug here:

 

It's reported. We need to wait for a fix. In the meantimme, use Petrovich as less as possible... 😐

  • Thanks 1

---

Posted (edited)

Hey. I got crash in the most recent MT OB while playing on multiplayer server on Syria map. It looks like the reason is out of memory error (in the attachments). I have 32GB of RAM and 64GB pagefile size. I'm curious whether it's not enough?

dcs.20230604-203356.crash dcs.20230604-203356.dmp

Edited by lester

Все написанное выше является моим оценочным суждением

Everything written above reflects my personal opinion

 

Занимаюсь "активной пропагандой Американцев на данном форуме" © Flanker

Posted

Attached dcs logs, but unfortunately they might have been already overwritten.

dcs.log.old dcs.log DxDiag.txt

Все написанное выше является моим оценочным суждением

Everything written above reflects my personal opinion

 

Занимаюсь "активной пропагандой Американцев на данном форуме" © Flanker

Posted

They show no sign of a crash, indeed. But at least, I can see DCS recognizes the 64 GB pagefile. You don't need that much, by the way. 32GB of pagefile should be enough.

If you get another crash, please attach your latest dcs.log file along with your latest zip (from the Logs folder too).

  • Thanks 1

---

Posted

Hi, this time its not about the Petrovitch bug:

2023-06-12 12:04:06.504 INFO    ASYNCNET (Main): Current ping: 10.3ms
2023-06-12 12:04:36.510 INFO    ASYNCNET (Main): Current ping: 10.4ms
2023-06-12 12:05:00.083 INFO    EDCORE (5228): try to write dump information
2023-06-12 12:05:00.112 INFO    EDCORE (5228): # -------------- 20230612-120500 --------------
2023-06-12 12:05:00.112 INFO    EDCORE (5228): DCS/2.8.6.41066 (x86_64; MT; Windows NT 10.0.19045)
2023-06-12 12:05:00.113 INFO    EDCORE (5228): E:\DCS World OpenBeta\bin-mt\Visualizer.dll
2023-06-12 12:05:00.113 INFO    EDCORE (5228): # C0000005 ACCESS_VIOLATION at 00007ff93f5d795c 00:00000000
2023-06-12 12:05:00.113 INFO    EDCORE (5228): SymInit: Symbol-SearchPath: 'E:\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'dimle'
2023-06-12 12:05:00.113 INFO    EDCORE (5228): OS-Version: 10.0.19045 () 0x100-0x1
2023-06-12 12:05:00.114 INFO    EDCORE (5228): 0x000000000011795c (Visualizer): smSceneManager::DestroySceneManager + 0x1072C
2023-06-12 12:05:00.115 INFO    EDCORE (5228): 0x000000000011c385 (Visualizer): smSceneManager::regLua + 0x4635
2023-06-12 12:05:00.115 INFO    EDCORE (5228): 0x0000000000105821 (Visualizer): smCamera_Implement::getClipRegion + 0x16931
2023-06-12 12:05:00.116 INFO    EDCORE (5228): 0x00000000000f5196 (Visualizer): smCamera_Implement::getClipRegion + 0x62A6
2023-06-12 12:05:00.116 INFO    EDCORE (5228): 0x0000000000108792 (Visualizer): smSceneManager::DestroySceneManager + 0x1562
2023-06-12 12:05:00.116 INFO    EDCORE (5228): 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71
2023-06-12 12:05:00.116 INFO    EDCORE (5228): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
2023-06-12 12:05:00.117 INFO    EDCORE (5228): 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14
2023-06-12 12:05:00.368 INFO    EDCORE (5228): Minidump created.

 

So far, I don't have many ideas.

I see in your dxdiag log that your motherboard has an active internal GPU. Sometimes, internal GPUs interfere with discreet GPUs, and I think we should check if that is the problem here.

Three solutions: you can either tell Windows or MSI (or both) to avoid using the internal GPU, or simply disable the internal GPU in your motherboard BIOS (look for the "How To Disable Onboard Graphics In Bios MSI" section).

You dxdiag log also shows that a Logitech utility is often crashing: "lghub_updater.exe". Unless you update your Logitech software on a weekly or monthly basis, I recommend you deactivate it.

 

  • Like 1

---

  • 3 weeks later...
Posted

Hey @Flappie. Look like I got memory error (ACCESS_VIOLATION) on MT Syria map on multiplayer server when flying Apache. Attached both generated zip and log file.

dcs.log-20230703-063100.zip dcs.log

Все написанное выше является моим оценочным суждением

Everything written above reflects my personal opinion

 

Занимаюсь "активной пропагандой Американцев на данном форуме" © Flanker

Posted

Thank you, @lester. It looks like this:

2023-07-03 06:30:47.407 INFO    ASYNCNET (Main): Current ping: 44.2ms
2023-07-03 06:30:59.648 INFO    EDCORE (32492): try to write dump information
2023-07-03 06:30:59.669 INFO    EDCORE (32492): # -------------- 20230703-063100 --------------
2023-07-03 06:30:59.670 INFO    EDCORE (32492): DCS/2.8.6.41363 (x86_64; MT; Windows NT 10.0.19045)
2023-07-03 06:30:59.671 INFO    EDCORE (32492): D:\games\dcs_world_open_beta\bin-mt\ModelDesc.dll
2023-07-03 06:30:59.672 INFO    EDCORE (32492): # C0000005 ACCESS_VIOLATION at 00007ffa60b76514 00:00000000
2023-07-03 06:30:59.673 INFO    EDCORE (32492): SymInit: Symbol-SearchPath: 'D:\games\dcs_world_open_beta\bin-mt;', symOptions: 532, UserName: 'iv_ma'
2023-07-03 06:30:59.674 INFO    EDCORE (32492): OS-Version: 10.0.19045 () 0x300-0x1
2023-07-03 06:30:59.675 INFO    EDCORE (32492): 0x0000000000016514 (ModelDesc): model::Node::hasAnimation + 0xD4
2023-07-03 06:30:59.676 INFO    EDCORE (32492): 0x000000000001650b (ModelDesc): model::Node::hasAnimation + 0xCB
2023-07-03 06:30:59.678 WARNING LOG (10192): 8 duplicate message(s) skipped.
2023-07-03 06:30:59.678 INFO    EDCORE (32492): 0x0000000000016190 (ModelDesc): model::LightNode::getVisibility + 0x860
2023-07-03 06:30:59.678 INFO    EDCORE (32492): 0x00000000000163b3 (ModelDesc): model::LightNode::getVisibility + 0xA83
2023-07-03 06:30:59.678 INFO    EDCORE (32492): 0x0000000000024b73 (NGModel): model::GRootNodeMT::applyMults + 0x5E3
2023-07-03 06:30:59.678 INFO    EDCORE (32492): 0x0000000000027ab4 (NGModel): model::GRootNodeMT::loadTextures + 0x9C4
2023-07-03 06:30:59.679 INFO    EDCORE (32492): 0x0000000000035352 (NGModel): model::NGModelLodsMT::ParseMT2 + 0x4D2
2023-07-03 06:30:59.679 INFO    EDCORE (32492): 0x0000000000035211 (NGModel): model::NGModelLodsMT::ParseMT2 + 0x391
2023-07-03 06:30:59.679 INFO    EDCORE (32492): 0x000000000000b1e6 (GraphicsVista): Graphics::GraphSceneObject::collectRenderables + 0x8A6
2023-07-03 06:30:59.680 INFO    EDCORE (32492): 0x0000000000003381 (Scene): (function-name not available) + 0x0
2023-07-03 06:30:59.680 INFO    EDCORE (32492): 0x000000000001515e (Scene): Graphics::SceneBase<DCSDemoSceneCollections::ObjectCollections,DCSDemoSceneCollections::LightCollections>::allowSceneWriteAccess + 0x7FE
2023-07-03 06:30:59.680 INFO    EDCORE (32492): 0x00000000000488f1 (edCore): ed::this_thread::yield + 0x15811
2023-07-03 06:30:59.681 INFO    EDCORE (32492): 0x000000000009ce21 (GraphicsCore): Graphics::SceneAggregator::collectRenderablesAggregated + 0x941
2023-07-03 06:30:59.681 INFO    EDCORE (32492): 0x0000000000118be3 (Visualizer): smSceneManager::regLua + 0xE93
2023-07-03 06:30:59.681 INFO    EDCORE (32492): 0x0000000000105829 (Visualizer): smCamera_Implement::getClipRegion + 0x16939
2023-07-03 06:30:59.681 INFO    EDCORE (32492): 0x00000000000f5196 (Visualizer): smCamera_Implement::getClipRegion + 0x62A6
2023-07-03 06:30:59.681 INFO    EDCORE (32492): 0x0000000000108792 (Visualizer): smSceneManager::DestroySceneManager + 0x1562
2023-07-03 06:30:59.681 INFO    EDCORE (32492): 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71
2023-07-03 06:30:59.682 INFO    EDCORE (32492): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
2023-07-03 06:30:59.682 INFO    EDCORE (32492): 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14
2023-07-03 06:30:59.947 INFO    EDCORE (32492): Minidump created.

 

Many users have been witnessing a lot of freezes and crashes since the latest OB (2.8.6.41363). Some of us think these crashes may happen when Intel Hyperthreading is enabled (and maybe SMT for AMD users but this is yet to be tested).

If these crashes happen often, try disabling Hyper Threading in your PC BIOS, or stick to DCS ST until this is fixed.

  • Thanks 1

---

  • 3 weeks later...
Posted (edited)

Hey @Flappie . Decided to post another OOM crash I got on MP server flying Hornet on Marianas map as I think looking into log this error is a bit different from the previous one.

2023-07-24 03:06:48.849 ERROR   DX11BACKEND (18824): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_PILOT_HELMET_NORMAL.dds. Reason: Not enough memory resources are available to complete this operation.
2023-07-24 03:06:48.864 ERROR   DX11BACKEND (18824): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_PILOT_HELMET_RoughMet.dds. Reason: Not enough memory resources are available to complete this operation.
2023-07-24 03:06:48.876 ERROR   DX11BACKEND (18824): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_RIO_HELMET.dds. Reason: Not enough memory resources are available to complete this operation.
2023-07-24 03:06:48.893 ERROR   DX11BACKEND (18824): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_RIO_HELMET_NORMAL.dds. Reason: Not enough memory resources are available to complete this operation.
2023-07-24 03:06:48.906 ERROR   DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_RIO_HELMET_RoughMet.dds'. Reason: The request is not supported.
2023-07-24 03:06:48.906 ERROR   EDCORE (18824): More out of memory in ed_malloc for 16777444 bytes.
2023-07-24 03:06:48.906 ERROR   EDCORE (18824): More out of memory in SharedBuffer for 16777412 bytes.
2023-07-24 03:06:48.906 ERROR   EDCORE (18824): Not enough memory to decompress: HB_F14_LOD1_3in1.dds
2023-07-24 03:06:48.906 ERROR   DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_LOD1_3in1.dds'. Reason: The parameter is incorrect.
2023-07-24 03:06:48.906 ERROR   EDCORE (18824): More out of memory in ed_malloc for 16777444 bytes.
2023-07-24 03:06:48.906 ERROR   EDCORE (18824): More out of memory in SharedBuffer for 16777412 bytes.
2023-07-24 03:06:48.906 ERROR   EDCORE (18824): Not enough memory to decompress: HB_F14_LOD1_3in1_RoughMet.dds
2023-07-24 03:06:48.907 ERROR   DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_LOD1_3in1_RoughMet.dds'. Reason: The parameter is incorrect.
2023-07-24 03:06:48.921 ERROR   DX11BACKEND (18824): Failed to create shader resource view for /textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_EXT_PILOT_SUIT.dds. Reason: Not enough memory resources are available to complete this operation.
2023-07-24 03:06:48.925 ERROR   EDCORE (18824): More out of memory in ed_malloc for 22369828 bytes.
2023-07-24 03:06:48.925 ERROR   EDCORE (18824): More out of memory in SharedBuffer for 22369796 bytes.
2023-07-24 03:06:48.925 ERROR   EDCORE (18824): Not enough memory to decompress: HB_F14_TF30_A.dds
2023-07-24 03:06:48.925 ERROR   DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_TF30_A.dds'. Reason: The parameter is incorrect.
2023-07-24 03:06:48.926 ERROR   EDCORE (18824): More out of memory in ed_malloc for 22369828 bytes.
2023-07-24 03:06:48.926 ERROR   EDCORE (18824): More out of memory in SharedBuffer for 22369796 bytes.
2023-07-24 03:06:48.926 ERROR   EDCORE (18824): Not enough memory to decompress: HB_F14_TF30_A_RoughMet.dds
2023-07-24 03:06:48.926 ERROR   DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_TF30_A_RoughMet.dds'. Reason: The parameter is incorrect.
2023-07-24 03:06:48.954 ERROR   EDCORE (30100): More out of memory in ed_malloc for 12198088 bytes.

 

dcs.log-20230724-030646.zip dcs.log

Edited by lester

Все написанное выше является моим оценочным суждением

Everything written above reflects my personal opinion

 

Занимаюсь "активной пропагандой Американцев на данном форуме" © Flanker

Posted

It looks like a memory issue. To be more precise, it looks like a pagefile issue. Ensure you have sufficient free space in your drives (~50GB per drive).

If you do, maybe the drive that hosts tbe pagefile is faulty. Try a chkdsk.

2023-07-24 03:06:45.996 ERROR   DX11BACKEND (18824): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_WING_RIGHT.dds'. Reason: The request is not supported.
2023-07-24 03:06:46.022 ERROR   DX11BACKEND (30100): Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_WING_RIGHT_RoughMet.dds'. Reason: The request is not supported.
2023-07-24 03:06:46.055 ALERT   EDCORE (30100): Out of memory in ed_malloc for 22369828 bytes.
2023-07-24 03:06:46.056 INFO    EDCORE (30100): try to write dump information
2023-07-24 03:06:46.065 INFO    EDCORE (30100): # -------------- 20230724-030646 --------------
2023-07-24 03:06:46.066 INFO    EDCORE (30100): DCS/2.8.6.41363 (x86_64; MT; Windows NT 10.0.19045)
2023-07-24 03:06:46.067 INFO    EDCORE (30100): D:\games\dcs_world_open_beta\bin-mt\edCore.dll
2023-07-24 03:06:46.068 INFO    EDCORE (30100): # 80000003 BREAKPOINT at 00007ffbd0e576bb 00:00000000
2023-07-24 03:06:46.069 INFO    EDCORE (30100): SymInit: Symbol-SearchPath: 'D:\games\dcs_world_open_beta\bin-mt;', symOptions: 532, UserName: 'iv_ma'
2023-07-24 03:06:46.070 INFO    EDCORE (30100): OS-Version: 10.0.19045 () 0x300-0x1
2023-07-24 03:06:46.073 INFO    EDCORE (30100): 0x00000000000276bb (edCore): ed::fatal_out_of_memory + 0x3B
2023-07-24 03:06:46.074 INFO    EDCORE (30100): 0x0000000000022c77 (edCore): ed::SharedBuffer::create + 0x37
2023-07-24 03:06:46.075 INFO    EDCORE (30100): 0x000000000005e658 (edCore): edvfs::FSMappedFile::tell + 0x10A8
2023-07-24 03:06:46.075 INFO    EDCORE (30100): 0x000000000005e42c (edCore): edvfs::FSMappedFile::tell + 0xE7C
2023-07-24 03:06:46.075 INFO    EDCORE (30100): 0x0000000000055533 (edCore): CoreUtils::TempFilesManager::TempFilesManager + 0x3BB3
2023-07-24 03:06:46.076 INFO    EDCORE (30100): 0x000000000000752a (renderer): render::openFirstOccurrence + 0x8A
2023-07-24 03:06:46.076 INFO    EDCORE (30100): 0x0000000000062e57 (dx11backend): createRenderer + 0x4AF47
2023-07-24 03:06:46.076 INFO    EDCORE (30100): 0x00000000000662eb (dx11backend): createRenderer + 0x4E3DB
2023-07-24 03:06:46.076 INFO    EDCORE (30100): 0x0000000000036305 (dx11backend): createRenderer + 0x1E3F5
2023-07-24 03:06:46.076 INFO    EDCORE (30100): 0x0000000000033c39 (edCore): ed::this_thread::yield + 0xB59
2023-07-24 03:06:46.076 INFO    EDCORE (30100): 0x0000000000049228 (edCore): ed::this_thread::yield + 0x16148
2023-07-24 03:06:46.076 INFO    EDCORE (30100): 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71
2023-07-24 03:06:46.090 INFO    EDCORE (30100): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
2023-07-24 03:06:46.091 INFO    EDCORE (30100): 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14
2023-07-24 03:06:46.096 INFO    EDCORE (30100): MiniDumpWriteDump failed. Error: 2147943855 

 

  • Thanks 1

---

Posted
10 hours ago, Flappie said:

It looks like a memory issue. To be more precise, it looks like a pagefile issue. Ensure you have sufficient free space in your drives (~50GB per drive).

If you do, maybe the drive that hosts tbe pagefile is faulty. Try a chkdsk.

Interesting. I definitely have ~300GB free on both of my M2 NVMe drives. But as you wrote maybe it's my local thing (also it seems it's time to upgrade 32GB RAM -> 64 GB RAM).

Thanks for checking!

Все написанное выше является моим оценочным суждением

Everything written above reflects my personal opinion

 

Занимаюсь "активной пропагандой Американцев на данном форуме" © Flanker

Posted (edited)

@Flappie Got another OOM error on the same MP server flying Strike Eagle on Marianas map.

Wanted to confirm: in both this log and the one in the previous message I see log entries related to Heatblur F-14 like:

Can't load image '/textures/liveries/f-14a-135-gr/vf-301 nd111/HB_F14_<something>

interleaved with out-of-memory errors. Are they unrelated?

It's also interesting that I don't get such errors flying on the same server, but on maps different from Marianas (which is indeed resource-heavy map).
UPDATE: actually just got another OOM error flying Apache on Syria map on the same server (see my message below).

I checked both my disks with chkdsk as you suggested, no issues found (see attached output). I have 32 GB RAM of physical memory and 64GB pagefile (see screenshot).

I thought it should be enough even for Marianas?

Thanks!

pagefile.png

dcs.log dcs.20230726-030837.crash dcs.20230726-030837.dmp chkdsk_output.txt

Edited by lester

Все написанное выше является моим оценочным суждением

Everything written above reflects my personal opinion

 

Занимаюсь "активной пропагандой Американцев на данном форуме" © Flanker

Posted (edited)

And just got another OOM error flying Apache on Syria map on the same server (I was switching between looking at F15SE on F2 view flying overhead and F10 map at the moment of a crash). I'm curious can it be a problem with physical RAM on my machine...

I see other reports about crashes in the most recent OB though:

I did delete fxo and metashaders2 folders (I do it every time after the update).

dcs.20230726-043434.crash dcs.log

Edited by lester

Все написанное выше является моим оценочным суждением

Everything written above reflects my personal opinion

 

Занимаюсь "активной пропагандой Американцев на данном форуме" © Flanker

Posted (edited)

Okay, I got a lot of OOM crashes recently, I even tried a different multiplayer server. No errors in single player so far.

The bad part of it is: it made DCS unplayable in multiplayer for me, the good part: my new 64GB RAM arriving tomorrow so hopefully these OOM errors should be gone.

It's probably caused my RAM given that I don't see a lot of other reports, the only thing disturbing me is that number of these OOM errors grew exponentially for me since the latest OB.

Attaching two recent crash logs when I flew on 2 different servers just in case (first Apache on PG map, second Strike Eagle on Caucasus map), because in both cases proper zip files were generated and they probably contain more information than in previous messages. For the second one it seems DCS process was still alive even after error message had been displayed until I pressed the button to send crash report.

 

dcs.log-20230728-004708.zip dcs.log-20230728-021820.zip dcs.log

Edited by lester

Все написанное выше является моим оценочным суждением

Everything written above reflects my personal opinion

 

Занимаюсь "активной пропагандой Американцев на данном форуме" © Flanker

  • 1 month later...
Posted

@Flappie After upgrading to 64GB of RAM got first OOM error on multiplayer server Syria map flying Apache. Pagefile settings are the same as above.

dcs.20230912-063313.crash dcs.20230912-063313.dmp dcs.log

Все написанное выше является моим оценочным суждением

Everything written above reflects my personal opinion

 

Занимаюсь "активной пропагандой Американцев на данном форуме" © Flanker

Posted

OK, this crash definitely looks like a pagefile issue:

2023-09-12 06:33:12.762 INFO    EDCORE (8324): # -------------- 20230912-063313 --------------
2023-09-12 06:33:12.763 INFO    EDCORE (8324): DCS/2.8.8.43704 (x86_64; MT; Windows NT 10.0.19045)
2023-09-12 06:33:12.764 INFO    EDCORE (8324): D:\games\dcs_world_open_beta\bin-mt\edCore.dll
2023-09-12 06:33:12.765 INFO    EDCORE (8324): # C0000005 ACCESS_VIOLATION at 00007ffea51be4a0 00:00000000
2023-09-12 06:33:12.766 INFO    EDCORE (8324): SymInit: Symbol-SearchPath: 'D:\games\dcs_world_open_beta\bin-mt;', symOptions: 532, UserName: 'iv_ma'
2023-09-12 06:33:12.767 INFO    EDCORE (8324): OS-Version: 10.0.19045 () 0x300-0x1
2023-09-12 06:33:12.769 INFO    EDCORE (8324): 0x000000000006e4a0 (edCore): mmfMemoryBlockPrefetch + 0x90
2023-09-12 06:33:12.770 INFO    EDCORE (8324): 0x000000000006d47f (edCore): mmfMemoryBlockPreload + 0x2F
2023-09-12 06:33:12.771 INFO    EDCORE (8324): 0x0000000000070568 (edterrain4): landscape4::GeometrySource::preload + 0x78
2023-09-12 06:33:12.771 INFO    EDCORE (8324): 0x00000000002537bc (edterrain4): landscape5::Surface5File::Square::preload + 0x5C
2023-09-12 06:33:12.771 INFO    EDCORE (8324): 0x000000000006be9d (edterrainGraphics41): edtg41::TerrainRenderable::dumpRenderItem + 0x56AFD
2023-09-12 06:33:12.771 INFO    EDCORE (8324): 0x0000000000033c39 (edCore): ed::this_thread::yield + 0xB59
2023-09-12 06:33:12.771 INFO    EDCORE (8324): 0x0000000000049228 (edCore): ed::this_thread::yield + 0x16148
2023-09-12 06:33:12.771 INFO    EDCORE (8324): 0x00000000000326b1 (edCore): ed::thread::_get_current_thread_id + 0x71
2023-09-12 06:33:12.772 INFO    EDCORE (8324): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92
2023-09-12 06:33:12.772 INFO    EDCORE (8324): 0x0000000000017614 (KERNEL32): BaseThreadInitThunk + 0x14
2023-09-12 06:33:13.039 INFO    EDCORE (8324): Minidump created.

 

Now that you have 64 GB of RAM, try setting a default pagefile (Windows will set a default 4 GB pagefile, which will do).

Simply tick that box:

image.png

If this does not help, please contact ED tech support: log into DCS website, click "Support", then click "Create a new ticket".

  • Thanks 1

---

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...