Consistent CTD when using Quickload after playing for a while

[Serenity_XXI]

I did a clean install of Skyrim a couple of days ago after it had become unstable due to problematic mods.
 
I now have a new problem which I never previousy experienced:
 
- After playing for a while (10...20+ minutes) whenever I use Quickload (F9 key) the game exits to desktop.
- There is nothing wrong with the save itself (e.g. it being corrupted), as after I reload the game it loads just fine and I continue playing normally.
- Game is otherwise stable, as there are no random CTD's while playing (like I had before), this only happens when using the Quickload.
 
Game version/info:
- Skyrim version 1.9.32.0 (latest update from Steam) - Dawnguard/Dragonborn DLC's NOT installed.
- SKSE version 1.7.2 (beta)
- NOTE: I also applied SSME - Skyrim Startup Memory Editor. Thinking this would help with the CTD's, but it didn't.
- I have a basic list of mods installed (see below), but from my past experience they're all stable and never caused this *particular* behavior of CTD on Quickload.

- Load order has been optimized using LOOT version 0.6.1.

- I am using the LATEST versions of all the mods I have installed.

 

I tried looking for a solution, but couldn't find anyone with quite the same problem.

 

Please HELP!!!
 
Thank you!
 

Update.esm
Unofficial Skyrim Patch.esp
ApachiiHair.esm
HighResTexturePack01.esp
HighResTexturePack02.esp
HighResTexturePack03.esp
Unofficial High Resolution Patch.esp
AMatterOfTime.esp
RaceMenu.esp
FNISSexyMove.esp
AlynShirArmor.esp
RaceMenuPlugin.esp
Guard Dialogue Overhaul.esp
dD - Realistic Ragdoll Force - Realistic.esp
RaceMenuPluginXPMSE.esp
Merta Assassin Tattoos.esp
Realistic Lighting Overhaul - Minor Cities and Town Interiors.esp
Realistic Lighting Overhaul - Major City Exteriors.esp
LayerBikini.esp
AzarHairPonyTail 03 - Havok.esp
RaceMenuMorphsCBBE.esp
Realistic Lighting Overhaul - Major City Interiors.esp
Realistic Lighting Overhaul - Dungeons.esp
Run For Your Lives.esp
UFO - Ultimate Follower Overhaul.esp
BlackSacramentArmor.esp
Insanity's Sorrow.esp
TheEyesOfBeauty.esp
SOSRaceMenu.esp
SkyUI.esp
Dual Sheath Redux.esp
The Dance of Death.esp
Dual Sheath Redux Patch.esp

[Gameplayer]

I wouldn't worry about that load order it looks fine.  If you put more mods on there your going to need Wyrebash and TesVedit to make patches.

 

Now your reason for crashing is likely quite a few combined problems.

 

 

Problem 1

 

Quickload and Quicksave have been a known issue for a long time, any search inquiry should yield quite a few reasons as for why you should forget that those features exist.

AutoSaves come in a close second.

 

These features can and have been known to lead to unloadable saves aka Corrupted Saves, and the game will even prompt you that your save is corrupted.

 

Problem 2

 

You likely have been putting in mods and taking them out while playing the game without even following what is commonly referred to as a safe uninstallation.  No Im not going to cover the steps they get lengthy.

The other thing to note is the usage of a Save Game Cleaner is quite popular, for removal of orphan scripts which are or were scripts that belonged to your former mods you removed.

 

Conclusion

 

This has led to a popular saying that one should not remove or add files mid game.  Though it is good advice for new comers its not exactly true when they claim it'll ruin your game.

 

Another idealogy spreading around is that somehow one infected save can infect another not true >< stupidly not true.

 

--------------------

 

A good method to practice for newcomers is simply if your going to add a mod to your game make sure you know which save you plan on reverting back to when it doesn't pan out.

Also its a damn fine idea to play with the mod right away because your going to have a better idea of what your getting into some call this testing.  For a good reason to cause a lot of mods wont pan out or you decide I don't like it.

 

 

[Serenity_XXI]

I wouldn't worry about that load order it looks fine.  If you put more mods on there your going to need Wyrebash and TesVedit to make patches.

 

Now your reason for crashing is likely quite a few combined problems.

 

 

Problem 1

 

Quickload and Quicksave have been a known issue for a long time, any search inquiry should yield quite a few reasons as for why you should forget that those features exist.

AutoSaves come in a close second.

 

These features can and have been known to lead to unloadable saves aka Corrupted Saves, and the game will even prompt you that your save is corrupted.

 

Problem 2

 

