Longstanding Skyrim CTD issues
Longstanding Skyrim CTD issues
Here we are. Many users face similar problems after trying what seemed like effective fixes. It feels like you're playing Skyrim when suddenly the game freezes with no warning or error. You installed most mods and ran everything on ultra settings, thinking your system (GTX 1080, i7-4770k, 24GB RAM) could handle it. Others reported that insufficient RAM allocation by the developers was the main problem. I downloaded the Memory Blocks Log mod to see how much memory is used during crashes. So far, Block 1 stays under 185MB (Blocks 1 and 2 each have a 256MB limit), which suggests it's not a memory shortage issue. Still, I wish I could get more RAM allocated, but right now my priority is stopping these crashes. I really need some assistance with this.
Do you have SKSE with the memory fix applied? Have you set up the unofficial patches? Is your load order accurate? Are you using enboost with that memory fix implemented? EDIT: Which mod organizer are you employing? Nexus? Mod Organizer? Manual?
I've completed all the unofficial patches and tested the memory patch called Skyrim Startup Memory Editor with the non-skse base game. The SKSE feature doesn't appear to function properly. I have the Data file in a .zip file, but when I attempt to "add from file" through the nexus mod manager, it displays an error saying it can't be added.
Yeah SSME isn't needed with skse. You can't install skse using the Nexus mod manager either. You need to add it yourself by following the instructions—it's really just dragging and dropping. Apparently, they even have an installer now.
http://skse.silverlock.org/
That's the key point you should remember.
Next, think about installing enboost. It's a bit more challenging, but there are many online guides. Mostly it involves dragging and dropping, but you'll need to edit the .ini files and adjust certain settings. This tool lets Skyrim utilize all your video card and computer RAM, which really improves performance.
Lastly, run LOOT to determine the best load order. Load order might be causing CTDs. With over 200 mods installed, I still don't get any CTDs after using LOOT to sort them.
Finally, you should seriously think about switching to Mod Organizer 2. The Nexus mod manager is outdated and doesn't perform well. (They even stopped offering it on their site.)
I'm attempting those options. I hope one succeeds. Yes, I'll try MO2—it seems to come straight from the nexus. Should I source it there or is there another better way?
Yes, that's where I got it.
MO2 stands out from NMM because it lets you identify which mods affect each other. For instance, if you have a high-res texture pack with everything from ground to clothing textures and also a clothing retexter or remesh mod, MO2 will alert you when those two try to overwrite the same file, giving you the chance to choose wisely. With NMM, the last one you installed would always win. With MO2, you can clearly decide which version to keep.
Additionally, MO2 supports creating "profiles" for the game, keeping your main folder intact (except for SKSE and ENboost). This makes installing or removing mods much simpler and removes the need to worry about installation order.
You can still download mods straight to MO2 or add them by uploading .7z or .zip files.
EDIT: MO2 also has the "sort" button turned on by default, so you just click it and it handles everything automatically!
If you aim for fewer CTDs, consider using Skyrim SE. With roughly 240 mods installed, I experience a CTD approximately every 30 hours. These CTDs originate from the same mods that trigger them in Skyrim LE.
In Skyrim LE, numerous mods can induce CTDs. Most of these issues stem from interactions between the mod and the game engine, rather than conflicts between separate mods.
Approximately 80% of the CTDs I encounter in LE come from spawning mods. These tend to affect areas that were developed earlier (from Whiterun to Falkreath). I can go weeks without CTDs in other parts of the map.
Another category of mods that often cause problems with the engine are weather mods. These CTDs appear at points where weather triggers occur. Mods featuring NPCs interacting with the weather exacerbate the issue. For instance, a CTD near the top of the waterfalls between Whiterun and Riverwood is typically linked to a weather change.
The mods responsible for the most CTDs in interactions are perk mods. These are also the ones frequently mentioned in the papyrus log. Mods such as Ordinator can create a minefield of CTDs if you select a perk that conflicts with another mod on your load list. I recently resolved this by removing perks that caused CTDs during the Dragonborn DLC installation.
Additionally, the more mods you install, the higher the likelihood of encountering conflicts. After installing 180 mods, every two new ones out of three led to issues. Even updates can trigger conflicts at that point.
Load order matters; it can cause conflicts between mods but rarely results in CTDs.
In heavily modded games, tools like Loot can introduce more problems than they solve. This happens because finding suitable solutions isn’t always straightforward. That’s why I manually create load lists. If I run into trouble with a mod, I try Loot to see where it would fit, but I don’t apply the change. Doing so in my LE game would have prevented it from running at all.
Hardware CTDs are usually linked to VRAM. LE requires 4GB, while SE needs 8GB for heavy modifications. All configurations should include ENB/ENBoost.
Weak CPUs can lead to low frames and reduced performance but rarely cause CTDs unless the system is operating near full capacity.
Running the game on an HD can result in pauses and CTDs during saves, depending on the load size. Certain 2K/4K texture packs may trigger this issue on HD systems.
I discontinued modding my Skyrim LE game in 2016. It’s the same game I began in 2011. I keep it on a portable HD and transfer it to new installations as my computer upgrades.
My Skyrim SE game is slowly coming closer to the look I desire. It should take another year or two before it’s fully ready.
It seems @jones177 spotted something interesting. The Disabled Ordinator in the data files menu has been active for 30 minutes without a CTD. Usually, a CTD would occur within the first minute of play. I’ll keep looking into it and direct my frustration toward the developer of Ordinator(s). I’m hoping to turn it back on someday, though it’s not essential. I’m just relieved to be back in the game!