resolved 2.7.0.4625 Open Beta crash at second mission load

[Conroy]

Try to update W10 to the last version released today, and delete FXO and Shader.

 

Give it a try.

 

For the fist time, i've played the same mission three time without CTD.

 

Edited April 29, 2021 by Conroy

[Flappie]

To all Intel CPU owners: someone fixed his DCS 2.7 multiple crashes by uninstalling a Windows patch, KB4589212 (Intel microcode update).

I usually don't advise to prevent/remove Windows updates, but since no solution has been found yet, it's worth a shot. Can a few Intel CPU owners test this?

[Flia]

Im starting to give up with this problem. I do every possible things. Cleaning folders with temps and fxo, updating windows, updating gpu driver, add dcs folder and user saved folder to exception for windows Defendet. Nothing helps. DCS still crashes after first mission load. I really dont knows what to do next.

[Gierasimov]

9 hours ago, Flappie said:

To all Intel CPU owners: someone fixed his DCS 2.7 multiple crashes by uninstalling a Windows patch, KB4589212 (Intel microcode update).

I usually don't advise to prevent/remove Windows updates, but since no solution has been found yet, it's worth a shot. Can a few Intel CPU owners test this?

I don't believe this is a solution at all. This KB4589212 updates this file:

 

Mcupdate_GenuineIntel.dll

10.0.19041.835

3,734,352

1/20/2021

20:43

 

I installed my current OS in December 2020 and I never received this update - as the update itself targets specific CPU's listed in the KB article.

 

In summary, I never had this KB installed and yet my DCS was also crashing, hence I don't think this is the likely fix.  

[Flappie]

To NVIDIA gfx users: someone saw his second mission loading crashes disappear once he installed the latest 466.27 NVIDIA drivers. It's worth a try.

 

 

[Snakedoc]

On 4/30/2021 at 9:58 AM, Flappie said:

To NVIDIA gfx users: someone saw his second mission loading crashes disappear once he installed the latest 466.27 NVIDIA drivers. It's worth a try.

 

 

 

FYI 466.27 is known to give a performance hit on some builds. *edit* my bad I meant 466.11, haven't tried the .27 which was released on the 29/4. I had 466.11 until yesterday and DCS was crashing constantly on second load of the same mission with those drivers.

 

Rolled back to 461.72 and game is still crashing. I did get some of the performance back though (not quite at the same level of 2.5.6 but a small improvement anyway). Link here to the other 3d:

MASSIVE fps drop after update to 2.7
 

 

What I found out recently is that reducing my preload setting to 100000 and deleting all the custom NVIDIA control panel settings for DCS seems to have reduced the frequency of the crashes. Now I can sometimes load the second time the same mission without issues, however it still crashes every now and again.

 

The mission I am testing this with is a custom F18C mission in Syria with some AI and many static units. Maybe RAM usage is linked somehow to the crash? This mission is quite RAM intensive (as is Syria by default). Reducing the preload could have an effect on RAM usage and therefore reducing the frequency of the crashes? 

I am sending the crash log with the prompt every time it happens. @Flappie if you need it I can also post them here

Edited May 1, 2021 by Snakedoc
added mission info

[XPACT]

They say curiosity killed the cat... well... I updated my drivers (AMD card) to the latest 21.4.1 and guess what, crashing is back hahaha I had 5 days without single one since I changed page file to fixed 32768MB yet I am now at square one again because I like to fiddle with things that "work"

 

I am pretty sure that rolling back won't bring me to previous state of no crashes

[Martin88]

Someone said that they had cured crashing with the latest Nvidia driver. Well, not for me. It is crahing more than ever.

 

ED, please do something about it, this is ridiculous.

[zone 5]

It can be fixed.

1. do a full repair integrity check of DCS (google it for standalone / Steam)

2. remove mods

3. update to very latest windows not the scheduled release

4. update drivers to Nvidia update Version 466.27 for Nvidia GPU

5. restart computer.

I had the same &%^%^%^&%^%^ crashes every 2nd mission till this morning, now totally stable. Hope this works for you.

[Flappie]

20 minutes ago, Snakedoc said:

I am sending the crash log with the prompt every time it happens. @Flappie if you need it I can also post them here

Send it over. I'll see if there's anything new.

 

@zone 5Thanks for sharing. The main problem with this crash is that there are like 10 different solutions already: a lot of users here have tested them all without seeing much progress. Every PC is different and this crash bug is here to remind us of this hard fact.

