[CRASH HELP] Modded game crashes when entering random doors.

[mason1204]

So I'm pretty sure my game is crashing because I modded the game. This only started happening the day I modded FO4. It has always been random doors that would crash my game. Sometime it would take two hours to crash, and other time it would take 15 minutes. But recently, it's been getting super bad. It takes all of five minutes. I crashed when trying to exit a house in Diamond City, loaded game back up, went into the bar, tried to exit and then crashed again! Now I've tried multiple things that I've read online. I've done all of the following:

-Used LOOT to sort my boot order -Verified my game cache -Deleted a ton of saves that I didn't need -I put "*" in front of everything in the plugins.txt -Made sure F4SE was up to date

Now I know I should probably go though and disable them all one by one but the problem is, is that a lot of mods I use would probably crash my games if I didn't have them because I've got modded workshop items placed in settlements and stuff like that. Also, sometimes I can get through a whole play session without a crash and if that happened during testing how would I know if a mod was a culprit? The list of mods I have is below and it is in the boot order I have them(Non esp and esm at the end):

-----Main Files----- -Fallout4.esm -DLCRobot.esm -DLCCoast.esm -DLCNukaworld.esm -DLCworkshop1.esm -DLCworkshop2.esm -DLCworkshop.esm -----MODS----- -Unofficial Fallout 4 Patch.esp -ArmorKeywords.esm -dinoshelf.esp -dinoshelf_extra_ammo.esp -OCDispenser.esp -OCDecorator.esp -OCD FarHarborDLC.esp -LaundryDay.esp -FunctionalDisplays.esp -FunctionalDisplays-Collectibles.esp -FunctionalDisplays-AID-Vanilla.esp -FunctionalDisplays-MISC-Vanilla.esp -FunctionalDisplays-Patch-DLC01.esp -FunctionalDisplays-Patch-DLC03.esp -ScrapDeadThings.esp -RichMerchants.esp -move that workbench!.esp -Armorsmith Extended.esp -Armorsmith Automatron.esp -Armorsmith Far Harbor.esp -Armorsmith Vault-Tec DLC.esp -NoNegativeAffinity.esp -HalfAffinityCooldown.esp -----NON ESP/ESM MODS----- -2k bottles label overhaul -Achievements -Arm and Hammer - Abraxo Retex -Black Pip-Boy -Bobblehats FO4 Edition -Bobby Pin Box Retex -Canned Dog Food - Pedigree Retex -Ephla's Unique Chems -Glowing Holotapes -Immersive 2015 Kraft Mac n Cheese - Blamco M&C Retex -Place Everywhere -Realistic Pre-War Money

So that is all my mods I have installed. If anyone knows how to fix this or has any suggestions please let me know! Also, I don't think it is a hardware issue bc it only happened after I modded and I have really good specs. But just in case I have 32gb ram, EVGA GTX 970 FTW, Intel I7 4790k OC 4.4ghz. I'm running on the optimized ultra settings. Thanks for any help you can provide!

 

[Bisaflor]

r u playing 1.7.15?

 

have u tried to load the save without f4se and use a door?

[mason1204]

r u playing 1.7.15?

 

have u tried to load the save without f4se and use a door?

No, I'm playing 1.7.12 And if I disabled f4se, wouldn't some of my mods that are dependent on that not work?

[Bisaflor]

play without f4se untill the next door

if it works u know that f4se or a f4se based mod causes the error which help to confine the problem

[mason1204]

play without f4se untill the next door

if it works u know that f4se or a f4se based mod causes the error which help to confine the problem

It still crashed.

[SharraShimada]

Bethesda engine is VERY picky with timing-settings. Every time you change the scene, data will be loadet from your harddrive. If only ONE part is not coming in time, the engine freezes.

If you dont run FO4 from an SSD, you should try to defragment your harddrive. Its known to solve many crash-problems.

 

If that dont solve your problem, try to use enb-boost, and allocate some of your system memory for extended graphics. You are playing on ultra, so your video-RAM ist filling really fast. And (like above) the engine does NOT like to wait for anything.

[jjb54]

Okay, this is going to suck and I know it well, as I have been there and done it myself.

 

1st - BACK UP ALL YOUR CURRENT SAVED GAMES INTO A DIFFERENT DIRECTORY.

 

Use NMM and turn > OFF < all mods.

 

NOTICE: DLC's are NOT MODS and do NOT turn them off.

 

Now, does the game crash entering a door?

 

... Yes?

 

Then the Saved Game File is likely corrupted due to mods, likely being installed and removed in current game. Rule of thumb. Do NOT install and/or remove 2 or more minor mods during a games.

 

Updates are not new mods and could / could not be an issue. You should read the Mod Page Description to note any warnings / alerts when updating a mod.

 

Only real solution is to start over.

 

... NO!

 

This is where the P.I.T.A. protocol begins. NO, it is not fun and depending on your mod count, is well a P.I.T.A.

 

Reactivate through NMM your first mod and play... until you are convienced the Door CTD is not happening.

Then reactivate through NMM the 2nd mod and so on, until you find the mod / mods.

 

Understand it could be more than 1 or even 2 mods at play in the cause / effect of the CTD.

 

When you find the first CTD and associated Mod ... go to that Mod's Description page and read and see if any known bugs are stated.

 

>>> ALSO:

 

Read the user posts. Sometimes a player might post a similar experience and might be able to help you find the answer.

 

Good Luck .....

[mason1204]

Okay, this is going to suck and I know it well, as I have been there and done it myself.

 

1st - BACK UP ALL YOUR CURRENT SAVED GAMES INTO A DIFFERENT DIRECTORY.

 

Use NMM and turn > OFF < all mods.

 

NOTICE: DLC's are NOT MODS and do NOT turn them off.

 

Now, does the game crash entering a door?

 

... Yes?

 

Then the Saved Game File is likely corrupted due to mods, likely being installed and removed in current game. Rule of thumb. Do NOT install and/or remove 2 or more minor mods during a games.

 

Updates are not new mods and could / could not be an issue. You should read the Mod Page Description to note any warnings / alerts when updating a mod.

 

Only real solution is to start over.

 

... NO!

 

This is where the P.I.T.A. protocol begins. NO, it is not fun and depending on your mod count, is well a P.I.T.A.

 

Reactivate through NMM your first mod and play... until you are convienced the Door CTD is not happening.

Then reactivate through NMM the 2nd mod and so on, until you find the mod / mods.

 

Understand it could be more than 1 or even 2 mods at play in the cause / effect of the CTD.

 

When you find the first CTD and associated Mod ... go to that Mod's Description page and read and see if any known bugs are stated.

 

>>> ALSO:

 

Read the user posts. Sometimes a player might post a similar experience and might be able to help you find the answer.

 

Good Luck .....

Well I disable every mod and I was able to play for over an hour without any issues. So I'm just gonna not play with mods anymore because I've wasted a lot of time screwing around with them. I'm lucky that my save wasn't corrupted and I'm too far in to start messing around with crap again. Also I did try disabling mods and stuff, but I left on like two that I wanted to have no matter what, and the game still crashed, so I'm pretty sure it had something to do with those.

[crawe1x]

Often it can be something quite unexpected... I kept getting crashes in a recent playthrough, particularly when fast travelling or quick-saving. I suspected it was mod related. I disabled all 130+ of the mods I had activated and then reintroduced them back into the game one by one. In the end, it was a very simple weapon mod that was causing the problem - don't know why; I'd had no previous problems with that mod. Anyway, like jjb54 says, you have to go through your mod list quite thoroughly and with patience.

[tjehu]

Do you recall which mod it was? I seem to be having the same issue.