View Full Version : OS Corruption


whiplash_CDC
Oct 25, 2008, 02:20 PM
I've played a kazillion hours of BTS SP using the 3.17 patch. Just lately the game locks up, usually on a save load. Nothing in my configuration has changed. What worked fine for a long time no longer does so.

A normal lock-up would just be a minor annoyance; but now it corrupts the XP operating system so that it won't reboot properly. I need to try multiple times or boot from the CD.

Any Ideas?

[KC]Bantams
Oct 27, 2008, 07:35 AM
sounds like a dying graphics card or maybe a dusty fan i would look inside pc case and and check its got good ventilation try playing with the side panels off might help airflow :p

Woody1
Oct 28, 2008, 05:37 AM
I've played a kazillion hours of BTS SP using the 3.17 patch. Just lately the game locks up, usually on a save load. Nothing in my configuration has changed. What worked fine for a long time no longer does so.

A normal lock-up would just be a minor annoyance; but now it corrupts the XP operating system so that it won't reboot properly. I need to try multiple times or boot from the CD.

Any Ideas?

You're not seriously suggesting that Civ4 is corrupting your O/S, are you? This doesn't sound like a problem that has anything to do with a bug in Civ4. You need to trash your current crappy computer and get a real one. It's dying.

HolyHandGrenade
Oct 28, 2008, 08:23 AM
I've played a kazillion hours of BTS SP using the 3.17 patch. Just lately the game locks up, usually on a save load. Nothing in my configuration has changed. What worked fine for a long time no longer does so.

A normal lock-up would just be a minor annoyance; but now it corrupts the XP operating system so that it won't reboot properly. I need to try multiple times or boot from the CD.

Any Ideas?This sounds like a hardware problem, mainly the harddisk. If you have a 2nd harddisk boot from this one and make a filesystemcheck. Perhaps you have the chance of doing a system repair at boot-time. If not :mad:

whiplash_CDC
Nov 20, 2008, 06:37 PM
Thanx for the suggestions. It turns out that the problem was overheating of the power supply.