Fallout 4 Modded Crashing 17 Seconds in

[petracttion123]

So my game crashes approximately 17 seconds in all the time. A few months back i started the game and got inside the game and all but after running for 17 seconds it CTD. It was working fine before.

 

This is what i have tried...

• Verifying Steam Game Files which lead to it installing 6 files, didn't work.
• According to LOOT and Wrye Bash the game seems to be alright. I have done everything LOOT told me to do.
• I started it without Fallout 4 Script Extender. It didn't crash after 17 seconds then.

 

I have 108 Enabled mods.

 

Do anyone know what i can do?

 

I got a few ideas left on what to do but i'm not so good at modding so i'd really appreciate if someone could save me the extra work. :happy:

[HeyYou]

Disable any dll mods you may have. (F4SE plugins) See if anything changes.

 

That's gotta be a mod conflict.

[Blinxys]

Sometimes, this happens on first load.

If I run it again without restarting steam it goes fine.

Maybe electronics or memory management, as HeyYou mentioned *'dll loading. IDK. :nuke:

 

Not much help here, just saying check ALL scenarios.

Can always do the Half and Half check, I'm a big fan of the half-and-half test for zeroing in on problems. :dance:

(Unless you know what changed last and can undo it, but that generally applies to Pragmatic Augmentation Practices). :ninja:

[petracttion123]

Disable any dll mods you may have. (F4SE plugins) See if anything changes.

 

That's gotta be a mod conflict.

Thanks for the reply!

 

I searched for any file in my fallout 4 folder that had a name with dll. Then i searched in Vortex with bits of their full name, because some dll files names didn't match with the names of the files in Vortex. Therefore is it possible that i didn't manage to disable all of them.

 

But it still CTD after 17 seconds.

 

As i wrote above, some of the files names in Vortex doesn't match the dll files names in the Fallout 4 folder. Is there anyway i can find a connection between the files in Vortex and in the Fallout 4 folder besides their names?

 

I guess i can just disable all my mods in Vortex and then reenable them. But that might not solve the problem forever. Solving this would at this point be quite interesting as i would like to know what mod it is that doesn't work.

 

I'm gonna try and make a new start and see if the game still CTD.

[Blinxys]

If you want to know which mod is of issue,

disable half of them, test game.

If it works, reverse the selection and divide that half by by half.

Repeat, Etc. al

 

Until you zero in on the mod in question.

 

"Half & Half (Again)."

[petracttion123]

Here comes an update...

 

So i did "Half & half". After disabling the first half it still didn't work and there weren't so many mods left to disable so i disabled 10 mods and then started the game until there weren't any mods left.

 

The game still CTD.

 

Now i have no plugins except the ones that come with the game and i got no mods.

 

I started a new game through F4SE and it still crashes.

 

So frustrating. No idea what to do right now... :geek: :confused:

[Blinxys]

Ok, that's good, so you know its not necessarily any plugin.

 

Sounds like there is something wrong with you f4se installation.

Did you copy the sub-folders. This was an issue when I started using it.

(you say "yeah, I did", (but it didn't really happen). :dry:

 

So aside from any other utilities, you are just running base game and using f4se launcher?

Seem to be narrowing down the hit list.

 

Have you started a new game or are you trying to load an old one?

If it is not a new game start one and see what happens!

 

Since you have nothing to lose except time, (you've put that in, now it should work for you). :sweat:

Could advise at this point, to rename your fallout 4 folder in steam and redownload/install.

Once completed verify and back up THAT folder. It should stand as a pristine example.

Get that new install running within acceptable parameters.

Install f4se, test.

 

The reason for this is although mods are disabled there is residue, and the game DOES read files it can see regardless of active state.

And right now that only confuses things when the base system is not running.

Since you will be building your own personal house of cards on this foundation, you'd do yourself well to make sure it was in order before all else.

 

Then when you add mods, add 1 test, rinse repeat.

At this point you are not trying to play the game but rather to build it up properly.

Use "SKK50's Fast start New Game" to skip the tedium. :ninja:

 

Important: Start a new game with each added mod. (Stuff changes potentially with each mod).

[G4M3W1NN3R]

grab this mod: https://www.nexusmods.com/fallout4/mods/47359

 

& all of its requirements.

 

then check to crash dump, to see what it says, can also post said crash dump in the mod page post section to get possible help on it.

 

also worth grabbing this: https://www.nexusmods.com/fallout4/mods/63346

 

crash after 17 seconds could be a number of things

 

1. Corrupted Nif files (100% Repeatable CTD, until Removed), can be triggered anytime a corrupted mesh file is present, typically when the PC is in close proximity, but can CTD any time 1 is loaded including, CTD via Loading Screens (this was present on Skyrim where the game would CTD in a loading screen, because a particular location had corrupted mesh files, so anytime the game would attempt to load that location, CTD, this could also be potential issue in Fallout 4) this could still be a potentional even if all mods are uninstalled, if the mod manager failed to remove said mesh files (which is a possibility).

 

1a. an Example of this, Buffout notified me of a Potentional Corrupted Nif File (another reason why i strongly recommend grabbing this mod), from the Mod, Better Goodneibour, this would actually cause my game to CTD 100% even on a new game (at Character Creation) likewise not even being anywhere near that location. deleted the Better Goodneibour mod, no more CTD on Character loading. so ye writing this as an example, that Corrupted mesh files can cause CTDs even outside of the 2 potentials mentioned on first line (proximity, and Loading Screens)

 

1b. Corrupted Mesh files can also be time based depending on the mesh file in question, such as Armor that has invalid dimensions, this will cause the game to CTD after X amount of time. also mentioning this as i have also experienced this type of crash, where 1 of the armor mods i was using had invalid Pixel dimensions, this would cause the game to crash after x amount of time when equipping said armor, not an immediate CTD but is a guaranteed CTD after a certain amount of time.

 

2. Third Party Programs interfering with the game, ie Anti-Virus Scanners/ Anti-Malware, or OSD interfering with ENB if Applicable (such as Msi Afterburner). etc etc.

 

3. Missing String Files, technically this should not be a potentional problem these days, as Bethesda has packed the String Files in the Archives, however this was not always the case, where they used to be loose files (once upon a time), likewise if the string files were tampered with/ Deleted/ or invalid to the game language, this would cause a 100% Repeatable CTD when the game attempts to load the options, such as new game, options and the like (not Nessarary 17 Seconds as per Op but, depends how long it would take the game to load) <-- probably not relevant here (as the OP title specifcially says 17 seconds in, which i would assume 17 seconds in the actual game world, and not loading game/ character creation), but it is worth mentioning nontheless.

Edited December 1, 2022 by G4M3W1NN3R

[Blinxys]

@GW I'll back up your recommendation for buffout, but I still think OP is looking at a scorched earth policy and proceed diligently from there. :nuke:

QAC each and every mod as it goes in. Technically should do a bash patch each time too.

But that is often saved for when your load order is nailed down.

(Always bugged by the disparity between load order and order loaded in to begin with). :confused: