Game crashes at start up, even after reinstall.

[Speedstripe]

I'm running Win 7, and the game had been working fine stock standard.

 

I tried to mod the game. Installed:

ArchiveInvalidation Invalidated! v1.0.6

Fallout Mod Manager (fomm 0_10_2)

Animated Prostitution (and all the files it was suggested it work best wtih?)

- Animated Prostitution ESM

- Alice Package

-APSoundPackV2

-bzFO3MalesV1dot6d

-bzsyArmourFixesV2dot2

-Fem_Voice_Package

-Naouak_Female_Body_Replacer_v4-1

-Type3_V2_TEXTURE_pack

-TYPE3RAIDERTEXURESfull

 

I thought I would give that one mod a try before downloading others.

I added the packages though Fallout Mod Manager, and ran Archive Invalidation Invalidated.

 

Tried to launch the game and it crashed straight away.

Unchecked all of the mods, tried again, no effect.

Tried uninstalling Fallout 3 completely and re-installing the game.

 

Before running any mods, I thought I'd give Fallout3 a try and it crashed at start up again.

 

So Uninstalling and Reinstalling the game had no effect, and now I'm still with out fallout :/

 

How many mods are there that change registry values?

 

I'm suspecting that ArchiveInvalidation Invalidated! v1.0.6 may be the culprut, but I can't be sure as I'm not entirely sure about how it does what it does.

Does this mod change redgistery values regarding Fallout 3. If so, what does it change, and what are those valuse supposed to be.

My origional F3 installation directory was in Program files, a place that ArchiveInvalidation does not like.

Even so I've re-installed the game to a different spot.

If a redgistry entry was changed, it wouldn''t have been changed back by the F3 uninstaller.

 

Could the other pervy mods have caused this?

[mechine]

LMAO sniffing parts out of car seats I see. naw none of that is your problem. All these mods you have listed are of a complex nature. Some being very complex. The only mods that will realy change the registry as far as we are concerned as modders are ones that use AutoInstallers. Which only change it as part of being made in such a was as to use the windows installer. Love it hate it, why worry.

 

Typically what you have on gettting a mod is raw data, folders and files, that's it. Packed into Rar's or 7Zipz, this is what you want as it's the best way to end up with a very clean install. The old guide used to say the best way is to just get in there an get your hands dirty. Open the rar in one window, then open your data folder in the other, make your way down thru the whole mod, checking to see what it may or may not replace, or mess with, an take a note on how well put together the mod is, then you decide if you want to use it. And while you can blindly drag an drop the whole folder in, and pick yes to all, It might be the case that you need to go thru there file by file an pick what you want in there.

 

FOMM FOSE and Fallout 3 probably change the registry a whole bunch, but it's nothing we need to even know about. The mods you get are not like Torents, you won't find malware or spyware, or underware in them, well maybe a bit of underware in your case. AutoInstallers could have that sort of thing, but from what I know, there's only a few of those anyway, I only use FOOK2's auto installer, an then unofficial fallout patch. If I can avoid a autoinstaller than I install it manually. Most times if you rename a FOMOD then it goes back to the manual install way. Plus people usually have both manual an auto version available for download.

 

One of the reasons that I only use stuff from Nexus is because I know it's all trustworthy stuff. You go off on other places there's no telling what you get.

 

 

 

Being that you are somewhat new to this, I would advise to start small with simple mods. Once you can get about 80 or more of those to work well then start building in the complex stuff one mod at a time. You have all the tools you need to be able to do whatever you want, but it's going to take sometime before you are any good at it. The first thing that will help you is the guide pinned topics here at nexus forums.

 

http://thenexusforums.com/index.php?showtopic=120735

 

http://thenexusforums.com/index.php?showtopic=125185

 

http://thenexusforums.com/index.php?showtopic=83642

 

 

From there go on to make a plan for your build, will you only use about 100 or go for 200 or go for the max 255. A 255 load order will take about 2 weeks to fix, but if you slowly build up to it, there might only be several parts of 2 day fixes which are seperated by months of game play. So you see the best way to do it is break it up into parts, so it's not so much like work. Autoinstallers are going to automaticly overrite anything that gets in their way with the same file name, so some care should be taken in your plan to either run them first a overrite them with only stuff that is hand picked from small mods. The opposite is true as well, but mind you this is only in cases where the vanilla base content was changed, custom content will not be overwriten, because usually it's in it's own folder.

 

