SkyRattlers said:
I'm having the ever common problem of the game playing for anywhere between 5 mins to an hour and locking up and crashing. I've tried adjusting the ini file. I've turned off AA, write faster, hardware acceleration, etc. I'm pretty sure I have all the latest drivers, directX, etc.
So here's my dxdiag file in hopes that someone can see something that might help me.
If DxDiag doesn't report any problems, then it's really not much of a help.
Zydor might reply that your HW doesn't meet the MSR (even if it clearly does) or state that your "hassles" are due to HW because it's not "acceptable" to him.
Some crashes are naturally due to HW faults (bad design, manufacturing defect, too much overclock/overvolt, etc.), but in such cases other similar games should crash too and the machine should be unstable in other ways. If you read the forum, it soon comes pretty evident that the suggested solutions are presented in the few key threads and once you have gone through all of them, nobody will be able to help you by just looking at some dxdiag report (which almost always list no dxdiag problems but give specs which can be attacked as the suggested cause of the problem).
I think that after all of the
standard solutions have been exhausted, the next step for everyone should be to send crash dumps, log files and traces directly to 2K Games Support (instead of Microsoft through their Windows Report Control). Coders at Firaxis are the only ones who have the sources and debug builds, who can actually find out why their SW crashes in particular situations. If they then discover a solution/work around, which is not a patch to their own code, they can post it as a FAQ answer in the 2K Games support site, so we can link to it from here. Even if they develop diffs which are not released as independent patches, waiting for a commit to the next main patch, they can still inform people who have the problem that a fix to it is on the way.
Core dumps can be generated from Python by setting
in CivilizationIV.ini and these will be written on disk to the user "temp" folder (rather large, but may be necessary for the devs to really find out what happened prior to the crash).
Instead of binary dumps, which might be difficult to send to support if they don't provide FTP or similar facilities for it, it might still be helpful to send basic logs with a text symbol table dump (such as provided by Windows standard
Dr. Watson). In any case, after all the help and suggestions other forum members can offer, only the coders can do something to fix bugs in CivIV. They won't be reading every thread and post here, if any, so it might be necessary to push the support email route to get this information to their attention.