Jump to content

Recommended Posts

Posted (edited)
1 hour ago, z929669 said:

In the MO Data tab, you can expand the SKSE\Plugins folder with ` .dll ` in the filter to see all the enabled DLLs. Right click to disable/hide, and repeat the play sequence you describe that seems to be reproducible. I would disable first half, test, then second half, test, and so on.

After you hide a file, be sure to click 'refresh' at the top of the data tab to see some other mod doesn't also provide the same-named DLL. They should be unique, but it's a possibility that I haven't investigated.

There may also be DLLs directly under SKSE\ (Pandora).

This is the full list of DLL files I have in the SKSE\Plugins folder.

SKSE Plugins DLL Files.txt

No DLL files in SKSE.  I'm currently using Nemesis, not Pandora.  I tested Pandora to see if the CTDs still occurred.  They did, so I went back to Nemesis.

Edited by Kattmandu
Posted
4 hours ago, Kattmandu said:

CTD with DynDOLOD.DLL hidden.  Just roaming around.  Followers had not spawned yet.  I noticed that my followers don't spawn in behind me immediately after loading a save with DynDOLOD.dll hidden.  They do immediately spawn in behind me with DynDOLOD.DLL unhidden.

crash-2025-06-08-14-15-29.log

DynDOLOD.log

skse64.log

Papyrus.0.log

While this time no call stack was recorded, it still is the same CTD as before.

You can see a list of all SKSE DLL plugins in the crash log under SKSE PLUGINS.

Something that could be related and easy enough to disable is stuff like ScriptEffectArchetypeCrashFix.dll or FootPrints.esp. Keep in mind though, while I can interpret the crash log information having probably to do effects and the virtual machine (script functions which can also be called by DLLs) I have really not much knowledge which mods to really look at in the load order.

Posted
2 hours ago, sheson said:

While this time no call stack was recorded, it still is the same CTD as before.

You can see a list of all SKSE DLL plugins in the crash log under SKSE PLUGINS.

Something that could be related and easy enough to disable is stuff like ScriptEffectArchetypeCrashFix.dll or FootPrints.esp. Keep in mind though, while I can interpret the crash log information having probably to do effects and the virtual machine (script functions which can also be called by DLLs) I have really not much knowledge which mods to really look at in the load order.

Re-enabled DynDOLOD.DLL test version 2025-05-09-03-19.  Disabled both Footprints and SPID for Footprints.  Also disabled Scrambled Bugs Script Effect Archetype Crash Fix.  CTD similar to others.  I really have no clue what mods to disable.

crash-2025-06-08-21-46-45.log

DynDOLOD.log

skse64.log

Papyrus.0.log

Posted
56 minutes ago, Kattmandu said:

Re-enabled DynDOLOD.DLL test version 2025-05-09-03-19.  Disabled both Footprints and SPID for Footprints.  Also disabled Scrambled Bugs Script Effect Archetype Crash Fix.  CTD similar to others.  I really have no clue what mods to disable.

crash-2025-06-08-21-46-45.log

DynDOLOD.log

skse64.log

Papyrus.0.log

The DLLs you listed are 'complete' with respect to the Step SkyrimSE 2.3 build. As I mentioned, I recommend disabling first half, test (using the same save and actions you took to generate the reproducible CTD), then second half, test. Continue testing by keeping enabled the half that did not produce the CTD, but then enable half again of the half that DID produce the CTD. Keep doing this with the now one quarter of DLLs disabled, then half of that (1/8), and half again (1/16)  ...until you wind up with the one or two DLLs that seem to be the culprit(s).

If sheson's suspicions are accurate, and you are able to narrow it down to one or two DLLs that seem to correlate with your CTDs, I can jump in to try to reproduce to rule out any OS or driver-related issues with said DLLs or otherwise related mods/assets.

Posted (edited)
59 minutes ago, z929669 said:

The DLLs you listed are 'complete' with respect to the Step SkyrimSE 2.3 build. As I mentioned, I recommend disabling first half, test (using the same save and actions you took to generate the reproducible CTD), then second half, test. Continue testing by keeping enabled the half that did not produce the CTD, but then enable half again of the half that DID produce the CTD. Keep doing this with the now one quarter of DLLs disabled, then half of that (1/8), and half again (1/16)  ...until you wind up with the one or two DLLs that seem to be the culprit(s).

If sheson's suspicions are accurate, and you are able to narrow it down to one or two DLLs that seem to correlate with your CTDs, I can jump in to try to reproduce to rule out any OS or driver-related issues with said DLLs or otherwise related mods/assets.

So just hide the DLL files or should I disable the mods that the DLL files are from?

