All kinds of errors!

So I just installed M2TW Kingdoms on a new drive, steam version outside of program files. Made sure it worked by starting a campaign. Everything works.
Downloaded EBII 2.2 installer version, didn't realize EB II 2.1b was still there, so uninstalled EBII, deleted old EBII files, redownloaded 2.2 installer to fresh folder. Reinstalled and its still crashing. Crashes first time on starting a campaign. Error message says: "Unspecified error. Please compress your error log in a zip format and upload it on the EBII technical help forum."
Restarted EBII and tried again. This time it ran but crashes again and tells me I have a fatal graphics error which is the first graphics error message I've had on any TW game or EBI or II version.

Here's a quick summary of all the things wrong in my error log. Pasted in word in landscape with zero margins I get 56 pages of errors! I've never seen so much and since this was my second installation with everything Funny thing is that my log doesn't go to "mods/ebii/logs/eb.system.log.txt" it goes to "C:\Steam\steamapps\common\Medieval II Total War\system.log"

[system.io] [warning] open: countless things missing!
[data.missing] [warning] missing/invalid cursor
[script.err] [error] Script Error in mods/EBII/data/export_descr_buildings.txt
[data.missing] [warning] Cannot find the portrait path
[script.err] [warning] Trigger parsing warning in mods/EBII/data/export_descr_character_traits.txt
[script.err] [warning] Trigger parsing warning in mods/EBII/data/export_descr_ancillaries.txt[script.err] [error] Script Error in mods/EBII/data/descr_sounds_units_anims.txt
[data.missing] [warning] Sound file missing

system.log.txt

Those errors happened to me the first time i launched a campaign but they were happening before this update too.
After that everything worked fine as usual. Maybe your map.rwm got messed up.

Most of that stuff isn't relevant at all; do a search on [error] to cull it down to the things that matter - there's 130 hits.

Of those, all those EDB errors are false positives; the game is reporting the fact that they have more than one upgrade option. It's not an "error" at all, and doesn't do any harm.

Most of the things it's reporting as missing are irrelevant vanilla files, which won't cause a crash. Even then, missing stuff is almost always defaulted to something else. Warnings don't matter.

This section is potentially problematic:

Code: [View]

13:10:29.187 [script.err] [error] Script Error in mods/EBII/data/descr_sounds_units_anims.txt, at line 1254, column 89
Volume is out of range.
13:10:29.187 [script.err] [error] Script Error in mods/EBII/data/descr_sounds_units_anims.txt, at line 1254, column 93
SOUND_DB::read_sound: Invalid sound

13:10:29.187 [script.err] [error] Script Error in mods/EBII/data/descr_sounds_units_anims.txt, at line 1256, column 11
SOUND_DB::read_sound: Invalid sound

13:10:29.189 [script.err] [error] Script Error in mods/EBII/data/descr_sounds_units_anims.txt, at line 1257, column 12
SOUND_DB::read_sound: Invalid sound

13:10:29.191 [script.err] [error] Script Error in mods/EBII/data/descr_sounds_units_anims.txt, at line 1258, column 12
SOUND_DB::read_sound: Invalid sound

13:10:29.193 [script.err] [error] Script Error in mods/EBII/data/descr_sounds_units_anims.txt, at line 1259, column 12
SOUND_DB::read_sound: Invalid sound

13:10:29.194 [script.err] [error] Script Error in mods/EBII/data/descr_sounds_units_anims.txt, at line 1260, column 12
SOUND_DB::read_sound: Invalid sound

13:10:29.196 [script.err] [error] Script Error in mods/EBII/data/descr_sounds_units_anims.txt, at line 1261, column 12
SOUND_DB::read_sound: Invalid sound

13:10:29.198 [script.err] [error] Script Error in mods/EBII/data/descr_sounds_units_anims.txt, at line 1262, column 12
SOUND_DB::read_sound: Invalid sound

Even then, the game gets past it fine. I can't see a terminating error in there at all; if this was a CTD, the last line should be the error.

It seems to be some bizarre bug whereby the first generation always crashes for some people, but then the game should run fine after that.

Cool, thanks for the prompt replies. I changed it to windowed to see if that fixes the graphics error message. So far so good.