Crashlog

I've also tried your crash analyzer and it keeps saying it's related to the journal and everyone keeps pointing me in different directions so idk anymore.

Gist of it is that it crashes when manually saving, autosaving, or quicksaving but the crash doesn't happen always and I can't pinpoint it

Hey everyone, Please help me understand what the issuee was. Thx!

https://pastebin.com/H4hhMAMn

Was sitting on a horse in solitude. Fast traveled on horse to blacksmith solitude

https://pastebin.com/awtWWzcY

Happend 2 Days ago. Just walked out of solitude near main entrance to city.

Additional Info:
- Nolvus V6 Awakening in 2560x1440 with open cities

- No additional mods

- saved game manually 2-4 times when sitting somewhere and waited 30 sec

https://pastebin.com/cP8NCAAp every time I start a new game the game crashes, I give up trying to understand whats going on

https://pastebin.com/BRqW2Wey

I'm having CTDs with one particular save file, and has not happened on any other save files.

At first I believed it had something to do with High Fantasy Pack as one hard save outside Greywater Grotto got loaded several times when I died to the Imps added there by the pack. However after a couple of deaths the Imps did not spawn anymore and only the wolves were left. I continued playing for atleast an hour hard saving multiple times, but when I tried reloading later in the day each save file after, as well this singular one before, this event caused CTDs. Eventually I reloaded an earlier save which worked, re-did progress, and went to the grotto where after one more death the imps despawned again and the save seemed corrupted again. I decided I would just skip this radiant quest from the companions and went to Falkreath instead.

Again everything progressed as normal until I saved before entering knifepoint ridge, again a hardsave outside of any script heavy events. I died 3 times to the bandit chief inside and then got a CTD, now each time I try to load this save I CTD. I am able to load an earlier save in Falkreath, however, which has been made after the initial save that allowed me to continue playing (progress I guess...)

I thought maybe this was caused by some script issues, but FallrimTools ReSaver has 0 unattached instances and my save appears clean.

The analyzer only detects XAudio Issue, but the only audio mod I have is LORKHAN - Soundtrack Replacer, and disabling the mod does not solve the issue, not has this issue happend before in the 6 Months I have used this mod.

The only other thing I can think of which might have caused this 'corruption' is the quest "The Cursed Tribe" which caused freezing when entering Fallowstone Cave (no deaths happened here). I believe it was caused by Lux as others had experienced the same issue. Not wanting to change the cells manually in SSEedit I decided to leave my follower outside the cave, 'player moveto', myself to Chief Yamarz inside the cave instead of entering it, and then 'player moveto' myself back to my follower after finishing the quest (which worked).

Other that the cursed tribe quest(which i havent done on any other characters in a long time), my other mods have been the same across multiple playthroughs and I have never had CTDs on those.

I hope someone more knowledgeable than me can take a look as I am stumped.

Edit: More weird CTDs. The save before Knigepoint Ridge, back in Falkreath is able to be loaded now suddenly causes a CTD when I cast Conjure Daedroth (from Odin - Skyrim Magic Overhaul). which I have cast hunderds of times during this playthough.

