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]

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 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!