Two games in a row CTD at turn 170. Playing two player multiplayer I was the client friend was the host. played flawlessly to turn 170. Then started getting memory allocation failures consistantly during my city build screens. It didn't matter what building I was building. This happend every other turn. Then he had the brilliant idea to save to another file name on each crash, that allowed it to go 4 or 5 turns before the memory allocation error. This never happened on the host only on my client machine, in every case he was able to save and we could continue.
As soon as I clicked on a building to build it would crash, on reload I found his machine accepted the build order. In every case I was just using the pop up drop down never entering the city screen. In every case it crashed as soon as I clicked on the building to buy. This seemed to be the only place it would crash.
Side note a couple of odd things, the AC counter pop up would appear and have to be manually removed by clicking on the AC counter itself a couple of times. Also one time in a city build screen on the pop up not in the city screen a pop up of a great person overlaid the drop down and had to be closed first before picking a building to build. I was thinking this or somthing like this may be causing the crashes.
We are both using patch N of course. Hope this helps nail down this annoying crash. Plus is there anything hardwired to happen around turn 170 - 171 ish? Like increase in inflation code or another event?
I dropped my resolution down to 1200 x 900 ish that didn't seem to help on the memory allocation errors. Is anyone else getting memory allocation errors? Especially in the city build screen right after selecting a build? What I am getting at is do I need to look at my system / hardware or clues in the game. All my 3d shooters play fine on maxed graphics at 1920 x 1080.
