F-4E Crashes constantly

[sultan_gr]

Hi to all!

I am facing continuous crashes after activating the F-4E module. I have tried all missions and the outcome is the same. The mission loads normally and 6-7 seconds after I jump in the cockpit, the game crashes. This behavior is the same on the "-mt" mode as well. The following list shows what I've done so far:

• Antivirus disabled
• Cleanup of the SaveGame directory
• Clean install of various Nvidia Drivers
• Clean install of DCS and activating only the F-4 module
• Installed on a new Samsung NVMe
• Memtest not revealed any faults

Can you help me with the upload of my log files? I can not find how to do so....

Thank you very much for your attention,

S.

 

 

Edited June 3, 2024 by sultan_gr
Files Upload

[hornblower793]

The logfile will be in your Saved Games folder (C:\Users\<username>\Saved Games\DCS.openbeta\Logs

When you are creating your forum post there should be the following option at the bottom of the message pane

Either drag your logfile (dcs.log) onto there or click on choose files...

[sultan_gr]

Thank you for the reply hornblower!

Most probably I have to wait as I am a new member and there is no such an option...yet???

Let's wait till tomorrow....

[sultan_gr]

...Uploading of the log files

dcs.log dcs.log-20240602-123642.zip

[sultan_gr]

Uploading another log file of another failed attempt...

However, I bumped into a workaround of the problem...If I fly (even for some minutes) in the Mustang and switch back to the F-4, the game doesn't crash...(at least for some minutes that I tried...) Does this ring any bell to you?

 

Tks a lot,

 

S.

dcs.log.old

[Cobra847]

Your crash logs seem to indicate some sort of memory allocation issue, which is odd. Does this happen on all maps?

[sultan_gr]

Hello Cobra847,

Thanks for the reply! Yes it was happening on all maps.. Right now (after the clean install) It happens on Caucasus and Marianas' as well... 

Tks a lot again,

S.

[sultan_gr]

I am still not being able to play as it keeps crashing...even after the update. And the "Mustang" thing is not working any more...

I am posting the latest log files in case someone can give a clue.

Another thing that I've noticed is that I can stay on the taxiway for hours. The problem starts when I get airborne.

Tks a lot,

S. 

dcs.log-20240607-165348.zip

Edited June 7, 2024 by sultan_gr

[hornblower793]

From your log it looks more like it might be a DCS issue rather than an F4 issue

Your log has the following when it crashes

2024-06-07 16:53:47.921 INFO    EDCORE (12936): try to write dump information
2024-06-07 16:53:48.062 INFO    EDCORE (12936): # -------------- 20240607-165348 --------------
2024-06-07 16:53:48.063 INFO    EDCORE (12936): DCS/2.9.5.55918 (x86_64; MT; Windows NT 10.0.22631)
2024-06-07 16:53:48.063 INFO    EDCORE (12936): D:\DCS World\bin-mt\DCS.exe
2024-06-07 16:53:48.064 INFO    EDCORE (12936): # C0000005 ACCESS_VIOLATION at 00007ff76a0e303b 00:00000000
2024-06-07 16:53:48.064 INFO    EDCORE (12936): SymInit: Symbol-SearchPath: 'D:\DCS World\bin-mt;', symOptions: 532, UserName: 'thkal'
2024-06-07 16:53:48.065 INFO    EDCORE (12936): OS-Version: 10.0.22631 () 0x100-0x1
2024-06-07 16:53:48.066 INFO    EDCORE (12936): 0x0000000000d0303b (DCS): SW + 0x841FAB
2024-06-07 16:53:48.066 INFO    EDCORE (12936): 0x0000000000d03bb8 (DCS): SW + 0x842B28
2024-06-07 16:53:48.066 INFO    EDCORE (12936): 0x0000000000d03610 (DCS): SW + 0x842580
2024-06-07 16:53:48.067 INFO    EDCORE (12936): 0x0000000000d4d01e (DCS): SW + 0x88BF8E
2024-06-07 16:53:48.067 INFO    EDCORE (12936): 0x0000000000d28f3d (DCS): SW + 0x867EAD
2024-06-07 16:53:48.068 INFO    EDCORE (12936): 0x0000000000d3cbc6 (DCS): SW + 0x87BB36
2024-06-07 16:53:48.068 INFO    EDCORE (12936): 0x0000000000d6ca9b (DCS): SW + 0x8ABA0B
2024-06-07 16:53:48.068 INFO    EDCORE (12936): 0x0000000000de85c0 (DCS): SW + 0x927530
2024-06-07 16:53:48.069 INFO    EDCORE (12936): 0x0000000000de760f (DCS): SW + 0x92657F
2024-06-07 16:53:48.069 INFO    EDCORE (12936): 0x0000000000d0b471 (DCS): SW + 0x84A3E1
2024-06-07 16:53:48.069 INFO    EDCORE (12936): 0x0000000000d38539 (DCS): SW + 0x8774A9
2024-06-07 16:53:48.069 INFO    EDCORE (12936): 0x0000000000dc5d6e (DCS): SW + 0x904CDE
2024-06-07 16:53:48.069 INFO    EDCORE (12936): 0x0000000000d0b471 (DCS): SW + 0x84A3E1
2024-06-07 16:53:48.069 INFO    EDCORE (12936): 0x0000000000d18d14 (DCS): SW + 0x857C84
2024-06-07 16:53:48.069 INFO    EDCORE (12936): 0x0000000000d19012 (DCS): SW + 0x857F82
2024-06-07 16:53:48.070 INFO    EDCORE (12936): 0x0000000000e74df6 (DCS): SW + 0x9B3D66
2024-06-07 16:53:48.070 INFO    EDCORE (12936): 0x000000000001257d (KERNEL32): BaseThreadInitThunk + 0x1D
2024-06-07 16:53:48.543 INFO    EDCORE (12936): Minidump created.
2024-06-07 16:53:48.543 INFO    Lua::Config (12936): stack traceback:
2024-06-07 16:53:48.548 WARNING LOG (5160): 3 duplicate message(s) skipped.
2024-06-07 16:53:48.548 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2024-06-07 16:53:48.548 INFO    APP (12936): enumerating loaded modules
2024-06-07 16:53:48.549 INFO    APP (12936): D:\DCS World\bin-mt\DCS.exe, 32202240 bytes, created 5:6:2024-21.51.29, written 5:6:2024-21.51.29, accessed 7:6:2024-16.53.48
2024-06-07 16:53:48.549 INFO    APP (12936): C:\Windows\SYSTEM32\ntdll.dll, 2187272 bytes, created 14:5:2024-23.1.15, written 14:5:2024-23.1.15, accessed 7:6:2024-16.53.48
2024-06-07 16:53:48.549 INFO    APP (12936): C:\Windows\System32\KERNEL32.DLL, 815448 bytes, created 14:5:2024-23.1.15, written 14:5:2024-23.1.15, accessed 7:6:2024-16.53.48

Which references the main DCS.exe

At the same point my log gives loading of terrain

2024-06-06 20:27:52.760 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2024-06-06 20:27:52.879 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-06-06 20:30:13.534 INFO    APP (Main): wcTanker::onEvent:0
2024-06-06 20:30:41.758 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-06-06 20:35:37.019 INFO    APP (Main): wcTanker::onEvent:0
2024-06-06 20:35:38.826 INFO    EDTERRAINGRAPHICS41 (14704):     surface5 gc() LOD 0 93 squares
2024-06-06 20:35:38.827 INFO    EDTERRAINGRAPHICS41 (14704):     surface5 gc() LOD 1 178 squares
2024-06-06 20:35:38.828 INFO    EDTERRAINGRAPHICS41 (14704):     surface5 gc() LOD 2 220 squares
2024-06-06 20:35:38.828 INFO    EDTERRAINGRAPHICS41 (14704):     surface5 gc() LOD 3 110 squares
2024-06-06 20:35:38.828 INFO    EDTERRAINGRAPHICS41 (14704): surface5 gc() 5.156700 ms

Have you tried creating a simple mission in the ME with just a player F-4E on a ramp somewhere (or even do a hotstart in the air and see if that will load for you)?

[sultan_gr]

Hi hornblower793! Thanks for the reply,

I have tried to create a Mission out of Batumi but the game crashes again as soon as I press the "Fly Mission" menu...

Tks again,

 

S.

dcs.log

[E69_DaniV]

Checked and posted my .log and same problems.

2024-06-07 18:45:55.831 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-06-07 18:46:22.005 WARNING LOG (2580): 2 duplicate message(s) skipped.
2024-06-07 18:46:22.005 WARNING BACKENDCOMMON (9556): Need to reprocess [DDS] image '/textures/container_nrm.dds'
2024-06-07 18:46:34.060 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/intakecompressorwhine_right): gain
2024-06-07 18:46:34.282 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/intakecompressorwhine_left): gain
2024-06-07 18:46:35.062 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/intakehowllowrpm_left): gain
2024-06-07 18:46:35.121 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/intakehowllowrpm_right): gain
2024-06-07 18:46:36.199 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/intakehowlmidrpm_right): gain
2024-06-07 18:46:36.279 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/intakehowlmidrpm_left): gain
2024-06-07 18:46:36.941 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/intakehowlhighrpm_right): gain
2024-06-07 18:46:50.734 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-06-07 18:46:51.506 WARNING LOG (2580): 1 duplicate message(s) skipped.
2024-06-07 18:46:51.506 ERROR   ED_SOUND (8520): can't load wave: "speech\eng\common\player\callsign\silverbow"
2024-06-07 18:46:56.788 ERROR   ED_SOUND (8520): can't load wave: "speech\eng\common\atc\callsign\silverbow"
2024-06-07 18:46:56.810 WARNING BACKENDCOMMON (3760): Need to reprocess [DDS] image '/textures/NukeTires.dds'
2024-06-07 18:47:14.116 WARNING BACKENDCOMMON (19748): Need to reprocess [DDS] image '/textures/container_nrm.dds'
2024-06-07 18:47:14.684 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-06-07 18:48:08.262 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/intakehowlhighrpm_left): gain
2024-06-07 18:48:14.915 ERROR   ED_SOUND (Main): invalid source_params(F4E_PILOT_COCKPIT:aircrafts/f-4e/cockpit/afterburnerint): gain
2024-06-07 18:48:27.643 WARNING BACKENDCOMMON (20436): Need to reprocess [DDS] image '/textures/container_nrm.dds'
2024-06-07 18:48:47.562 WARNING LOG (2580): 1 duplicate message(s) skipped.
2024-06-07 18:48:47.562 ERROR   SCRIPTING (Main): Mission script error: [string "C:\Users\Usuario\AppData\Local\Temp\DCS.openbeta\/~mis00006AAE.lua"]:6400: attempt to index local 'EventMeta' (a nil value)
stack traceback:
    [C]: ?
    [string "C:\Users\Usuario\AppData\Local\Temp\DCS.openbeta\/~mis00006AAE.lua"]:6400: in function 'onEvent'
    [string "Scripts/World/EventHandlers.lua"]:13: in function <[string "Scripts/World/EventHandlers.lua"]:11>
2024-06-07 18:49:13.501 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/rearclosehighpower): gain
2024-06-07 18:49:13.501 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/distantmil): gain
2024-06-07 18:49:13.501 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/frontdistant): gain
2024-06-07 18:49:13.501 ERROR   ED_SOUND (Main): invalid source_params(woLA-16933120:aircrafts/engines/j79/afterburner/rearafterburnercrackle): gain
2024-06-07 18:50:00.062 ERROR   EDTERRAINGRAPHICS41 (2940): metashaders/terrain/5.0/surface5.0.fx|metashaders/transformmodifiers/transform_simple.meta.hlsl|CLIPMAP_NORMAL_MAP=;CLIPMAP_SHADOW_MAP=;COLORCLIPMAP_ALPHA_IS_AO=;COLOR_CLIPMAP=;DIRECTX11=true;LAKE_COLORCLIPMAP=;NODEFINITIONS=;NOISE_OP=PhotoshopOverlay;PBR_TEXTURES=;SPLATMAP=;SURFACE5=;TAD_CLIPMAP=;USE_DCS_DEFERRED=1;USE_TERRAIN_PALETTE=;VARYHOUSELOD_SELFILLUM_FLIR=|: no subgeometry current
2024-06-07 18:50:11.156 WARNING LOG (2580): 30 duplicate message(s) skipped.
2024-06-07 18:50:11.156 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2024-06-07 18:52:20.196 WARNING LOG (2580): 3 duplicate message(s) skipped.
2024-06-07 18:52:20.196 WARNING BACKENDCOMMON (14108): Need to reprocess [DDS] image '/textures/desertsand.dds'
2024-06-07 18:52:22.925 WARNING LOG (2580): 1 duplicate message(s) skipped.
2024-06-07 18:52:22.925 WARNING BACKENDCOMMON (10328): Need to reprocess [DDS] image '/textures/f-5e_cockpit_normal.dds'
2024-06-07 18:52:32.819 INFO    DX11BACKEND (Main): Compile shader: particlesystem2/overwingvaporcomp.fx:DIRECTX11=true;THREAD_X=25;THREAD_Y=10;USE_DCS_DEFERRED=1;
2024-06-07 18:52:33.216 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2024-06-07 18:52:33.216 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME

 

