Crashes on Gigantic Battles?

Quintillus

Resident Medieval Monk
Super Moderator
Supporter
Joined
Mar 17, 2007
Messages
9,306
So I've been playing Medieval II all summer (autumn now) in one epic campaign. Now that the Timurids have invaded I'm having some really epic battles - up from the 2500 or so maximum I'd see in Europe to 3500 and even 4000 and 4500 troops in a single battles. That's all well and good, except for one thing - I get lots of crashes. It seems that the epic battles are pwning my computer even more than the Timurids are pwning most of my armies (I maintain I am winning the war against them nonetheless, in a Grant vs. Lee in 1865 fashion).

What happens is that I can deploy my troops, but shortly after I start the battle (a couple seconds in the 4000 and 4500 troop battles, somewhere in the first minute with 3500), I usually get a "Medieval II has encountered an unspecified error" message and the game quits. I tried the 3500 once five times and it crashed three of those (hit Auto-Reload Last Save by accident after the first non-crash time). I've had two crashes and no successes on the 4000/4500 one.

The battle that's crashing now is an open field battle with the Timurids; the earlier one was a city siege in which I was attacking and the Timurids were both defending and reinforcing. I have fought battles with the Timurids both in and our of cities, with and without pachyderms, without problems.

The easy solution would be to auto-resolve the battles, as smaller ones don't seem to encounter this error, but what's the fun in that? So I ask, is this a common problem (my guess by Google is it is), what's the cause of it ("unspecified error" is a great help, isn't it? :rolleyes:), and what's the solution?

Specs:

M2TW Version: 1.00 (unpatched because I don't know if the patched versions are save-compatible [Civ3Conquests 1.00 and 1.20 aren't, hence the uncertainty] and I don't have Disc 2 to reinstall with if the they aren't. I'll try patching if it's save-compatible)
Core 2 Duo T7500 (2.2 GHz) - seems pretty maxxed out with this many troops
GeForce 8600M GT DDR2 256 MB with up to 256 MB additional from shared system memory - it has occured to me that perhaps I'm running out of VRAM with this many troops. Lower graphics settings hasn't solved it yet but I haven't bottomed them out.
3.5 GB DDR2 RAM (2x2 GB) - not even coming close to using all of it
XP Home SP3 32-bit
Game Year: 1454 Anno Domini
My Civilization: France
Affected armies: So far only Timurids, haven't fought in other armies in that large of a battle though so my guess is all of them
No mods have ever been installed

If it's fixable I'm suspecting it's a patch version problem, but as noted, if it isn't save compatible I'm not patching.

Thanks! Can't wait to fight an even more epic battle than my ones thus far have been!

Further information: I could not get it to crash on a few garguantan Custom Battles. Both a 4000-man battle involving Timurids (including the vaunted elephants and elephant artillery), as well as a 9000-man battle involving all European nations did not results in a crash (though the latter did cause a massive frame rate drop). However, I did receive a warning that battles above 4000 were not recommended for based on detected settings.
 
The crash is because your motherboard exceded its temperature failure, and before it burns all modern motherboards/graphic cards have a safety switch that either causes the game to crash like in that message or the entire screen to go black.

I sugest you download a temperature control software to know how hot your pc is. Cooling is something very important in nowadays powerfull computers and there are cheap and expensive solutions for the problem.

A cheap way off cooling down your pc tower duing large battles:
Chakra.jpg

70$

or just buy two fans for 10$ and make small holes in the front and side panels and glue the fans in yourself ;)

My dual core 3.3 ghz, 1 Giga DDR, 256Mb Ati Radeon 9600 Pro can easily play up to 12,000 at same time but beyond that point it slows down and freezes over 20,000 but never had a crash.
 
Seriously? But then why would it not crash on the 9000-unit test battle I did? It fails even when I have not been playing the game for a long time. I will try underclocking my CPU and GPU; adding fans isn't feasible as I'm on a laptop but I'm quite certain the temperatures are within safe ranges even if they are a bit warmer than ideal and I have been monitoring them for some time. I've even undervolted the CPU to help lower the temperature.

I recently dropped back to stock Dell drivers instead of newer, modding, unofficial ones, but it did not solve the problem.

Edit: Tested it again with fans on maximum and both CPU and GPU underclocked (by 18% and 21%Core/15%Mem) and CPU undervolted (saving 33% power in addition to underclocking savings). It lasted longer than it had by a minute or so, but still crashed, this time with quite moderate maximum temperatures:

CPU: 59C
GPU: 60C
RAM: 54C
Motherboard: 57C
HDD: 39C

Now I know I've run games (and clocks/voltages/non-maxed fan settings) that have caused temperatures to go much higher than this - I've hit 89 CPU, 70 GPU, and 70 chipset before in other games with no problems whatsoever (as well as significantly higher ambient temps), and even those temps were within thermal specs. So I don't think it is temperatures that's the problem. Any other ideas? Or can someone confirm save-compatibility?
 
The best thing to do would be to download the patches. But also, on the main menu of the game, go to options, and I think its game options(could be something else) and change the unit scale from whatever you have (probably large) and lower it to small or normal.
 
The best thing to do would be to download the patches. But also, on the main menu of the game, go to options, and I think its game options(could be something else) and change the unit scale from whatever you have (probably large) and lower it to small or normal.

It sounds kind of like a resource conflict. Unless you have stopped all other unnecessary programs. Or it's possibly a hardware conflict if you have recently added new hardware to your system.

Though I would try downloading and installing all the patches as Churchill has stated, as this could also be the cause of the problem.
 
The patch seems to have fixed it, and thankfully didn't break any compatibility. There's a few changes in how the game runs from the patch, but nothing that big.
 
The patch seems to have fixed it, and thankfully didn't break any compatibility. There's a few changes in how the game runs from the patch, but nothing that big.
That was a very lucky solution for you.
 
Back
Top Bottom