@ op
The mod works fine without crashing, it just pushes the boundaries a bit with regards to textures, sound etc. , just like some other mods, but as python, the language used to write the mod, is a bit unforgiving (to be non technical), it can cease to function during the game, and present a RGL log to help identify the cause.
It happens a lot in some large expansive mods, and some work may need to be done to discover why your particular machine spits the game out. The fact that it will play native is because it does not push the boundaries as much as some of the big mods, like this one.
When you first start Warband, before selecting a mod, it allows you to "configure" Warband. There are not many options there, but you will see "force single threading" (i think that is the exact text). It is put there for a reason, that is because Pyhton is a bit old, and can have problems when running on multiple cores, so make sure this is ticked if you have multiple cores. Textures on demand is another one to help with lower spec machines.
So
1) What are those settings, i.e. which boxes are ticked
2) You say you like using cheats to check the game out. What cheats are you using? battle size etc.
3) What sort of machine are you running this on? Ram CPU graphics, will it run in Dx7 (selected in game when the mod is active).
4) Try disabling sound, my machine does not like playing some large Warband mods with my Soundblaster XFI enabled, I have to play using the motherboard onboard sound, just an example of how finicky the game can be.
If you prefer not to enlighten us with such details, why not search for guides to help people with this problem, there are a number, usually at the start of the mod, (I think one was put at the start of 1776), if not still there, pick any big mod and a search, that should give you a guide.
Last, this is a great mod in the making, worth taking the trouble to explore why it will not run on your box, but that is up to you, there is not much more help I can give
