CTD at splashscreen

[Eternaldreams]

So I admit I have a heavily modded game.  However, I've looked both in LOOT and in Wrye Bash and I don't see any conflicts/errors for or between any of the mods.  I also admit I know just enough when it comes to modding to be dangerous.  When I start SKSE it will get all the way past the Bethesda logo to the splash screen and I think right before it would show the new game, continue, load game, etc is when it CTD.

 

Papyrus log:  https://pastebin.com/sakdRk7g

 

List of everything I'm running: https://pastebin.com/V2jSjtuR

 

Load order:  https://pastebin.com/WV3i0MZ1

[Dodzh]

Here are some of the things I keep in mind when i start new loadorder.

 

1- never start a save you are going to be playing before you test all your mods, get a clean save and test mods first. dont wait til you have all your mods installed to test, do test as you install groups of mods.

 

2- loot should only be run once before running your test or start a new save. do not change order of mods once you start your save

 

3- don't install too many animations, although you could get away with installing a large amount having more than the amount provided by the basic FNIS allows is a recipe for CTD's

 

4- if you have any mods that textures requiring DynDOLOD make sure is properly installed and running.

 

5- for sexlab mods test them well, some have lots of requirements and they all need to be installed.

 

basically take your time testing things well before you start a save you going to play with, changing mods mid game not advised unless you know very well what you doing.    

 

Edited April 28, 2023 by Dodzh

[Seijin8]

1 hour ago, Eternaldreams said:

So I admit I have a heavily modded game.  However, I've looked both in LOOT and in Wrye Bash and I don't see any conflicts/errors for or between any of the mods.  I also admit I know just enough when it comes to modding to be dangerous.  When I start SKSE it will get all the way past the Bethesda logo to the splash screen and I think right before it would show the new game, continue, load game, etc is when it CTD.

 

Papyrus log:  https://pastebin.com/sakdRk7g

 

List of everything I'm running: https://pastebin.com/V2jSjtuR

 

Load order:  https://pastebin.com/WV3i0MZ1

 

Crash after logo almost invariably means a missing master/plugin.

 

17 minutes ago, Dodzh said:

2- loot should only be run once before running your test or start a new save. do not change order of mods once you start your save

 

A stable load order has no issues with mod shuffling.  If LOOT breaks your shit, your shit was already broke.

[traison]

Like was already mentioned, missing master plugin is quite likely. Load everything as-is in xEdit and it will tell you where the problem is if your mod manager is not doing it already. Otherwise if that's not it then:

 

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

Edited April 28, 2023 by traison

[Eternaldreams]

Ok thanks for the input so far.  For the missing masters neither Loot, nor Wrye Bash show anything missing.  So I'm a little stumped there.  Looking in SSEEdit nothing comes up when I load everything into it.  Now when I apply the filter to show conflicts it does but from what I've read there are going to be conflicts no matter what I load.  I did take the advice and try the crash logger but I can't understand what it's saying in the log.  Any help would be greatly appreciated.

 

Crash logger log: https://pastebin.com/umJcPqbu

[traison]

Your issue is in DreadPrisonPatchARVMAS.esp, formid 0xd0ac. It may have something to do with LOD data.