The game crashes during the Please Wait screen, so then it is on an AI processing turn.
Okay, that helps a bit. Try using only three of the four mods (i.e., not both Mythology and Ascension) and see if it still happens.
I don't know what logfiles are, kind of an idiot in modding, I don't make mods.
No problem. It's like this:
1> Find your user directory. In Win7, it'll be in My Documents/My Games/Sid Meier's Civilization V/. This is the directory containing the MODS folder you placed my mod's files in, so I'm sure you know where it is.
2> In that folder, open the file "config.ini" in notepad.
3> Right at the top is "EnableTuner = 0". Change it to a 1.
4> About two-thirds of the way down the file is "LoggingEnabled=0". Change it to a 1.
5> Near that entry will be a bunch of other flags involving logging, all of which default to 0. You can turn whichever ones look interesting to you to 1, but they're not really necessary for this.
6> Okay, now back in that user directory is a "Logs/" subdirectory. Within that folder, the game will create a bunch of logfiles. The only ones that really matter are Database.log, xml.log, and Lua.log. Now, the core game will give assorted warnings and errors in those files (especially in the Lua.log file), so you might want to start up a non-modded game once, to see what sort of things are "normal" in each file. Then, when you load up my mods for a game, you can see if it added any additional errors to each.
I have noticed also that when I see my Settler in the beginning the promotions of the unit are so abundant that they cover the top parts of the letters that spell 'Settler.'
That's the conflict I mentioned between Mythology and Ascension. The game breaks if there are more than 200 promotions in the database; Base+Empires+Mythology or Base+Empires+Ascension each come in just below that line, but the full set of 4 goes about 20 over the limit, so every unit will be given the last 20 promotions in the table. It's possible that one of those promotions is responsible for the crashes (if it's something the unit it's on isn't supposed to have), so try running only 3 of the 4 and see if it still crashes.