You should also take the time to have a good install of fallout 3 before you get into mods. I install, patch, then install FOMM FOSE GECK the GECK update, FO3edit. Then using the RAOTW method (random A**hole Of The Wastes) creating a random charicter an running around in the game to see how well it runs. Then I use the TweekGuide http://www.tweakguides.com/Fallout3_1.html While also testing any changes with my RAOTW. Then I install the DLC's an test it again, with the DLC's in the order they came out. Once it's running very smooth I'll move on to mods. Which in my case I will start with about 60-80 tiny simple mods, which don't even really have that much content.

 

When the mods are installed, I try to figure out a load order, which usually is like things with other like things, armor with armor, perks with perks, weapons with weapons. Fallout.esm at the top, the DLC's follow next in order, then all the other stuff. Once I get it kind of right I try to load the game, if it crashes at the load screen or before it means the order is wrong, to which I'll open the whole load order with FO3edit to figure out which one is causing the problem, change it, once I get it so that it will load up an not crash, maybe even enter the game world I move on to the next step.

 

Web-ensized FO3edit Guide by CSB http://www.fallout3nexus.com/downloads/file.php?id=9616

 

FO3edit will namely create a Merge Patch (semi automated gathering an filling of holes in spreadsheet like lists across the load order) Then Master Update will change all the mods into Psudo .esm (as the .esm method is rather dirty compared to .esp plug ins) But master update also does other things we don't really need to know about other than it gets rid of crashing. Between the Merge Patch an the magic Master Update does you just got rid of about 50% of the crashes or more. With the other 50% being how well your system an build is.

 

First I create a merge patch, save it, then fix the stuff in the merge patch with FO3edit. After that I start at the top an work my way down, fixing everything. If it can't be fixed by normal drag an drop or copy paste means, then I create an override to do it, which is a .esp plug in, with mods added as need as masters to it allowing the use of all content contained. Usually it's scripts an other data which need the overrides to fix, but you can make things work like they never were intended to work. Take 8 different effects from 8 different mods an apply them to one item in game. Then following the plan, after everything is fixed in the whole load order. I'll master update it an play.

 

 

While doing this I'm not only fixing things, but giving final aproval on the things the people that created the mod made as choices, high damage, high health, or too much of one thing or the other, I pick the best settings, an use them. Recently I don't really get down into the dialog, cell, or worldspace too deep trying to fix something, because those are the really huge parts of data. I'm lazy, so I just scan over them.

 

 

Now I'll start the new game, when I exit Vault 101 I don't move, I let the system catch up an all the 10,000 scripts start up, an finish, then the DLC's too. Then I go to a small cell with nothing in it. I'll set all my FOSE in game settings for mods. Maybe even ~showracemenu an go over my charicter again. Then ~PCB purge the cell buffer, an create a new save, never auto save, disable it, each time press ESC an create a new save, then never delete any save until your ready to delete them all. Then never add in mods to your load order until you are ready to delete the save games an start a new game, as it's risky adding mods to a existing save game.

 

 

After that really all I do different is purge the cell buffer every so often, with help from Groovatrons teleport ablity, I'll go to the black room an ~PCB watch the data go by, then teleport back to where I was in the wasteland, only with a clean cell buffer for performance. Then depending sometimes I double load my save games because it's usually faster the second time, load a save fast travel somewhere then load the save again.

 

You won't find it anywhere but if you turn off fallout 3's AA an AF (performance) an force whatever AA an AF you want from your grapics card contorl panel, it will run better.

 

 

 

 

Remember start out small an simple then work your way up, building in complex things as seperate jobs you can focus on after you have played for a while.

[Speedstripe]

But, any ideas on how I can get a workin installation of Fallout 3 now.

 

As I've said, I tried uninstalling and reinstalling the game, and the game will not work anymore, with out any mods.

[Smosh]

But, any ideas on how I can get a workin installation of Fallout 3 now.

 

