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

[Bleazo]

Hey,

 

I got a big problem, causing my game to crash without an error, when I try to enable my mods in Fallout4Custom.ini.

I added the following lines:

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

 

Important: The crash to desktop happens always when i am about to reach a specific area in the northeast of mass fusion near the sea.

If i use old the old .ini file, the game works perfectly, but i cant use mods obviously. Everything is up to date, nmm, graphics driver etc

 

Thanks for any help!

[Bleazo]

bump

[UhuruNUru]

Well the two aren't related

Fact 1: Vanilla game no CDT

Fact 2: Enabling Mods gives CDT

 

Your unsupported theory ithat enabling mods causes CDT, is wrong.

 

A plugin mod is most likely, to be causing the CDT, not simply enabling them.

 

First suspect is your Load Order, you can use FO4Edit, to find the problem, if you run it with all mods ticked it will stop at the plugin the game crashes on.

 

You can manually check that mods come after their Masters in NMM, but FO4Edit will be correct, even if the masters not listed as it should be.

 

 

[Edit] Assuming that basic FO4Edit function is enabled for Fallout 4 yet, I've not tried to do this with Fallout 4, but it's why all mod users should use FO4Edit plus DLC will need cleaning, Bethesda's Developers make DLC with Dirty Edits, which also can cause CDT's with mods.

That's for DLC and Mod Authors should not leave dirty edits, though, a few are very rarely required for a mod to work as planned.

 

Anyway install FO4Edit in the Game folder and click on the FO4Edit.exe, it should appear with all your active plugins pre-selected simply OK it and wait for it to stop. When it stops check the last few lines and you will know, the mod that needs moving.

 

One tip is, last plugin always wins any conflict, so last one always loads, is a good testing position.

It should be clear what the Plugin is called that caused a CTD.

[Bleazo]

Well, i've tried it out with mods, few mods i already played perfectly with, and without. It doesn't matter, the ctd appears!

 

+++ It worked before, but when patch 1.2 was out not anymore!

Edited December 14, 2015 by Bleazo

[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

Edited December 14, 2015 by j0hnicus

[j0hnicus]

I think I fixed it! I was having the same problem, see post above.

I noticed that the guide that NMM links to says to edit your Fallout4Custom.ini file, but I actually had none after deleting the .inis earlier. It seems that now you need to have Fallout4.ini, Fallout4Custom.ini and Fallout4Prefs.ini. Here is what I did tonight and now I can play with mods and no CTDs in the areas I was seeing it before.

 

Note: I uninstall/reinstalled the game and all mods before this, but I don't think that was the fix as it was still crashing until I...

1.) Delete your Fallout4.ini file so that the game gives you a brand new one. Don't edit this file.

2.) Paste the below into your Fallout4Custom.ini file instead:

 

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

 

3.) Now paste the below Under [Launcher] in your Fallout4Prefs.ini file:

 

bEnableFileSelection=1

 

4.) Boot up the game, load a save in or near a problem area, or load and zone to one. You should notice that it loads instead of crashing!

 

If you don't have a Fallout4Custom.ini file, which was my problem, here is the entire contents of mine and that should be all that you need.

[Display]

iLocation X=0

iLocation Y=0

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=

Edited December 15, 2015 by j0hnicus

[SharraShimada]

You could also try, to make the changes as before, and then set the inis to read only. NMM frequently messes them up for no reason. It will cry it cannot access the files, but NMM wont need write access at all.

Hell, waiting for "Mod Organizer" to be released.... far better coded than NMM.

[Bleazo]

Well like i said, i got the Fallout4Custom.ini and the other two, but my game still crashes for some reason.

Tried everything out, same problems like j0hnicus.

 

"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"

And your fix is that, what i actually have done before I started this thread :sad:

EDIT: Found out that the bug ctd only appears when I am starting the game through NMM or MO, mods still aren't relevant.

So it seems like i can't play in this area with mods at all i guess, because I can't even use Nmm or Mo to start the game (ofc i could, but it doesnt allow me to play without ctd in this area).

Edited December 15, 2015 by Bleazo

[SharraShimada]

Wait a second, you use NMM AND MO at the same time? You know, that´s never a good idea, because they handle mod-implementation in a very different way.

[Bleazo]

No i had only NMM, but ive tried MO for eventually solving the issue. But it didn't help.