Constant CTD Even After Uninstall Mods

[bruhpenis]

Hey, downloaded an ENB and the game began to start crashing consistently (everytime around 10 seconds after loading the save), so I disabled every mod and returned back to the base game essentially, crashes continued so I then disabled the ENB, crashes are still occurring. I'm essentially just launching the base game and it continues to CTD, anyone have a fix?

[Blinxys]

Delete all saves, and start a new game.

Retro save affect corrupts load.

 

Case and point:

First run deleting all saves CTDs even before intro vid.

Running again all is good.

 

Theory/Conclusion: base game loads using temp file even before game save is loaded. CTD/Total restart wipes temp, all is good.

[michaelodle710]

From my experience even after uninstalling all mods the said uninstalled mods leave remnants in your fallout 4 directory hence corrupting your game and your data files. First, I would verify integrity of game files in steam and if this doesn't work then I would uninstall and reinstall. I recently had to do this because I was having troubles getting my game to work, what i did was I backed up my saves on a memory card and deleted them then uninstalled and reinstalled. After this I launched the game created a new character saved the game before I exited vault 111 and quit to desktop after leaving then I took my save games I backed up on my memory card and put them back in my documents folder where save games are stored by default and loaded a save that had not been previously modded and this worked for me. On a side note, do not install your game files into your program file directory especially on Windows 10 running build 1803 or higher as Microsoft has implemented something called UAE as an extra layer of security and this will mess with your system being able to access certain files and setting in your game if it is installed in your program files directory.

[Blinxys]

@Bruh

Yes, as @ michaelodle710 said verify your installation.

 

Also,

 

check your ini's and make sure fallout4prefs.ini is identical in

 

Documents\My Games\Fallout4\

as well as

{%Steam%}\Fallout 4\Data\Fallout4\Fallout4

 

If it still CTDs revert to default inis and work them up again.

 

Look for stray files, desktop.inis, symlinks, meta.ini etc.

Also I think base game uses different format plugin.ini format than mo and vortex.

that is in your user\appdata\yadda\yadda folder.

 

I keep a spreadsheet to track mods installed and resources.

Slightly more tedious but rather effective.

Since modern software has a way of losing "your HISTORY" (actual events) while sending "YOUR history" (personal preferences) to the mothership.

(messed up emphasis goes to the shareholders of big data). :pirate:

 

Have a *verified* zipped copy of base game locally, and mow install down whenever things get kooky to be sure.

Also, never install directly from mod manager over-web. DL first and install from local SSD- if you can. (Faster, easier, more stable/predictable).

(This really worked out well overall considering the mod-scatter by recent Nexus (shareholder) policies and the issues of some modders).

 

Anyway, AFAIK (and I'm no expert) data is not supposed to be stored with code. That is exactly the issue/problem with retro-save data.

The game should store "save data" and inline-code storage physically outside of "save data". (typically a cache file) But no...

(People often prefer being lazy-minded when only vigilance will do). :sleep:

 

The scientific process has been corrupted too (for two decades and going strong). :devil:

 

@ michaelodle710 What you are describing may be a result of A) corrupt base game files B) Mods that modify base game files/values/loose files which corrupted save data. (May introduce problems later in-game play-through). C) Corrupted Mod Installation file(s).*

 

The only way to know anything for certain is to have attempted your final step first. i.e. Delete/Move modded saves, then load unmodded save before rebuilding. See if it worked, if not- at what stage in your process does it begin to work properly? :ninja:

 

You are also spot on about avoiding Program Files Folder. The UAC problems are a more recurrent microsoft theme than its themes were.

If I could save game data and plugins.ini to the game's own folder I can stop launching my MM in administrator mode (UAC completely defeats any benefits bestowed upon the user of UAC). :unsure:

 

*NMM sometimes gets confused and installs into its "virtualFolder" as opposed to actual folder resulting in bunk installation(s). Generally gets it right after a lil install/uninstall rinse/repeat cycle. Problem is, you have to catch it in the act and it goes by fast sometimes, you can't easily know/check/see what it really did at any time. That history emphasis thing.