Jump to content

CTDing everywhere in the Kilkreath Temple


Glitchiie

Recommended Posts

Hi, sorry for a bother - (and sorry if this is supposed to be in Mod Support)

I'm super dumb with mods or anything, I promise, but this all seems kinda out of my reach now. I started doing The Break of Dawn on my 100+ hour save and... now I'm trapped in the Kilkreath Ruins, unable to get out because no matter where I go Skyrim decides to CTD.

I run a lot of mods, but they're all cleaned (even the manual ones!) and I'm not sure what else I can do at this point beyond coc'ing to Whiterun, setting the quest done, and giving myself Dawnbreaker.

 

CTD started happening ONLY after hitting the third beacon in the first part of the temple ("Ruins"), and no matter where I go it just CTDs. I've never had consistent CTD before now.

What I've tried: sneak-rolling through the entire thing, running through the entire thing, ignoring the extra chest you can get before the next area and running through, coc'ing myself into the next area (also CTDs, which means I'm gonna get this all over the temple), updating LOOT and checking for updates, trying to use a crash logger (it legitimately wouldn't work for me for some reason).

I've not installed anything like the SSE Engine Fixes mod or anything, due to fear of installing -anything- mid-playthrough. (It ruined my last save...)

 

https://modwat.ch/u/Sataesim

This is my mod list + ini + prefs, and I use Vortex for the record. If there's anything else needed, please just let me know! I just wanna know what's causing it, even if I do end up having to abuse the console.

 

EDIT/UPDATE: Skyrim is CTDing everywhere on that save; did a coc Whiterun just to see what would happen. Reloaded a previous save before ever entering the ruins, and no CTDs even in the ruins. I'm still wondering what happened, because what in the name of god about the Kilkreath ruins would do that to a save?

Edited by Glitchiie
Link to comment
Share on other sites

  • 2 weeks later...

We're guessing that specific save is corrupted.

 

That save likely cannot be reused. What has worked for us is to start the Temple again from outside, and then at each key decision in the Temple, make a hard-save to maintain your progress.

 

Lots of events can corrupt saves: if you're on pc, your windows security may try to update, and interfere with Skyrim. Using the console at any time in gameplay, and then saving a game after using the console, can create corrupted saves.

 

Using autosave or the function key to quick save can corrupt a save beyond re-playability. WE disable autosave, and delete all autosaved files after we've finished quests.

 

Conflicting textures and meshes within the cell can corrupt a save, for example, if any of the mods in your list alter the interior pf Kilkreath Temple in any way and conflict with other mods that may also do so.

 

We don't remember the name of it, but there is a papyrus or SSE mod that makes a log after a CTD, so you can open and examine it and find out what is triggering the crash. Perhaps it is the SSE Engine fixes that does this log keeping.

 

Perhaps try the following: add the SSE Engine fixes to your mod list, enable it. Next load a save that you know still works without a CTD. While in game, open the menu and now load the suspect save, and see if you can play the Temple through. If you CTD, look at the log, and bring the details to the Forum?

 

Good luck!

Link to comment
Share on other sites

  • Recently Browsing   0 members

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