DCS error VCRUNTIME140.dll

[BatovE]

Good afternoon, before posting this appeal, I read a lot of reports about a similar error.
I have VCRUNTIME140.dll error. BUT I played DCS for a long time on this hardware.
And so, i5 11400,
32 Gb, SSD 1Tb, 3080ti.
Not the current moment I have - new OS, new DCS, new GPU drivers, new SSD drive! and still an error!
I achieved stability in offline flights by lowering the frequency of the GPU, but as soon as I go to a public server - a crash.
I am attaching the log files.

 

dcs.log-20221103-190445.zip dcs.log-20221103-172735.zip dcs.log dcs.log-20221103-165805.zip dcs.20221103-163223.dmp dcs.20221103-163223.crash

[Flappie]

I had never seen this error before: "Something went wrong with PrefetchVirtualMemory". This might be helpful.

2022-11-03 19:04:44.834 ERROR   EDCORE (7176): Something went wrong with PrefetchVirtualMemory.
2022-11-03 19:04:44.835 INFO    EDCORE (7176): try to write dump information
2022-11-03 19:04:44.837 INFO    EDCORE (7176): # -------------- 20221103-190445 --------------
2022-11-03 19:04:44.838 INFO    EDCORE (7176): DCS/2.8.0.32235 (x86_64; Windows NT 10.0.19045)
2022-11-03 19:04:44.839 INFO    EDCORE (7176): D:\Steam\steamapps\common\DCSWorld\bin\edCore.dll
2022-11-03 19:04:44.841 INFO    EDCORE (7176): # C0000005 ACCESS_VIOLATION at 4E3EE6EA 00:00000000
2022-11-03 19:04:44.847 INFO    EDCORE (7176): SymInit: Symbol-SearchPath: '.;D:\Steam\steamapps\common\DCSWorld;D:\Steam\steamapps\common\DCSWorld\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*https://msdl.microsoft.com/download/symbols;', symOptions: 528, UserName: 'User'
2022-11-03 19:04:44.848 INFO    EDCORE (7176): OS-Version: 10.0.19045 () 0x100-0x1
2022-11-03 19:04:45.287 INFO    EDCORE (7176): 0x000000000005E6EA (edCore): mmfMemoryBlockPrefetch + 0xAA
2022-11-03 19:04:45.287 INFO    EDCORE (7176): 0x000000000005D7CF (edCore): mmfMemoryBlockPreload + 0x2F
2022-11-03 19:04:45.288 INFO    EDCORE (7176): 0x0000000000060428 (edterrain4): landscape4::GeometrySource::preload + 0x78
2022-11-03 19:04:45.288 INFO    EDCORE (7176): 0x000000000022CABC (edterrain4): landscape5::Surface5File::Square::preload + 0x5C
2022-11-03 19:04:45.288 INFO    EDCORE (7176): 0x0000000000067FCD (edterrainGraphics41): edtg41::TerrainRenderable::dumpRenderItem + 0x53C0D
2022-11-03 19:04:45.288 INFO    EDCORE (7176): 0x000000000002D9D7 (edCore): ed::this_thread::yield + 0x1337
2022-11-03 19:04:45.288 INFO    EDCORE (7176): 0x000000000002BCC0 (edCore): ed::thread::_get_current_thread_id + 0xA0
2022-11-03 19:04:45.289 INFO    EDCORE (7176): 0x0000000000021BB2 (ucrtbase): _configthreadlocale + 0x92
2022-11-03 19:04:45.289 INFO    EDCORE (7176): 0x0000000000017034 (KERNEL32): BaseThreadInitThunk + 0x14
2022-11-03 19:04:45.289 INFO    EDCORE (7176): 0x00000000000526A1 (ntdll): RtlUserThreadStart + 0x21
2022-11-03 19:04:45.723 INFO    EDCORE (7176): Minidump created.

 

Your pagefile is rather small. Try this: https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/

Set a manual size of 32GB:

• Initial size: 32768
• Max size: 32768

Ensure you have sufficient free space on your pagefile drive before doing this.

[BatovE]

its not work

dcs.log dcs.log-20221105-105539.zip

[BatovE]

I did as you recommended and enlarged the swap file, but it didn't work. Then I extracted one of the two 16Gb RAM and ran a test. Crash didn't happen. After that, I installed a second 16Gb RAM and also conducted a test in multiplayer mode and ... miracle, it works!

[Flappie]

Oh, it was a defective RAM stick, then.

Nice job! Thanks for your feedback.

[BatovE]

It's me again! After the last mistake, a week has passed. I didn't launch the game and now the weekend has come, it's time to fly! Received video driver updates. I also thought about whether it's worth doing! But I decided to update it anyway. And, I get the same error! I start doing all the same steps to fix the error, remembering that the error is from memory! 1. Install the 32Gb swap file - it didn't help. 2. I roll back the video card drivers - it didn't help. 3. I remove and plug in one of the two 16Gb RAM again - it didn't help. 4. I start the game using 1 RAM 16GB - Bingo! Now I have 32GB RAM running, but I swapped them in dual mode. I think yes, one of the 16Gb RAM has damage in some address space. But I can't detect it using the memtest program. Motherboard Asus Prime B560-Plus \ CPU Quadcore Intel Core i5-11400, 4300 MHz (43 x 100)\ NVIDIA GeForce RTX 3080 Ti Video Adapter (12 GB) \DIMM2: EX283083RUS 16 GB DDR4-2666 x2. I hope this information will help someone, even if your RAM passes the test, it does not mean that it is alive!