Matrix Games Forums

On 3 different attempts to play the first scenario in Chains of War, I received the Windows error "Command has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available." After pressing the Close program button, Command does not close, but continues to work until that error comes back again perhaps 30 seconds later.

After the second time this happened, I verified the Steam files and 5 had to be reacquired. Not sure which ones.

Running C:MO v1.07 - Build 1567

.NET Framework 4.8.1 is installed

Command is using my discrete GPU: NVIDIA GTX 1060 6GB

--------------- Starting new GUI-client session - 2/28/2025 11:24:48 AM Build v1.07 - Build 1567 -----------------

User's machine
Machine's name :
Thread's culture : en-US
Installed culture : en-US
Available virtual memory : 140732423.3Mo
Available RAM : 23004.4Mo
Total virtual memory : 140737488.2Mo
Total RAM : 34264.5Mo
OS name : Microsoft Windows 11 Pro
OS platform : Win32NT
OS version : 6.2.9200.0
>>Not running as administrator ! <<

Can you try running Command as administrator?

Yes. I ran Command.exe as administrator. It appeared to work until I started to use my artillery to attack enemy artillery positions. This, to me, now appears to be the issue because it's consistent across the previous 3 times.

On another note, I am also unable to set missions to Triggered in the Mission Editor. I can however do that in the Operations Planner.

lowcycle wrote: Sat Mar 01, 2025 2:36 am Yes. I ran Command.exe as administrator. It appeared to work until I started to use my artillery to attack enemy artillery positions. This, to me, now appears to be the issue because it's consistent across the previous 3 times.

Can you please post a save from just prior to commencing this counter-battery strike? Thanks.

On another note, I am also unable to set missions to Triggered in the Mission Editor. I can however do that in the Operations Planner.

Can you please open a separate thread for this, together with a suitable save? Thanks.

Tech support guidelines: https://www.matrixgames.com/forums/view ... 0&t=255656

Here is a save for the "Command has stopped working" error. It occurred at 5/1/2018 12:00:44 AM in game after my artillery destroyed another artillery site.

Just as a datapoint, I ran it for six hours and knocked out almost all the NK coastal artillery sites without a crash.

I attempted to benchmark the scenario, Blue Dawn, but got the same error on the second iteration.

Any ideas?

Can you give it a try with the new Build 1567.6 update and see if anything has changed ?

I just tried it. Unfortunately, I still experience the issue.

Try to run the game through the Windows clean boot environment(*) and check if the issue persists. A "clean boot" starts Windows with a minimal set of drivers and startup programs, so that you can determine whether a background program is interfering with your game.
If this resolves the issue, enable the startup applications and services one at a time to determine which one is causing the problem. You will need to reboot Windows between each application you enable. Alternatively,  The most efficient way to do this is to test half of them at a time, thus eliminating half of the items as the potential cause with each reboot of the computer.
As you're on Steam don't disable Steam services and Steam app.

(*) https://support.microsoft.com/en-us/top ... 7a1807f3dd

Thanks for the recommendation! I will give it a try.

Below is a copy/paste from Windows Event Viewer, in case anyone understands what it means:

Fault bucket 2125234243809185161, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: Command.exe
P2: 1.0.0.0
P3: 67c8143f
P4: Command
P5: 1.0.0.0
P6: 67c8143f
P7: 1a71f
P8: e
P9: Debugger.Break
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.a46a7588-bf50-47c7-8a43-8e92bab704f8.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.5dbf8883-4815-4e3b-87c0-e4156e622de2.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.09213454-f6f5-4c83-bcc3-1aa4adf0e4e7.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.43a9b786-edf9-417f-9af4-8bcd9410e13c.tmp.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.deb4ddb0-7752-4570-b229-c9241ec0b644.tmp.xml

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Command.exe_7b5fe4e79ad76460ebf8cbea327bf9216f46e7da_211c4336_72d94893-23c1-4065-bb0c-29b2c6794542

Analysis symbol:
Rechecking for solution: 0
Report Id: 9c5839e7-6a64-41fe-86f8-0de47063d2da
Report Status: 268435456
Hashed bucket: d288ea8dcebf80907d7e5948e6be0d89
Cab Guid: 0
-------------------------------------------------------
Faulting application name: Command.exe, version: 1.0.0.0, time stamp: 0x67c8143f
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x00000000
Fault offset: 0x00007ff8d8753061
Faulting process id: 0x3860
Faulting application start time: 0x1DB96B545EF7010
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Command - Modern Operations\Command.exe
Faulting module path: unknown
Report Id: 9c5839e7-6a64-41fe-86f8-0de47063d2da
Faulting package full name:
Faulting package-relative application ID:

The Debugger.Break call sounds familiar. We had an issue related to this recently (and specifically related to unguided weapon impacts, as in your artillery example) which should be fixed for the next update.

(Still, it's pretty wierd that a Debugger call would crash the application..... something in your OS configuration must be quite unusual.)

This has been fixed, issue will no longer be present in the next version.