My load order is the smallest I've made, but it's already causing a CTD where Preston is.

[TreshMek]

As the title suggests, whenever my game fully loads the area where the character first encounters Preston Garvey, the game will instantaneously crash. What is happening is this: my character walks to where Preston is fighting the Raiders, then the game crashes after a few seconds. Sometimes the crash occurs the very moment Preston appears. Compared to the load orders I've created before, this load order is quite possibly the smallest I've made. It contains, what I believe to be, only the barest minimum set of mods that I've been using as a foundation to develop the rest of the load order. Unfortunately, as I've mentioned, it's already made the game crash upon entering Preston's initial encounter. Irritatingly, Buffout4's crashlog text file does not write anything about the crash. It probably doesn't help that the previous load order I made was last year and there might be some steps that I am overlooking. I do know this: if my load order is crashing the game at Concord, then most definitely it will crash similarly in many other places.

 

I'd like some help here, please. Normally I don't paste my load order list... but, this time, I definitely need some help picking out which ones to scrutinize. My current load order should be small enough to warrant at least a looksee.

 

Here is my small load order:

 

Fallout4.esm
DLCRobot.esm
DLCworkshop01.esm
DLCCoast.esm
DLCworkshop02.esm
DLCworkshop03.esm
DLCNukaWorld.esm
Unofficial Fallout 4 Patch.esp
ArmorKeywords.esm
HUDFramework.esm
WorkshopFramework.esm
clothingoverhaul.esp
ClothingOverhaulSP_XB1_PC.esp
Consistent Power Armor Overhaul.esp
More Power Armour Mods.esp
More Power Armour Mods - Automatron.esp
PAMAP.esp
Brotherhood Power Armor Overhaul.esp
BPAO - Automatron Patch.esp
BPAO - PAMAP 2.0 Patch.esp
BPAO - PAMAP 2.0 Automatron Patch.esp
CBBE.esp
LooksMenu.esp
LongerPowerLines3x.esp
LegendaryModification.esp
LegendaryModification2LM.esp
LegendaryModificationMisc.esp
BrighterSettlementLights_LessHarsh.esp
VeryRichMerchants.esp
VisibleCompanionAffinity.esp
BetterGenerators.esp
Adamantium Skeleton Improved - No Falling Damage.esp
Strong Back - Improved -- Far Harbor.esp
Skb_MachinegunsRebirth.esp
Skb-MinigunsRebirth.esp
Skb_RiflesRebirth.esp
DD_All_the_COncrete.esp
BullpupBozar.esp
DP_CaravanShotgun.esp
GreaseGunSMG.esp
HuntingShotgun.esp
WattzLaserGun.esp
Armorsmith Extended.esp
EnclaveX02.esp
More Power Armour Mods - X-02.esp
EnclaveX02_PAMAP.esp
StartMeUp.esp
StartMeUpFarHarborPatch.esp
StartMeUpNukaWorldPatch.esp

AmazingFollowerTweaks.esp

 

 

Edited July 3, 2022 by TreshMek

[TreshMek]

Update: something is genuinely whack. The game still crashes even with all mods disabled, including the Unofficial Patch. I'm all out of ideas. :sad:

[nexusclod]

A couple things here: Just because you're crashing when you first encounter Preston doesn't mean he is the issue. The other item you first encounter near Preston is Power Armor. As a majority of your mods are PA related, I'd start there.

"I do know this: if my load order is crashing the game at Concord, then most definitely it will crash similarly in many other places" How do you know this? Have you tried going other places? Open the console, type tgm, hit enter, type tcl, hit enter, close the console, then run around the map and see if other locations are causing ctds.

You only have a few companion mods, should be simple to test if those are the issue. Disable one at a time, reload, repeat.

"Update: something is genuinely whack. The game still crashes even with all mods disabled, including the Unofficial Patch. I'm all out of ideas" Are you talking about on the same save, or a new save? If you disabled all your mods then loaded the save that had all those mods, ctds/failure to even start the game is expected behavior. Anytime you add/remove a mod you are changing your load order and your form ids, this is a bad idea. You might get away with it depending on your load order and what mods you are using, but this WILL bite you in ass eventually. A good idea is to create a clean save (no mods at all) right before you leave Vault 111. Having a known clean save can be super handy when testing mods/conflicts, and saves a lot of time.

If you haven't already, go get FO4Edit https://www.nexusmods.com/fallout4/mods/2737 , open it with all your mods loaded and start looking for conflicts.

How are your specs, are they good enough? Can you run 60fps consistently without mods? Have you done the archive invalidation in your .ini? (This thing:

[Archive]

bInvalidateOlderFiles=1

sResourceDataDirsFinal=)?

Have you validated your files through steam? Do you have f4se installed correctly? Are you sure you have buffout4, and all its dependencies installed correctly?

There's a few ideas to get you started

 

[TreshMek]

You listed literally everything I've tried except going through FO4Edit.

 

FO4Edit does show me conflicts, but I've got no idea what to do with the information if I've got no idea what I'm looking for. Thanks for the measly help, though. There is something seriously whack going on and I'm set to try and figure this out another time.

[fraquar]

I can't replicate the problem with the exact same mods and load order.

Chose the "it's a dream" option in Start Me Up, saved at the vault door then went to Concord.

Quests triggered, Raiders died, Preston wouldn't shut up as usual.......

 

I use Mod Organizer 2 for my mod manager.

 

I will say this though, even if you get it working you need to merge those Power Armor patches.

Right now you got patches getting overwritten by either other patches or Armorsmith Extended.

That might be what you want, I'm not sure - but it sure seems odd.

[Guest deleted34304850]

i'd empty your data folder - then delete it entirely.

then i'd use steam to validate game files.

then i'd start a brand new game - make sure it starts and you can do the opening quests.

i'd do them up to the point of leaving the vault then i'd save and exit.

 

at this point, i'd add a couple of mods.

 

start and load your last game - try to complete the sanctuary quests - if all goes well - save. exit.

 

add a couple more mods - nothing mega - just a couple.

 

get to the point where your previous game was failing - i will bet you good money you're past that now.

 

save. exit.

 

add a couple more mods, start the game, rinse, repeat.