Crash logs. What are they, and how to read it them, a real question

[Mancuerna]

Hello friends, companions, and colleagues. I have another problem, and I would like to ask for your help. It seems the latest Skyrim update has created some problems with the mods. I downgraded my version of Skyrim to match the mods, and it's been going well, but lately I have been having a problem that's causing my game to crash. At first, I tried a few crash loggers, removing mods, and starting a new save, but none of it worked. I tried reinstalling the game and starting from scratch, but I still have the same problem. At this point, I was hoping any of you friends would know more about this than I do and could lend me a hand if you're feeling kind. I would really appreciate it if you did, or at least guided me through this process. I thank you all for taking the time to read this message

crash-2026-08-30-01-07-15.log

[flutie]

 

 

[traison]

This crash occured in SKEE (RaceMenu). There's a null pointer somewhere, as it tried to dereference RAX at a time when it was 0x0. It's having issues with an IFileStream interface (presumably) which had something to do with an SKEEFixedString most likely representing "OBody". This interface/string had something to do with reference id 0x0D0D1096 "Bard" in form id 0x01002FD1 "Bloodchill Cavern". Reference id 0x14 "Chen" was also involved.

 

Note that something appears to have gone wrong in the stack unwinding, since for example the callstack entry OverlayFix.dll+0008AC3 is not visible in the stack. The interface and SKEEFixedString information is probably reliable but the rest I don't know about.

 

Since OBody is a mod that's doing things it shouldn't be doing, I would start by removing that and testing again.

Edited August 30 by traison

[Mancuerna]

7 hours ago, traison said:

This crash occured in SKEE (RaceMenu). There's a null pointer somewhere, as it tried to dereference RAX at a time when it was 0x0. It's having issues with an IFileStream interface (presumably) which had something to do with an SKEEFixedString most likely representing "OBody". This interface/string had something to do with reference id 0x0D0D1096 "Bard" in form id 0x01002FD1 "Bloodchill Cavern". Reference id 0x14 "Chen" was also involved.

 

Note that something appears to have gone wrong in the stack unwinding, since for example the callstack entry OverlayFix.dll+0008AC3 is not visible in the stack. The interface and SKEEFixedString information is probably reliable but the rest I don't know about.

 

Since OBody is a mod that's doing things it shouldn't be doing, I would start by removing that and testing again.

I have tried taking Obody from my mod list, but it still crashed. I'm still reading through it, but I can't find the culprit. I would appreciate it if you could still help me, friend

crash-2026-08-30-12-41-42.log

[traison]

13 minutes ago, Mancuerna said:

I have tried taking Obody from my mod list, but it still crashed. I'm still reading through it, but I can't find the culprit. I would appreciate it if you could still help me, friend

 

The Obody string is still there. It's coming from somewhere else.

 

If this crash is occuring while loading a saved game the issue is probably in the SKSE cosave.

[Mancuerna]

9 minutes ago, traison said:

 

The Obody string is still there. It's coming from somewhere else.

 

If this crash is occuring while loading a saved game the issue is probably in the SKSE cosave.

Then should I try to make a game without it? See if it works? Thanks. I will try, and if it crashes, I will update this message

[traison]

2 hours ago, Mancuerna said:

Then should I try to make a game without it? See if it works? Thanks. I will try, and if it crashes, I will update this message

 

Personally I would use my string search utility to run through all files in Skyrim looking for "OBody". Once the mods that it finds have been disabled and it's still crashing I would temporarily nuke the cosave to see if the problem goes away. If the problem goes away with the cosave and you want to attempt to rescue the save, there's instructions and hacked dlls here for skipping loading of the SKEE chunk.

 

The string search utility is available on request. I assume you're going to want it so I'll send you the link in a minute.

 

Edit: Fixed letter casing for search term.

 

 

Edited August 30 by traison

[Mancuerna]

On 8/30/2026 at 1:44 PM, traison said:

 

Personally I would use my string search utility to run through all files in Skyrim looking for "OBody". Once the mods that it finds have been disabled and it's still crashing I would temporarily nuke the cosave to see if the problem goes away. If the problem goes away with the cosave and you want to attempt to rescue the save, there's instructions and hacked dlls here for skipping loading of the SKEE chunk.

 

The string search utility is available on request. I assume you're going to want it so I'll send you the link in a minute.

 

Edit: Fixed letter casing for search term.

 

 

crash-2026-09-07-02-02-09.log

Edited September 7 by Mancuerna

[traison]

That latest crash was most likely caused by Papyrus. There's a paper on reading them in my signature; section 6.1 probably being the most relevant.

[Mancuerna]

Papyrus.0.log Understood, I attach the Papyrus Log

[traison]

18 minutes ago, Mancuerna said:

Papyrus.0.log Understood, I attach the Papyrus Log

 

• You have over 400 errors about missing scripts and script properties. These should be cleaned up before you do any serious playthroughs.
• BWAroused looks broken.
• CV_RichterScript is trying to apply expressions to something that does not have face expression morphs.
• mmearmorscript looks broken.
• _AhegaoAlias looks broken.

There does not appear to be any stack dumps in this Papyrus log so either this log is not from a session that crashed, or it crashed while trying to dump the first context. Stack dumps from Papyrus occur when scripts do not stop when asked to. ReSaver can be used to inspect Papyrus threads - use a save that's close to when the crash happens (for instance a save that you can load but not save again).

[Mancuerna]

Ok, I have both Papyrus logs: one from before the crash and one from after. If nothing can be done, I understand.Papyrus.BEFORE.log Papyrus.AFTER.logg

Papyrus.BEFORE.log

[ThePostalDude22]

Hi, I had a series of crashes with similar error definitions for unhandled exceptions and was able to resolve most, if not all by using the script in xEdit to "undelete and disable reference" for my modlist. And don't forget to clean your Bethesda files after every update with xEdit.

I use Obody, too, and tought it would introduce more problems, but it works really well with SL, Ostim, FHU, DD, Softbody, Soulgem Oven and so on (mods manipulating body parts).

 

If you happen to have the mod "StepUpOnto SKSE", try to deactivate it for testing. It crashed my game too, but that was a few mod updates ago.

 

Edit:
sometimes useful to analyse your log, sometimes not, but for your log there may be some important steps to follow (RAM advice, BIOS settings)
https://phostwood.github.io/crash-analyzer/skyrim.html?tryFormIDs

Edited September 9 by ThePostalDude22

[traison]

On 9/9/2026 at 11:53 PM, ThePostalDude22 said:

I had a series of crashes with similar error definitions for unhandled exceptions...

 

"Similar" means absolutely nothing unfortunately. If the exception offset and image version are identical you have the same bug. If you have the same bug but the callstack is different then you have a different problem. For instance, 2 players might be crashing because of the same bug in a string length measuring function, but one is crashing because they're wearing a hat with a corrupted editor id string and the other because of a malformed language file in an MCM menu. If the image version or exception offset is different, you're crashing because of a completely different bug.

 

If similar was enough, you could say every Skyrim crash in the past 15 years was caused by the same bug: they all had error code 5, and each was about reading or writing memory.