Jump to content

Need help, Getting CTD whenever I load a game once IN the game.


venombeyond

Recommended Posts

So I've recently started playing again. Things were fine, then I noticed that once out in the world, in most areas, once I load up a game from a quicksave, an autosave or loading on dying. My game instantly Crashed to Desktop. I load into the game fine, and can run around and do things just fine, and in SOME areas, loading up a save doesn't crash me. Places like the entrance to Riverwood, and some interior places are OK, but more often than not I'm met with a CTD if I'm killed in combat outside, or quickly load up a save from quicksave or autosave that I just had happen a few moments prior. Any help would be appreciated.

 

This is my load order and all my mods (Please don't judge some of the more lewd ones)

GameMode=SkyrimSE
Skyrim.esm=1
Update.esm=1
Dawnguard.esm=1
HearthFires.esm=1
Dragonborn.esm=1
Unofficial Skyrim Special Edition Patch.esp=1
Schlongs of Skyrim - Core.esm=1
RaceCompatibility.esm=1
Snow_Elf_Race.esm=1
ApachiiHairMales.esm=1
SGHairPackBase.esm=1
SkyUI_SE.esp=1
Dolomite Weathers.esp=1
Circlets and Masks with all Robes and Hoods.esp=1
Hothtrooper44_Armor_Ecksstra.esp=1
Hothtrooper44_ArmorCompilation.esp=1
SMIM-SE-Merged-All.esp=1
Skyrim Flora Overhaul.esp=1
Verdant - A Skyrim Grass Plugin SSE Version.esp=1
dD - Enhanced Blood Main.esp=1
dD-Larger Splatter Size.esp=1
Joy of Perspective.esp=1
Skyrim Immersive Creatures Special Edition.esp=1
skyBirds_SSE.esp=1
1 Day Respawn.esp=1
Alex's Guardian Stones Overhaul.esp=1
Immersive Weapons.esp=1
Schlongs of Skyrim.esp=1
Phenderix Magic Evolved.esp=1
TheAmazingWorldOfBikiniArmor.esp=1
SOS - Shop.esp=1
VisualAnimatedEnchants.esp=1
CraftingSupplies_AIO_ALL.esp=1
R18pn - lingerie Set.esp=1
Apocalypse - Magic of Skyrim.esp=1
Apocalypse - Waterstride Spell Addon.esp=1
UIExtensions.esp=1
AddItemMenuSE.esp=1
OnsonWeighlessIngredients.esp=1
BetterMasterSpells.esp=1
CarryWeight x25.esp=1
Apocalypse - Cheat Chests.esp=1
ChooseYourSign.esp=1
FNIS.esp=1
SOS - VectorPlexus Regular Addon.esp=1
Better Vampires.esp=1
RaceCompatibilityUSKPOverride.esp=1
CBBE.esp=1
RaceMenuMorphsCBBE.esp=1
VioLens SE.esp=1
Skyrim Unlimited Rings And Amulets SSE.esp=1
SetYourSkills.esp=1
RichMerchantsSkyrim_x10.esp=1
InigoPerkPointGiver.esp=1
KillCam Invulnerability.esp=1
Dragon Spawn 24 hours.esp=1
EBT - skyBirds Patch.esp=1
Full Magic Scaling.esp=1
LrsamwaysExpandedSkyrimWeaponry.esp=1
Aasimar Race.esp=1
Snow_Elf_Reprise_Castable.esp=1
Snow_Elf_Followers.esp=1
The Chiss.esp=1
EBT - IC PATCH.esp=1
JoP - Immersive Armors Patch.esp=1
SOSRaceMenu.esp=1
DSHg - Hats.esp=1
DSHg - Helmets.esp=1
DSHg - Hoods.esp=1
DSHg - UpdateDB.esp=1
DSHg - UpdateDG.esp=1
Nightingale_Armor_DaedricImprovable.esp=1
KS Hairdo's.esp=1
Gelebor_and_Vyrthur.esp=1
SGHairPackAIO.esp=1
LongerTradeSkillsbartercarrypotions.esp=1
EnchantAndSmithingPotionDuration_dlc.esp=1
OnsonWIDawnGuard.esp=1
OnsonDragonbornWI.esp=1
SGEyebrows.esp=1
TAWoBA - JOP Patch.esp=1
icepenguinworldmapclassic.esp=1
AIO SE TATTOOS.esp=1
AHZmoreHUD.esp=1
Fgem's Female Orcs.esp=1
Orcs are Strong.esp=1
Player Size Adjuster.esp=1
Whistle.esp=1
MOD - Simply Better Horses (SSE).esp=1
Customizable Camera.esp=1
Slow and Freeze Time Spells -TwinCrows.esp=1
pickpocket100.esp=1
MultipleEnchants6.esp=1
Nightingale Enchantments Redone.esp=1
The Jarl Stone 50.esp=1
Unlimited Shouting.esp=1
Unlimited Sprinting.esp=1
RaceMenu.esp=1
XPMSE.esp=1
RaceMenuPlugin.esp=1
Alternate Start - Live Another Life.esp=1
ChooseYourSign_LAL.esp=1
RealisticWaterTwo.esp=1
RealisticWaterTwo - Waves.esp=1
Modern Brawl Bug Fix.esp=1
Again, if anyone can help I'd really appreciate it. Even if I have to get rid of some mods I'm not thinking about, I'll do so, but this is getting out of hand, and I don't want to lose them all.
Link to comment
Share on other sites

Autosave and Quicksave have been an issue since day one. The problem is: the game doesn't pause when one of those two saves are initiated, which sometimes results in corrupted saves as there are half-finished scripts firing in the background when the save is being made. The common solution is to simply disable autosaves and try to remember to manually make "hard" saves (by going into the game menu and clicking "Save") on your own. The problem with that is, most of us get too wrapped up in playing to remember. There were a couple of mods for LE that automated this for you, I've never looked to see if there are any good ones for SSE, but it's something to look into.

Link to comment
Share on other sites

Autosave and Quicksave have been an issue since day one. The problem is: the game doesn't pause when one of those two saves are initiated, which sometimes results in corrupted saves as there are half-finished scripts firing in the background when the save is being made. The common solution is to simply disable autosaves and try to remember to manually make "hard" saves (by going into the game menu and clicking "Save") on your own. The problem with that is, most of us get too wrapped up in playing to remember. There were a couple of mods for LE that automated this for you, I've never looked to see if there are any good ones for SSE, but it's something to look into.

 

It was happening with ANY save type, even hard ones, I should have mentioned that. However I some how stumbled upon and fixed the issue. It was something to do with one of the animation styles I had chosen with XM32. I discovered this by mistake, when I realized I didn't even like the "First person weapon draw" animations, and redid it. All of the crashing just vanished.

 

I tried to reinstall Open Cities but the crashing began once more so, since not having that in either, all crashing has stopped. This is how I solved it for myself, hopefully anyone having issues like mine can go in and double check their XM32 Animations.

Link to comment
Share on other sites

Autosave and Quicksave have been an issue since day one. The problem is: the game doesn't pause when one of those two saves are initiated, which sometimes results in corrupted saves as there are half-finished scripts firing in the background when the save is being made.

This is not true and never has been. Autosave, quicksave, manual saves, and even console initiated saves all run through the exact same code path on the way to writing the file. All of them stop the Papyrus VM before the file is written to disk. You can easily verify this as the game is running. Hit F5, then go look at the Papyrus log for the current session. You should see the "VM Frozen" message.

 

There has never been a valid case of any form of save corrupting from normal use. If this is happening to you, either your operating system is broken (not bloody likely) or you have a bad drive. Actual file saving in all of Bethesda's games uses standard Windows IO functions. Just like every other game out there.

Link to comment
Share on other sites

The only way with a chance to solve this, is to disable the installed mods in the mod manager and than try to continue the game. It must be a mesh or script conflict issue, which is causing the CTDs. So you must not disable texture mods or "safe mods" as unofficial skyrim patch. I recommend in your case that you start to disable mods in 25 mod steps.

If that doesn't help, the bad news bear has bad news for you: http://www.iamhoneydill.com/new-stuff/2017/4/30/percival-the-bad-news-bear

 

Prepare to start a new game and not with the same mods installed again, because your personal modded version of skyrim is not 100% running correct.

 

Edit:
You could also try to load an older savegame and see if the CTDs still happen. If you are lucky, it's just a corrupt savegame. Maybe due to deinstalling scripted mods during gameplay.

Edited by COMBATFUN
Link to comment
Share on other sites

Disabling mods on an active save is a sure way to fry it. So don't do that.

Link to comment
Share on other sites

 

Autosave and Quicksave have been an issue since day one. The problem is: the game doesn't pause when one of those two saves are initiated, which sometimes results in corrupted saves as there are half-finished scripts firing in the background when the save is being made.

This is not true and never has been. Autosave, quicksave, manual saves, and even console initiated saves all run through the exact same code path on the way to writing the file. All of them stop the Papyrus VM before the file is written to disk. You can easily verify this as the game is running. Hit F5, then go look at the Papyrus log for the current session. You should see the "VM Frozen" message.

 

There has never been a valid case of any form of save corrupting from normal use. If this is happening to you, either your operating system is broken (not bloody likely) or you have a bad drive. Actual file saving in all of Bethesda's games uses standard Windows IO functions. Just like every other game out there.

 

 

Thank you for that explanation.

 

I had always been under the impression that Autosaves, and quicksaves were inherently unstable.

 

One reason I enjoy reading forum posts is that I can learn about the game even if the post has no direct bearing on my game.

Link to comment
Share on other sites

By disabling (actually uninstalling is better) and then testing against a new save that's never had the mod loaded. If all you do is test by disabling mods on an existing save you're never going to find the problem and your save will be toast.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...