Fallout 4 Crash To Desktop Fixl
Amice Golden
- Check that box, and in the text box underneath (it lights up when you check the check box), add fallout3.exe. Do NOT use spaces, since ffdshow will think that's part of the filename. A valid entry would be explorer.exe;fallout3.exe.
Its funny i had this issue once before, but what i did was remove Alchemy witch does mean things to Fallout, if you are running windows 7 try install the older audio drivers from xp, this is in windows seven pro, install them using the the xp compatibility mode it should work, the xp drivers don't use alchemy.
When I create a merged patch with FO3Edit, it generates it just fine, and then I exit. It shows that window with the merged patch checked, and I press OK. Finally, when I go into FOMM, it shows no merged patch. I go to my Data folder, and there is no merged patch there at all.
i used to play this game on my windows xp computer, had no problems. computer died, bought a new computer with windows 7, tried to play, and it won't. i click on continue and the game crashes. figured it might be a mod so i took out my mods, tried again, crashed. tried to get a new game started instead cause i figured i had corrupted saves, hit new and game crashes.
I started playing Fallout 3 again yesterday after putting playing on hiatus about 2 months ago. The game ran without incident, and I hadn't made any major changes to my OS, other than video card drivers. Last week, I had updated my video card drivers to Nvidia's 258.96 WHQL to make another game run correctly. I started up Fallout 3 version 1.7 with Pitt/Steel/Anchorage loaded, and decided it was time to start a new game from scratch.
The game didn't crash up until I left the vault. I made it to megaton, did a few things, then headed out into the wasteland. I couldn't travel very far until the game crashed. I reloaded my autosave, and it crashed again in just a few minutes time. What went wrong? The game ran just fine months ago.... until I loaded new video card drivers.
I tried everything. FFDShow was already fixed. I turned off everything threaded in fallout.ini. I ran the game in windowed mode. I ran the windows live disabler program. I turned off my paging file. After making all sorts of changes, I would run the game for a few minutes and it would crash to desktop in a matter of minutes. It seemed that no matter what I did, the game would always crash. I was about to go through the process of re-installing the entire game, re-patching it, and re-loading windows live, when I thought I'd try doing something else for a change:
Long story short, I deleted my old falloutprefs.ini and fallout.ini, put the DVD in, let it detect the graphics settings, and restore the game's default configuration. I was able to play the game for an hour straight, even after modifying some of the graphics settings. It worked in full-screen, windowed mode, any resolution. I have been playing it nonstop since this morning and have not seen a crash yet.
I'm unable to play Fallout 3 and New Vegas. I can't even load a save or start a new game. Instant crash to desktop and removing all the mods, tweaks, INI settings or having the game in its vanilla state doesn't seem to have any effect. Rolling back to previous version solves the problem but I don't plan to stick with older drivers just to play a 13 years old game. Any solution to this problem in the next release would be appreciated. I have a 6750 XT. I'm enjoying to overall experience but these minor things adds up.
Pretty much carried out the same steps as yourself, full reinstall of the game. Starts up fine, the moment you try to load or start a new game, intro will play, then when you get the the loading screen it lasts for about 2 seconds then crashes.
Worst thing about this whole ordeal is I had a pretty crowded mod base for my Tale of Two Wastelands installation. You know, the thing that merges Fallout 3 and New Vegas together. I basically nuked the whole thing in order to identify the problem. Well, I did, and I still can't play it. Let's hope for a swift and smooth solution. I'd make a joke about 7900 XTX not being enough to handle a game like New Vegas but I'd imagine it wouldn't be a very original one. Cheers!
Well, I'm glad to see I'm not the only one having this happen. At least now I don't feel so cursed. Vanilla games wouldn't work so I went the TTW route thinking that would fix. It didn't. I tried so many different things for hours on end to figure out what was going on to no avail. I can load up into the main menu but as soon as I try to load in or start a new game it crashes to desktop after about 2 seconds of loading. On a 6950 XT.
You need to roll back your drivers to a 23.x.x pre 24.x.x. It looks like just general driver degradation which is very sad to see because I don't want to have to roll back my drivers every time I want to play one of my favorite games ever (New Vegas). Please fix this AMD!
Update:
Hey guys, I found a fix.
The fix is easy. Just grab DXVK and run the game in Windowed mode. If you do not run it Windowed, the game will be extremely extremely laggy
However, some might find that Windowed mode does not provide full resolution. To fix this, just run bethINI and set your settings there. Make sure to tick "windowed mode".
Done! Let me know if you guys have any questions
Purchased a new RX 6650 XT a few weeks ago that runs all my other games just fine. EXCEPT for FO3 & NV! Same issue as those above. Get to the loading screen and Crash To Desktop when continuing, loading a save, or starting a new one. I just switched from the green team(1060 3gb). I really hope the next driver release fixes this issue.
Basicaly AMD version of dx9 Drivers is broken so we need to inject an old one with special info (Gpu info) to fake the Detection of the GPU by the game. Like that Fallout 3 / Fallout NV engine will setup the rendering mode correctly and configure FaceGen (it's the thrid party tool used for the faces of the PNJ ) properly.
If you go to steam forum for FO:NV, there is a sticky post for stability and anti-crashing. I installed "New Vegas Script Extender" and the "anti crash" mods. I ran it from steam, and it worked, which I think ironically does not actually use the mods. So I ran it from the NV script launcher for steam and it continued to work.
nah modding is not a solution. I don't have an account for that woke infested website and I want my achievements. Its a problem with the drivers because it works fine with versions from the year 2023. AMD needs to fix this. New games are not the only reason why people build gaming pc's. Everything from the past should always be supported.
It took me and hour or so of trying to figure out the problem thinking it might be related to the mods, but doesn't work without any mods either, the game crashes on both 'load' and 'new game' after the intro video before you get into the game.
I have been reading everything I can find about Kerbal Space Program and crashing. There are NUMEROUS threads about it over the last FOUR years, but nothing in any of the threads here, or on Steam, or various reddits have done anything to fix the problem.
Now, I DO run about 100 mods, but I get them through CKAN and they are installed properly and with very few exceptions they are of the appropriate version to match the 1.4.3 KSP version I am running. The handful that are a for an earlier 1.4.x, I asked in the corresponding thread if they are compatible and the answer was yes.
Despite this my game was regularly crashing after trying to return to or exit the VAB/SPH after a flight. After leaving and entering the ship building buildings several times my game would crash. Since the game takes about 10 minutes to load with a lot of mods, waiting for it to load over and over to play for about 5 minutes is pretty damn tedious. I was spending more time watching the loading screen than playing the game.
I have about 20 crash.dmp files that I have no way to open or read myself and taking the time to zip them with the Output_log, error log, and KSP log files and then uploading them to dropbox to post a link here... and then get no response from any of the Devs is obviously not worth anyone's time.
Out of all of the Error reports generated with the crash.dmp files my RAM was averaging 50%-60%, but despite this Linuxgurugamer suggested I was running out of RAM or my RAM was bad. I put Memtest86 on a USB drive and ran multiple passes.....my RAM is not bad and has no errors. Since more then half of it isn't being used by the game or the mods, I don't understand how I could be running out of it. I don't have anything else running in the background. I disabled all my Windows startup processes.
I then did a file search for xinput1_3.dll and noticed it is located in several different places in my C drive. I also noticed that it came in different file sizes. So I Googled about it on the Internet. I learned that there is a 32bit and 64bit version of it. The 64 bit file size is about 105KB and the 32bit version is about 80KB. As you can see from my second spoiler above it is using the larger file size which makes sense because I am running the 64bit version of KSP.....I also learned that System32 is the 64bit program folder for Windows and Syswow64 is the 32bit folder.....that doesn't make sense to me and seems counter-intuitive....
What also doesn't make sense to me after doing my file search for that file, is WHY Kerbal Space program comes with two copies of it, one in KSP_Data\Plugins and one in KSP_x64_Data\Plugins and when I run the game with the KSP_x64 shortcut on my desktop it uses NEITHER of them? If you look at what is says in the error above it is using MY Windows copy of it in C:\WINDOWS\SYSTEM32\xinput1_3.dll. Why is it using the one in my windows folder when the game comes with it's own two copies?
b37509886e