solved Single Player crash after repair and mods removed

[Gault05]

After a repair and disabling mods from the manager aside from the base mods, I went to try a SP TTI mission. Managed to takeoff, but the game crashed as I released my fuel tanks frommy F/A-18C. Created a crash file afterward to send to support, but wanted to post here to find any solutions.

 

dcs.20250329-012747.crash

dcs.log

[rob10]

For starters, while you said you have "disabling mods from the manager aside from the base mods" your log is showing you have a pile of mods still installed.  I'd start there.  The CH mods are great but are memory intensive and beyond that you have a pile of other mods as well.  The SU-57 has been a problem since the last big patch (unless they've updated it, no idea if they have) so that and the other SU-xx mods would be a good starting point to uninstall.

[Gault05]

1 hour ago, rob10 said:

For starters, while you said you have "disabling mods from the manager aside from the base mods" your log is showing you have a pile of mods still installed.  I'd start there.  The CH mods are great but are memory intensive and beyond that you have a pile of other mods as well.  The SU-57 has been a problem since the last big patch (unless they've updated it, no idea if they have) so that and the other SU-xx mods would be a good starting point to uninstall.

So you're essentially saying instead to get rid of said mods if that solves the problem by the log files. This incudes the weapon mods too? Then what after all is cleared from the game?

[rob10]

43 minutes ago, Gault05 said:

So you're essentially saying instead to get rid of said mods if that solves the problem by the log files. This incudes the weapon mods too? Then what after all is cleared from the game?

Sorry, not understanding what you're trying to say here .

Yes, you should remove your mods (at a minimum the SU-xx mods, and if that doesn't work, then all of them).  While it seemed like you were trying to say you HAD removed all your mods already, the log you provided shows a large number of mods still installed.  I think there is a language issue somewhere here.

[Gault05]

15 minutes ago, rob10 said:

Sorry, not understanding what you're trying to say here .

Yes, you should remove your mods (at a minimum the SU-xx mods, and if that doesn't work, then all of them).  While it seemed like you were trying to say you HAD removed all your mods already, the log you provided shows a large number of mods still installed.  I think there is a language issue somewhere here.

You said that by the logfile, I had the mods installed, but were only disabled. To start, I would have to uninstall the certain mods(The Su-XXs at least, if not, all of the mods not ED or official), which I have done(Presume that all the mods are uninstalled here). What would be the next step to ensure that this doesn't occur again?

[Gault05]

1 hour ago, Gault05 said:

You said that by the logfile, I had the mods installed, but were only disabled. To start, I would have to uninstall the certain mods(The Su-XXs at least, if not, all of the mods not ED or official), which I have done(Presume that all the mods are uninstalled here). What would be the next step to ensure that this doesn't occur again?

New files posted after removing all the mods and did a repair build, still crashes at weapons release. Occured at 10:33 PST.

 

comment.txt  dcs.20250329-053133.crash dcs.20250329-053134.trk

[MAXsenna]

3 hours ago, Gault05 said:

New files posted after removing all the mods and did a repair build, still crashes at weapons release. Occured at 10:33 PST.

You're crashlog doesn't say much. Were you able to save a track? Then the dcs.log file should be available too.

[Flappie]

Hi @Gault05. There are clear signs in your log that DCS is having a hard time with your CPU:

2025-03-29 01:17:25.446 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2025-03-29 01:17:29.171 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2025-03-29 01:17:29.492 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2025-03-29 01:17:36.499 WARNING LOG (7736): 11 duplicate message(s) skipped.
2025-03-29 01:17:36.499 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2025-03-29 01:17:36.736 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2025-03-29 01:17:37.499 WARNING LOG (7736): 3 duplicate message(s) skipped.
2025-03-29 01:17:37.499 INFO    SCRIPTING (Main): TTI: Debug - Detecting active Mission: [Convoy Mission], [10] units remain, threshold is set to [0]
2025-03-29 01:17:39.579 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2025-03-29 01:17:39.628 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2025-03-29 01:17:45.089 WARNING LOG (7736): 16 duplicate message(s) skipped.
2025-03-29 01:17:45.089 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2025-03-29 01:17:45.313 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2025-03-29 01:17:47.204 WARNING LOG (7736): 8 duplicate message(s) skipped.
2025-03-29 01:17:47.204 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2025-03-29 01:17:47.505 INFO    SCRIPTING (Main): TTI: Debug - Detecting active Mission: [MR8], [11] units remain, threshold is set to [3]
2025-03-29 01:17:47.811 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2025-03-29 01:17:49.000 WARNING LOG (7736): 1 duplicate message(s) skipped.
2025-03-29 01:17:49.000 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2025-03-29 01:17:50.329 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2025-03-29 01:17:56.142 WARNING LOG (7736): 6 duplicate message(s) skipped.
2025-03-29 01:17:56.142 INFO    SCRIPTING (Main): TTI: Debug - Running Main A2A Constant Detection! Alive status: [true]
2025-03-29 01:17:56.142 INFO    SCRIPTING (Main): TTI: Debug - A2A_CONSTANT-#001 is still alive! Respawn skipped...
2025-03-29 01:17:56.649 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2025-03-29 01:17:57.630 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2025-03-29 01:17:57.681 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2025-03-29 01:17:59.051 WARNING LOG (7736): 1 duplicate message(s) skipped.
2025-03-29 01:17:59.051 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED
2025-03-29 01:17:59.312 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME
2025-03-29 01:18:02.816 WARNING LOG (7736): 7 duplicate message(s) skipped.

("ANTIFREEZE ENABLED" all over)

Furthermore, DCS noticed at the beginning of your log that you're having parked cores. 

2025-03-29 00:42:22.125 WARNING EDCORE (Main): CPU HAS PARKED LOGICAL CORES (this can be source of stuttering and reduced performance especially on hybrid CPUs with P/E-cores)
2025-03-29 00:42:23.588 INFO    EDCORE (Main): Platform Timer Resolution: 2.01ms
2025-03-29 00:42:24.128 INFO    EDCORE (Main): Created boot pool: n:12
2025-03-29 00:42:24.130 INFO    APP (Main): Command line: "C:\Program Files\Eagle Dynamics\DCS World\bin/DCS.exe" --restarted
2025-03-29 00:42:24.130 INFO    APP (Main): DCS/2.9.14.8394 (x86_64; MT; Windows NT 10.0.19045)

And I see you're still using Windows 10. You should upgrade to Windows 11 which handles E-cores better.

[Gault05]

Okay, after getting some needed sleep, I tried to start up the game again. Went to try an Instant Action in the A-10A, expecting another Weps Release crash, but it fired without any problems.

 

Went to the BFM IA mission in the F-16C to confirm this again, and fired A2A weapons with no game crash.

Then did the F/A-18C Weps Practice Mission to check one more time, dropped a few bombs without problems now.

Turns out it needed a PC restart to properly function again, not just a game restart, but will report any further incedents if it occurs again. Track files will be posted.

 

A-10ACrashTestFile.trk F-16CCrashTestFile.trk F-18CBaseCrashTestFile.trk

[silverdevil]

2 hours ago, Gault05 said:

Turns out it needed a PC restart to properly function again, not just a game restart, but will report any further incedents if it occurs again. Track files will be posted.

good to hear. i am a sysadmin and i cannot tell you how many times windows righted itself after a restart. new users especially think i am blowing smoke when i direct them to restart.