Sexlab Kidnapped Redux SE event after ctd

[naber88]

Hi everyone, I installed the Sexlab Kidnapped Redux SE mod, then I installed and overwrote the fix 22 mod from this thread: https://www.loverslab.com/topic/133759-bugfixes-for-various-mods-sexistguards-sl-kidnapped-redux/page/3/#comment-2995054. The mod works, the MCM menu and everything appears, but after being kidnapped and rescued, when I try to save and load it, the game crashes. I'm sharing my Papyrus and crash logs. I hope someone sees my message and helps me.

 

I'm playing Skyrim SE version 1.5.97.

Papyrus.0.log crash-2026-08-10-03-43-29.log

[traison]

The crash was caused by Papyrus. You have over 600 errors about missing scripts and script properties. You also have something that's preventing it from freezing propetly, causing it to dump its thread stacks into the log. Fix your Papyrus situation and you can play again.

 

Other issues:

1. Your installation directory is not a valid Steam library. The game was moved manually.
2. The exe has been modified, its checksum does not match a clean 1.5.97.0.
3. You ran the game with elevated privileges which is a HORRIBLE idea, especially when you're running mods with dlls.

[naber88]

Thanks for taking the time to look at my crash log. I understand that I have a lot of Papyrus errors, but I’m not sure how to properly clean up my Papyrus situation.

Could you explain what I should do to fix these errors? Do I need to uninstall/reinstall certain mods, clean my save, or is there a specific way to identify which mods are causing the missing scripts and script property errors?

I don’t want to start removing hundreds of mods randomly and make my save even worse. If possible, could you give me a step-by-step explanation of how I should troubleshoot and clean up the Papyrus errors?

Also, should I do this on my current save, or should I start from an earlier save before the Kidnapped Redux event?

[Dorabella]

57 minutes ago, naber88 said:

or should I start from an earlier save before the Kidnapped Redux event

A new game is always better . 

[traison]

56 minutes ago, naber88 said:

Could you explain what I should do to fix these errors?

 

There's a paper on that subject in my signature.

 

58 minutes ago, naber88 said:

...should I do this on my current save...

 

You fix whichever save has issues. Keep in mind that scripts get embedded in the save, and that not all scripts are running at all times. Even if you fix everything now does not mean it won't be a mess again 25 hours into a playthrough.

 

1 hour ago, naber88 said:

...how I should troubleshoot and clean up the Papyrus errors?

 

Start by picking out easy or common problems from the log. Fix them. Start a new game, do your testing then review the new Papyrus log and repeat until you're satisfied with the number of errors you're getting. I personally didn't bother fixing the errors in the Bethesda CC content, so those are still broken (like CC Pets) but since I don't use them it's whatever. They're not broken in a way that negatively affects the Papyrus engine.

[naber88]

 

Would starting a new game be enough to guarantee that I have a clean Papyrus state? I really don’t want to go through the process of fixing all those Papyrus errors manually.

[traison]

1 hour ago, naber88 said:

Would starting a new game be enough to guarantee that I have a clean Papyrus state?

 

Depends on when the damage was made. If you uninstalled mods mid-playthrough then starting a new playthrough will get rid of the missing script errors. Missing properties are basically always scripting errors by the mod author or incompatible mod patches; these won't go away on their own.

 

If you only want to get rid of the CTD then it might be enough to use ReSaver to identify which scripts are preventing the Papyrus engine from freezing and fixing these. Then you can most likely continue playing with otherwise broken or at least partially broken mods, but no immediate CTD. See section 5.5 of my paper.