CTD without error

[Tobblish]

I started playing TATW again with MOS, played the campaign and later started to play around with custom battles.

Using HUGE teams etc and the game just crashed at one point. [My PC Specs in spoiler]

Spoiler Alert, click show to read: 

CPU: 2500k @ 4.5 Ghz
GPU: GTX 580 also OCed
RAM: 12GB

Now I can't start a new campaign with any faction, can't run custom battles either.
I can however run quick battles without problems.

When I click the start button on the campaign screen it just returns me to the main menu.
If I then click the Campaign button again it CTD with no error.
If I click the custom battle panel it just CTD without error.

I've tried to reinstall everything, deleting the geo files without success.

It's ONLY with MOS installed that the problems occur.
Is there some hidden file that I have to delete?

Running the Steam version.
Windows 7 UAC is long gone.
Using the version to rename the TATW folder to americas, have changed to the others as well.

EDIT:
Ok somehow it now works after a 3rd full uninstall of TATW.
I ran one normal TATW Campaign one time before installing the MOS mod.

Awesome troubleshooting yey! \O/

[Ulfgard the Unmaker]

I realize that this thread was from last week and the OP fixed his problem himself, but I am also experiencing CTD without explanation. I find this odd, as I've been able to play TATW 3.2 in the past. I cannot fathom why I would start having problems NOW.

Whenever I try to start a new campaign, regardless of faction, I get a CTD with no error message whatsoever. The loading progress bar will fill all the way, but for the smallest fraction at the end, and then it will hold there for a few minutes. At this point, the game CTD's with no explanation. I can still load custom and quick battles.

Running Windows 7; steam version of M2TW:K. As I've said, I could run it fine a few months ago. I set the mod aside and focused on Hyrule Total War, and Call of Warhammer: Rage of Dark Gods, as well as Wrath of the Norsemen for some time. I haven't the foggiest why TATW seems to be acting up now. Any thoughts?

Incidentally, I did a clean install after I first encountered this problem today. No luck yet. Also, in my first reinstallation, I tried to install 3.0, then patch successively to 3.1 and 3.2. Last time around, I decided to skip trying to patch, and I found that the problem persists with a clean install of 3.0

[StealthFox]

Do you have Steam set to auto-update M2TW? It could have overwritten some of TATW files with vanilla Kingdoms files.

[Ulfgard the Unmaker]

I just disabled it. I'm going to delete and run another clean install.

No luck. Still getting the same crash. I can't imagine what's gone wrong.

-----
So, for as much as I don't want to do this and have to re-install the other Kingdoms mods that I have, do you think a clean install of Kingdoms might be in order? Up 'til now, I've been just trying to work on fixing my problem by doing clean installs of TATW.