***Thanks in advance , if you find something to light the path of the phantom ****

1. I´ve repaired.

2.I´ve cleaned up.

3. I´ve Updated.

4. Antivirus restricted and added full exclusions to all related to DCS and Saved Games folders to make them free.

Cheers.

 

dcs.log

Edited June 8, 2024 by E69_DaniV

[sultan_gr]

Another Crash even after moving the "SaveGame" folder to the same SSD of the game and after reinstalling DirectX from the "distr" directory... 

Tks a lot,

 

S.

dcs.log

[aaronwhite]

On 6/4/2024 at 1:26 PM, Cobra847 said:

Your crash logs seem to indicate some sort of memory allocation issue, which is odd. Does this happen on all maps?

Hey Cobra,

Out of curiosity, what in the logs is indicating that? I've been having crashing issues myself, and so far it's seeming like maybe switching to launching the Single Core launcher specifically, and turning down settings seems to be helping, albeit a bit confusingly as the computer I have now since I've got 64GB of RAM and a decently sized VRAM for the GPU as well, but that happens. I'm able to get steady frames of around 100fps (sometimes going up to around 140 and down to 90 or so). 

Anyhow, initially, I thought it might be the F-4, since that's when I was seeing crashes, but then I slowly realized it was just a DCS issue in general, and I've been working to pinpoint what specifically might be the issue. If you're curious, here is just my general post featuring some logs, and some (hopeful) progress getting things working by knocking settings like SSAO and SSLR off, and was able to fly without crashing for about 45 minutes over lunch, which has been my most successful flight so far. This thread is from when I thought it was tied to the F-4, before figuring out it wasn't, but still has some logs available.

