How to Install & Use Process Monitor (ProcMon) - to gather data about loading CTD's

[Hound of Ulster]

I've only had two CTDs when loading and the first hasn't occured since (Loading Campaign map after starting campaign with Casse) with the most recent was while loading the battle map for a single-unit engagement with the Samourtae. I went around the crash by reloading the campaign autosave and disbanding the unit in question, then saving the named campaign file. It strikes me that most loading CTDs occur because of cranky hardware more than the mod itself. My computer does get squirrelly if I've played Rome and its mods for an extended period of time. EB's one problem for me (and a potential cause of loading CTDs) is how large and detailed the campaign map is. It takes at least 10 minutes for my computer(a fairly new Dell laptop) to load the campaign map for the first time going into the game.

[Malik of Sindh]

It takes at least 10 minutes for my computer(a fairly new Dell laptop) to load the campaign map for the first time going into the game.

It takes 15 minutes for my crappy old computer with NVIDIA GeForce FX 5200 (128 MB) to load the campaign map,and I still think EB is worth the these 15 minutes.

[Hound of Ulster]

It most defiently is worth the wait.

[Sygrod]

Can ProcMon capture problems caused during battles? That's where I have a world of problems.

[Tellos Athenaios]

During? I wouldn't count on it. Mostly because by the time you are actually in-battle you do not have to load very much (for you've just done that to get in-battle), do you?

[bovi]

I think Tellos is right, but it sure can't harm to run it.

[oz_wwjd]

Would Process Monitor work for MTW2 as well? I've been having some problems with CTD's when I try to play a battle myself instead of autoresolving and I've been unable to track down exactly why it's doing it.