Hiding half the DLL files causes the game to crash while loading a save.  I unhid a few DLL files such as PapyrusUtil, ScaleTranslationPP, SSEDisplayTweaks and UniqueMapWeather and now it loads the save.

CTD when my followers spawned into the landscape with the following DLL files hidden.

  • No Lockpick Activate.dll
  • oxygenMeter2.dll
  • po3_ENBLightForEffectShaders.dll
  • po3_LockVariations.dll
  • po3_SimpleOffenceSuppression.dll
  • po3_SpellPerkItemDistributor.dll
  • po3_SplashesOfStorms.dll
  • po3_Tweaks.dll
  • poisoner.dll
  • ShowPlayerInMenus.dll
  • SimpleDualSheath.dll
  • SkyrimUncapper.dll
  • SoftShadows.dll
  • StormLightning.dll
  • VendorRespawnFix.dll
  • WhoseQuestIsItAnyway.dll
  • YesImSure.dll

crash-2025-06-08-23-49-54.log

DynDOLOD.log

skse64.log

Papyrus.0.log

Edited by Kattmandu
Posted
28 minutes ago, Kattmandu said:

So just hide the DLL files or should I disable the mods that the DLL files are from?

Hiding half the DLL files causes the game to crash while loading a save.  Unhid a few DLL files such as PapyrusUtil, ScaleTranslationPP, SSEDisplayTweaks and UniqueMapWeather and now it loads the save.

CTD with the following DLL files hidden.

  • No Lockpick Activate.dll
  • oxygenMeter2.dll
  • po3_ENBLightForEffectShaders.dll
  • po3_LockVariations.dll
  • po3_SimpleOffenceSuppression.dll
  • po3_SpellPerkItemDistributor.dll
  • po3_SplashesOfStorms.dll
  • po3_Tweaks.dll
  • poisoner.dll
  • ShowPlayerInMenus.dll
  • SimpleDualSheath.dll
  • SkyrimUncapper.dll
  • SoftShadows.dll
  • StormLightning.dll
  • VendorRespawnFix.dll
  • WhoseQuestIsItAnyway.dll
  • YesImSure.dll

 

MO shows you the 'Mod' from which the DLL is sourced in the Data Tab, so you can hide the mod, which is probably better, since hiding only the DLL could cause other issues.

image.png

Hiding certain DLLs will cause CTD/ILS due to dependencies (e.g., skse64.dll should not be hidden ever). I was just providing a rundown of the iterative 'binary' algorithm via deduction based on whether or not you CTD doing the specific actions that you have found to be reproducible.

If you CTD with those DLLs hidden, then they should be unhidden whilst hiding (or disabling the source mods of) the remainder. You are simply trying to find one or more DLLs that could be related to your CTDs. If you do not CTD with a subset NOT disabled, then those are 'good' and should be left enabled in your next test. In this way, you can narrow down the problematic DLL(s) in about 6 tests (if it is indeed related to a DLL, which is just our working assumption for now).

Posted
10 minutes ago, Kattmandu said:

CTD after hiding the following DLL files as well.

  • AHZmoreHUDInventory.dll
  • AHZmoreHUDPlugin.dll
  • BugFixesSSE.dll
  • DP_Extender.dll
  • EVLaS.dll
  • ExATKDataPlugin.dll
  • Fuz Ro D'oh.dll
  • HDLocalMap.dll
  • ImmersiveEquipmentDisplays.dll
  • ImWalkinHere.dll
  • MagExtender.dll
  • MaxsuAIProcessFix.dll
  • MoreInformativeConsole.dll

crash-2025-06-09-00-18-27.log

DynDOLOD.log

skse64.log

Papyrus.0.log

The useful info is what DLL files are NOT hidden when you CTD. You listed 50 DILLs previously. Cumulatively, you have listed 30 DLLs that don't appear to be related to your CTDs (you CTD with them disabled), so there are 20 remaining ( you CTD with those enabled), minus enginefixes.dll & skse64.dll (which should not be disabled), that leaves 18 suspects.

Narrow down further by disabling 9 of them and so on.

BTW, I do not see skse64.dll in your previous list, so is that mod installed properly in your testing?

Posted (edited)

CTD after hiding the following DLL files as well.

  • ENBHelperSE.dll
  • FixNotesForSkyUI.dll
  • HorseStaminaHUD.dll
  • MCMHelper.dll
  • PapyrusTweaks.dll
  • PapyrusUtil.dll
  • SoundRecordDistributor.dll
  • StayAtSystemPageSE.dll
  • UniqueMapWeather.dll

crash-2025-06-09-00-45-23.log

