Page 1 of 1
CTD With Latest Updates 1.10 1900.20 and 23
Posted: Fri Oct 16, 2026 6:37 pm
by Tred
Hello. Is anyone else experiencing crashes to desktop with the latest updates?
I'm a technologically challenged Gen Xer so all I've tried is to reinstall the latest version from Steam. But so far, I've played two large self-created scenarios five times total with the newest updates and every single game has ended in an abrupt crash to desktop. Twice within 15 minutes of starting. Once about 40 minutes in. And twice a couple of hours into playing. But all have ended in a crash, which never happened before.
I'm wondering if its something on my end or if anyone else is having that problem too.
Thanks.
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Sat Oct 17, 2026 6:57 am
by Dimitris
Can you try shutting down all other applications and processes one by one? Unfortunately many common applications and tools
(including recently bloody Discord
) are aggressively using overlays over what they see as "the current running game", and this can seriously interfere with Command's rendering pipeline.
Also, can you post the exception log? It might give us a better idea of what went on specifically in your system.
Thanks.
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Tue Oct 20, 2026 3:47 am
by Tred
Thanks Dimitris. Hopefully I did this correctly from my last CTD.
I'm experimenting with shutting down apps (or at least ones I feel comfortable shutting down, remember, I'm a technologically challegned Gen Xer. lol). I have been having trouble lately with my mechanical HD hitting 100% sometimes...do you think that could be causing the CTD? I suspect that's not the case since I wasn't having this persistent CTD problem prior to the latest patches even with the slow HD. But I have no idea.
Thank you.
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Tue Oct 20, 2026 9:34 am
by Dimitris
Something that sticks out from your exception is that Command is not running as administrator. Can you please configure it to run as admin ?
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Tue Oct 20, 2026 8:38 pm
by rmeckman
I've been experiencing relatively frequent CTDs in 1900.20 and 1900.23 but have not been able to discover a consistent set of actions to reproduce them from the last save before the crash. Also, they normally don't leave any traces in the log files. One I had today did leave the following lines in the exception log:
20/10/2026 13:50:24 -- Bv1.10 - Build 1900.23 -- Object reference not set to an instance of an object. -- Scen : Mediterranean Fury 1, The Road to Byzantium, 1994 -- DB : -- Exception: Object reference not set to an instance of an object.
Stack Trace: at System.Collections.Generic.Dictionary`2.FindEntry(TKey key)
at System.Collections.Generic.Dictionary`2.TryGetValue(TKey key, TValue& value)
at ThreadSafeCollections.TDictionary`2.TryGetValue(TKey key, TValue& value)
at Command_Core.Module_Unit.Unit.get_IsInsideThisArea(List`1 theArea, Scenario theScen, Boolean UseCache)
Call Stack & Error details:
Error at 100873: !Load assembly: CMORTMP, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from C:\Program Files (x86)\Steam\steamapps\common\Command - Modern Operations\CMORTMP.dll
!Load assembly: PlayFabClient, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null from C:\Program Files (x86)\Steam\steamapps\common\Command - Modern Operations\PlayFabClient.dll
Of course, this CTD leaving a trace may mean that it is unrelated to the others that don't leave a trace. The only common thread in my CTDs is that they often occur when my units are firing on enemy units.
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Wed Oct 21, 2026 4:57 am
by Dimitris
rmeckman wrote: Tue Oct 20, 2026 8:38 pm
Of course, this CTD leaving a trace may mean that it is unrelated to the others that don't leave a trace. The only common thread in my CTDs is that they often occur when my units are firing on enemy units.
This is probably a long shot, but: If you are using sound effects & music, can you try disabling them for a while (Game Options --> Sounds/Music) and see if stability improves in the same context? Thanks.
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Wed Oct 21, 2026 3:16 pm
by Nikel
Tred wrote: Tue Oct 20, 2026 3:47 am
ExceptionLog_2026_10_15.txt
I'm experimenting with shutting down apps (or at least ones I feel comfortable shutting down, remember, I'm a technologically challegned Gen Xer. lol). I have been having trouble lately with my mechanical HD hitting 100% sometimes...do you think that could be causing the CTD? I suspect that's not the case since I wasn't having this persistent CTD problem prior to the latest patches even with the slow HD. But I have no idea.
Thank you.
There is a fuse exception with you monster scenario "Preempting North Korea"
Have you a new version of it?
The last you posted was this
https://forums.matrixgames.com/viewtopi ... 6#p5234966
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Thu Oct 22, 2026 6:35 pm
by Tred
A new version of it? Like a rebuild of it?
No. It's the same scenario I've had and been trying to finish playing forever now. But I wasn't having any CTD with it (or only very rarely) until the last two updates (1900.20 and .23).
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Thu Oct 22, 2026 7:43 pm
by Nikel
Any change or update in the scenario.
I ask because run it for some time and did not get any fuse exception. Not much time because the simulation is very slow as you know.
Perhaps was it a save?
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Thu Oct 22, 2026 7:46 pm
by Tred
Nikel wrote: Thu Oct 22, 2026 7:43 pm
Any change or update in the scenario.
I ask because run it for some time and did not get any fuse exception. Not much time because the simulation is very slow as you know.
Perhaps was it a save?
No changes on my end. Whenever a new update comes along I always just start playing the scenario over again from the beginning. It's always slow because it is so big. But I've never had these CTD's with it until now.
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Thu Oct 22, 2026 7:51 pm
by Tred
Dimitris wrote: Tue Oct 20, 2026 9:34 am
Something that sticks out from your exception is that Command is not running as administrator. Can you please configure it to run as admin ?
I thought for a minute this fixed it. It did seem to help.
To recap: I rarely ever had CTD's in my custom scenarios. But with the last two patches, the first five games I played all ended up in a CTD.
I did as you suggested and ran a game the other night, same big scenario, as 'administrator' launching from the .exe file, and I played for well over four hours with no CTD.
Then I ran it again not as administrator and got a CTD within 20 minutes.
So I then started it again as 'administrator' thinking that the problem was solved. And I got to play for a couple of hours...but unfortunately that also ended in a CTD. Here is the exception log for it:
Why would running it as 'administrator' make a difference with the latest patches as opposed to previous ones? I never ran the game as administrator until now.
Thank you.
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Sat Oct 24, 2026 12:07 am
by rmeckman
Dimitris wrote: Wed Oct 21, 2026 4:57 am
This is probably a long shot, but: If you are using sound effects & music, can you try disabling them for a while (Game Options --> Sounds/Music) and see if stability improves in the same context? Thanks.
Turning off the sound/music seems to have no effect. My CTD today (1900.23) appears to have left no trace as far as error messages, but I've attached the log files from shortly after the crash just in case. I also checked the Windows Event Viewer. The only thing posted around the time of the crash was a Security-SPP Event ID 16384. This appears to be a common information message that likely has no relevance.
Re: CTD With Latest Updates 1.10 1900.20 and 23
Posted: Sat Oct 24, 2026 12:11 pm
by Nikel
In the Event viewer, "Windows logs - Application" selected, on the right there is find button.
Click on it and type Command.exe to find any issue related with CMO.