Fallout 4 constantly crashing at menu even with mods disabled? HELP

[Kajukenbo96]

Basically, I tried to install all the mods I downloaded with nexus manager, because I assumed thats all I needed to do to get all the mods to work. Do some of these needs extra manual work? The problem is, after I installed them, I crashed at Menu. I tried to uninstall all of the mods, but not delete them in the nexus manager, and I'm still crashing. How can I get my default Fallout 4 back so I can test one by one?

[LordGrievous]

What mods did you install? Anything with an .esp file can potentially cause savegame corruption.

[ShinraStrife]

He might have leftover files from the mods if I'm reading the OP right (disabled the plugins but didn't delete the files?)

[LordGrievous]

Disabling the mods(red circle with a line button) in NMM on the mods tab should remove all associated files, if that's the issue.

[ShinraStrife]

Disabling the mods(red circle with a line button) in NMM on the mods tab should remove all associated files, if that's the issue.

 

If that doesn't fix it, there might be something wrong with his INI files.

[bls61793]

 

Disabling the mods(red circle with a line button) in NMM on the mods tab should remove all associated files, if that's the issue.

 

If that doesn't fix it, there might be something wrong with his INI files.

 

 

I concur... if he's crashing at the menu it sounds like an .ini problem.

 

OP: I'd suggest going to your Fallout/ Data Folder (Generally: C:/ProgramFiles(x86)/Steam/SteamApps/Common/Fallout4/Data)

You should have the following files:

Strings [Folder]
Video [Folder]
Fallout4 - Animations.ba2
Fallout4 - Geometry.csg
Fallout4 - Interface.ba2
Fallout4 - Materials.ba2
Fallout4 - Meshes.ba2
Fallout4 - MeshesExtra.ba2
Fallout4 - Misc.ba2
Fallout4 - Shaders.ba2
Fallout4 - Sounds.ba2
Fallout4 - Startup.ba2
Fallout4 - Textures1.ba2
Fallout4 - Textures2.ba2
... there are a total of 9 different "Fallout4 - Textures#.ba2 (they are numbered 1-9)

Fallout4 - Voices.ba2
Fallout4.cdx

and lastly: Fallout4.esm

Make sure that you have all of those files, and delete any files other than these. (Unless you know what the files are and are sure you want to keep them).

 

After you've done this, go to MyDocuments/MyGames/Fallout4 and delete your .ini files.

After you've done all this, go to Steam, right click on Fallout4 in your library. Go to "Properties" then click the "Local Files" tab.

Once here click "Verify Integrity of Game Cache"

 

This feature of steam should search your documents and game directory and find any missing files and replace them with original copies.

 

Give this a shot. I think it should fix your issue. Another way to go about this is just to uninstall and reinstall.

[Uzibeatle]

If I read the OP's post correctly.

He installed a bunch of mods before even starting the game for first time.

 

Once you get it fixed, if ya do .. just DONT" do that in the future.

 

Start the game vanilla and play it out of the intro area to wasteland.

Then and only then if you are hell bent to mod this game, or ANY game...

make a known good save.

 

Install ONE mod and rinse and repeat the save process with hard saves, not quicksaves.

 

Especially in the case of using any mod that has a plugin .esp file.

THis can also apply to mods that are nothing more than texture plugins.

I have found in the past, for this game and other TES engine based games, texture mods uploaded to

NExus that can and will crash the game on load.

Due to incorrect packing of the textures. You wont get save corruption in that case (usually) but it can be a massive

PITAS to track the one mod that was doing that if you just go to Nexus, download and install a bunch of cool looking mods, and expect all to be hunky dory.

 

Just say NOPE and don't do that. One at a time, smoke test and move on.

 

Edit. I should add so far NMM shows I have 58 mods activated. I've done so without issue but I've been adding them one at a time for

the past week.

I did have to remove a few for issues they caused. One was a flag texture mod that crashed the game as soon as it loaded. The author

of that mod pulled it when made aware.

Edited November 23, 2015 by Uzibeatle

[ShinraStrife]

If I read the OP's post correctly.

He installed a bunch of mods before even starting the game for first time.

 

Once you get it fixed, if ya do .. just DONT" do that in the future.

 

Start the game vanilla and play it out of the intro area to wasteland.

Then and only then if you are hell bent to mod this game, or ANY game...

make a known good save.

 

Install ONE mod and rinse and repeat the save process with hard saves, not quicksaves.

 

Especially in the case of using any mod that has a plugin .esp file.

THis can also apply to mods that are nothing more than texture plugins.

I have found in the past, for this game and other TES engine based games, texture mods uploaded to

NExus that can and will crash the game on load.

Due to incorrect packing of the textures. You wont get save corruption in that case (usually) but it can be a massive

PITAS to track the one mod that was doing that if you just go to Nexus, download and install a bunch of cool looking mods, and expect all to be hunky dory.

 

Just say NOPE and don't do that. One at a time, smoke test and move on.

 

Edit. I should add so far NMM shows I have 58 mods activated. I've done so without issue but I've been adding them one at a time for

the past week.

I did have to remove a few for issues they caused. One was a flag texture mod that crashed the game as soon as it loaded. The author

of that mod pulled it when made aware.

 

What he said. One at a time and check the comments/bug reports for each mod you plan to download. Other downloaders might have some insight to whether the mod works as intended or not.

[DeadlyAzuril]

Kajukenbo96

Here is what you need to do.

1. delete ini file

the game will make a new one with default values - do this first as its the easiest solution.

 

2. verify game cache

Go into steam > fallout 4 > properties > local files > Verify Integrity of Game Cache

 

Some very stupid mod makers repackaged .bsa files and had you replace them entirely rather than through an .esp, this will double check all game files and redownload any that have changed

 

This should do the trick, as you will effectively have a fresh install. past this, look to more hardware/driver specific problems - graphics drivers, make sure your not overclocking (system stability) , and always double check what your mods are actually changing

 

[alekriid]

Hello everyone, if you diasable any mod and try to load your game save fallout4 will crash
to prevent this :
1. diasble unistall any mod you want
2.open fallout4.exe NOT f4se_loader
3.load the game save that was crashing (it will load with no mods at all)
4.make a clean save and exit
5.now open f4se_loader load your game save it wont crash because the mod that was missing isnt now on the save that we made

Worked for me i was frustrated because i unistalled a mod and lost my character with hours of gameplay
hope this works for you !