Potaters12

In a nutshell, it greatly improves visuals. However, depending on the ENB, it can also radically reduce performance as well.

Yes it does. Save bloat is a common cause for CTD's and game instability. Checking your papyrus log can determine if your save is running rampant scripts or not. It looks like the OP is having script issues, most likely due to uninstalling script heavy mods.

Looking at your load order, you should most definitely use both SSME and ENBoost. If you use an ENB already (above version .2) you should have ENBoost already, if not then you can install ENBoost without ENB feautres. You are using mods that add A LOT more NPCs (immersive settlements, and immersive patrols ). These mods will require the Skyrim engine to use a lot more memory, usually much more than it was built to handle, causing CTD's. I guarantee you your CTD's aren't really random at all. They probably happen when you near a settlement(from immersive settlements),when a group of NPC's spawn (from immersive patrols), or when you're riding fast on your horse(causing the world to load quickly). Usually Skyrim crashes when there are 35 or so NPCs spawned at once(in addition to being in a memory hogging area). SSME (through expanding memory block allocation) will definitely fix most of those crashes. SSME is a simple install, however make sure it is running properly with Memory Blocks Log. You did say you used a lot of texture mods, and as a result, the 2.0gb of VRAM on your card may be insufficient. ENBoost will improve Skyrim's VRAM usage, and not only add preformance, but reduce crashes as well. You could use the Skyrim Performance Monitor to see how much VRAM and RAM your system is using when playing Skyrim. Definitely use the two, and report back the results. I also noticed that you are using more than a few script heavy mods(Frostfall, Footprints, Wet and Cold etc...). I wouldn't be surprised if script related crashes are also happening on your system. If that is the case, then there is not much that could be done. I would recommend you to enable papyrus logging within your Skyrim.ini, and then check your papyrus log to see if your save is bloated. Remember: Don't uninstall script heavy mods, because that could potentially screw up your save even further. [Papyrus] bEnableLogging=1 bEnableTrace=1 bLoadDebugInformation=1

No problem, In the plugins tab within NMM, select a plugin. Once you have a plugin selected a description box should appear to the right, underneath the mod description it should say "Masters" and then list various .esm/.esp files. These files are required for the mod to run. Most mods just have "Skyrim.esm" or "Update.esm" listed, however many mods require additional master files to run. Check every single plugin within the plugins tab to make sure that you have every single file listed under "Masters". If you are missing a master file, then that is the mod most likely causing your instant crashes, and you should disable said plugin. Are you using CoT Winters Edition and CoT Sounds? You have patches for both, but I can't seem to find the corresponding masters in your load order. If you are not using CoT Winters Edition or CoT Sounds then the SoS patches may be the culprit for your crashes. Try disabling all the SoS patches for CoT Winter and Sound, see if that works.

Most instant crashes on startup are due to missing master plugins. In NMM, check to make sure you have all the .esm/.esp's required for each mod.

Most instant crashes on startup are due to missing master plugins. In NMM, check to make sure you have all the .esm/.esp's required for each mod.

You didn't really post too much information for me to work with. Are you using SSME or ENBoost to radically reduce memory related crashes? What are your system specs? Where does it usually CTD (before entering cities, riding horse etc...)? Could you post your load order or perhaps a papyrus log?

I used to use Autosave Manager as well, and found out that it often causes crashes on autosaves. Perhaps you could reduce the instances Autosave Manager autosaves, or try to disable its features in MCMM. Try not to uninstall it all togethor because that could further script issues within your save. Do that and see if the issue presists. Speaking of scripts you certainly have more than a few script heavy mods, I wouldn't be surprised if your save is bloated or just generally screwed up. If that is the case then there is not much that could be done to salvage your game. Perhaps you could post a papyrus log? PS: You double posted this thread

*DELETED POST*

So, I've been enjoying a pretty stable modded playthrough (over 180 mods) for about 3 weeks now until a very odd bug occurred. At a seemingly random time my camera (both in third and first person) got completely stuck in my horse's perspective, even when I'm inside a cell. I can still see my character and control him, however I'm seeing him in the horse's POV. When this happened the first time, I simply loaded an older save (about three saves back) and the issue was gone. However once it happened the second time, I started trimming mods off my load order to find a culprit. I clipped off Immersive First Person, Customizable Camera, Convenient Horses, and loaded the save without SKSE, but to no avail. After looking online a bit, I found one other person who had this issue, and he was playing on the PS3. Since the PS3 has no mods, I can be certain that this issue isn't mod related at all. To troubleshoot even further, I tried to force the camera to reset in game through use of various tricks. I tried TFC, using a tanning rack/forge/workbench, mounting and dismounting another horse, using horse call(convenient horses), and I even entered different interiors. Once I enter an interior, my camera's position is located outside the cell and in the position where my horse would be outside. For example if I parked my horse at the Whiterun stables and went inside Whiterun, even though my horse isn't loaded in the world, my camera would still be rooted at the stables outside of Whiterun where my horse would have been. I've tried killing my horse too, but the camera still remains locked on the (now) dead horse. I do have a save that is free of this issue, however it is likely that it will pop up again. Perhaps there are some people out there who have come across this extremely odd bug as well, and have squashed it. I haven't the slightest clue as to what could be repeatedly causing this. Any ideas at troubleshooting would be greatly appreciated. This is a very game-breaking issue, especially due to the fact that I don't like my horse very much as it is. Thanks

That's exactly the type of answer I was looking for. Much appreciated. To be honest, the command seemed way too good to be true anyway. Another quick question, if I were to keep Wet and Cold Installed, but disable all features within the MCM would that lead to script issues?

In order to reduce the amounts of scripts my game uses, I've been looking at uninstalling wet and cold, player headtracking, and footprints. However, I understand that in doing so, I'm putting myself at risk for save bloating. Apparently there is a command in SKSE called ClearInvalidRegistrations. When turned on, it is supposed to clear up unused scripts within your save. This seems beyond brilliant, yet it doesn't appear to be mentioned that much. Therefore, it lead me to believe that there must be some sort of catch. How effective is this command exactly? If I apply it will it rid my savegame of any trace of wet and cold, player headtracking etc... I would like some clarification on the situations in which this command should be effective. Thanks