DynDOLOD.log

skse64.log

Papyrus.0.log

11 minutes ago, z929669 said:

The useful info is what DLL files are NOT hidden when you CTD. You listed 50 DILLs previously. Cumulatively, you have listed 30 DLLs that don't appear to be related to your CTDs (you CTD with them disabled), so there are 20 remaining ( you CTD with those enabled), minus enginefixes.dll & skse64.dll (which should not be disabled), that leaves 18 suspects.

Narrow down further by disabling 9 of them and so on.

BTW, I do not see skse64.dll in your previous list, so is that mod installed properly in your testing?

These are the DLL files I still have unhidden

  • CrashLogger.dll
  • DynDOLOD.DLL
  • EngineFixes.dll
  • GrassCacheHelperNG.dll
  • MapMarkerFramework.dll
  • msdia140.dll
  • NGIO-NG.dll
  • ScaleformTranslationPP.dll
  • ScrambledBugs.dll
  • SSEDisplayTweaks.dll

Are you referring to skse64_1_6_1170.dll in the game's base directory?  I'm only hiding DLL files in SKSE\Plugins.

Edited by Kattmandu
Posted
15 minutes ago, Kattmandu said:

Are you referring to skse64_1_6_1170.dll in the game's base directory?  I'm only hiding DLL files in SKSE\Plugins.

No, sorry. I have RaceMenu active in my build, and it uses 'skee64.dll', which I misread. I wasn't thinking correctly when I mentioned skse64.dll ... of course, it's in the Data folder outside of MO control :doh:

Posted
3 minutes ago, z929669 said:

No, sorry. I have RaceMenu active in my build, and it uses 'skee64.dll', which I misread. I wasn't thinking correctly when I mentioned skse64.dll ... of course, it's in the Data folder outside of MO control :doh:

Oh, yeah. I have RaceMenu and Skyrim Character Sheet disabled.  Forgot to include those two in my list of DLL files.

Posted
6 hours ago, Kattmandu said:

Re-enabled DynDOLOD.DLL test version 2025-05-09-03-19.  Disabled both Footprints and SPID for Footprints.  Also disabled Scrambled Bugs Script Effect Archetype Crash Fix.  CTD similar to others.  I really have no clue what mods to disable.

crash-2025-06-08-21-46-45.log

DynDOLOD.log

skse64.log

Papyrus.0.log

Do not reenable anything if it did not to contribute to a problem so that in the end only the things remain that are required for the issue to happen.
In fact I would disable the entire DynDOLOD output in one of the next steps, then the Resources and all scripts etc. Same with other mods, plugins.

Since this crash seems related to effects, followers, I would also remove everything in one big step that most likely has nothing to do with it first to cut down the size of suspects.

You do not need to post similar crash logs that show no change.

2 hours ago, Kattmandu said:

CTD after disabling these two DLL files

  • EngineFixes.dll
  • SSEDisplayTweaks.dll

crash-2025-06-09-01-29-00.log

DynDOLOD.log

skse64.log

Papyrus.0.log

 

Not sure what else I can disable.  I can't disable ScrambledBugs.dll because the game will CTD when loading a save without it.  Can't disable CrashLogger.dll or msdia140.dll because crash log files won't generate without them.

The last crash log with "Teldryn Sero" is different to the ones with the "Steadfast Dwarven Sphere". That one is again about animations.
It could be two different types of crashes. It could be same issue just looking different in what it affects.

Effects, animations and related mods etc. are not my expertise.

Posted (edited)
16 hours ago, sheson said:

Do not reenable anything if it did not to contribute to a problem so that in the end only the things remain that are required for the issue to happen.
In fact I would disable the entire DynDOLOD output in one of the next steps, then the Resources and all scripts etc. Same with other mods, plugins.

Since this crash seems related to effects, followers, I would also remove everything in one big step that most likely has nothing to do with it first to cut down the size of suspects.

You do not need to post similar crash logs that show no change.

The last crash log with "Teldryn Sero" is different to the ones with the "Steadfast Dwarven Sphere". That one is again about animations.
It could be two different types of crashes. It could be same issue just looking different in what it affects.

Effects, animations and related mods etc. are not my expertise.

 

Disabled DynDOLOD Output.

CTD like the others.

Disabled DynDOLOD DLL NG and DynDOLOD Resources SE 3.

CTD like the others.

Disabled Nemesis Behavior Engine and Ice Skating Fixed for Real

CTD but took much longer.  I was in a fight.  So it either happened when I died or I was close to dying. 

crash-2025-06-09-20-55-07

skse64.log

Papyrus.0.log

 

Edited by Kattmandu

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.