Crashing when saving

[MonolithK]

So just to clarify this is the process:
Open game
New game
Enter racemenu
Finished racemenu
Approx 1-3 secnds then crash (I am using alternate start)

 

Crash log: https://ufile.io/tzj0k8gg - (I ran this crash clog through a log reader online and it claimed level lists induced crash but I highly doubt it?)
DynDOLOD/TexGen Logs: https://ufile.io/mme5g6ia

 

As far as I know almost everything I have should be up to date or almost up to date, as for DynDOLOD specifically I am fairly certain it is all fully up to date as I was just performing a fresh setup for DynDOLOD etc. This crash seems consistent, I have more things to test but so far, disabling "occlusion.esp" appears to thwart the crash at least after leaving racemenu. Please bare in mind, this issue has only just happened to me. My load order since last time has not substantially changed aside from mod updates etc (and yes this DynDOLOD was generated all after the updates testing on a brand new game)
Occlusion.esp is at the bottom most of my load order also.

I have yet to test more, but hopefully some insight can be offered or advice, thank you in advance to anyone who can lend a hand!

[sheson]

5 hours ago, SarcasticDragon said:

Sorry, my mistake, I hope this is correct. No bugreport.txt was generated this time, but I also included several crash logs, though they are all nearly identical as far as I can tell, as well as two papyrus logs for good measure:https://www.mediafire.com/file/crplt53x4rvqdd1/DynDoLODlog.zip/file

I apologize if the SSE Debug log is unusually large, but as far as I can tell there's nothing to truncate from it, it's all from a single session of the tool running.

I forgot to mention that I am aware of what happens when a save file gets too large and I did confirm that's not the case here, I've also had SaveGameMaxSize = true for a long time, and it's still turned on. I also did confirm that this issue does not manifest in a save game with DynDoLOD removed from the game entirely. This also isn't a problem with any one worldspace, it seems to be present in all of them. I tried the different compression settings in Skyrim.ini, it doesn't change the outcome. Again though, I have to emphasize the bizarre fact that saving works totally fine the first time a new DynDoLOD patch is installed (Or on a new game), but as soon as I make a save there and reload it, the issue returns. 

Which of the crash logs is with iCompression=1 and which one which iCompression=0?

https://dyndolod.info/Generation-Instructions#2-Generate-The-LOD-Mod-with-DynDOLOD
Finalize the load order as explained in the prerequisites above. Clean and error check the load order with xEdit. Make sure all mods, plugins and patches (..) are enabled and their overwrite order is sorted. 

The load order of plugins is different between the DynDOLOD log and the last crash log.
The actual sort order of plugins, plugins that are reported in the DynDOLOD log are not listed in the crash log and vice versa.

The generated plugins are not sorted correctly to load as last as possible for their respective type.
https://dyndolod.info/Generation-Instructions#2-Generate-The-LOD-Mod-with-DynDOLOD
In case Occlusion.esp was generated, it should be the last plugin to load right after DynDOLOD.esp. If a DynDOLOD.esm was generated it should be the ESM with the highest priority possible or just before the first non-ESM.

It looks like the save that is being loaded was not cleaned and contains old data. See https://dyndolod.info/Help/Clean-Save

If issue persists, test with a new game if saving, existing game, starting game and loading that save and then saving again works.
If issue persists, disable/hide SkyPatcher.dll to see if that makes a difference.

[sheson]

9 minutes ago, MonolithK said:

So just to clarify this is the process:
Open game
New game
Enter racemenu
Finished racemenu
Approx 1-3 secnds then crash (I am using alternate start)

 

Crash log: https://ufile.io/tzj0k8gg - (I ran this crash clog through a log reader online and it claimed level lists induced crash but I highly doubt it?)
DynDOLOD/TexGen Logs: https://ufile.io/mme5g6ia

 

As far as I know almost everything I have should be up to date or almost up to date, as for DynDOLOD specifically I am fairly certain it is all fully up to date as I was just performing a fresh setup for DynDOLOD etc. This crash seems consistent, I have more things to test but so far, disabling "occlusion.esp" appears to thwart the crash at least after leaving racemenu. Please bare in mind, this issue has only just happened to me. My load order since last time has not substantially changed aside from mod updates etc (and yes this DynDOLOD was generated all after the updates testing on a brand new game)

I have yet to test more, but hopefully some insight can be offered or advice, thank you in advance to anyone who can lend a hand!

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs
In case of CTD in the game, upload the entire crash log from .NET Script Framework or Crash Logger. Also see ..DynDOLOD\Docs\DynDOLOD-README.txt.

