CTD when entering dungeons with or without any mods installed

[Falkner35]

It's not within my power or attention span to check whether all dungeons CTD when entering, but from my experience both Helgen Keep and Bleak Falls Temple CTD upon entering them.

I initially started with mods, I didn't know this was a problem until I entered bleak falls barrow because of Live Another Life not requiring me to enter Helgen Keep. After the crashes,

I tried disabling *some* mods, then all of them, then my ENB, then I tried running the game without SKSE64, and then I tried deleting my Skyrim and SkyrimPrefs ini files. As far as I know, these are all the ways I could possibly isolate and prevent a crash.

Verifying Integrity Of Game Cache returns that all files were verified.

The save that I've been using to test this issue has one mod that was since disabled, which is Live Another Life, so that I wouldn't have to do the intro.

I somewhat expect to be told to try a save with absolutely no since-unloaded mod content, but if that's all that anybody can think of, I'm probably going to cut my losses because LAL is probably one of the most well-behaved mods I've ever used.

Any suggestions of other avenues to try and fix my game (Reinstalling the game is an absolute last resort that I'm not going to resort to because of my terrible download speed as well as the havoc reinstalling the original skyrim wreaked on how Nexus Mod Manager behaves) are HIGHLY appreciated. Thanks.

EDIT: Forgot to mention that I was also sorting my load order with LOOT.

Edited January 27, 2018 by Falkner35

[Jannifer]

Try going through this guide -- http://wiki.step-project.com/Guide:Make_Skyrim_Vanilla_Again The file structure is the same for both games, so that shouldn't be an issue. It sounds like there's something left over from a mod installation that's borking your game.

 

Once you've gotten everything cleared out, reinstall SKSE64 and LAL. Start a new game and create a save that you are only going to use for testing mods. When you start reinstalling mods, install just a few at a time. Read all mod descriptions carefully and take notes if you need to. Mod authors often give important information in their mod descriptions such as required mods and suggestions about load order. LOOT is an excellent tool, but it is not perfect, so you'll need to double-check what it's doing.

 

Once you have a mod installed, do NOT remove it. If you change your mod list, start a new game. You might be able to use one of the save game tools such as Fallrim Tools to rescue a borked save, but don't count on it.

 

The reasons for the above recommendations aren't always made clear to folks who're struggling with their mod lists. First, if you remove a mod, you change all the item IDs for every single mod below it in your load order. Skyrim and SSE both use a numbering system which relies on where a mod is in your load order. So, all those xx372ab5 numbers? Where those X's reflect where the mod is in your load order? Those all change when you remove a mod, which can bork things royally. Secondly, Skyrim stores an amazing amount of stuff in your save. This is why you might remove a mod and still see evidence of it in the game. You may indeed have removed all everything, but there's information still stuck in your save game which will exist until long after your character has gone to Sovngarde.

 

One mod manager on its own isn't going to bork your game. MO and NMM work differently, but both of them use a virtual install system to keep stuff out of your Data folder. I have been told that the latest version of NMM does install information to the Data folder, but that doesn't seem to be consistent for everyone. NMM does add an .esp to tell the game where the real information is, but shouldn't install anything else. However, some people truly prefer to manage their mod installations the old-fashioned way by manually installing and uninstalling their mods. Personally, I use an older version of NMM which still installs everything directly into the Data folder because I don't like anything getting in between me and my file structure, although I like the convenience of using a mod manager. So, use whatever method you like to install your mods, just be consistent. :)

 

Do not ask me how I know these things. :pinch: I had to stubbornly learn some things through long and sad experience even as more experienced players were telling me otherwise. I hope your journey is less frustrating.

[Falkner35]

Try going through this guide -- http://wiki.step-project.com/Guide:Make_Skyrim_Vanilla_Again The file structure is the same for both games, so that shouldn't be an issue. It sounds like there's something left over from a mod installation that's borking your game.

 

Once you've gotten everything cleared out, reinstall SKSE64 and LAL. Start a new game and create a save that you are only going to use for testing mods. When you start reinstalling mods, install just a few at a time. Read all mod descriptions carefully and take notes if you need to. Mod authors often give important information in their mod descriptions such as required mods and suggestions about load order. LOOT is an excellent tool, but it is not perfect, so you'll need to double-check what it's doing.

 

Once you have a mod installed, do NOT remove it. If you change your mod list, start a new game. You might be able to use one of the save game tools such as Fallrim Tools to rescue a borked save, but don't count on it.

 

The reasons for the above recommendations aren't always made clear to folks who're struggling with their mod lists. First, if you remove a mod, you change all the item IDs for every single mod below it in your load order. Skyrim and SSE both use a numbering system which relies on where a mod is in your load order. So, all those xx372ab5 numbers? Where those X's reflect where the mod is in your load order? Those all change when you remove a mod, which can bork things royally. Secondly, Skyrim stores an amazing amount of stuff in your save. This is why you might remove a mod and still see evidence of it in the game. You may indeed have removed all everything, but there's information still stuck in your save game which will exist until long after your character has gone to Sovngarde.

 

One mod manager on its own isn't going to bork your game. MO and NMM work differently, but both of them use a virtual install system to keep stuff out of your Data folder. I have been told that the latest version of NMM does install information to the Data folder, but that doesn't seem to be consistent for everyone. NMM does add an .esp to tell the game where the real information is, but shouldn't install anything else. However, some people truly prefer to manage their mod installations the old-fashioned way by manually installing and uninstalling their mods. Personally, I use an older version of NMM which still installs everything directly into the Data folder because I don't like anything getting in between me and my file structure, although I like the convenience of using a mod manager. So, use whatever method you like to install your mods, just be consistent. :smile:

 

Do not ask me how I know these things. :pinch: I had to stubbornly learn some things through long and sad experience even as more experienced players were telling me otherwise. I hope your journey is less frustrating.

Did everything you suggested, reinstalled mods in batches using NMM (I was using it the whole time in case it wasn't clear) and it turns out that the mod which was causing my crashes is Noble Skyrim, which can't even be installed with NMM for special edition. So I guess I'll be using a different texture mod! Thanks.