[zone 5]

5 minutes ago, Flappie said:

Send it over. I'll see if there's anything new.

 

@zone 5Thanks for sharing. The main problem with this crash is that there are like 10 different solutions already: a lot of users here have tested them all without seeing much progress. Every PC is different and this crash bug is here to remind us of this hard fact.

agreed the problem is everyone's setup is different, what worked for me might very well not work for others; lets hope DCS figures it out.

[Martin88]

12 minutes ago, zone 5 said:

It can be fixed.

1. do a full repair integrity check of DCS (google it for standalone / Steam)

2. remove mods

3. update to very latest windows not the scheduled release

4. update drivers to Nvidia update Version 466.27 for Nvidia GPU

5. restart computer.

I had the same &%^%^%^&%^%^ crashes every 2nd mission till this morning, now totally stable. Hope this works for you.

I already did all you suggested 10 times. Nothing works so far. I even reinstalled the whole thing.

dcs.log

Edited April 30, 2021 by Martin88

[Flia]

Also latest nvidida drivers 466.27 did not help. Still crashing. No difference.

[Snakedoc]

57 minutes ago, Flappie said:

Send it over. I'll see if there's anything new.

 

 

 here they are.

 

*edit* re-upload (it was messy before).

 

-923 & -802 had a large track file in them, had to delete it due size constrain upload

 

dcs.log-20210419-103802.zip dcs.log-20210415-151923.zip dcs.log-20210418-090242.zip dcs.log-20210429-185348.zip dcs.log-20210429-180418.zip dcs.log-20210428-195226.zip dcs.log-20210427-221736.zip

dcs.log

Edited April 30, 2021 by Snakedoc

[Flappie]

Thanks. I see no variations in your crashes. Still the same "Graphics::Renderer::FreeUnusedResources + 0x20".

 

One thing, though. Your DCS systematically gets less than 16GB of pagefile at startup. I have no idea if that changes throughout your game sessions (the log only shows pagefile size at startup). Since a few users found a workaround setting a manual pagefile size, you should give it a go. Set initial size to 32768 and max to 32768 (howto).

[Flia]

7 minutes ago, Flappie said:

Thanks. I see no variations in your crashes. Still the same "Graphics::Renderer::FreeUnusedResources + 0x20".

 

One thing, though. Your DCS systematically gets less than 16GB of pagefile at startup. I have no idea if that changes throughout your game sessions (the log only shows pagefile size at startup). Since a few users found a workaround setting a manual pagefile size, you should give it a go. Set initial size to 32768 and max to 32768 (howto).

Im running on system With 32 GB RAM and with page file set to 32 000 and im still crashing.

[Flappie]

@FliaI'll quote myself:

 

2 hours ago, Flappie said:

Thanks for sharing. The main problem with this crash is that there are like 10 different solutions already: a lot of users here have tested them all without seeing much progress. Every PC is different and this crash bug is here to remind us of this hard fact.

 

[Wali763]

2 hours ago, zone 5 said:

It can be fixed.

1. do a full repair integrity check of DCS (google it for standalone / Steam)

2. remove mods

3. update to very latest windows not the scheduled release

4. update drivers to Nvidia update Version 466.27 for Nvidia GPU

5. restart computer.

I had the same &%^%^%^&%^%^ crashes every 2nd mission till this morning, now totally stable. Hope this works for you.

Out of curiosity, would you plz report back in three or five days?

I also had some "solutions", that I thought, "now it works" and two starts later it was the crashing was back.

[Snakedoc]

19 minutes ago, Flappie said:

Thanks. I see no variations in your crashes. Still the same "Graphics::Renderer::FreeUnusedResources + 0x20".

 

One thing, though. Your DCS systematically gets less than 16GB of pagefile at startup. I have no idea if that changes throughout your game sessions (the log only shows pagefile size at startup). Since a few users found a workaround setting a manual pagefile size, you should give it a go. Set initial size to 32768 and max to 32768 (howto).

 

Thanks! I'll give it go  no idea why it is set at <16gb.. it's a new pc build (last December) with a fresh DCS install and haven't changed any component since except my gpu

[theoklahomaaviator]

19 minutes ago, Flappie said:

@FliaI'll quote myself:

 

 

The problem is almost all of these “fixes” aren’t fixes.  It’s just coincidence that X, Y, or Z was done and it stopped crashing… temporarily.  I even thought a few times that I had it resolved the problem and then the crashes returned after restarting the sim or the computer.  I’m convinced there isn’t anything wrong with my computer.  I’ll try anything to help narrow what is broken with DCS but nobody has replied to my posted crash logs either.

