Matrix Games Forums

I keep having the same crash (has persisted over several versions). Scenario size does not matter. It appears randomly without warning. As you can see from the save (attached), there are only a few ships set up, none which are particularly complicated.

There is no reason I can see for this "out of memory" crash. I am operating an less than 6 month old Alienware x17 R2 with 12th Gen Intel 2.50 GHz with 64.0 GB RAM.

Error message and save attached.

Thank you.

Oof. Something is fingering your Direct3D pipeline. That will be "fun" to untangle....

Sorry. Please let me know if there is anything I can do to help.

taylorgeorge wrote: Mon Dec 05, 2022 1:32 pm Sorry. Please let me know if there is anything I can do to help.

Hi taylorgeorge -- Do you recall if you had minimized the Command window, switched focus to another application, or had your lock screen / screen saver activate during the game where this error occurred?

SteveMcClaire wrote: Thu Dec 08, 2022 5:29 pm
Hi taylorgeorge -- Do you recall if you had minimized the Command window, switched focus to another application, or had your lock screen / screen saver activate during the game where this error occurred?

I do recall, but unfortunately, I did not take any of the actions you describe. Every time it happens, the sim is up and operating normally, right until the moment it doesn't. There does not seem to be any consistency. Sometimes I have the weapons window open on a unit, sometimes just the main map, sometimes I am building, sometimes the sim is running. There is nothing consistent I can find. I can sometimes be doing nothing; just looking at the map trying to decide what to do next, and suddenly the dialog box pops up, "Error in the application".

Updating this issue. It persists to this day, despite multiple updates (I am now to 1304.1, so I updated the subject line). I still cannot find a correlation to anything happening. It happened last night when all I had were a few squadrons built, no action in progress, while I was resetting weapons engagement options.

Any thoughts? Anything else I can provide?

Can you attach the exception file from the logs folder?

Let's try to clear out the usual suspects:

* Is the OS fully updated? Graphics drivers updated? Direct-X 9 installed?
* Is Command running as admin? (ie. prompting you "are you sure you want to run this program" when you launch it)
* (Steam only) Are Steam overlays disabled for Command?
* (Steam only) Is Direct-Write disabled on the Steam client?
* Are all other applications (and especially hardware-helper apps like RivaTuner, Nahimic, MSI Afterburner etc.) shut down?
* Are you using a high-DPI desktop? (ie. font size >100%)
* Are you using Norton antivirus? (This POS is very frequently silently blocking file updates)

Appreciate the questions. In order:

1. Yes. Fully updated Windows 11, through 2023-01. I ran every update there is. Direct-X 12, according to dxdiag.
2. Yes, running as Admin.
3. Not on Steam.
4. Not on Steam.
5. I have EVERYTHING else off. Nothing else running not absolutely necessary.
6. No - smallest size I can.
7. MacAfee - but I suppress the firewall anytime I run an update, as I had seen that too, especially with the official updates of CMO.

I am fully up to date on CMO, running Beta 1304.1.

The only thing I can think of I haven't said is about half of the time, this happens when I am moving the map. But also happens when I am on a menu, reading a unit description, or sometimes doing nothing (e.g., walked away from the computer for a few minutes while still building the scenario, so nothing should be happening, only to come back to find the "Error in Application" box.)

For the elimination of all doubt - I'm cool with everyone. Its just a bug we need to work together to figure out. Glad to be part of the solution.

This may be a long shot, but: Can we get a look at your DxDiag log file ?

Also, anything strange showing up on Event Viewer ?

I would also check if CPU is seated correctly . Sometimes 1 pin can cause memory , drive or pci-e issues without your system crashing . Have u done benchmarks? ( it's a longshot and because it is a laptop it's hard i know but if everything else fails you could check that too)

DimiHendrix wrote: Thu Jan 19, 2023 11:16 am I would also check if CPU is seated correctly . Sometimes 1 pin can cause memory , drive or pci-e issues without your system crashing . Have u done benchmarks? ( it's a longshot and because it is a laptop it's hard i know but if everything else fails you could check that too)

Unless you know what you're doing, don't muck around with your CPU. If its only CMO don't do this

M

You can easily stress test your CPU with free benchmarking tools that will pick up problems. But I think its a last resort. This looks like a DX issue, which points to the GPU or driver. I would check to see if CMO is using the big GPU (nVidia or AMD) or its Intel onboard GPU. I would then switch to the other one and see if it helps. CMO will actually tell yopu which GPU is being used if you turn on the diagnostics line in options.

thewood1 wrote: Thu Jan 19, 2023 6:36 pm You can easily stress test your CPU with free benchmarking tools that will pick up problems. But I think its a last resort. This looks like a DX issue, which points to the GPU or driver. I would check to see if CMO is using the big GPU (nVidia or AMD) or its Intel onboard GPU. I would then switch to the other one and see if it helps. CMO will actually tell yopu which GPU is being used if you turn on the diagnostics line in options.

This is actually a very good idea. We've had reports in the past that dual-GPU laptops were running CMO just fine with the discrete GPU but had various issues if they forced it on the onboard one.