Remove trainwreck and install crash logger for proper crash logs.

Actually checking the available crash log reveals:
Occlusion.esp is not even mentioned in that crash log. All it contains is world and cell records with updated occlusion data, which can not cause crashes by itself.
Looking for names of functions shows:
BGSSaveFormBuffer
Win32FileType
TESLevItem
BGSSaveLoadManager

https://dyndolod.info/Official-DynDOLOD-Support-Forum#post-Logs#Check-the-FAQ

https://dyndolod.info/FAQ#ILS-or-CTD
If there are problems saving in Skyrim Special Edition, install SSE Engine Fixes 4.8 or newer and set SaveGameMaxSize = true in the EngineFixes.toml. Alternatively add/set [SaveGame] uiCompression=1 in Skyrim.INI to change from the default 2 for LZ4 to 1 for zlib compression. 0 means no compression like games are saved in Skyrim.
Install a crash logger and troubleshoot the real cause of crashes as explained in the ..DynDOLOD\Docs\DynDOLOD-README.txt.

[MonolithK]

31 minutes ago, sheson said:

Remove trainwreck and install crash logger for proper crash logs.

Actually checking the available crash log reveals:
Occlusion.esp is not even mentioned in that crash log. All it contains is world and cell records with updated occlusion data, which can not cause crashes by itself.
Looking for names of functions shows:
BGSSaveFormBuffer
Win32FileType
TESLevItem
BGSSaveLoadManager

https://dyndolod.info/Official-DynDOLOD-Support-Forum#post-Logs#Check-the-FAQ

https://dyndolod.info/FAQ#ILS-or-CTD
If there are problems saving in Skyrim Special Edition, install SSE Engine Fixes 4.8 or newer and set SaveGameMaxSize = true in the EngineFixes.toml. Alternatively add/set [SaveGame] uiCompression=1 in Skyrim.INI to change from the default 2 for LZ4 to 1 for zlib compression. 0 means no compression like games are saved in Skyrim.
Install a crash logger and troubleshoot the real cause of crashes as explained in the ..DynDOLOD\Docs\DynDOLOD-README.txt.

So actually, you are entirely correct, Occlusion.esp seems not be responsible, I've managed to launch the game (3 times) now without any crashes and I've kept Occlusion.esp enabled for these rounds!

I also didn't realise the problem seemed save related, so I my pardon there! Also, I have not changed my settings yet in SSE Engine fixes, I will continue to play without the change to settings in hopes of reproducing the crash and providing a new log.
I'd actually like to mention something however:

When I received the crash I actually turned out to be running a slightly dated (not partcurly old) version of crash logger alongside Trainwreck, I'm not sure if running these two together at the same time is potentially the cause of the save crash or if its worth further investigating, if I can provide a new crash log I will share it here just in case keep this issue updated (if it continues or returns in a way that I can't solve with the solution you provided). Also worth mentioning, running the two together appears to block Crash Logger from generating a log entirely.
Thank you so much, hopefully thats the end of the issue however!

Edited July 19, 2024 by MonolithK

[MonolithK]

Slight update: https://ufile.io/epime17l

My newest crash log, I am suspect that this is a totally different crash related log, but if it could be looked into I'd still appreciate it!

[MonolithK]

Hopefully final update on the problem: 

Generated new Dyndlod etc and then crashed after race menu and this time I was using crash logger specifically.
Crashlog: https://ufile.io/z7vtrv23

So hopefully it is just the saving issue and nothing else!

[sheson]

On 7/21/2024 at 4:54 PM, MonolithK said:

Slight update: https://ufile.io/epime17l

My newest crash log, I am suspect that this is a totally different crash related log, but if it could be looked into I'd still appreciate it!

This crash is caused by using an outdated version 1.4 of ConsoleUtil instead of ConsoleUtilSSE NG 1.5.1

8 hours ago, MonolithK said:

Hopefully final update on the problem: 

Generated new Dyndlod etc and then crashed after race menu and this time I was using crash logger specifically.
Crashlog: https://ufile.io/z7vtrv23

So hopefully it is just the saving issue and nothing else!

I am not sure why you generated new DynDOLOD output or why you believe it has something to do with the crash.

This crash again indicates a problem with BGSSaveFormBuffer. Use Engine Fixes and/or the INI setting as explained in the FAQ.

It is also possible there is an issue with the mentioned leveled item list with the form ID 000D9F89.

