SSE CTD on Save After Hours of Gameplay

[squireoivanhoe]

This happened to me on a 700+ hour playthru...

I think it may have been on account of saving over an autosave as was mentioned elsewhere, but I have done that many times with no issues in this playthru.

I did have Skybirds and have just cleaned it out of my save, hopefully it works...

its very frustrating, because it happened just after I deleted most of my old saves lol fml... :sick: :ermm:

Skybirds was probably your issue. Be sure to try the fix listed earlier.

[macrocosm144]

Yes i edited my previous post with the update, cleaning out skybirds fixed it :D

[squireoivanhoe]

Yes i edited my previous post with the update, cleaning out skybirds fixed it :D

Great! Glad it worked for you!

[BlueGunk]

Apologies for general ramble...

 

Well, I decided my game was irretrievable (surprise!). So I am building yet another.

 

I've been doing a little research over on the forum thread to do with False Save Corruption, where I was active a few months ago. There is a strong similarity in what these folks are experiencing to what we have.

They agree that certain mods and certain builds are known to be trouble. But putting those aside, after 111+ pages of discussion they still can't put their finger on any one cause.

 

Their general opinion is a combination of too many heavy mods, mods that alter too many world spaces, add NPCS (who all need AI), mods like Skybirds and Convenient Horses, etc., stress the game engine too far.

OK, we know that already...however there is an interesting take on this with Skyrim SE.

 

Their findings are: although SSE 64bit is a much more stable platform, it adds about twice as much vanilla content to the basic game engine as Oldrim. And, even though it's 64 bit, underneath it is a reconditioned and upgraded Bethesda two-stroke petrol lawnmower engine.

Instead of CTD like Oldrim, the cracks in SE start to show with small things like a missing texture, missing menu items, other bugs, then false save corruptions, etc., and the game slowly becomes unusable.

Therefore wrecking it is a more insidious process. Put in a mod - yay it works. 100 hours play later the engine starts to leak oil and die.

 

Their canary in the coal mind is the 65,500 string limit. That it is still valid.

Their conclusion is to assume the some of the 32bit faults are still there, if deeply buried, and mod SE as if it were Oldrim.

 

TL:DR - while SE is much more robust, it also breaks more slowly. Instead of a CTD, problems can emerge hours of play later as the engine stresses and finally breaks.

 

I'd be interested in opinions on this with regard to our save game freeze issue.

[squireoivanhoe]

Apologies for general ramble...

 

Well, I decided my game was irretrievable (surprise!). So I am building yet another.

 

I've been doing a little research over on the forum thread to do with False Save Corruption, where I was active a few months ago. There is a strong similarity in what these folks are experiencing to what we have.

They agree that certain mods and certain builds are known to be trouble. But putting those aside, after 111+ pages of discussion they still can't put their finger on any one cause.

 

Their general opinion is a combination of too many heavy mods, mods that alter too many world spaces, add NPCS (who all need AI), mods like Skybirds and Convenient Horses, etc., stress the game engine too far.

OK, we know that already...however there is an interesting take on this with Skyrim SE.

 

Their findings are: although SSE 64bit is a much more stable platform, it adds about twice as much vanilla content to the basic game engine as Oldrim. And, even though it's 64 bit, underneath it is a reconditioned and upgraded Bethesda two-stroke petrol lawnmower engine.

Instead of CTD like Oldrim, the cracks in SE start to show with small things like a missing texture, missing menu items, other bugs, then false save corruptions, etc., and the game slowly becomes unusable.

Therefore wrecking it is a more insidious process. Put in a mod - yay it works. 100 hours play later the engine starts to leak oil and die.

 

Their canary in the coal mind is the 65,500 string limit. That it is still valid.

Their conclusion is to assume the some of the 32bit faults are still there, if deeply buried, and mod SE as if it were Oldrim.

 

TL:DR - while SE is much more robust, it also breaks more slowly. Instead of a CTD, problems can emerge hours of play later as the engine stresses and finally breaks.

 

I'd be interested in opinions on this with regard to our save game freeze issue.

That sounds pretty spot on. Like I speculated earlier, they are probably different symptoms of a similar problem.

[macrocosm144]

Well, it worked for a day lol, I was able to play and saved about 20 times, but today none of them will save again. Oh well, I think its probably best to just start a new game and never go anywhere near skybirds again, even after cleaning out skybirds there were still all sorts of spawn errors in the following saves, so you cant actually uninstall skybirds cleanly like some other mods. 700 hour playthru down the shitter. It will be nice to have a fresh new game though, been playing this one since 2016 lol, now theres a bunch of other mods I can add/remove too so its all good.

[squireoivanhoe]

Well, it worked for a day lol, I was able to play and saved about 20 times, but today none of them will save again. Oh well, I think its probably best to just start a new game and never go anywhere near skybirds again, even after cleaning out skybirds there were still all sorts of spawn errors in the following saves, so you cant actually uninstall skybirds cleanly like some other mods. 700 hour playthru down the shitter. It will be nice to have a fresh new game though, been playing this one since 2016 lol, now theres a bunch of other mods I can add/remove too so its all good.

Yes, probably that same "fix" of removing ANY mod that grants you a few hours of play. Sorry for your loss!

[BlueGunk]

Bad luck, macrocosm144. I've done that a few times, too. It's mortifying and a horrible feeling.

 

In that strings stuff I was reading, I gather some mods leave debris behind in the strings table. So even if you clear out Skybirds, etc., junk remains buried in that table.

 

I've just finished building a new Skyrim game (is this game attempt 150? :laugh: ).

This time Skybirds is a small heap of ash on my PC table. I've kept the opening string count to maximum of 47,500 which I hope will give me a full play-through (ha ha - where have we heard that one before?).

I've also removed some script heavy and world-altering mods as well. I'm not bothering with Dyndolod, either. I read in a Reddit thread of someone's experiences that it can ruin a heavily modded game by tipping it over the edge - with prejudice.

 

Here goes... (if you hear a 'boom' that's my PC exploding.)

[macrocosm144]

Yes lol FML its all good I guess, but, here's hoping since Skyrim has new life breathed into it by SSE there will become a way to cleanly uninstall mod, Resaver may be able to get us there eventually. Im kind of excited to start over though lol so I guess im not too mad, but damn it does suck lol. My Legacy of the Dragonborn Gallery was really starting to fill up too! lol

Edited March 17, 2018 by macrocosm144

[macrocosm144]

Well... I found a pleasant surprise, I was able to fix it by disabling an old SMASH patch I had in my load order... lmao.... I only discovered it because I couldnt get the game to start again after doing some mod updates, it would just hang on the loading screen even though there were no missing masters or anything. So once I figured out which mod was causing the trouble and the game started I tried on a whim one of my old saves, and its working fine, I can use all the different saves and such. yay! Im guessing my patch had some skybirds stuff in it that I missed cleaning out after removing skybirds as a master.

Edited March 21, 2018 by macrocosm144