As I've said, I tried uninstalling and reinstalling the game, and the game will not work anymore, with out any mods.

 

It sounds strange that you can't get it to work. Do you have CCleaner to clear old registry entries?

 

Uninstall Fallout 3

 

Run CCleaner

 

Reinstall Fallout 3

 

See if that works at all.

[TweekedOut]

I'm having somewhat of a similar problem. Win XP SP2 though, as opposed to Win 7. An uninstall of FOOK2, FOMM, then the game proper. Deleted the remainder of the files in the F3 directory (DLC stuff). Reinstall, put in DLC, patch to 1.7. Did this several times. Now, I'm getting a Windows error message on the patchings and it ends up shutting down fallout3.exe.

 

The game hangs at a black screen right before the title slides. No music, most times no program manager on hitting CAD, and requires a hard reboot. I've run CCleaner and Auslogics registry cleaner. Fixed all the problems there.

 

It is really weird and it's really bothering me. I want to play, but this problem is making me very mad and frustrated, that it continues to happen and seems to be getting worse.

 

I'm not about to do a clean install of Windows. No game is worth the time and trouble of doing so.

 

Edit - Hmm...I don't know what's going on now. Nothing has changed, but this time I a) defragged my secondary drive and b) installed to that secondary drive. Now, I can at least get the title slides to come up, granted I haven't put in the DLC packs yet, but it is at version 1.7. Nothing else has changed. OP, try putting it on something other than the C:\Program Files\Bethesda\Fallout 3. Try a different drive, if you have one.

[arkentera666]

There is a simple solution to all of this, Alls you got to do is uninstall the game, then locate the program files folder and delete the leftover files from in the bethesada folder. Actually you can just delete the bethesada folder. This will garuntee fixed. Let me know if this helps you!

[cur7is]

I'm having this same problem on Windows 7 64bit. Fallout crashes at startup even after a fresh reinstall. I've run CCleaner before and after reinstall to no avail.

[Fonger]

I'm having this same problem on Windows 7 64bit. Fallout crashes at startup even after a fresh reinstall. I've run CCleaner before and after reinstall to no avail.

1 - did you delete the surviving fallout folder(s) after the uninstall??

 

2 - did you correctly - install to other than the default location!! Or did you place it where the Windows XP game asks to be put (that Windows 7 causes problems with)

[Katuko]

Finally I find someone with the same problem as me. I've been on several forums looking for people with the same issue to no avail.

 

Whenever I try to run Fallout, I just get a black window. No sound, just an infinite "loading" cursor until Windows finally tells me it's not responding and shuts it down.

The weird thing is that the problem did not occur due to faulty mods: Everything was running smoothly until one day it just stopped working. And it took the Battlefield games with it, it seems. I can't run those either now.

 

And to tell the truth, it's happened twice. First I was running Vista and got the problem. My friends said it was a problem with my drivers, so I updated all of those (I dunno how many times I've reinstalled the damn NVIDIA GEForce 9600M GT driver. It didn't work, so I didn't bother until about a week later when I installed Windows 7 and everything worked fine again. Now, six months later, the problem has returned.

 

Uninstalling mods did not work.

Reinstalling Fallout 3 did not work.

Updating drivers (again!) did not work.

Cleaning the registry and reinstalling Fallout in a different location did not work.

 

I'll try what you said: Removing any and all traces of Fallout and Bethesda from my hard drive, then install it again. I don't think it'll work, but I'll try. Like TweekedOut, I'm not keen on having to reinstall Windows itself to get this working again. I'm pretty sure whatever a reinstall fixes can be mimicked by a small, Fallout-specific fix.

[Fonger]

The weird thing is that the problem did not occur due to faulty mods: Everything was running smoothly until one day it just stopped working. And it took the Battlefield games with it, it seems. I can't run those either now.

that may be a clue

 

Nothing in FO3 could influence Battlefield games

 

so its a common operating system function.

 

I'm willing to bet that it has something to do with Windows Live

 

In FO3nexus you can find at least 1 mod that remove GFWL from FO3 (or at least dummy up the ddl)

 

since you have nothing to lose, give it a whirl.

 

Alternately - update GFWL (microsoft site)