CTD while loading saves

[fartooloud]

I would love to get some help with the crash log, while trying to load saves. 

I tried 3 autosave saves, and one quicksave that take place in the same general area (2 indoors, 2 outdoors). Crash logs are weird, everytime I try to load a game different crash log appears. One time it loaded into the game but, when I tried to make new save it crashed instantly. I'll post 2 crash logs, one that is empty, and one from the game it was able to load in.

I'm, running skyrim AE, modded with step guide 2.1.0, with few mods added on top (I already tried, and disabled all additional mods, loaded the game, but the same happened) so far game was realy stable, not dropping below 35 fps around riften while using hard enb and DynDOLOD. 

I have only one more save that is about 15h of game time before the crashing saves happen, and it works fine. (I will definitely make more saves after this situation )

I read recent question about similiar issue, which concluded, that it was problem with SPID, and I wonder if its the same problem, but I cant decipher the crashlog by myself sadly.

crash-2022-11-30-15-16-00.log crash-2022-11-30-15-33-50.log

Edited November 30, 2022 by fartooloud

[Kattmandu]

1 hour ago, fartooloud said:

Well, thats harsh  Starting over after 44 ingame hours is realy discouraging, and still I don't realy know what happened. 

I've logged more than that in the last two weeks but I'll still keep logging more and then start a new game once Step 2.2.0 is released.  I'd rather start new after completing the 2.2.0 guide than continue with my current save and have a crashing issue arise after another 50 hours into it.  Been there.  Sucks.

[Mousetick]

2 hours ago, fartooloud said:

All mods are enabled at this point. Nothing has changed on the save, [...] and playing from the save that i created before. So, load order, and list of mods didn't change at all. Is it realy ****ed after that?

Ok, got it. No, it shouldn't be too bad with only CACO removed and re-added. It should be fine. You may have crap leftover in the save file, but it should be orphaned and unused. I can't really speak from experience as I've never had any issue with CACO.

2 hours ago, fartooloud said:

If it is, what is the point of the brute force method of checking the mods if you can't play on the save afterwards

The point is to troubleshoot and try to pinpoint the root cause, just like you did. The type of solution then depends on the root cause. Disabling a mod in order to keep playing is not a general, safe solution. Even if it's re-enabled later. If you save after disabling a mod, some bits are either cleanly removed from the save, or left hanging in it. Either of those things can break your game later on. Again, it depends on the mod.

[fartooloud]

Well, thank you guys for sticking with me, probably didn't loose my sanity trying to pinpoint the issue just because of you.