Fallout 4 crash to desktop when changing .ini file to enable mods

[jzoro431]

I am having this EXACT same problem, actually and came to the same conclusion after a weekend of testing. It will crash when I get near bunker hill if I have this in my ini file:

 

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

 

Happens every time, whether mods are loaded or not.

Deleting the ini files so that the game generates new ones without the line will allow the game to work normally without crashing in these areas.

This happens even if mods are loaded, even though they won't work without this setting.

Here is a breakdown so that it will make sense.

 

Mods loaded, ini changes present: CTD near bunker hill

Mods not loaded, ini changes present: CTD near bunker hill

Mods loaded, ini files NOT changed: no CTD near bunker hill

Mods not loaded, ini files NOT changed, no CTD near bunker hill

Can anyone verify this working? Other than you, of course. I am going to try it tomorrow but I would like to see if anyone has had success using this method.

[j0hnicus]

 

I am having this EXACT same problem, actually and came to the same conclusion after a weekend of testing. It will crash when I get near bunker hill if I have this in my ini file:

 

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

 

Happens every time, whether mods are loaded or not.

Deleting the ini files so that the game generates new ones without the line will allow the game to work normally without crashing in these areas.

This happens even if mods are loaded, even though they won't work without this setting.

Here is a breakdown so that it will make sense.

 

Mods loaded, ini changes present: CTD near bunker hill

Mods not loaded, ini changes present: CTD near bunker hill

Mods loaded, ini files NOT changed: no CTD near bunker hill

Mods not loaded, ini files NOT changed, no CTD near bunker hill

Can anyone verify this working? Other than you, of course. I am going to try it tomorrow but I would like to see if anyone has had success using this method.

 

Sadly this only seemed to work temporarily so it may be true what the previous poster wrote about NMM messing up the ini file. I was able to play with mods in the affected area for a bit, but the problem has returned. I'm also wondering if it might be due to a mod that has been removed still being called for by the game when mods are enabled and crashing because it's not there.

[ndkneko]

I tired this fix and still crashes to desktop... I even tried reinstalling everything

[j0hnicus]

I tired this fix and still crashes to desktop... I even tried reinstalling everything

Ok I think I might have fixed this.

 

When you uninstall your mods, are you just disabling them in NMM (it will have a red circle with a line through it) or are you right clicking it and selecting "Uninstall from all Profiles". You'll know you did it right if the text for the mod becomes greyed out, like it was before you installed it for the first time.

 

It took me a while, but doing this for every mod and loading the problem areas I was able to finally narrow it down to one mod causing a CTD and it turns out the author has a CTD fix on the mod page now. For me it was the mod called "CREEPY MONSTERS OF WASTELAND". It looks like I only installed part 2 of a total of 3 files for this mod, which you have to download from the archive page. With all three parts and the CTD fix..... I think it's working.

 

Theory:

The mod isn't being disabled properly, so unless you uninstall it correctly Fallout will still be trying to reference records or something that the mod has changed and will result in CTD if the mod is bugged. That's why we were seeing that the only way to stop the CTD was to completely remove all of the ini files and start over--this was preventing Fallout from loading any of the modded files. As soon as we added the ini changes back in, it was trying to call the borked records from the borked mod.

 

It's still pretty early, so if I start experiencing the same crashes again I'll be back with more information. Please let us know if this works for you!

[ndkneko]

I uninstalled everything. I did a clean sweep of all fallout 4 and nexus mods files on my system.. deleted them all that was left after uninstalling.

I reinstalled Fallout 4 run game no crashes.

I installed nexus mod manager with out changing the .ini files.. game runs

I changed the .ini files to what they want and CTD happens. so something with changing the .ini files is causing the crashes.. I haven't even installed a mod and its CTD

[themajormajors]

Never mind twas a mod.

Edited December 22, 2015 by themajormajors

[j0hnicus]

 

I tired this fix and still crashes to desktop... I even tried reinstalling everything

Ok I think I might have fixed this.

 

When you uninstall your mods, are you just disabling them in NMM (it will have a red circle with a line through it) or are you right clicking it and selecting "Uninstall from all Profiles". You'll know you did it right if the text for the mod becomes greyed out, like it was before you installed it for the first time.

 

It took me a while, but doing this for every mod and loading the problem areas I was able to finally narrow it down to one mod causing a CTD and it turns out the author has a CTD fix on the mod page now. For me it was the mod called "CREEPY MONSTERS OF WASTELAND". It looks like I only installed part 2 of a total of 3 files for this mod, which you have to download from the archive page. With all three parts and the CTD fix..... I think it's working.

 

Theory:

The mod isn't being disabled properly, so unless you uninstall it correctly Fallout will still be trying to reference records or something that the mod has changed and will result in CTD if the mod is bugged. That's why we were seeing that the only way to stop the CTD was to completely remove all of the ini files and start over--this was preventing Fallout from loading any of the modded files. As soon as we added the ini changes back in, it was trying to call the borked records from the borked mod.

 

It's still pretty early, so if I start experiencing the same crashes again I'll be back with more information. Please let us know if this works for you!

 

When you uninstalled did you delete your data folder and all traces of nexus mod manager? For me it was being caused by the incomplete install of the Creepy Monsters mod and things not being uninstalled property. I have a feeling there is some remnant of a mod that is causing your issue.

[EpiceneBlue]

Hello there. So, I uninstalled and deleted EVERYTHING. Totally wiped the existence of Fallout 4 from my computer. With an entirely vanilla game, no CTD. If I have the Fallout4Custom.ini with the instructed mod enabling lines on the Nexus page - http://wiki.tesnexus.com/index.php/Fallout_4_Mod_Installation - with NOT EVEN ANY MODS INSTALLED - I get CTD on pod exit in the Vault. I get CTD here there and everywhere. This is not good. So I either play with no mods, or I can't play at all. Anyone that figures out how to fix this, please PM ME! I am a mod author and cannot even work on my own mod.

[whodat1]

I had a similar problem (different location in map). I made a save close (but not in ) to the crash point. I then renamed my data\textures directory to something else and tried the game (with about 60 modes still installed). The game did not crash. So I created an empty 'textures' directory and started copying the texture sub directories over from the renamed one to the new one, one at a time (testing the games after each copy) until the CTD came back. Then started copying individual textures in that sub directory out until I found the culprit. In my case, it was a single texture causing the problem.

 

A number of people have been getting what seems to be a random texture file corruption. I think the corrupted texture in my case was used in the area where the CTD was happening.

[Dunmait]

I had a similar problem (different location in map). I made a save close (but not in ) to the crash point. I then renamed my data\textures directory to something else and tried the game (with about 60 modes still installed). The game did not crash. So I created an empty 'textures' directory and started copying the texture sub directories over from the renamed one to the new one, one at a time (testing the games after each copy) until the CTD came back. Then started copying individual textures in that sub directory out until I found the culprit. In my case, it was a single texture causing the problem.

 

A number of people have been getting what seems to be a random texture file corruption. I think the corrupted texture in my case was used in the area where the CTD was happening.

This seemed to be the only thing that worked for me, Gore Overhaul was causing the crashes here!

Thanks so much for the tip!!