Varden

It does look like it is a common theme among the crashes listed here with the exception of Scottishhans who I believe posted he had an Intel Pentium 4 processor. Might be something to this though.

Reinstall did not work for my particular case. Still crashes at same point and during autosave. No error message no error recorded in event viewer. Hero Save did work in the Necropolis area though. Upon actually trying to restore a Hero Save when saved in the Necropolis it also crashes to desktop no warnings.

There have been instances where there was a world save in progress and the game shutdown and I got an error box saying it needed to shut down and I did the submit info. I would have to experiment more with some of my earlier saves to try and duplicate it to see what exactly happens. In this case with the autosave it simply kicks me out to desktop with no error messages at all. Here is the message in the Event viewer I received from one of the crashes last night. At 12:45:16 Faulting application fable.exe, version 25.7.13.149, faulting module msvcr71.dll, version 7.10.3052.4, fault address 0x000029c1. 0000: 6c707041 74616369 206e6f69 6c696146 0010: 20657275 62616620 652e656c 32206578 0020: 2e372e35 312e3331 69203934 736d206e 0030: 37726376 6c642e31 2e37206c 332e3031 0040: 2e323530 74612034 66666f20 20746573 0050: 30303030 31633932 0a0d At 12:45: 28 Fault bucket 223255251. 0000: 6b637542 203a7465 32333232 35323535 0010: 0a0d31 Second Attempt and Error at 1:19:27 Faulting application fable.exe, version 25.7.13.149, faulting module msvcr71.dll, version 7.10.3052.4, fault address 0x000029c1. 0000: 6c707041 74616369 206e6f69 6c696146 0010: 20657275 62616620 652e656c 32206578 0020: 2e372e35 312e3331 69203934 736d206e 0030: 37726376 6c642e31 2e37206c 332e3031 0040: 2e323530 74612034 66666f20 20746573 0050: 30303030 31633932 0a0d No other errors are displayed in the Event Viewer for my crashes this morning. On a side note after a crash during a save or autosave the save becomes corrupted and can no longer load. I just did an uninstall and moved a copy of my save games out of the folder to try and see if this will fix anything. I am fairly certain that during any crash with an Autosave there will be no error messages and any crash during a world or hero save will give an error message. I will try to see if I can duplicate this too.

Ok here's a problem I have run into and its repeatable. The game seems to want to crash at specific points where it autosaves after completing a quest. The first time I experienced this was with the "Break the Siege" sidequest. The quest ran fine but afterwords I would attempt a save or autosave it would crash. I did not try anything here but simply sidestepped the issue by not doing the quest all together The second instance is 100% repeatable and is Main Quest critical. At the Necropolis where you must dig up all the glyph tablets once I actually complete the quest and get the 4th tablet by defeating the "summoners" and opening the grave. I get the quest completed window and the experience rewards and the Summoner guantlet trophy and immediatly the autosave window comes up and then crashes to desktop. I have tried to do the following: Update my graphics card driver and sound card driver Reduced video settings to lowest settings and resolution Turned off music and sound Adjusted configurations on character in game that had particle effects Attempted clean boot procedure as described at support.microsoft.com/games I have found no other documentation of this problem thus far or any patches to date on the game it being a fairly new release I don't suspect I will any time soon. Setup is the following: AMD Athlon 64 X2 dual 3800+ 1.0GB RAM ATI Radeon Xpress 200 series 256mb integrated Realtek AC'97 Audio integrated