Crashing(freezing) on FO3 1.703

[Dragunover]

CPU : AMD Athlon II X2 240 3.3Ghz

GPU : Nvidia GTX 260 Core 216, 65nm, 257.15 drivers

MoBo : ECS A780GM-A

RAM : 4 sticks, 2x2GB, 2x512MB

OS : Windows 7 64 bit, up to date

Load Order

http://i977.photobucket.com/albums/ae252/Dragunover/FOMMLO.jpg

 

It would seem like every 2-20 minutes my game just freezes up. It seems to do it more often when fast traveling, saving, or during battle. I don't recall it doing a CTD or any actual bug reports (EDIT: It just did that, but in the same old regular style of randomly doing it). Just that the game is unresponsive. When I force-kill it through task manager, it's usually running ~600-1,000MBs of RAM.

My other issue lies within my CRT's resolution. It can go to 1920x1440 or 2048x1536 on custom resolutions, but EDID denies that. I've been using Nvidia's customizable resolutions, and even though Fallout 3 doesn't recognize them (it's set to run @ 1600x1200 and won't go higher) it will still hang when starting up IF I am running the resolutions on windows.

[Dragunover]

Really hate to have to bump, but this is still very much so a problem.. 47 views and no responses????

[vettexl]

I replied to a similar topic to this, try some of what I posted. http://thenexusforums.com/index.php?showtopic=210228&view=findpost&p=1840027

[anokii]

I suspect it's your NVidia drivers.

According to the NVidia website the version your using are Beta which I wouldn't recommend under any circumstance unless the readme specifically addresses a problem you are having.

 

In my case I found an obscure thread on another website where the guys there were talking about general performance and stability and they mentioned that version 186.16 was the best to use. I downgraded mine and I can now run over four hours continuously without a CTD and I'm running a fair few mods. Up to that point I went mad with trying all sorts of fixes. NVidia has a tendency to break things during their driver updates / upgrades so be careful with updating them once you get some stability.

 

You'll need to go to the NVidia website and do a search for the drivers under Beta and Archived drivers.

 

BTW: I'm running the same OS and GTX 260 as you are.

 

One last thing - you should always load esm's before any esp's.

[Dragunover]

I suspect it's your NVidia drivers.

According to the NVidia website the version your using are Beta which I wouldn't recommend under any circumstance unless the readme specifically addresses a problem you are having.

 

In my case I found an obscure thread on another website where the guys there were talking about general performance and stability and they mentioned that version 186.16 was the best to use. I downgraded mine and I can now run over four hours continuously without a CTD and I'm running a fair few mods. Up to that point I went mad with trying all sorts of fixes. NVidia has a tendency to break things during their driver updates / upgrades so be careful with updating them once you get some stability.

 

You'll need to go to the NVidia website and do a search for the drivers under Beta and Archived drivers.

 

BTW: I'm running the same OS and GTX 260 as you are.

 

One last thing - you should always load esm's before any esp's.

Actually, this problem has been occurring over several generations of nvidia drivers, it's just that I recently have been trying to fix the issue. If it is an nvidia driver issue it has nothing to do with a specific driver but rather with the fact that they just can't make one that will agree with the game.