Fallout 3 on Windows 7.

[Wishmaster]

I would certainly install Fallout to a directory other than Program Files. Like C:/Games or whatever.

After installing all your mods, did you update and run BOSS?
BOSS for FO3 - Better Oblivion Sorting Software for Fallout3 at Fallout 3 Nexus - Fallout 3 mods and community

If not, try that.


I would just delete the ini files, and start the regular Fallout launcher.
Set your settings and Res there, then close it.

Next, open FOMM and install all mods. Run BOSS after you install each Mod.
Then make the merge patch with FO3 Edit and place at end of load order.



It is possible, one of the mods is crashing the game.

If all of the above fails, what I would do is start disabling 1 mod and try again.

Keep disabling 1 mod at a time untill the game starts. Then youll find your culprit.
Time consuming I know .. but it works.

I had a issue a while back where the game would crash upon entering a building. It was driving me nuts trying figure out what was wrong, but since it was a reproducable crash, disabling 1 mod at a time pin-pointed it. It was all because of 1 lantern mod.


**You should also be able to get a version of FO3 edit that does not need to be installed. Just drop it and its content into your Fallout directory.
And BOSS should just be dropped into the DATA directory.

Hope this helps.

 

[hankelc1974]

Thank you for the advice. This solved one conflict...the patch for Marts Mutants and Merc 2 RE: corpse flies was causing the lockup. So things load up and run, but of course there's the matter of textures. Some of them don't work without ArchiveInvalidation, but if I turn it on the game crashes in about 5 seconds after loading up. Turn it off and no crash, but nothing that requires it will quite work either, i.e. no replaced textures. So this is the next bug to fix.

Solutions so far:
use FO3 loader from disc to place FO3 in it's own folder under games, not programs - GO
use FOMM, FOSE, FO3Edit and BOSS to integrate mods - GO
run without corpse flies from Mart's and thus no need for the patch - GO

However = run with ArchiveInvalidationInvalidated - NO GO = CTD

 

[Wishmaster]

Have you tried enabling it, disabling it, the re-enable it?
Ive had wierd things where this fixed it.

The only other thing I can think of, is double check the path is correct you extracted the new textures too. Especially if it was a manuall install. I know it sounds silly, but something that can be easily overlooked.

I use ArchiveInvalidated myself, but never had such an issue. So Im a bit unsure what to suggest.
Did you put it in the DATA folder?

 

[hankelc1974]

Have you tried enabling it, disabling it, the re-enable it?
Ive had wierd things where this fixed it.

The only other thing I can think of, is double check the path is correct you extracted the new textures too. Especially if it was a manuall install. I know it sounds silly, but something that can be easily overlooked.

I use ArchiveInvalidated myself, but never had such an issue. So Im a bit unsure what to suggest.
Did you put it in the DATA folder?

I did try the on-off-on with AII but it was still a no-go, and it was in the DATA folder...however, it may not have been in the merged patch that FO3Edit created...I will give that a try.

I also tried manually reloading the bugged textures into the data files, but that only worked for one session; when I next powered up they were bugged again. These are the ones the authors say "needs AII to work"

We shall see what the latest experiments reveal.

 

[hankelc1974]

the source of the crash

Having tried the experiment(s) unsuccessfully and done some research, I came across mention of a bug reportedly identified in 2008 when Archive Invalidation Invalidated was applied to Fallout 3. Setting the value from 0 to 1 to allow the new .bsa's to operate would case a crash in Windows for reasons unknown. In 2009 no fix had been found. I'm 99% certain this is the cause of the crash (and the reason FO3 new textures never work; the game crashes and never runs the complete script). So, has anyone found a solution to this bug since then?

 

[Wishmaster]

One other thought ...

Are you running AI as Admin? I would guess your are, but just a thought.
I know it needs to be to work properly.

 

[hankelc1974]

One other thought ...

Are you running AI as Admin? I would guess your are, but just a thought.
I know it needs to be to work properly.

I've been using the built-in with FOMM, set to Admin mode. I suppose I could try running it as a separate program in Admin mode.

 

[Wishmaster]

One other thought ...

Are you running AI as Admin? I would guess your are, but just a thought.
I know it needs to be to work properly.

I've been using the built-in with FOMM, set to Admin mode. I suppose I could try running it as a separate program in Admin mode.

Ive had issues in the past with Fomms built Invalidation, and no longer use it myself.

Give this one a shot:
ArchiveInvalidation Invalidated at Fallout 3 Nexus - Fallout 3 mods and community

