CTD almost immediately on loading save files

[Waggish]

Just what it says in the header. I'll start a new game and have zero issues so I'll calibrate my mods and things will run fine with no detectable issues, but the instant I save and quit and then go to reload the game I get an immediate CTD as soon as I pick a save file.

 

There will have been no changes to mods in between, nothing removed, added, or updated. I'll just run SKSE through MO2 and it launches fine with the main menu coming up without issue or long load times but the instant I go to Continue or Load and selecting a file (even ones with, again, no mod changes from what's current in MO2) I get a half second of seeing whatever model they're showing for the loading screen along with the level/experience bar and then CTD almost as soon as these register. Interestingly, quitting to main menu from one of those aforementioned new games also causes a CTD with a shorter crash log.

 

I've tried plugging both logs into phostwood with no luck, it's telling me "No highest-confidence crash indicators detected" and nothing stands out. The first attachment with "load" at the end is the loading the save issue that's my biggest problem (as I don't actually mind if I need to boot the game again instead of going to the main menu) while the second is the main menu CTD issue. I'm mostly just including the second for another reference point as they're resulting in the same issue so it may provide information I'm unable to pick out myself.

 

Thanks in advance for anyone that weighs in.

crash-2025-06-25-01-46-00 load.log crash-2025-06-25-02-08-56 main menu.log

[traison]

Both of these look like they could've come from Papyrus. Post your Papyrus log.

[Waggish]

2 hours ago, traison said:

Both of these look like they could've come from Papyrus. Post your Papyrus log.

 

Thanks for replying and oh, yikes, that's a lot of warnings and errors. I admit I'm pretty new to modding so I didn't even think to check that. (Or know how until two minutes ago.) Not sure why it's missing so much though, I always did my best to make sure I got all my requirements taken care of when choosing new mods.

Papyrus.0.log

[traison]

Yeah those 3000 missing scripts and properties is most likely the source of your problem.

 

37 minutes ago, Waggish said:

Not sure why it's missing so much though...

 

Start a new game, let the game sit for a minute or 2, quit and check the most recent log. If you don't have an alternate start mod, then issue the "coc qasmoke" command from the main menu. Use this new log as a reference when fixing issues.

 

37 minutes ago, Waggish said:

...I always did my best to make sure I got all my requirements taken care of when choosing new mods.

 

There's several reasons for errors like these:

1. Badly made mods. References to removed properties and scripts got left behind after a refactoring. The mod providing sic_orespawner seems like it might fit in this category.
2. Mods containing scripts removed during an active playthrough.
3. Missing dependencies. In your case XPMSE seems to be unhappy with FNIS_aa. You're probably using Pandor, which is for some reason missing the FNIS scripts. You can also install XPMSE such that it doesn't use FNIS (this is an FOMOD option).
4. Mods overwriting other mods. SL P+ is quite popular in this category.

Edited June 25, 2025 by traison