[MonolithK]

19 hours ago, sheson said:

This crash is caused by using an outdated version 1.4 of ConsoleUtil instead of ConsoleUtilSSE NG 1.5.1

Yup I managed to successfully correct this side of the crash!

Quote

 

I am not sure why you generated new DynDOLOD output or why you believe it has something to do with the crash.

This crash again indicates a problem with BGSSaveFormBuffer. Use Engine Fixes and/or the INI setting as explained in the FAQ.

 

Don't misunderstand! You already explained the save issue, I was reposting a recreation of my initial post but with crash logger instead as you mentioned that trainwreck wasn't good for this type of thing, I actually agree and believe your solution, but for the sake of clarity with the problem I preferred to try and recreate the problem so that it would match and just incase no other problem slips through! As for why I regenerated Dyndolod, same reason really, a few mod updates, not changes just newer versions so I didn't want to produce a new obscure problem due to using a prior generation.

Sorry for posting that final one, I've actually already been playing with the fix as you suggested! and so far no problems! I just wanted to make sure I provided to full extent of the logs as you originally wanted! And I really do appreciate the support so much!

[SarcasticDragon]

I'm new here, so I apologize if I'm doing any of this incorrectly, or if this is the wrong place to post this, but I'm really at my wits' end. Ever since I updated to the latest version of DynDoLOD, I've been suffering from a crippling issue that is repeatable.

 

Basically, the game will crash on save, and it produces the same crash log every time, always mentioning a reference called "ThouShaltBowtoSheson", xEdit says it's something called the "Master Activator". But there's another weird pattern to it. If I regenerate my DynDoLOD patch and install that, the first time a save is loaded with it fresh or otherwise, I am able to save my game while that instance of the game is running. Closing the game and restarting causes the issue to return, and it stays that way until I regenerate the patch again. This issue is not related to save corruption and persists on a new game too. I've been using DynDoLOD 3 for a few years now and have never had an issue like this before.

 

Here is the crashlog, I also checked every mod in the callstack, they don't seem to have anything to do with it:https://pastebin.com/yWf0gcVn

And here are the DynDoLOD logs: https://www.mediafire.com/file/trbnts40ddzw5j6/DynDoLODlogs.zip/file

[z929669]

2 hours ago, SarcasticDragon said:

I'm new here, so I apologize if I'm doing any of this incorrectly, or if this is the wrong place to post this, but I'm really at my wits' end. Ever since I updated to the latest version of DynDoLOD, I've been suffering from a crippling issue that is repeatable.

 

Basically, the game will crash on save, and it produces the same crash log every time, always mentioning a reference called "ThouShaltBowtoSheson", xEdit says it's something called the "Master Activator". But there's another weird pattern to it. If I regenerate my DynDoLOD patch and install that, the first time a save is loaded with it fresh or otherwise, I am able to save my game while that instance of the game is running. Closing the game and restarting causes the issue to return, and it stays that way until I regenerate the patch again. This issue is not related to save corruption and persists on a new game too. I've been using DynDoLOD 3 for a few years now and have never had an issue like this before.

 

Here is the crashlog, I also checked every mod in the callstack, they don't seem to have anything to do with it:https://pastebin.com/yWf0gcVn

And here are the DynDoLOD logs: https://www.mediafire.com/file/trbnts40ddzw5j6/DynDoLODlogs.zip/file

Moved to DynDOLOD Support

[sheson]

3 hours ago, SarcasticDragon said:

I'm new here, so I apologize if I'm doing any of this incorrectly, or if this is the wrong place to post this, but I'm really at my wits' end. Ever since I updated to the latest version of DynDoLOD, I've been suffering from a crippling issue that is repeatable.

 

Basically, the game will crash on save, and it produces the same crash log every time, always mentioning a reference called "ThouShaltBowtoSheson", xEdit says it's something called the "Master Activator". But there's another weird pattern to it. If I regenerate my DynDoLOD patch and install that, the first time a save is loaded with it fresh or otherwise, I am able to save my game while that instance of the game is running. Closing the game and restarting causes the issue to return, and it stays that way until I regenerate the patch again. This issue is not related to save corruption and persists on a new game too. I've been using DynDoLOD 3 for a few years now and have never had an issue like this before.

 

Here is the crashlog, I also checked every mod in the callstack, they don't seem to have anything to do with it:https://pastebin.com/yWf0gcVn

And here are the DynDoLOD logs: https://www.mediafire.com/file/trbnts40ddzw5j6/DynDoLODlogs.zip/file