Just drop it in your DATA folder, and run it as admin, and enable.
Ive never had issue with this one, (The Program Version) and hopefully it will resolve the problems you are having.

Let us know how it works out for you.

 

[hankelc1974]

I gave your suggestion a try but it didn't work. FO3 crashes 7-10 seconds into loading any time the AII.bsa is present in the data directory.

 

[hankelc1974]

I gave your suggestion a try but it didn't work. FO3 crashes 7-10 seconds into loading any time the AII.bsa is present in the data directory.

Next experiment: place AII.bsa in DATA manually, and manually reconfigure the Fallout3.cfg file (no .ini file was found, and changes were seen in .cfg if AII pgm used) resulting in .... no crash, but still no acceptance of new texture paths. It seems to have ignored my manual changes. Note that I changed 0 to 1 in AII without the .bsa mentioned later on on files, and nothing changed or crashed, so I think the problem is a conflict with where the .bsa is coming in.

*of note* but perhaps unimportant, when FO3Edit runs, it mentions "11 expected" for "FO3" so perhaps there is other data missing. No idea.

Next experiment - try turning all the .esp's into .esm's vs. repair files.

 

[hankelc1974]

It turns out there are 2 fallout.cfg's . . . one in the Fallout directory, that I was manipulating to no actual effect, and one here : C:\Users\[myname]\Documents\My Games\Fallout3

Manipulating the fallout.cfg file in C:\Users\[myname]\Documents\My Games\Fallout3 replicates the crash, whether using AII manually, with the separate AII program, or with AII baked into FOMM

So, question 1: should there be 2 fallout.cfg's?
question 2: is there a possible benefit to merging C:\Users\[myname]\Documents\My Games\Fallout3 and C:\Games\Bethesda Softworks where the .exe, data files, etc. reside?

 

[Wishmaster]

The ini file in the Fallout directory itself is just for the default settings. It will have no impact on the in game settings you set.

Merging the documents w/the Installation directory will not help, No.


Im really not sure what to recommend here. Ive never really had such issues with textures.
At this point, I would completely uninstal FO3, and delete any file left over.
Re-Install so that you have a fresh copy of the game.

I would delete the Fallout ini and Fallout Pref. ini located in the Documents/My games Folder. (Actually I would delete these before uninstalling the game)

Start the normal launcher itself, and set it to Med. Quality, and then set the resolution (For now-You can bump up the settings once you get the game stable)

Boot the game in its vanilla state, and close it once you get to the main menu.
-->>By doing this, you will recreate the settings at default values in the Documents/My Games Folder<<--


You can go ahead and active GFWL now if you want. Lots of people disable it, I have myself in the past. But, as of late I just leave it enable. Ive had no issues with it and I run a lot of mods. With the exception of any mod that requires FOSE. But, FOSE will disable it anyway. I've found disabling is not at all needed, even if you want to run FOSE.

Then open Fomm, start activating mods 1 at a time, and run BOSS after each mod.

After you activate 1 mod, and sort it, boot the game (with Fomm) and ensure you get to the main menu. (No need to start a game, just make sure it will launch)
If by chance all is going well, and the game starts crashing after a mod gets installed, you'll know its a likely culprit. Disbale it, and try again to verify.

Keep going like this until you get all your mods installed.

Then, run AII (from the DATA directory) and activate it. It should all work now.

Dont forget to make a Merge Patch with FO3 edit after all this is done, and put it at the very end of your load order.


This is the procedure I do, and never had any major issues, aside from a buggy mod here and there.... Not really sure what may be causing the issue for you TBH.

 

[SarumanW]

For those of you who are still struggling with this.. or at least the 0xc00005 Exception at New Game, I did something that fixed my problem that MIGHT fix yours.

Locate and download the d3d9.dll and place it in the same folder as the Fallout3 executable.

See if that works.

 

[hankelc1974]

Problem solved

I did finally fix the problem. Steps:
1) clear everything
2) reload, register and update FO3 and all DLC
3) load AII and run from FO data directory as admin
4) load all mod management programs and run as admin
5) reload all mods / patches, running BOSS, etc. for them
6) test each one for crashes and conflicts
7) avoid "corpse flies / MERC 2" patch - causes CTD on load
8) remove "better intervention" patch - causes CTD on load

Result: works fine

Thank you to everyone here who did provide input / advice, all of which was helpful and never snide or condescending

 

[Wishmaster]

Thanks for the update & glad you got it all sorted out.

Now you can enjoy a modded version of one of the best games ever, at least IMO.

 