[Flappie]

I 100% agree with you: those aren't "fixes", only workarounds. DCS 2.7 introduced a lot of new stuff, but also new crashes for some users. The difficulty here for ED is to try and reproduce these crashes. And as long as they cannot reproduce them, there sole mean to determine what happens to you guys is to read the logs that are sent to them.

 

I've read all crashlogs in this thread, all of them, including yours. They nearly all show the same thing. There are minor differences which are:

 

1. Which DLL crashes: dx11backend.dll or d3d11.dll ?
2. Is there a Lua stack at the end of the crashdump ? (me_map_window.lua script )

... and that's it.

 

As long as you get "Graphics::Renderer::FreeUnusedResources + 0x20" in the crash dump part of your log, you can be sure this is the same bug everyone is having in this thread. And you have it in your log (last line):

 

2021-04-17 13:42:26.617 INFO    EDCORE: # -------------- 20210417-134226 --------------
2021-04-17 13:42:26.619 INFO    EDCORE: DCS/2.7.0.4625 (x86_64; Windows NT 10.0.19042)
2021-04-17 13:42:26.620 INFO    EDCORE: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\dx11backend.dll
2021-04-17 13:42:26.620 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 6E60CC13 00:00000000
2021-04-17 13:42:26.621 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'theok'
2021-04-17 13:42:26.622 INFO    EDCORE: OS-Version: 10.0.19042 () 0x300-0x1
2021-04-17 13:42:27.033 INFO    EDCORE: 0x000000000000CC13 (dx11backend): RenderAPI::DX11Renderer::useTesselatorStage + 0x7B43
2021-04-17 13:42:27.034 INFO    EDCORE: 0x000000000000CD82 (dx11backend): RenderAPI::DX11Renderer::useTesselatorStage + 0x7CB2
2021-04-17 13:42:27.035 INFO    EDCORE: 0x0000000000031612 (NGModel): model::ModelMaterial::draw + 0x5DE2
2021-04-17 13:42:27.035 INFO    EDCORE: 0x0000000000034F54 (NGModel): model::ModelMaterial::draw + 0x9724
2021-04-17 13:42:27.035 INFO    EDCORE: 0x0000000000020ED3 (NGModel): model::graph::GraphNodesFactory::bootstrap + 0x473
2021-04-17 13:42:27.035 INFO    EDCORE: 0x0000000000037E02 (NGModel): model::ModelMaterial::draw + 0xC5D2
2021-04-17 13:42:27.035 INFO    EDCORE: 0x0000000000041EF5 (NGModel): init_graphics_plugin + 0x2EE5
2021-04-17 13:42:27.036 INFO    EDCORE: 0x0000000000042038 (NGModel): model::NGModelLods::~NGModelLods + 0x48
2021-04-17 13:42:27.036 INFO    EDCORE: 0x000000000004286E (NGModel): model::NGModelLods::~NGModelLods + 0x87E
2021-04-17 13:42:27.036 INFO    EDCORE: 0x0000000000036B73 (GraphicsVista): Graphics::Models::gc + 0x1B3
2021-04-17 13:42:27.036 INFO    EDCORE: 0x0000000000032970 (GraphicsVista): Graphics::Renderer::FreeUnusedResources + 0x20

 

Edited April 30, 2021 by Flappie

[BIGNEWY]

Our team and testers are unable to reproduce the issue currently.

 

It is very important to make sure windows and all drivers are up to date, remove all unofficial mods and run a cleanup and repair or verify if steam. 

 

thanks

 

[XPACT]

13 minutes ago, BIGNEWY said:

Our team and testers are unable to reproduce the issue currently.

 

It is very important to make sure windows and all drivers are up to date, remove all unofficial mods and run a cleanup and repair or verify if steam. 

 

thanks

 

 

By going so up to date my game is now crashing again... Now I am at point where I can't believe that nobody managed to reproduce it, your testers should try fiddling with drivers, pulling memory sticks out, changing pagefile size, at some point since this is obviously memory related it will happen to someone.

[theoklahomaaviator]

19 minutes ago, Flappie said:

I 100% agree with you: those aren't "fixes", only workarounds. DCS 2.7 introduced a lot of new stuff, but also new crashes for some users. The difficulty here for ED is to try and reproduce these crashes. And as long as they cannot reproduce them, there sole mean to determine what happens to you guys is to read the logs that are sent to them.

 

