Crash to desktop fix?

[AngelsDefiance]

So i do a lot of modding obviously and i have been running into a lot of issues with it lately for the past 3 weeks. but luckily i have made a decent amount of progress. however...

it seems now i have one final hurdle to pass before i can finally play fallout 4 with mods

which is.... the crash to desktop bug. long story short, if i download mods via NMM, acitivate them, or deactivate and reactivate mods i currently have installed and activated or basically do anything of the sort:

my fallout 4 will break where basically if i go to certain areas (which can be anywhere, like first it was the big water tower east of the RR station and anything east of that, then it was near where the automatron DLC starts so on so forth) my game will crash to the desktop. and all i have found to fix this from people online is that you gotta start a new game.

but i /really/ dont want to have to start a new game every time i find a mod conflicts with another mod and i have to uninstall one or some nice looking new mod comes on the Nexus and i wanna download it.

so is there any way to fix this that doesnt involve erasing my saved game and starting a new one? just cause i actually wanna be able to play the game with mods and progress

[Crosstieger]

Long story short: There is no magical fix for the type of ctd you describe. You just encountered the worst type of ctd. This is the price you pay for modding a bethesda game. Sorry :happy:

 

There are a lot of potential problems why your game could crash. It could be that one of your mods conflicts with nearly every other mod you wanna try, your safe game could be corrupted (which can't really be fixed) or you use in general unstable mods. It's not really easy to tell. The ctd you describe is all to familiar to me and I just accepted that you cannot test every single mod on the same character.

 

Just recently I tried the mod "Legacy of the dragonborn" for Skyrim SE. It is just not possible to get the mod to run on my existing character. It only works on a new character.

 

Also you violated an important rule when it comes to modding a beth game. NEVER UNINSTALL A MOD. The issues that can occur are way too mysterious... If you want to uninstall a mod always continue with a safe game where the mod was never present.

[JimmyRJump]

A CTD is not a "bug". It's the result of many possible influences. It can be caused by an unstable (read: dying) mechanical hard drive that has damaged sectors; it can be caused by an intrusion from a third party program like your Anti-Virus software; it can be caused by using large texture files for which you have not enough GPU power/RAM to load them. Or a mod conflict can lay at the basis.

 

Mod conflicts are either the result of using one ore several mods that don't work well -if at all- together. Check mod descriptions. A conflict can also arise when some mods need a specific load order, i.e. one needs to be loaded above the other.

 

I've been using close or over 4000 different mods for FO4 and a lot of the time, using mods is hit and miss which you'll need to learn by checking things. I have uninstalled tons of mods midway through a game without any negative results, although I won't advise doing it too often, certainly when it concerns mods that alter storyline or dialogue or some such.

 

To begin, start using LOOT for load order purposes. It's not a magic tool that will solve all issues, but it is reasonably trustworthy. Keep an eye on mod descriptions where the author mentions to add the mod very low in the load order. You'll have to relocate such a mod manually in NMM after having sorted the load order with LOOT.

 

I currently am 420hrs into my game, with 692 active mods and 299 active plug-ins (251 esm/esp, 48 esl) and the game runs stable. So far I've had six out-of-the-blue CTDs without further consequences.