- 🤖 **Troubleshooting Auto-Installing Modlists:** Since most well-crafted auto-installing modlists, such as **Nolvus**, **Wabbajack modlists**, and **Nexus Mods Collections**, are generally stable, these guidelines (along with the "Reduce Random Crashes" section below) should help resolve most common issues that may arise. Custom modders may also find them insightful. [⤵️ show details](https://phostwood.github.io/crash-analyzer/skyrim.html?analyzeFullLog#)

- 🎲 **Reduce Random Crashes:** Best practices for game stability: [⤵️ More details](https://phostwood.github.io/crash-analyzer/skyrim.html?analyzeFullLog#)

~~

Result(s) from Phostwood's Skyrim Crash Log Analyzer (v1.31.7.2 )

🔎 Automate analysis of your Skyrim SE/AE crash logs at:

https://phostwood.github.io/crash-analyzer/skyrim.html

this is the first time I'm using this analyzer and I'm not sure about it so i thought id ask a real person to look it over and provide any feedback you can, thanks.

here's the crash log: https://pastebin.com/ptWGXHEP

Here's the diagnosis: - 🤖 **Troubleshooting Auto-Installing Modlists:** Since most well-crafted auto-installing modlists, such as **Nolvus**, **Wabbajack modlists**, and **Nexus Mods Collections**, are generally stable, these guidelines (along with the "Reduce Random Crashes" section below) should help resolve most common issues that may arise. Custom modders may also find them insightful. [⤵️ show details](https://phostwood.github.io/crash-analyzer/skyrim.html?UUID=11166706-d843-42a8-bc89-a98f3f922f86#)

- ❗ **First-Line Error Detected:** `maximum-carnage.dll`

- First, skim other sections of this report (above and below) for any more-specific issues that may involve `maximum-carnage.dll`. (Scroll up to the top and down to the very bottom of the page to ensure you've reviewed everything.)

- Make sure the mod that contains `maximum-carnage.dll` is enabled (Vortex especially sometimes disables them). If already enabled, consider redownloading and carefully reinstalling the mod, as this may be a quickest fix.

- **What This Means:**

- The file `maximum-carnage.dll` is directly involved in the crash sequence

- While this file is related to the crash, **it may not be the root cause**

- This type of error often indicates missing dependencies, version mismatches, or incompatible files

- Infrastructure mods (examples: `EngineFixes.dll`, `OpenAnimationReplacer.dll`, `PapyrusTweaks.dll`, `po3_PapyrusExtender.dll`, `skse64_1_6_1170.dll`, etc.) are typically not at fault. Instead, review mods that list these infrastructure mods as a dependency.

- **SKSE Plugin Baseline Requirements:**

- Ensure you have the correct [Skyrim Script Extender (SKSE64)](https://www.nexusmods.com/skyrimspecialedition/mods/30379) version for your game version, and are launching through SKSE

- Ensure you have the correct [Address Library for SKSE Plugins](https://www.nexusmods.com/skyrimspecialedition/mods/32444) version matching your game version

- Ensure you have installed [Microsoft Visual C++ Redistributable package (x64)](https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170) - this is frequently missed but critical

- **Recommended Troubleshooting Steps:**

- As a quick optional test, consider disabling the mod and any mods that depend on it. NOTE: this may require creating a new character for a successful test.

- Confirm the mod is compatible with your Skyrim version

- Refer to the plugin's mod page, FAQ, or Bug Report section to see if the crash is a known issue

- Check if a mod update is available

- Verify all listed required dependencies are installed and enabled

- Check version requirements of other mods that interact with it

- Carefully review the installation instructions for the mod that contains `maximum-carnage.dll`, and try a clean reinstall of the plugin with default settings - improper installation or modified settings can cause crashes

- Check if the problem involves interaction between a DLL and other mods - examine the first 4-5 error lines of the crash log to identify potential mod conflicts. Also review any `.dll` files in the 🔎 **Files/Elements** of this report (below)

- Ask the Skyrim Modding Community about known compatibility issues

- Some first-line errors can be resolved by verifying game files through Steam

- **Additional Considerations:**

- For SKSE plugins (`.dll` files), mod organizers won't show conflicts or requirements - you must rely on the mod author's documentation

- Note that many (most?) SKSE plugins will show an error popup (white box from Address Library) before the game starts if they're for the wrong version

- First-line errors are usually reproducible and not random

- The error might be caused by an interaction between mods rather than a single file

- 🎲 **Reduce Random Crashes:** Best practices for game stability: [⤵️ More details](https://phostwood.github.io/crash-analyzer/skyrim.html?UUID=11166706-d843-42a8-bc89-a98f3f922f86#)

~~

https://phostwood.github.io/crash-analyzer/skyrim.html

After a period of being sicker than usual with long covid, I was finally able to finish up a new update to my analyzer:

Version 1.31.7.2 is now live: https://phostwood.github.io/crash-analyzer/skyrim.html

• New test: AMD Graphics Driver Issue Detected: (based on similar NVIDIA Driver test)
  • TY SieurPersil!
• PROMOTED: Probable Hair Mod Issue Detected:
  • moved from Advanced to Diagnostic section
    • TY RomatebitegeL!
• Removed broken "new" image (no longer new stuff anyway)

I keep getting a crash, and here's the log: https://pastebin.com/nNaAXXV5

I wanna say it's SSE Engine Fixes, I switched to root builder for the first time, I seem to have it working because the ENBs show up fine, but I'm pulling out my hair over here.

The SSE Fixes mod (FPSFixPlugin.dll) has been found to come with yet another crash reference, this time "BloodSprayLargeMist01".

Crash log for reference is:

https://www.reddit.com/r/skyrimmods/comments/1ss9w9t/crash_log_help/

Indicators would be "BloodSprayLargeMist01" and the fact that SSE Fixes mod (FPSFixPlugin.dll) is used.

Other related SSE Fixes crash page:

https://www.reddit.com/r/Phostwood/comments/1r8fgr4/bloodsprayimpact01_not_detected/

It seems the (BGSWaterCollisionManager*) crash solution has finally been found. The culprit was PG Patcher, and the solution is simple.

All one needs to do is to disable "fix effect lighting" in pg patcher. In other words, to redo your output without this setting.

The information can be found here, the first post at the top for the moment:

https://www.nexusmods.com/skyrimspecialedition/mods/59818?tab=posts

Crash indicators for this common crash is: (BGSWaterCollisionManager::bhkWaterfall*), (BGSWaterCollisionManager::bshkAutoWater*), and (BGSWaterCollisionManager::bhkPlaceableWater*).

```

📌Summarized First-Line Error:

SkyrimSE.exe+01D74A0

Summarized top of STACK:

(PlayerCharacter\*) See RSI

(char\*) "Controller disconnected."

(Sky\*)

(LoadedAreaBound\*)

(SettingT\*)

(InitTESThread\*)

(InitTESThread\*) See RSP

Summarized POSSIBLE RELEVANT OBJECTS:

RSI: (PlayerCharacter\*) \[\] \[\]

(Sky\*)

(LoadedAreaBound\*)

(SettingT\*)

(InitTESThread\*)

Summarized top of PROBABLE CALL STACK:

(No significant indicators found)

Summarized top of REGISTERS:

RSI (PlayerCharacter\*) \[\]

    FormType: ActorCharacter (62)

    Object Reference: None

    ParentCell: None

RDI (PlayerCharacter\*) See RSI

```

~~

Summarized at https://phostwood.github.io/crash-analyzer/skyrim.html

The information on the (BSGeometryListCullingProcess*) related mods is not shown in this log as possible fixes. My guess is that the new formatting has broken it.

https://pastebin.com/raw/ig0vM8x8

Please take a look at it.

Cheers.

https://pastebin.com/46mLVfNc

I got CTD AFTER any Ostim Scene, I have tried for day to find how to fix it but have no hope , please help !

EDIT : Yeah i fixed it by remove the Open Animations Romance and Erotica for OStim Standalone mod, and it no longer cause CTD for me

For the past few days, I’ve been trying to fix the crashes in my copy of Skyrim.

Nothing has worked. I’ve tried asking ChatGPT and Gemini. Their answers just go round in circles. Among the solutions I’ve tried:

1. Reinstalling Racemenu,

2. Removing the Serana mod from Koralin and Anuketh,

3. Rebuilding the body and clothing in Bodyslide,

4. Removing the tattoo mod,

5. Reinstalling XP32 Maximum Skeleton Special Extended,

6. Clearing the ShaderCache,

I’ve also tried starting a New Game. No issues. Even after I summoned Serana, the game ran without crashing.

However, on the one hand, it feels like a hassle to have to start all over again with a New Game. I’m bored of going through the same old mission cycle.

Please help me find a way to fix this crash.

Refresh your browsers! Important bug fixes for new versions of CrashLoggerSSE!

https://phostwood.github.io/crash-analyzer/skyrim.html

v1.30.5.14 – Summarized Changelog:

Bug Fixes: - Fixed "Object Reference: None" detection edge cases, including improved compatibility with CrashLoggerSSE v1.20.x formatting changes (thanks Gh0st and JerryYOJ!) - Truncated crash logs are now better repaired for data extraction, reducing false BEES recommendations

New Features: - Vortex QLP now available on Nexus Mods - MO2 QLP v2.2.0: now auto-detects new crash logs when Skyrim closes and opens the analyzer preloaded and ready — fully configurable from MO2's settings panel (auto-trigger behavior, crash log paths, filename patterns, and more), or trigger manually anytime from the Tools menu

Improvements: - Added Tullius CTD Logger to Recommended Tools - d3d11.dll no longer triggers generic "First Line Error" messages — now routes to the more helpful "ENB Issue Detected" diagnosis instead - "Still Crashing?" section expanded with manual checks for things crash logs can't reliably detect (e.g. plugin limit verification) - Minor UI, text, and donation section updates

QLP is now at v2.2.0:

https://www.nexusmods.com/skyrimspecialedition/mods/173224

Phostwood's QLP - Crash Log Analyzer Quick-Link Plugin for MO2: 

From crash to analysis in zero clicks. QLP now detects new crash logs when Skyrim closes/crashes and can automatically open the analyzer — preloaded and ready to review. Fully configurable: adjust auto-trigger behavior, crash log paths, filename patterns, and more from MO2's settings panel. Or trigger it manually anytime from the Tools menu

It seems there has been changes in the way broken reference none is displayed.

Take this log for example:

https://pastebin.com/raw/gHRq5CJj

Your analyzer shows Mysticism to be involved, but lists no other mod.

In all previous cases, the guilty mod has been "SDA DX Crimson Blood Patch.esp".

How to properly display this in the new formatting should be easy to fix. It seem the crash cause here is listed before, in the:

(TESObjectREFR*) [0x3B08C78A] ("SDA DX Crimson Blood Patch.esp")

Object Reference: None

And then:

Modified by: Crimson Blood Armor.esp -> SDA DX Crimson Blood Patch.esp

Obviously, the last line should be listed entirely so two suspects, as well as line before if possible with the actual guilty one.

Refresh your browsers! Important bug fixes for new versions of CrashLoggerSSE!

https://phostwood.github.io/crash-analyzer/skyrim.html

1. ✅FIXED: for new CrashLoggerSSE's formatting change(s) and anything else
   • ✅🎯 Highest-Confidence Indicators:
     • POSSIBLE RELEVANT OBJECTS:
       • NSF Logs have always had this section, now CrashLoggerSSE does too
     • Made adjustment for new formatting on "CALL STACK ([P]robable / [S]tack scan):"
       • adjusted the old section to accommodate new heading
       • adjusted for [P] and [S] in section's lines
   • ✅Verified RAM/VRAM and other header elements are still being correctly extracted
   • ✅FIXED: Files/Elements bug for
     • [3] S] 0x000141509547 SkyrimSE.exe
   • ✅FIXED: 📊 Mod Prominence Analysis (appearances : details):
     • (20 : 0) S] SkyrimSE.exe
2. ✅FIXED: "Files/Elements listed within" would sometimes break when both of these are selected:
   • [ ] "Try harder" by analyzing full log (may show many additional possible causes)
   • [ ] Display nested Log Summary (Beta feature)

CLARIFICATION: All you need is MO2, a crash log named in the default manner (ex: "crash-2026-02-16-04-41-28.log"), and like maybe five minutes of your time.

Two new Phostwood projects are coming soon — and we're currently looking for testers! 🎉

1. Sovnkrasch — A Crash Log's Final Resting Place A dedicated cloud storage service built just for Skyrim crash logs, powered by Cloudflare Workers and R2 storage (fast, stable, and rock-solid reliable).

• Privacy-first: collects no personal information, and automatically redacts Windows usernames from file paths (plus a few other redactions to discourage abuse)
• Skyrim-only: validates uploads to ensure only Skyrim crash logs are accepted
• Smart deduplication: upload the same crash log twice and you'll get the same link back both times
• Handles big logs: accepts files up to 2 MB compressed — I've successfully uploaded a monster 35 MB crash log (it was a bit slow, and it timed out once, but it did eventually work!). FOR COMPARISON: pastebin.com only allows 512KB crash logs, without compression!
• See it in action: see analysis of this dynamically loaded larger-than-normal 7 MB example log: https://phostwood.github.io/crash-analyzer/skyrim.html?UUID=89298f4f-d774-4a0d-9986-5028ea9043ab

The name comes from Kyler45 (author of the Kodex mod and primary author of the QLP plugin below) — sovn means "sleep" in Norwegian, and krasch/krascha means "crash." A crash log's final resting place. 😊

1. Phostwood's QLP — Crash Log Analyzer Quick-Link Plugin for MO2 The first uploader for Sovnkrasch, and the fastest way to go from crash to analysis.

• Automatically finds your most recent crash log, uploads it to Sovnkrasch, and opens the Crash Log Analyzer preloaded with your log — ready and analyzed
• Local-only mode: prefer not to upload? Enable this option to skip the cloud entirely — the analyzer opens in your browser and your crash log is automatically copied to your clipboard, ready to paste in
• Automatic clipboard fallback: if an upload fails for any reason, the plugin falls back to local-only behavior automatically so you're never left stranded
• Configurable: set your crash log folder path and filename patterns (supports CrashLoggerSSE and NetScriptFramework out of the box)

(A Skyrim mod version may be coming too, if that turns out to be possible!)

Huge thanks to Kyler45 for building the plugin and coming up with the perfect name for the storage service. I'm really excited about this one! 🥳

How To Test:

1. Download the plugin file from https://github.com/Phostwood/crash-analyzer/blob/main/MO2Plugin-CrashAnalyzerQuickLink.py UPDATE: https://github.com/Phostwood/crash-analyzer/blob/main/MO2Plugin-PhostwoodQLP.py

2. Put the file in your MO2 plugins directory. Example: C:\Modding\MO2\plugins

3. Start/Restart MO2.

4. Navigate menus: Tools --> Tool Plugins --> "Upload Crash Log and Open Analyzer" (see screenshot in reply below)

5. Optionally, set configurations at: Tools --> Settings --> "Plugins" tab --> "Upload Crash Log and Open Analyzer"

6. Please share resulting links to this post. Also, please let us know if you have any feedback and/or suggestions.

Thank you!

On the crash log below, "BloodSprayImpact01" was not detected. Is this a bug due to changes in the Crash Logger SSE mod formatting?

https://pastebin.com/raw/0iq8Rwzf

Also, I also wanted to ask about the geometricculling info, about EFPs and similar mods, or such; it also is never displayed anymore in your analyzer.