Matrix Games Forums

Hello,

I installed CMO on a newly built computer (i5 12th gen, integrated UHD 770 graphics, 32MB RAM) and I've been having my map screen replaced with a red X on white background every few minutes while playing. A window has popped up a couple of times with "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." I've only seen this issue on Northern Fury 34, but that is because that is the only scenario I've tried on this PC. The music and sounds continue and seem to indicate the game is still running while this takes place, but attempting to load an autosave gets a "SytstemOutOfMemoryException" error. Restarting the game seems to fix the problem, but only for a few minutes.

I've tried restarting, running CMO as admin, removing Steam overlays and DirectWrite, reinstalling Steam, reinstalling CMO, reinstalling DirectX June 2010 runtimes, reinstalling graphics drivers, and reinstalling NET Framework 4 and 6.

Any ideas? What info do you need? Log file attached.

Hi,

What happens if you run a smaller scenario ?

I just ran Canary's Cage and got the error again after about a day of ingame time at max speed. In this case it seemed to happen when a sub was attacking a surface task force. Exception log attached.

Edit: also, attempting to load an autosave doesn't appear to do anything; the white screen with red X remains.

I'm still getting this error and more often another one: "CL Error", "Error in the application." Any ideas? DXDiag attached.

The graphcis driver seems not the latest, is also not digitally signed. How did you update the graphcis driver? May you can to install another one? Maybe download directly from Intel

I've tried updated graphics drivers both from the Intel site and Windows Update and I don't think it is the problem. I got the same "CL Error" message again, this time with the graphics driver from Windows Update. Stack trace in the Exception Log looks like it points to DirectX, but I don't know enough to say for sure.

I installed a proper graphics card today and haven't had this problem since. Still not sure what the issue was, but it's over at least.

I have encountered this before, it was because of graphic card.

This was supposed to be fixed a while back but I still see it

Not likely anything will get done about this