I've read all crashlogs in this thread, all of them, including yours. They nearly all show the same thing. There are minor differences which are:

 

1. Which DLL crashes: dx11backend.dll or d3d11.dll ?
2. Is there a Lua stack at the end of the crashdump ? (me_map_window.lua script )

... and that's it.

 

As long as you get "Graphics::Renderer::FreeUnusedResources + 0x20" in the crash dump part of your log, you can be sure this is the same bug everyone is having in this thread. And you have it in your log (last line):

 

2021-04-17 13:42:26.617 INFO    EDCORE: # -------------- 20210417-134226 --------------
2021-04-17 13:42:26.619 INFO    EDCORE: DCS/2.7.0.4625 (x86_64; Windows NT 10.0.19042)
2021-04-17 13:42:26.620 INFO    EDCORE: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\dx11backend.dll
2021-04-17 13:42:26.620 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at 6E60CC13 00:00000000
2021-04-17 13:42:26.621 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;C:\Program Files\Eagle Dynamics\DCS World OpenBeta;C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530, UserName: 'theok'
2021-04-17 13:42:26.622 INFO    EDCORE: OS-Version: 10.0.19042 () 0x300-0x1
2021-04-17 13:42:27.033 INFO    EDCORE: 0x000000000000CC13 (dx11backend): RenderAPI::DX11Renderer::useTesselatorStage + 0x7B43
2021-04-17 13:42:27.034 INFO    EDCORE: 0x000000000000CD82 (dx11backend): RenderAPI::DX11Renderer::useTesselatorStage + 0x7CB2
2021-04-17 13:42:27.035 INFO    EDCORE: 0x0000000000031612 (NGModel): model::ModelMaterial::draw + 0x5DE2
2021-04-17 13:42:27.035 INFO    EDCORE: 0x0000000000034F54 (NGModel): model::ModelMaterial::draw + 0x9724
2021-04-17 13:42:27.035 INFO    EDCORE: 0x0000000000020ED3 (NGModel): model::graph::GraphNodesFactory::bootstrap + 0x473
2021-04-17 13:42:27.035 INFO    EDCORE: 0x0000000000037E02 (NGModel): model::ModelMaterial::draw + 0xC5D2
2021-04-17 13:42:27.035 INFO    EDCORE: 0x0000000000041EF5 (NGModel): init_graphics_plugin + 0x2EE5
2021-04-17 13:42:27.036 INFO    EDCORE: 0x0000000000042038 (NGModel): model::NGModelLods::~NGModelLods + 0x48
2021-04-17 13:42:27.036 INFO    EDCORE: 0x000000000004286E (NGModel): model::NGModelLods::~NGModelLods + 0x87E
2021-04-17 13:42:27.036 INFO    EDCORE: 0x0000000000036B73 (GraphicsVista): Graphics::Models::gc + 0x1B3
2021-04-17 13:42:27.036 INFO    EDCORE: 0x0000000000032970 (GraphicsVista): Graphics::Renderer::FreeUnusedResources + 0x20

 

 

Gentlemen, is there anything I can do to help narrow what is causing it?  I would be willing to do a clean install of Windows to see if the problem is resolved although I fear that won’t tell us what the conflict was.  Can I disable hardware systematically or perhaps try specific system graphics settings?  Do you think the problem is in regards to graphics or memory?  If you COULD reproduce it on your system, what would you do?  Give me instructions and I’ll follow them to the letter.  I can mirror someones Nvidia graphics settings that isn’t experiencing crashes.  Everything on my system is currently up to date (windows, drivers, and any additional software installed).  Help me help you.  About all I do with this computer is DCS.  I’m at your disposal.

[wowbagger]

I think whatever is causing the crashing doesn't have just a single symptom. The Page File change stopped my Second Load crashing entirely. I can use pretty much all my modules without fear of crash. However on WednesdayI decided to re-install the A-10A and on the very first attempt to load a mission it crashed. By contrast I then took the same mission, edited it in the Mission Editor to use the A-10CII and it worked flawlessly.  And I have played several other missions/modules/campaigns since without issue.

 

@BIGNEWY I assume you guys have been trying to track what kind of hardware the crashes are happening on to see if there is any trend. It is so strange that no one at ED can replicate it.

 

It must be that everyone at the office has the HIND already installed and it contains the cure. You should probably release the HIND this weekend to fix all these issues for the rest of us.