Jump to content

'FO4 Has Stopped Working' message


UgTheViking

Recommended Posts

I find that running Fallout can occasionally cause the "runtime broker" process to nerf out, which causes all sorts of weird problems in Windows 10, like the Windows/Home icon not working. Hitting CTRL-SHIFT-ESC to bring up the Task Manager, then killing Runtime Broker (it will restart itself immediately minus the glitches) can save having to reboot sometimes.

Link to comment
Share on other sites

Hey there, thanks for all the replies. I'm going to reply without using all the quotes....I'm running Windows 7 and yes, I use mods. (It's actually the only reason I buy Bethesda games. The modding community is just truly amazing...and greatly appreciated.) I am not in any of the Beta programs. I have rebooted the computer and even restored it to an earlier point. I have reinstalled FO4. I've checked all my ini. files......I am at a loss on this one. It's been 3 days now (starting to go into withdrawls, heh) and it hasn't worked once. Again, I can watch the intros all day and it runs fine. It just wont load or start a new game, Am about to resort to ancient sacrificial rites to appease the fallout gods.....or something.

Link to comment
Share on other sites

Hey there , rabbit - No, nothing yet. Have run it up to 10 times in a row and still crashes at same exact point. Tried googling some more to no avail. Re-added Skyrim just to make sure my computer hadn't tweaked somehow and just wouldn't run games but that is up and working fine. So, really, am at a total loss on this one. But thanks for checking in, 'tis appreciated.

Link to comment
Share on other sites

Not sure if this would help, but if you can track it to a single mod.

 

Fallout 4 CTD when loading safe with Homemaker/Snap N. Build (Possible Fix)

 

Ok, so Since the last 3 non-Beta pushes I’ve been crashing when loading saves, and after ruling out my other 130 other mods it’s linked to Homemaker and/or Snap N/ Build.

Using GoogleFu I came across a couple fixes for previous updates and none worked, but it lead to some solid core info to experiment with.

 

The following has worked for me, and I’ve tested it with 3 different saves 2 times each to make sure it works.

 

  1. Go to your saves folder, find your most recent two saves. Copy the filename, but without including the “.fos” and past them into a text document.
  2. Load your Mod manager, record the order of the mods (you can export that with NMM).
  3. Removed Homemaker (and Its plugins), Snap N. Build (and Its plugins), and Settlement Keywords.
  4. Start Fallout 4 and Load your most recent save.
  5. Save your game (not quicksave or auto, full save)
  6. Exit FO4
  7. Load your Mod manager and add back Homemaker (and Its plugins), Snap N. Build (and Its plugins), and Settlement Keywords w/ patches.
  8. Fix the order to what it was @ step 3
  9. Load Fallout 4
  10. Open your most recent save (To be clear the one WITHOUT Homemaker)
  11. Open the console and use the following command Load “SaveXXX_XX_XXX_Commonwealth_XXX_XXX_XX” The exact name would be the save filename from Step #1
  12. Wait for the save to load, for me it took longer than normal, but worked. Once loaded Save a fresh full save.
  13. Travel to a settlement and make sure All SnB & homemaker items are still intact, check Build menus to make sure items are there.
  14. Exit FO4
  15. Start FO4 and make sure the new clean save loads.
  16. Rejoice!
Edited by Thirdstorm
Link to comment
Share on other sites

Hey there , rabbit - No, nothing yet. Have run it up to 10 times in a row and still crashes at same exact point. Tried googling some more to no avail. Re-added Skyrim just to make sure my computer hadn't tweaked somehow and just wouldn't run games but that is up and working fine. So, really, am at a total loss on this one. But thanks for checking in, 'tis appreciated.

If you go into Event Viewer under Windows/Applications are there any errors logged?

Prolly something like Faulting Application Blah Blah Blah followed by an exception code and a string of hex numbers.

The code would be handy.

 

 

 

 

Corrupt or duplicate MS VC files often cause applications to crash....they're a headache, u can end up completely reinstalling .NET. Total pita..

 

My first thought is HDD with bad sectors but I see you reinstalled already...if all else fails maybe try another driv...

Edited by PillMonster
Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...