Common Errors and/or Crashes Section

Status
Not open for further replies.
Have you tried clearing the cache? (It might have bad values after your initial run)

Yes I've tried that too.

Do you suppose it could be a problem with graphics memory? I am using the mobo chipset since my video card took a dump on me not long ago.
 
Yes I've tried that too.

Do you suppose it could be a problem with graphics memory? I am using the mobo chipset since my video card took a dump on me not long ago.
Do any other complex Civ4 mods work (e.g. RoM:AND, the FfH2 derivatives, ...)?
 
Noticed a bug/error with the Great Generals. Not sure how long it's been there as I haven't actually checked this particular thing before.

Strategic Command (ZoC) and Initiative IV (continues attack while at full strength) don't work.

Cheers
 
Yes I've tried that too.

Do you suppose it could be a problem with graphics memory? I am using the mobo chipset since my video card took a dump on me not long ago.

Spec's on PC pls:confused:
 
@SO
That model only shows 1024MB of on board ram. Mine has 2048MB.

MSI R6450-MD2GD3/LP Radeon HD 6450 2GB 128-bit DDR3 PCI Express 2.1 x16 HDCP Ready Low Profile and it cost me $59.99 plus shipping. I also picked up an ASUS DRW-24B1ST/BLK/B/AS Black SATA 24X DVD Burner for only $18.99. Both from NewEgg.

Now back to the CTDs, everytime I crash the last part of the Microsoft report has a Python failed init string. I had one last night that I thought was reproduce-able as long as I didn't save. But once I saved it would not repeat. From my observations the crashes are generally at end of turn and right after an autosave. I have the Mod setup, per Kosh'd instructions, to autosave in Max Compat. But the game acts like the autosave is incompatible with the mod or the autosave finction of BtS.

Since I have today off I'll do some more testing to try anf get some concrete results.

JosEPh
 
Well from the review of what i just read here: http://au.answers.yahoo.com/question/index?qid=20101107213408AAFR1u6 your video card is mainly just for very low end games and C2C is very very high end. Sorry:blush:
Still, the initial screen should work fine when it works for mods like RoM:AND.
And C2C is mainly high in its memory usage I think which might collide with system memory usage in such onboard graphics.

You could try some very low resolution to see if it has something to do with graphics memory.
 
@SO
That model only shows 1024MB of on board ram. Mine has 2048MB.

MSI R6450-MD2GD3/LP Radeon HD 6450 2GB 128-bit DDR3 PCI Express 2.1 x16 HDCP Ready Low Profile and it cost me $59.99 plus shipping. I also picked up an ASUS DRW-24B1ST/BLK/B/AS Black SATA 24X DVD Burner for only $18.99. Both from NewEgg.

Now back to the CTDs, everytime I crash the last part of the Microsoft report has a Python failed init string. I had one last night that I thought was reproduce-able as long as I didn't save. But once I saved it would not repeat. From my observations the crashes are generally at end of turn and right after an autosave. I have the Mod setup, per Kosh'd instructions, to autosave in Max Compat. But the game acts like the autosave is incompatible with the mod or the autosave finction of BtS.

Since I have today off I'll do some more testing to try anf get some concrete results.

JosEPh
Try this DLL. I included the Minidump mod so it will create a Minidump file when a crash occurs which I can open to see the trace (within C++).
Also check if it is any slower than the normal DLL or if we can include this DLL as default so people can send us Minidumps of crashes.
 

Attachments

Just D/L'd it and will put it in. Thanks AIAndy.

JosEPh :)
 
Just crashed on a new Pre Era game with the minidump dll. Logs attached.

This time I didn't even get a black screen 1st. 1 second I was in the game and next second I was on my desktop.

JosEPh
 
Just crashed on a new Pre Era game with the minidump dll. Logs attached.

This time I didn't even get a black screen 1st. 1 second I was in the game and next second I was on my desktop.

JosEPh
Probably because of the Minidump. Look in the folder with the BtS Exe for a MiniDump.dmp and send it.
 
This CTD occurred at 8000BC. Minidump and Logs attached.

I have been keeping track of the Autosaves and it's not always the same # of turns. Is this normal?

From the 1st CTD @9600Bc the next autosave (as) was 9040 (7 turns), then 8800 (3 turns), followed by 8480 (4 turns), 8160 (4turns) then ctd @8000Bc. Do not know if any of this is relevant or helpful? But it seems that the CTDs always follow an Autosave by 1 or 2 turns. Maybe just coincidental.

JosEPh
 
7520BC CTD 1 turn after autosave @ 7600BC. Minidump attached.

JosEPh
 
This CTD occurred at 8000BC. Minidump and Logs attached.

I have been keeping track of the Autosaves and it's not always the same # of turns. Is this normal?

From the 1st CTD @9600Bc the next autosave (as) was 9040 (7 turns), then 8800 (3 turns), followed by 8480 (4 turns), 8160 (4turns) then ctd @8000Bc. Do not know if any of this is relevant or helpful? But it seems that the CTDs always follow an Autosave by 1 or 2 turns. Maybe just coincidental.

JosEPh
Thanks for the dump. Fixed that one, it was actually a different bug in the AI civic choice than I originally thought.
 

Attachments

7520BC CTD 1 turn after autosave @ 7600BC. Minidump attached.

JosEPh
Ah, looks like I need to keep the PDB files from past compilations. Since I fixed the other bug the PDB changed and it no more displays the actual line it happens in for this dump.
Please send the minidump when it happens again. I can only tell that it is some Python code that calls a DLL function and then it crashes right in that function.
 
This new .dll has the mini function still in it I'm assuming. Plus the civic fix. :cool:

Will post as soon as it happens.

JosEPh
 
This new .dll has the mini function still in it I'm assuming. Plus the civic fix. :cool:

Will post as soon as it happens.

JosEPh
Indeed it has. And if you don't see a significant speed drop I will keep it in as it makes debugging crashes far easier.
 
Status
Not open for further replies.
Back
Top Bottom