Comments - nutmeg_

If you haven't fixed this, please provide a screenshot of your medieval 2 base directory that contains the executables.

This advice is not accurate. Crashes are typically caused by memory outage, something likely with a mod that lobs on massive model after massive model. Medieval2.exe is identical to kingdoms.exe in the game engine's consideration. If this is such a good fix, point your launcher at kingdoms.exe in the first place and have people duplicate before installation as many large profile mods already do, and please, end the memory outages by integrating LAA.

No, no, no. Renaming medieval2.exe to kingdoms.exe and nothing else simply screws up the base game and only has a single function - to correct the mod launcher not finding kingdoms.exe if it's not configured to find medieval2.exe. No crashes will be fixed unless the launcher is buggered up in the first place and doesn't know how to find m2 - which, by the way, would launch the vanilla game, not crash it.

Copy medieval2.exe and rename it to kingdoms.exe for maximum compatibility with old mods.

To actually fix crashes, apply the Large Address Aware fix to medieval2.exe, or that + kingdoms if you made a copy. The game runs out of memory past a certain point, and this effect is accelerated if little effort is made to make economic models for the engine. LAA allows the game to access more memory and thus have a much reduced chance of crashing. This, by contrast, is a good idea even if you're playing something like the lighter resource mod Stainless Steel, which still has a high chance of running out of memory on large sieges left at the 32 bit limit.

You could at least give credit to the teams that made your asset-rip mod possible (DAC, reforged...) but, you probably won't.

Shameful display. Passing users - play a real mod, like the ones I mentioned instead.