Got a problem in your Fallout game? Post it right here, in this thread. First post is a problem which I solved. I can't tell you all how ecstatic this makes me.
FALLOUT 3 CRASH TO DESKTOP WHOA #1
So this is a bit of troubleshooting for those who might also have this same problem. It's about a very specific CTD I I kept having: crashes at Megaton's gate. Urgh. Maybe the solution below will also take care of all the random CTDs I keep having... usually they'll occur anywhere form a half-hour or later into playtime.
Go into the main Fallout 3 folder and right-click on FalloutLauncher. Maybe you'll need to left-click and then right-click. There should be a large panel which pops up. Select Properties, and then the Compatibility tab.
Select "Run This Compatibility Mode For" and then choose whichever operating system in the scroll-bar. I've got Windows 8. Click Apply, Click OK.
That is all. I've walked my character in and out of Megaton like seven times now.
Your random CTDs might be the multi core bug in Fallout 3. When the game was being made, multi core cpus were still being invented. So it was made for the old-fashioned single-core cpus. But by the time the game was released, multi core cpus were a thing, and the game often crashed on them. This might fix it.
Open up the fallout.ini file in: My Documents\My Games\Fallout3
Find the following lines, and change the values to these. If they don't exist, paste them in:
This will limit the game to 2 cores and prevent the engine bug from causing the game to freeze.
If it still crashes, try setting it to iNumHWThreads=1
I had the multicore bug too and got it fixed, as well as the Windows LIVE thing. Thankfully, when I installed Fallout 3 on my backup computer I got it to work without hickups
Good you got it sorted, Renee. I've never had anything work by doing what you did so I'm glad to see it work for once
The only fix which helped me, when I was having lots of CTDs in FO3, was to place the New Vegas (yes, New Vegas!) anti crash file in the FO3 folder. CTDs ever since have become extremely rare. I've tried all other possible fixes, even some of those mentioned above, but none of them worked. It's good that we post different solutions / fixes here, because what may work for someone, may not work for someone else.
Rosa: Thank you. I also did check out the multi-core processor .ini fix, but my FALLOUT.ini file already has the appropriate lines added in. I think because I have that Unofficial patch (I forget its full name) this already made those changes.
mirocu: Yes the Games For Windows Live nonsense is what plagued me back in 2016 when I was trying to get Fallout 3 on my PC. That was extremely aggravating, and I don't think Steam (which is where I got F03) even mentioned having to deal with GFWL. In my opinion Steam should put a warning in BIG BOLD LETTERS right up front about this. It's only because I've become somewhat of a pro at PC crises that I did not immediately try to get my money back. Right Lopov?
Polov: Wow, that's very unusual. I already do have an anti-crash dll file installed, but not from New Vegas. Maybe now I will try removing this .dll file, because maybe my game is fine with the Compatibility fix stated in the OP.
It is very true that everyone's game seems to be different. Even with consoles, you'll have one group of people claiming their game is broken to unplayability, and an entirely different experience from another group.
Something else you can add to the list that causes unexplained CTDs is using Gysnc. I did not realize I had my Gsync turned on, and was having CTDs at random. Then once I realized it, I set the game to run on a fixed refresh rate, and that fixed it. It is the standard problem of Bethesda's games being made to only run at 60 fps. Going over that breaks the games.
Ha I don't know what Gsync is. I wonder if I have that activated. I don't think I do. I would remember that term since it's an obvious play in Vsync. My game is capped at 60, but I don't think I use Gsync.... I've got something else influencing framerates.
G-sync is a relatively new monitor technology. I wrote about it in the Gaming Technomancy topic somewhere around here. http://chorrol.com/forums/index.php?showtopic=5904. It basically replaces V-Sync, by automatically changing your monitor's refresh rate to match whatever your video card is putting out at that very instant. So it goes up and down dynamically, and that dramatically reduces stuttering, which is typically caused by the video card being unable to keep up with the 60 fps that V-sync demands it run at.
But it also means that the video card can run as fast as it wants to as well, which can mean frame rates of up to 144. On most games that just means they look really good. But Bethesda's games have their internal timing locked into 60 fps. If you go over that, it breaks the games. I forgot that.
I just cannot seem to get this game to run with mods anymore. I played through the intro without mods just fine, but when I added the unofficial patch and Fallout3 redesigned, it crashes like every 15-20 minutes! I checked all of the things in this thread and added the New Vegas anti crash file Lopov mentioned, but it just will not cooperate! I’m at a loss as it’s never given me this much trouble before.
Is Fallout 3 Redesigned a mod? If so, I know you might not want to hear this, but maybe try disabling that and see how it goes.
I must say, Fallout 3 is my most unstable game, so you're definitely not alone. Skyrim is most stable.
Hmm, well if it only affects faces, that can't be the culprit, but I'd still try disabling it. I could live without prettier faces for a short duration, I look at myself in the mirror every day after all. Yeah, I'd turn that off. Go in and out of Megaton's cells, back into the Wasteland, travel on foot for awhile, and so on. Go for a half hour, then an hour. If CTDs still occur, then it's something else, which is Ooouf, definitely not fun.
Is that the only mod you've got? Like I said in my story thread, I recently had a CTD every time my character walked from Fort Independence to the Wasteland (inside to outside, in other words). I tracked the culprit down to Mart's Mutant Mod. Bummer, but I'll live.
I don't think that the UOP is the issue, so I'd try disabling that Redesigned Mod. I've never used the Slower Item Degradation Mod either, so I can't be of much help here. Are you running the GOTY version?
I had the GOG version as well and I've been using UOP since forever and didn't notice that it'd cause CTDs. In my case problems were other mods and some unsolved conflicts between them, I guess. But as I said, the NV Anti-crash file made the game work like a charm again.
I agree... it can't be UOP. I use that as well.
I dunno. I do not use the Unofficial Patches because in my experience they caused as many bugs as the removed. But everyone's mileage varies on that.
^ See, that was my experience with Skryim. There were three main unofficial patches for awhile, then all the sudden the new patch came out, and it was an all-in-one patch, rather than 3 parts. I forget its name. But everyone started using it, so I did too. And it really crushed my game for awhile! Going in and out of cells in Windhelm was absolutely brutal, whereas before the patch, my Skyrim was mostly flawless. Even after I removed the patch, I had to go back to an earlier save, because that patch got baked into my save and it was still messing stuff up. Grr...
I hate to ask this one, but what about hardware? What sort of video card have you got Khajiit? Dedicated, or integrated? Sorry, that's rather intrusive. Weaker cards / hardware can be a source of crashes, though.
It might be Windows 10. It does not always play nice with older applications.
I have seen suggestions that you play it in Compatability mode for Windows XP, run it in Windowed mode, and run it as an administrator.
Ok so did a clean reinstall of F3 and it’s doing fine. Played through the intro and got outside to the first series of blasted buildings in Springvale and saved. Later tonight I’ll add back some mods and see how it goes.
You haven't truly experienced Fallout, until you've installed and reinstalled it a few times prior to playing.
... You haven't experienced Fallout yet, until you've had to figure out what Games For Windows Live is, and you'll need to disable it just to start your game. Maybe GOG disables this automatically when you buy Fallout 3. Steam does not.
OH! Khajiit, have you installed Archive Invalidation yet? https://www.nexusmods.com/fallout3/mods/944. Without that utility funny things can happen to some mod-added textures.
Ok well I guess I was doing something wrong before. I added back all of the mods I had earlier and a couple more and was able to play for a good couple hours today before having to stop to get ready for work. No crashes at all.
Awesome, good to hear. Now post some pictures!
Hey, I tried.
I just ran into a brick wall with the Gog version of Fallout 3. I am in the basement of Smith Casey's Garage. When I click on the door to Vault 112 the game crashes. I have spent the last few hours trying to find a workaround. I already tried removing all my mods, no luck. I tried going back to my save from the tutorial exit, and going straight to the garage and trying the door, no luck.
I tried using the console to simply skip the quests tied up with the vault. I can use the console to get into Tranquility Lane. But when I finish that, the game crashes again. Because when you complete it you go back to Vault 112.
So I tried skipping Tranquility Lane as well, and using the console to advance the quests. That works ok. Until Dad.
I think I have narrowed it down to Dad who is causing the CTD. Dad is in Vault 112 and the game crashes. He is also in Tranquility Lane, but as a Dog, so different actor. Game works. When I use the player.placeatme to spawn him, the game crashes.
I am not sure what about Dad crashes the game. There are multiple versions of him, which makes things confusing. Most of them are for different stages of the Tutorial. Only one seems to be for when you are an adult and finally discover him outside the Vault. That is the version I (and the game) are trying to spawn.
You did the right thing and turned all those mods off. So next thing I would try is going on UESP. See if others have encountered this horrible glitch.
Another option is to see if GoG has its own Fallout forums, and if others have seen this as well.
Other people have had this over the years. No one has offered up a solution.
I tried an experiment just now. I started a new game from scratch, COC'ed to Smith Casey's Garage, and I was able to enter Vault 112 with no CTD.
When I tried going back before to an earlier save, it was to one at the tutorial exit. I think that save was made on my original version of Fallout 3 (the one I bought on cd back in the day). I am now playing on the Gog version with the same saves. So maybe there is an incompatibility between saves from the original version and the Gog version? I have had no problem opening other saves from the original version and playing them. But I never tried doing the Main Quest with them either. I don't think so however, as some of the other people who wrote about this same issue online had it years before the Gog version of the game came out.
So now I have to decide if I really want to do the MQ, or start completely over with these new saves.
I dug up one of Hecate's old saves from about 5 years ago, and she was able to get into Vault 112 with no trouble. So I don't think this is an original vs. Gog version issue. It must be just some glitch in January's original game. I was also able to spawn Dad in her game with no trouble as well.
Having Daddy Issues really is annoying...
That's so weird. Why would the GrandOldGames version be any different from the disc or even Steam? I can see maybe there's some differences in the way the game loads from desktop, or the way it installs. But this is something which Beth wrote and it should be the same in all versions?
See, now I am glad I got my disc drive swapped instead of trying the GOG version of Oblivion. Anyway at this point I would also be asking that same question: do I want to start over from scratch? For me, this leads to a second question. "How much do I love this game?"
Back when I was newer to PC gaming (2015 or so) I had some problems in Oblivion which required me to go to a much earlier save. Like, hundreds of saves in the past. I thought it over for awhile and then decided to just go for it. Because that's how much I love OB. And I think others with ginormous games (Decrepit, Acadian, etc.) have had to go back to earlier game saves.
I appreciate this thread. Renee helped me with modding my FO3 game on my first go, and it made it pretty dang easy.
So as many of you know, I was having issues with the GOG version of Fallout3. This morning while having my morning coffee, I reinstalled it, took Subbies advice and ran it in compatibility mode. It still gave me an error message, but then it launched just fine (with some noticeable awkwardness with the controller, but not unplayable). I’ll try adding a few mods later.
What did the error message say?
https://www.gog.com/forum/fallout_series/fallout_3goty_crashes_at_launch_in_windows_10 It looks like an old .ini file was to blame with this person's issue, and deleting it solved the issue. Other people are chiming in that the NV No Crash Fix solved it for them, and another that it was save files from a previous version of the game.
I ought to just leave well enough alone, but deleting the .ini files in the my games folder didn’t stop the error message, but the game seems to launch ok.
For your information, the error message reads as follows:
This app can’t run because it causes security or performance issues on Windows. A new version may be available. Check with your software provider for an updated version that runs on this version of Windows.
But it does run. I played through the entire intro just yesterday morning.
Cool, well if the game runs, I guess don't worry about it for now. I understand about error messages though. They make me nervous, too.
It is my turn to have Fallout 3 issues again. I started up a new playthrough as Blood Raven today. But I have been getting CTDs like crazy. Sometimes it is when I try to load a save. Sometimes it is just at random points in the game. I never seems get more than 5-10 minutes without a CTD.
I have gone through a ton of fix attempts. I tried that Windows 10 fix I linked to last page. That did nothing. I think because it is for the Steam version of the game, and I have the Gog version. I made sure I was using a fixed refresh, had v-sync on. I put in compatability mode for Windows XP, ran it as administrator, etc... No joy.
My last gasp has been to install New Vegas Anti Crash, and run it in borderless windowed mode thanks to the mod https://www.nexusmods.com/fallout3/mods/25118.
So far this seems to be working. I started it up and let it sit running for about 40 minutes without a crash. So fingers crossed that one of those two things fixed it.
Edit: And it just did it again. Sigh.
I was about to ask Windows 10? But you've already thought of that.
Last time you played (as Jan, as I recall) were you using the Steam version but now it's Grand Old Games version. Have you ever used GoG before (not that it should matter, but maybe it does)?
Also, is this a Brand new game, as in, starting over from scratch with everything? Hmm, I guess a better question: Are you using the same mod-set from last season? Is there anything new?
Actually, 40 minutes of play might be about what you can expect. Vicious and Cho's game... with both of their games I'll save & reload (assuming I remember to) after a half-hour or so, due to Fallout 3's memory issues, and solely to avoid the dreaded crash which I know is going to come. That's as good as it gets.
I feel it’s past time for Fallout3 to receive the remaster treatment. BGS has paid so much attention to Skyrim, but meanwhile the games that saved and elevated their company (Morrowind, Oblivion, Fallout3) barely run on modern machines. I’m not even advocating for graphics improvements or any extra stuff. Just fixes that will let them run more smoothly on current PCs. I really don’t understand why this hasn’t happened yet.
I reinstalled Fallout 3 (using the Gog version), I think I had the Gog version the last time I played. But I am not sure if I installed it before I went to Windows 10 or after. So maybe that had something to do with it.
In any case, I just did a test while I took a bath. I started a new character, ran through the opening childhood bits up until Amata tells you that your father left and Jonas is dead. I left her standing there in the bedroom while I took a bath and puttered around. I came back over an hour later, and it was still running. So it looks like that did the trick.
Now I will just have to start adding back mods, and see if one of them is what is causing the crash.
I have spent all day fighting with Fallout 3. As soon as I started adding mods, it started crashing again. I went through all the 'standard' tweaks: updated my video drivers, reinstalled the game, set it to run as administrator and in compatability mode for Windows XP, ran it in a window, used New Vegas Anti Crash, etc... I even tried a couple of the Windows 10 fix mods, that have you put a d3d.dll file in your base Fallout folder.
What finally seems to have worked is the https://www.nexusmods.com/fallout3/mods/24913 mod. It does a lot of things, the main one being downgrading the game to the previous version (which worked better with mods). It also removes the Games for Windows Lives stuff, makes the executable large address aware, fixes a mod limit bug, and more. It works with both the Gog and Steam versions of the game.
If you are using FOSE, don't start the game with the fose launcher file after installing this (It won't let you if you try). Instead start it with Fallout3.exe, and it will automatically use FOSE if you have it.
So far so good with this. I hope I am not jinxing it by talking about it.
Wow, that took full 'SubRosaTech' mode to fix! I sure hope it works.
I hope it works for you. There are so many Fallout 3 CTD fixes on Nexus, none of them really work 100%, from what I've found some of them don't work at all.
Ugh, ok, so I’m testing mods and playing a bit while I’m doing so (which I guess is my first mistake). The character I’m currently running has finished the first chapter of Moira’s quest and I noticed that the Unofficial Patch wasn’t activated, so I activated it. Now certain NPCs are running around in their underwear! It was definitely the UP that caused this, so I loaded a new character from the auto save point just before stepping out into the wasteland and it seems to work just fine. I’m so confused.
Too much skooma will do it to you.
Sorry, not constructive but couldn't resist! So funny!!
This is one of the reasons I do not use the Unofficial Patches in any Bethesda game. I have found they always cause new bugs, even if they fix old ones.
All these years (especially when the official forums were opened) whenver a n00b player would ask "which mods should I get?" the answer usually started with UOP. So this is my first time hearing anybody say avoid them.
Come and think of it though, I never installed any unofficial patches for Fallout 3.
Supposedly this can be fixed by simply loading your save game with all of the mods turned off, then saving the game, then turning all of the mods back on and reloading the save. Will try and report back tomorrow.
I don't remember the bugs the UOPs caused anymore. It was a long time since I used any of them. Now when I come across a specific bug, I just fix it, simple as that. I don't need more headaches.
That's so crazy though, Khajiit. All those people suddenly lost their clothes due to just that one change! WTF.
Powered by Invision Power Board (http://www.invisionboard.com)
© Invision Power Services (http://www.invisionpower.com)