*** Prim3D has run out of cache space for rectangles ***
Your video card ran out of memory. So it switches to sys ram, or VMem so you are correct in that respect.
*** Pool's Allocated Space has been used up. new / delete is being used as a fallback. ***
That one is new to me. I never saw it before even on my old amd sempron box. Sounds like a low resource warning.
c:\gs\entrenchment\CodeSource\GS\Player\PlayerOrbitBodyInfo.cpp(170): assert! [squad != 0]
Its one of your hangar defense structures. AFAIK Hangar defense must have at least one squad assigned or sins spazzes out. Check out all your structures that are supposed to have squads, and make sure you have command points assigned.
c:\gs\entrenchment\CodeSource\Engine\DataStructures\DynamicVector.h(172): assert! [i >= 0]
The line of doom.... Yup that does herald a dump. The infamous dont bother to tell us what freaking file its is that sins cant read dump.
That error usually means there is an older sins version file in your mod somewhere that 1.041 wont read. You just have to guess which file it is. That is the reason i am rebuilding SoA 2 from scratch. I got that very same crash error with SoA 2 0.3e.102, When i eventually got an answer that is what i was told. Its a bad file header somewhere. Which means older sins version file. I just wish DEV.exe threw us a freaking bone as to which one/s they were.
You need to go over your mod and make sure that any unmodded vanilla sins files are NOT in your mod folder. You also need to make sure what you do have in the mod folder is from version 1.041. You dont need to copy the entire sins gameinfo folder, or any other folder for that matter into the mod folder anymore. You only need to put in what is actually modded, or changed. Also make sure if its an entrenchment mod that the foundation files are from entrenchment.
Hope that helps.