Fallout3

[Cobweb]

I have been having a running battle with Bethseda Softworks ever since I bought my super Quad Core ASUSM2n SE Phenom with 4Gb RAM 64bit vistaHP in a sesame bun . I install the game fine but every time I try to start a new game it crashes to desktop. I have been through everything including adopting the suggestion that I temporarily uninstall Smart Doctor and ASUS Gamer OSD in spite of my protests that it was integral to my pre-delivery configuration and that every other game compatible with F3 (eg Mass Effect) worked fine. I have since updated both software apps to a more up to date version. Bethseda are still insisting that these two programs and the ASUS mobo are likely causes of the problems.

Has anyone come across this problem with Fallout3? I have tried the Bethseda Forums already and drawn a blank

Any suggestions would be of great help. I would like to tell Bethseda that they are sorely in need of a patch for their software but I am currently coming up short on reasons

Many thanks

[red fox]

I understand what you are going through, I spent some time on those forums trying to troubleshoot my own problems, which turned out to be hardware related.

What graphics are you running and what drivers?

I still watch that forum, I will keep my eyes open and post back if I see anything that may help, but your best bet if you havent done so already is post a dxdiag there and see if anyone spots a problem.

[Cobweb]

Originally Posted by red fox

I understand what you are going through, I spent some time on those forums trying to troubleshoot my own problems, which turned out to be hardware related.

What graphics are you running and what drivers?

I still watch that forum, I will keep my eyes open and post back if I see anything that may help, but your best bet if you havent done so already is post a dxdiag there and see if anyone spots a problem.

Hi redfox

Here's the latest data on my graphics. NVIDIA 9600GT Driver version (from Windows Device Manager) 7.15.11.8250 dated 27th March 2009

[Cobweb]

Thanks for the advice redfox. I have posted my dx data as advised. wolfpup has come up with a few helpful suffestions which I will check out via his links. Mine may turn out to be a hardware issue as well, but it is really frustrating not being ablke to bottom this out. I have never had a problem that has caused so many difficulties and has avoided analysis. It feels sometimes as though I am trying to unravel a plate of spaghetti