Hahaha! I think I may finally have some satisfactory asnwers folks! I just installed Fable: TLC a few days ago and was experiencing syptoms quite alike to the ones you are all suffering. In my case, the game was crashing almost arbitrarily without discernible causes. I could only play the game for periods of time between two minutes to fifteen minutes (sometimes thirty if I was lucky). Like most of you I suspected the drivers for various hardware including video card, sound card, chipsets, etc, and of course Microsoft isn't very helpful. I mean, this [expletive] game doesn't even have any patches?! However after spending a fruitless day reinstalling and restarting my damned infernal machine I finally stumbled on what I think may be the real issue behind the spontaneous crashes plagueing this glitchy piece of [expletive] game in pure desperation! A POSSIBLE SOLUTION FOR COMMON ARBITRARILY OCCURING CRASHES: Start > Run... > Type "msconfig" in the "Open:" dialogue box and click "OK." msconfig is a system configuration utility that allows users, among other things that I am not an authority on, to control which programs are allowed to automatically execute at system startup. System Configuration Utility > Startup (Tab). All of the items that are checked in the list are programs that initiate on their own at startup and usually work in the background (possibly without you even knowing!). Uncheck EVERYTHING that is not necessary. Because I am not exactly sure which of these services was causing my game to crash, I unchecked almost everything, with the exception of the most basic, necessary of items (Soundblaster Volume Control, Rundll32, ATI Radeon, Shaw Update Loader, that sort of stuff). The things I did end up UNCHECKING included stuff like ItunesHelper, Ipod services, Quicktime, Adobe Acrobat Speed Launcher, Logitech SetPoint, and even Symantec & Norton Antivirus services. You those sorts of things that are extra things, half of which I didn't even know where running in the background. This will sort of make some things a pain in the [expletive] in that they will have to be manually loaded via launching the .exe files, but seriously...it's not that much of a pain. Hopefully that helps somebody, and if anyone actually does figure out exactly which background service is actually causing the disruption, be sure to point it out to the rest.