I think I may have sorted it, but I'm all for any advice that'll help me parse the log if it does crash again. Sorry to hijack this one!

[zaelu]

Just want to chime in without opening another thread about crashes.

My game also freezes then crashes constantly while in Phantom. I always send the reports by automatic reports sending feature after crash. Should I post something in here also? Logs etc?

Most of the times crashes are in heavier maps than Caucasus. On Caucasus if I have just the F4 I don't think it crashes ever. Most of the times on Mariana map I can't even take off. I don't think I managed to take off once in default F4 missions "Paradise Lost". So must be either too much sudden load on the system (that works without other issues in other games like MSFS). The system is a bit tuned up but not overclocked. When I say tuned up I am referring to stuff like: No E Cores on CPU activated in BIOS (I5 13600K), Core Isolation off. HAGS On, Game mode Off, Nvidia Low Latency set to to Ultra. Also I am playing only in VR though Virtual Desktop that needs to "Boost Game Priority" by increasing Priority of the game exe I think.

I am not sure if the crashes are not related with the radar as it seems more stutters are when is on and also last time it crashed was few seconds after turning the pilot radar screen on.

I was recording at that moment and this is how last seconds looked.





 

dcs.log-20240616-000303.zip dcs.log-20240615-000127.zip dcs.log-20240614-232225.zip

Edited June 16, 2024 by zaelu

[hornblower793]

If you attach logs here then people can take a look at them to see what errors are in there

[zaelu]

8 hours ago, hornblower793 said:

If you attach logs here then people can take a look at them to see what errors are in there

OK, I did. Thanks

[hornblower793]

In the log I have looked at your graphics driver has crashed with a DX11Backend DX device removed error 0x887A0006. I know there are other threads about possible solutions and @Flappie might have some good ideas.

