why fallout 3 keeps crashing

[Deleted54170User]

I uninstalled everything down to the regedit and used a Registry Cleaner to wipe out the remaining files and deleted the XLive\DLC\Content as well before charging up the Registry Cleaner. I am going to wait a day or two and let my temper simmer down. When I reinstall I will do so without GFW LIVE 1st and than if I am really desirous of mental pain and anguish I will re-install the GFW LIVE software I removed too.

 

That is; if I am really interested in playing anymore of the GFW LIVE games!

[overload1977]

also when you reinstall only get the first patch then get the fake patch from the Nexus try that

[Deleted54170User]

also when you reinstall only get the first patch then get the fake patch from the Nexus try that

 

Thanks for the advice.

[RigorMortis]

I apologize if this "solution" to the constant crashes that many of us have experienced with FO3 DLC "The Pitt" seems trite or has been posted before, but in case not here's my situation and how I seem to have managed to overcome it.

 

First, my system in brief:

 

Fallout 3 patch 1.50

Vista Home Premium 32-bit SP1

Intel Core2 Quad Q9550 @ 2.83 GHz (no OC)

4 GB DDR3 RAM

Nvidia GTX 280 (1GB RAM) no OC

Non-RAID Hitachi 7200rpm 500GB HDD

 

First off, I find that killing unnecessary background procs can make a difference with a lot of game problems so I use the handy program "EndItAll" (make sure you know how it works before using!).

 

I discovered that many of MY crashes happened when I pressed F5 for Quicksave. It also tended to crash in conjunction with fast travel. The solution for the F5 problem seems to be completely overcome by using the console ~ and "save <savename>". I have reached and entered "The Pitt" and various spots therein without a single crash or other problem. I use the ~ save frequently, and it's just about as fast as F5. Why this is the case I don't know, but I was about to trash the mod shortly before I tried this out. I had terrible problems with the first DLC for this game OA, and gave up on it. I'll reconsider it and hope I can get similar improvements. :thumbsup:

 

If it helps anyone I'm happy for you. :biggrin:

 

RigorMortis

[RigorMortis]

Call me anything but Ishmael. :confused:

 

This reads more like a (very) short story than a demand for answers (but please read on). :thanks:

 

I guess I'm at that age where the well-intentioned, but woefully lacking in self-analysis, game designers of the razzeldazzel demands in recent years of creating my passion for the great PC-oriented FRPG diversion from the harsh realities of my real-world life.

 

I've been playing Fo3 since it came out, and for much of the original game, except for a few situations where I found a specific place or method of entry/action, I had relatively few problems with the game (and I'm well acquainted with Bethesdas TES games and files, etc).

 

As time went on I added a number of user created mods and embelishments, mostly without problems. I first came up against a wall when I (after an insane amount of unnecessary complexity in purchasing, downloading, and FINDING the d/l'd datafiles for OA) :blink: I discovered that once I plugged OA into the game Problems Ensued with nearly every step. I struggled to work with it but gave up and unplugged OA.

 

Since then the game returned to working pretty well. :biggrin: So, after almost finalizing the Main Plot, I decided to do a comprehensive exploration of all the places I had not yet seen, and that has been fun and mostly problem free. There still remained a few spots left (probably most notably the Oasis) when I decided to acquire "The Pitt". Once installed I experienced many crashes, but I managed to get from my luxury apartment in Megaton all the way to the tunnel to the Pitt, and once there I had NO PROBLEMS throughout playing this interesting DLC mod. The problem is, that once I returned to the Wasteland ALL the crashing (always a little window telling me "This program has stopped working") :wallbash: . I wanted to, at least, visit the Oasis, before installing Broken Steel, but the primary problem is that I can play the game as long as I want, but virtually every attempt to SAVE the game results in a crash (as described above). :wallbash: :wallbash:

 

So I un-pluged "The Pitt" and again tried to make my way, but I now experience a crash on every attempt to save, which makes any attempt to play the game pointless. I've tried to eliminate several user-mods to no effect. I shut down all non-essential background procs, to no effect. :wallbash: :wallbash: :wallbash:

 

I'm a disabled man of 60, using and programming computers for half my life, with a love for RPGs. I don't get out much (and hate programming anymore) and I put a lot of very precious money into building this machine so it might last me more than a year or 2, and I'm hearing stories that these high-power CPUs and grafix cards are possibly causing the problems! This is INSANE! :verymad: :wallbash: :confused: :wallbash:

 

Here's what I have, briefly:

 

Fallout 3 patched to 1.5.0

Vista Home Premium 32-bit SP 1

CPU: Intel Q9550 @ factory settings

GPU: Nvidia 280 (1GB VRAM) @ default speeds, latest drivers

4GB DDR3

2 x7200 rpm 500GB Hitachi HDD (not RAIDed)

Other assorted bells and whistles not related to gamplay

 

I went through numerous problems with the previous TES games from Bethesda, and someone somewhere found a solution to all of them, and I loved and played the hell out of them, but as much as I enjoy Fallout 3, the problems seem like they can't be fixed, and I'm not in the mood to go through the hellacious issues of re-installing the game on another

 

Please, please help me, oh High Emperor of Bethesda, or anyone else that can. Are you testing my faith, as God tested Job in a similar sado-masochistic orgy of anguish? :whistling:

 

Your humble slave,

RigorMortis

[RigorMortis]

well i installed it on a drive that windows is not install and as never had fallout3 install too

 

then used CCleaner 4 times just to be safe to clean up, cleaned the Registry as well

 

also before i installed again i del everthing to do with fallout and used Diskeeper 2009

 

oh and used scandisk took agessss but everthings working great.

 

one other thing i redownloaded my driver for my 3d card

 

so far i have the pitt ,OA and about 25 mods installed and no bugs what so ever but still got to get back my old saved games, but then again i may just forget them and start anew with new chars

 

i dont think i will install all my mods again untill i get Broken Steel in 3 days and see how that runs

Hi - I ran CCleaner, defraged, chkdskd the HD and reinstalled Fo3, and removed all GFWL, and the game worked fine and completed the in-game mini-quest "The Grove" without problems. I returned to my flat in Megaton. I think that's when I applied the Official Patch v1.5.0 and now the game crashes ALWAYS, and so far ONLY when a SAVE is attempted, either AUTOSAVE, F5 Quicksave or console save. The game just won't save. So that leads me to question if, under Vista 32-bit SP1, could there be a collision with the OS that is suddenly preventing the program access to writing to the default SAVE directory? I'm scanning the .ini files, but I don't know (or like) Vista as much as I did XP (and AmigaOS and BSD UNIX before all that I have today!), and don't rightly know where to look for a solution short of tedious the tedious and voraciously un-deserved methods described in great detail in the previous messages. :wallbash:

 

I'm much obliged to anyone with a working paradigm for this issue, :thumbsup:

 

RigorMortis