[personrawr]

Okay, I just bought the GOTY edition, installed the game on my 64bit windows 7 pc, and launched it. It works fine until I click 'new game' (it crashes immediately). I've done every fix for this issue I've seen and still cant fix it.

 

[Jerbuta]

Okay, I just bought the GOTY edition, installed the game on my 64bit windows 7 pc, and launched it. It works fine until I click 'new game' (it crashes immediately). I've done every fix for this issue I've seen and still cant fix it.

Hey man, I had that the first time I played it, connect it to Games For Windows and do the latest update.

 

[Doa744]

i still can't get fallout 3 to work :/
compt. mode doesn't change a thing.
i can always start the game and if i get lucky i get to play like a minute, if i'm not it freezes the moment the game is loaded.
i tried it as both system administrator and non priv'ed user

system is:
Window 7 Home Premium 64bits version 6.1.7600

 

[VisMajorX]

I THINK I may have figured out why Fallout 3 doesn't work on Win7 x64 - the "Crash to Desktop" (C2D) problem at least, because I had it myself AFTER installing all my DLCs, Mods and of course the 1.7 patch. I wasn't even aware that this problem existed.

Anyways, I uninstalled it and went back to playing Vegas.

HOWEVER, something today made me try it out again.. just wanted to waste some time I guess.

1) So I installed the game, I DID NOT INSTALL ANYTHING ELSE. Nada. Didn't even change the graphics settings. DID NOT CHANGE OR INSTALL ANYTHING BUT THE BASIC GAME!
2) I started up the game, and Win 7 freaked out about my AERO desktop theme causing issues with the game and got the Crash to Desktop. Well that was new... so I went in to the desktop settings and changed the theme to CLASSIC BASIC... okay. Lets try again.
3) Started up the game, and ... no crash. Played through to the end of chapter ESCAPE! and exited the vault, all in glorious 640x480 + low quality settings. IDK if thats necessary to do.. its just what I happened to do. NFI why I did it either.. probably just so surprised that it was working and wanted to see how long it would. OH! It crashed once on me after basic character creation, so I restarted and then it worked fine all the way out the vault.
4) THEN... I installed PATCH 1.7 and.. started the game back up again... and, no crash. There I am standing outside of the Vault... so I walked to MegaTon... no crash, met the Sheriff, had a chat.

So I have NOT installed ANY of the DLCs AT ALL, yet! IDK if you guys have tried (I'm sure you have though) to run the game, just the patch also without DLCs. Right?

ALSO, I turned the theme back on just now and started the game and it worked, so now I'm a tad confused. HOWEVER, it could just be that FIRST START UP, you need the graphics set to DEFAULT and the desktop theme not as Aero, but classic/basic. Play a bit (if it starts up with no C2D), save and THEN set your graphics options.

(Also, I noticed my dt res is set to 1600x900 for some odd reason and I'm quite sure that the last time I tried to run FO3 it was at 1920x1080 ... so perhaps that has issue too.)


I KNOW this sounds asinine but it might work. The game was doing the same thing for me, I didn't change compatibility or anything like that, I haven't done ANYTHING to my system since uninstalling it the last time (couple weeks ago) when it wouldn't start up (wouldn't get past 1 second of the load intro) EXCEPT PERHAPS I installed the update for my ATI card for the game RAGE from ID ... but basically, no... my system is a wreck (its a mess in here) and for some reason this time it started up.. hope this helps.

People also say that they DELETED the FALLOUTPREFS.INI and all other setting INIs.. I'm wondering if since the game perhaps responds poorly to those files existing on first start up, if that is a bit similar to my own "playing the game on basic settings" for awhile before changing graphics options (also I'm now seeing other people removing the aero theme from running while playing), seems like a similar issue since deleting those files WOULD set all the options back to the lowest default, right?

Update: I installed the DLCs while my character was at MegaTon and the game still plays fine.

 

[DDDimo]

When i play Fallout 3 the game just freezes. It happens every 1 to 5 mins. It gives no errors just "not respond" in the task menu so i hae to constantly end task it. I tryed restricting the processor to 2 cores or even 1 (intel core i5 2500k), the drvers of the vdeo card are up to date (Radeon HD 6700). I heve 4gb ram. Chaneged the run as adminaistrator and XP servis pack on the launcher and the other icon. There was a d3d9.dll file suggested in you tube that might worck. I am on 1.7 pach (don't know uk or us). Running on windows 7 ultimate.
Sorry if this was already discused.