Game crashes at specific time in win2000

[DroidDr]

Ok here goes :

I am playing the greeks, and the romans have 1 city left, when I defeat all its defenders, the game just crashes. ( 'civilisation.exe has created an error, generating error log.' or something like that, the typical win2000 program dying). Whatever I do to alter the situation, chosing razing or occupying won't change a thing. So I decided not to take the city but later this happened :

After I finish a turn in 1955, the opponents do some of their moves and then the game crashes, just like the above problem, but now I can't continue. Anything that I try to alter the situation again solves nothing.

I put the saves so people can look at them if desired.

Also during, the game, often the music playback does a scratchy noise and then no more music (sounds are ok though). Sometimes the music comes back later. Looks like an mp3 playback issue.



My computer is : (although these problems do not look like a driver issue)

Athlon XP 1700 +
Asus A7V266-E Raid
512 MB DDR
ASUS V8200 Ti200 DELUXE Video card
40 Gig Maxtor 7200 ATA133 drive
SoundBlaster Audigy OEM
Pioneer DVD drive
Yamaha CDR 8424 IDE

Drivers :
Video : ASUS drivers -> based on 21.81 Detonator Drivers
Via 4in1 4.36

Win2000 SP2

Civ3 : new patch (the good one)

Norton Anti-Virus 2002 disabled, no other significant programs running.

[Rhandom]

I've got the exact same problem. I'm playing a large map, have wiped 2 civs already, and killed all of the persians except a tireme. I built a caravel to go kill it, but every time I do, the game crashes.

I also have win2k, and this is the first time I've had the problem. AMD duron 800, 300+ram, blah blah blah. I've got it saved, loading it after rebooting changes nothing. Figures, it was looking to be my best monarch game.

I can include it if anyone cares.

[threejaguar]

Same here. As soon as one of my saved games gets to a certain point it crashes.

I saw on one of the other threads that it has something to do with AI declarations of war.

The infogrames site says it is just a bad executable in the pre 12-7-2001 version of the 1.16f patch, but I loaded the latest, and it still crashes.