The archive only contains TexGen logs. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting
In case of issues in the game, test if the problem persists without any DynDOLOD output.

https://dyndolod.info/FAQ#ILS-or-CTD
If there are problems saving in Skyrim Special Edition, install SSE Engine Fixes 4.8 or newer and set SaveGameMaxSize = true in the EngineFixes.toml. Alternatively add/set [SaveGame] uiCompression=1 in Skyrim.INI to change from the default 2 for LZ4 to 1 for zlib compression. 0 means no compression like games are saved in Skyrim.

Post new crash log if there still is a crash with SaveGameMaxSize = true. If it was already set, test with the INI settings.

[SarcasticDragon]

Sorry, my mistake, I hope this is correct. No bugreport.txt was generated this time, but I also included several crash logs, though they are all nearly identical as far as I can tell, as well as two papyrus logs for good measure:https://www.mediafire.com/file/crplt53x4rvqdd1/DynDoLODlog.zip/file

I apologize if the SSE Debug log is unusually large, but as far as I can tell there's nothing to truncate from it, it's all from a single session of the tool running.

 

I forgot to mention that I am aware of what happens when a save file gets too large and I did confirm that's not the case here, I've also had SaveGameMaxSize = true for a long time, and it's still turned on. I also did confirm that this issue does not manifest in a save game with DynDoLOD removed from the game entirely. This also isn't a problem with any one worldspace, it seems to be present in all of them. I tried the different compression settings in Skyrim.ini, it doesn't change the outcome. Again though, I have to emphasize the bizarre fact that saving works totally fine the first time a new DynDoLOD patch is installed (Or on a new game), but as soon as I make a save there and reload it, the issue returns. 

[SarcasticDragon]

You are totally right, the plugins are completely out of order. And upon manually correcting that, the issue has gone away. It seems Vortex shuffled them around a bunch without my knowledge. Up until now it's never caused any serious problems and I don't like to make big changes if I don't have to, but I guess I'm really gonna have to reevaluate my relationship with Vortex after this one.

Very sorry to have wasted your time and thank you so much for everything you do!

Edited June 28 by SarcasticDragon

[LeadMetal]

Game CTDs when saving/quicksaving. After asking for help on reading the log, I was shown two different suspects:

Object Reference: 
File: "DynDOLOD.esp"
Flags: 0x04400208 kInitialized
Name: "ThouShaltBowToSheson"

File: "0Kaidan.esp"
Flags: 0x00000008 kInitialized
Name: "Kaidan's Nodachi"
FormID: 0x5000A697
FormType: Weapon (41)
GetFullName: "Kaidan's Nodachi"

I don't know how all of this works, so any help would be appreciated]

crash-2025-09-16-09-02-52.log

Edited September 16 by LeadMetal

[sheson]

33 minutes ago, LeadMetal said:

Game CTDs when saving/quicksaving. After asking for help on reading the log, I was shown two different suspects:

Object Reference: 
File: "DynDOLOD.esp"
Flags: 0x04400208 kInitialized
Name: "ThouShaltBowToSheson"

File: "0Kaidan.esp"
Flags: 0x00000008 kInitialized
Name: "Kaidan's Nodachi"
FormID: 0x5000A697
FormType: Weapon (41)
GetFullName: "Kaidan's Nodachi"

I don't know how all of this works, so any help would be appreciated]

crash-2025-09-16-09-02-52.log 72.75 kB · 1 download

Moved to an appropriate thread for problem. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to also upload when making posts.

https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-the-Latest-Versions
Always use the latest version of DynDOLOD Standalone, DynDOLOD Resources and DynDOLOD DLL NG and Scripts. Bugs and other problems may already be fixed or addressed.

Update DynDOLOD DLL NG and Scripts. No need to generate/update the DynDOLOD output again, just replace.

See https://dyndolod.info/FAQ#ILS-or-CTD
If there are problems saving in Skyrim Special Edition, install SSE Engine Fixes 4.8 or newer and increase SaveGameMaxSize = 128 for newer versions or set SaveGameMaxSize = true for older versions in the EngineFixes.toml. Alternatively add/set [SaveGame] uiCompression=1 in Skyrim.INI to change from the default 2 for LZ4 to 1 for zlib compression. 0 means no compression like games are saved in Skyrim.

Report, double check / increase the SaveGameMaxSize setting in the EngineFixes.toml.

Also see https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting, e.g. test what happens without the output.