You likely have been putting in mods and taking them out while playing the game without even following what is commonly referred to as a safe uninstallation.  No Im not going to cover the steps they get lengthy.

The other thing to note is the usage of a Save Game Cleaner is quite popular, for removal of orphan scripts which are or were scripts that belonged to your former mods you removed.

 

Conclusion

 

This has led to a popular saying that one should not remove or add files mid game.  Though it is good advice for new comers its not exactly true when they claim it'll ruin your game.

 

Another idealogy spreading around is that somehow one infected save can infect another not true >< stupidly not true.

 

--------------------

 

A good method to practice for newcomers is simply if your going to add a mod to your game make sure you know which save you plan on reverting back to when it doesn't pan out.

Also its a damn fine idea to play with the mod right away because your going to have a better idea of what your getting into some call this testing.  For a good reason to cause a lot of mods wont pan out or you decide I don't like it.

Thank you for taking the time to reply!

 

Few notes:

- This is a fresh install from 2 days ago, and I did not take out any mods mid-gameplay.

- I already used Save Game Cleaner (version 2.04 beta), and it found no orphan scripts.

- As previously mentioned, the save files are not being corrupted by quicksave/autosave, since they work fine after restarting the game.

- I had never previously experienced this issue of CTD's *specifically* upon using Quickload (and I've had this game since it came out).

- CTD's in general sure, and due to different events. But having a CTD *consistently* on Quickload, when there is no corruption with the save itself, never.

 

Hope that cleared things up a bit about my problem!

 

Question:

Is there some sort of error log/dump file that specifies crash reasons on CTD's?

 

Thanks!!

[Effie]

I used to get CTDs on only fast travel or quicksave, when my skyrim was too heavy for my computer. Have you remembered skse's memory patch? What about the enbboost thing?

I haven't gotten a single ctd on anything for months now, and that's because i've made sure to keep my games memory as low as possible, by not using script-heavy mods, texture heavy stuff etc etc

[Gameplayer]

I've actually never been able to start a game in Helgen.

 

Not with HDT, stuff...  HDT and I think even some bbp or was TBBP can cause the Cart to fly off and weirdness ( or is that way old news been patched...)

 

Actually I'm having to remember stuff that I had basically forgotten but....

 

Helgen is very sensitive to mods and I'm thinking if that's where the ctd's crop up?

 

It'd been more helpful to know where your character is in the game world and the level.

 

But since your saying its a new game.

 

How about trying Live Another Life, plus patch it up with a Bash but double check that Patch in Tes just something I do to ensure I got the changes I wanted.

[sidfu]

I wouldn't worry about that load order it looks fine.  If you put more mods on there your going to need Wyrebash and TesVedit to make patches.

 

Now your reason for crashing is likely quite a few combined problems.

 

 

Problem 1

 

Quickload and Quicksave have been a known issue for a long time, any search inquiry should yield quite a few reasons as for why you should forget that those features exist.

AutoSaves come in a close second.

 

These features can and have been known to lead to unloadable saves aka Corrupted Saves, and the game will even prompt you that your save is corrupted.

 

Problem 2

 

You likely have been putting in mods and taking them out while playing the game without even following what is commonly referred to as a safe uninstallation.  No Im not going to cover the steps they get lengthy.

The other thing to note is the usage of a Save Game Cleaner is quite popular, for removal of orphan scripts which are or were scripts that belonged to your former mods you removed.

 

Conclusion

 

This has led to a popular saying that one should not remove or add files mid game.  Though it is good advice for new comers its not exactly true when they claim it'll ruin your game.

 

Another idealogy spreading around is that somehow one infected save can infect another not true >< stupidly not true.

 

--------------------

 

A good method to practice for newcomers is simply if your going to add a mod to your game make sure you know which save you plan on reverting back to when it doesn't pan out.

Also its a damn fine idea to play with the mod right away because your going to have a better idea of what your getting into some call this testing.  For a good reason to cause a lot of mods wont pan out or you decide I don't like it.

 

all thats tru but for the idea about other saves not getting infected.ive had it happen. a good exmple is a few restarts ago was looking to decide which preg mod to use so on was starting new gaems left and right. i installed the old hentai preg mod and worked to give a belly but it wouldnt reset the bely so i loaded a save before they even got preg they still had belly. so next exited game and then loaded teh save before preg they still had belly.

its a weird issue ive had a few times. i just think its skse getting log jamed at times luckly ive only had it happen 3 times and normaly exiting out and going back farther in saves fixes it.

 

 

[Oter]

Just had the exact same problem, I found the new skeleton to be the problem.

 

the 2.70+ versions caused me to crash on load so tried 2.50 and that worked

 

TRY it!