[Flappie]

Hi @zaelu. Here are some things you can try (no need to redo what you've already tried):

 

[zaelu]

On 6/16/2024 at 11:48 PM, Flappie said:

Hi @zaelu. Here are some things you can try (no need to redo what you've already tried):

[link]

I did the registry trick and the mission didn't crashed anymore but it has a ton of stutters.  It must be something in the missions also that makes the game crash, I don't think is the UPS etc... Possible the multi-threading of DCS to be still in it's infancy because these horrendous locks and stutters appear only in Multi-Threading mode. However MT gives overall better performance.

[Flappie]

What do you call the "registry trick"?

Please send me the mission, or if it's part of the sim, tell me which one it is.

Edited June 18, 2024 by Flappie

[zaelu]

  

12 hours ago, Flappie said:

What do you call the "registry trick"?
Please send me the mission, or if it's part of the sim, tell me which one it is.

 

Mission is stock: F-4E_Single_Marianas_Paradise Lost - 1 - Covey 41.miz and the registry trick is that one where you add some values to delay to 60 seconds wait until an app is considered it crashed. It's one of the suggestions of the threads linked above iirc.

Edited June 18, 2024 by zaelu

[Flappie]

Oh right, the TDR timeout. It tells apps to wait a little before giving it up when your GPU does not answer them. This might explain the stutters. Instead of crashing, DCS now waits a few seconds until your GPU answers.

Try these steps:

1. Ensure your GPU is plugged on the x16 port:

2. If step 1 was OK, try disabling your internal GPU in the BIOS by doing this:

Settings\Advanced\Integrated Graphics Configuration

• Initiate Graphic Adapter - Set to PEG
• IGD Multi-Monitor = Disabled

3. Ensure the power cable(s) is (are) well seated into the GPU.

 

 

Edited June 18, 2024 by Flappie

[zaelu]

Hey thanks for reply.
About your recommendations. The Intel GPU is disabled.
Since the card it's a 4080 it goes without saying it's in the 16x slot otherwise it would not play anything  and also will burst into flames ... mainly it wouldn't fit anywhere else even if I would be so silly to try  because the PSU is right under the Mainboard and 4080  "needs" 4 pci slots width wise..
Also the power cord is well sited (I triple checked since it's a custom connector and I wouldn't want to have it melting on me... I checked the temps on it by hand also several times. And I have it insight (when not in VR) because the case is just in front of mouse area and is transparent with red lights in it. SO I am confident it's OK. The PSU it's not a real monster but it's almost OK... a Be quiet! BN310 Straight Power 11 Platinum of 1200W.
But!
I did some... testing. As I said with that registry setting the game/mission doesn't crash anymore but has those stutters however after playing once again the mission for an hour and so (I died so I will go to sleep lol) But also after seeing an update to the Pico Connect Streamer and doing some starts of the mission with it I noticed in that streamer (normally I use Virtual Desktop) I don't have stutters... And so I remembered that Virtual desktop has that "Boost Game Priority" option so I disabled it and poof... stutters are gone... at least after just starting the mission but it used to be a stutter fest all the time especially if I press F2 and switch planes and camera jumps all over the map... Nothing. All smooth...38fps but Smooth and with "Boost game priority ON I don't have more FPS I think... need more checking but I think is the same.

So that boost of game priority is not good as I think it boosts only one thread or something and then there is a problem with syncing in DCS mind.

I will do more testing tomorrow maybe if I still have some time.

Also I am running HWinfo64 in the back so here is a shot with what it recorded in mins maxes and averages for values that I am usually interested. I placed some red arrows on interesting parts. You can see Power is an issu but most probably just some rare spikes. Probably on those freezes. I will see tomorrow if that goes away with "Boost priority OFF".
Thanks again for support!
 

Edited June 18, 2024 by zaelu

[Flappie]

And thank you for your precious  feedback! Keep them coming. It might help some other users.

[zaelu]

23 hours ago, Flappie said:

And thank you for your precious  feedback! Keep them coming. It might help some other users.

I did the mission today and everything went smooth. Not a single freeze... I even finished the mission. Yey.
In HWInfo64 I had the same limitations regarding power to GPU but no problems.
null