CTD with Cathedral Weathers and Seasons - Help?

SuperOwen · June 2, 2022

I've finally gotten through the mod install process, and gotten to the stage where we start testing/benchmarking everything. Upon attempting to open SSE, I get a CTD.

After some searching the forums, I first looked at my Crash Log, and couldn't make any sense of it. I then started disabling whole mod groups to find the culprit, and I found it instantly. As soon as I disabled Cathedral Weathers and Seasons, the game booted fine.

I'm pretty sure I followed every step to the letter, disabling plugins when asked and installing the right files, and I've re-downloaded and re-installed the mod with no success (I'm not going to be using an ENB, so skipped any mods or options that referred to post-processing)

What could be the cause? I've obviously done something wrong, and I'll gladly have somebody point it out to me, but I'd really like to fix that one thing instead of reinstalling everything. (I've been doing this over the course of weeks, stealing the odd hour or two each night after my daughter goes to sleep!)

Any ideas?

Here's my crash log if you're interested:

Spoiler

Skyrim SSE v1.6.353
CrashLoggerSSE v1.0.0

Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0x7FF6BDCD6370 SkyrimSE.exe+0196370

SYSTEM SPECS:
   OS: Microsoft Windows 10 Home v10.0.19041
   CPU: GenuineIntel Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz
   GPU #1: Nvidia GP104 [GeForce GTX 1070]
   GPU #2: Microsoft Basic Render Driver
   PHYSICAL MEMORY: 7.65 GB/15.92 GB

PROBABLE CALL STACK:
[0] 0x7FF6BDCD6370 SkyrimSE.exe+0196370 -> 14371+0x10

REGISTERS:
   RAX 0x2104 (size_t)
   RCX 0x30 (size_t)
   RDX 0x0 (size_t)
   RBX 0x0 (size_t)
   RSP 0x5384DFF638 (void*)
   RBP 0x5384DFF6B9 (void*)
   RSI 0x1D51B576080 (PlayerCharacter*)
       File: ""
       Flags: 0x00200400
       Form ID: 0x00000014
       Form Type: 62
   RDI 0x1D51B576080 (PlayerCharacter*)
       File: ""
       Flags: 0x00200400
       Form ID: 0x00000014
       Form Type: 62
   R8 0x2104 (size_t)
   R9 0x0 (size_t)
   R10 0x1D4BC8C8B50 (void*)
   R11 0x5384DFF720 (void*)
   R12 0x0 (size_t)
   R13 0x0 (size_t)
   R14 0x0 (size_t)
   R15 0x1D521C74C90 (void*)

STACK:
   [RSP+0 ] 0x7FF6BDDD71A0 (void* -> SkyrimSE.exe+02971A0)
   [RSP+8 ] 0x0 (size_t)
   [RSP+10 ] 0x1D51B576080 (PlayerCharacter*)
       File: ""
       Flags: 0x00200400
       Form ID: 0x00000014
       Form Type: 62
   [RSP+18 ] 0x5384DFF6B9 (void*)
   [RSP+20 ] 0x2D02EF8D5A05DF1B (size_t)
   [RSP+28 ] 0xACF9600238A7 (size_t)
   [RSP+30 ] 0x1D51B5C0F00 (void*)
   [RSP+38 ] 0x1D51B596C80 (void*)
   [RSP+40 ] 0x7FFB984DE546 (void* -> EngineFixes.dll+002E546)
   [RSP+48 ] 0x0 (size_t)
   [RSP+50 ] 0xFFFFFFFFFFFFFFFE (size_t)
   [RSP+58 ] 0x0 (size_t)
   [RSP+60 ] 0x1D521C74C90 (void*)
   [RSP+68 ] 0xACF960023F37 (size_t)
   [RSP+70 ] 0x4 (size_t)
   [RSP+78 ] 0x7FF6BDB40000 (void*)
   [RSP+80 ] 0x7FF6BDCCCC29 (void* -> SkyrimSE.exe+018CC29)
   [RSP+88 ] 0x0 (size_t)
   [RSP+90 ] 0x0 (size_t)
   [RSP+98 ] 0x1D51B576080 (PlayerCharacter*)
       File: ""
       Flags: 0x00200400
       Form ID: 0x00000014
       Form Type: 62
   [RSP+A0 ] 0x768 (size_t)
   [RSP+A8 ] 0x1D4BCAB6501 (void*)
   [RSP+B0 ] 0x0 (size_t)
   [RSP+B8 ] 0x0 (size_t)
   [RSP+C0 ] 0x1D521C74C90 (void*)
   [RSP+C8 ] 0x0 (size_t)
   [RSP+D0 ] 0x1D51B576080 (PlayerCharacter*)
       File: ""
       Flags: 0x00200400
       Form ID: 0x00000014
       Form Type: 62
   [RSP+D8 ] 0x768 (size_t)
   [RSP+E0 ] 0x7FF6BE167235 (void* -> SkyrimSE.exe+0627235)
   [RSP+E8 ] 0xFFFFFFFFFFFFFFFE (size_t)
   [RSP+F0 ] 0x1D4BCAB6501 (void*)
   [RSP+F8 ] 0x768 (size_t)
   [RSP+100] 0x1D400000000 (size_t)
   [RSP+108] 0x2 (size_t)
   [RSP+110] 0x7FF6BE11F9E7 (void* -> SkyrimSE.exe+05DF9E7)
   [RSP+118] 0x1D521C74C90 (void*)
   [RSP+120] 0x768 (size_t)
   [RSP+128] 0x1D500000069 (void*)
   [RSP+130] 0x0 (size_t)
   [RSP+138] 0x1D500000000 (void*)
   [RSP+140] 0x7FF6BDFA7B4F (void* -> SkyrimSE.exe+0467B4F)
   [RSP+148] 0xFFFFFFFFFFFFFFFE (size_t)
   [RSP+150] 0x4500000045000000 (size_t)
   [RSP+158] 0x0 (size_t)
   [RSP+160] 0x1D4BCAB6501 (void*)
   [RSP+168] 0x0 (size_t)
   [RSP+170] 0x0 (size_t)
   [RSP+178] 0x7FF6BF223FF8 (char*) "Controller disconnected."
   [RSP+180] 0x7FF6BE117E04 (void* -> SkyrimSE.exe+05D7E04)
   [RSP+188] 0x2 (size_t)
   [RSP+190] 0x2 (size_t)
   [RSP+198] 0x0 (size_t)
   [RSP+1A0] 0x1D521C74C90 (void*)
   [RSP+1A8] 0x1D4F9920400 (Sky*)
   [RSP+1B0] 0x1D51B6C3600 (LoadedAreaBound*)
   [RSP+1B8] 0x0 (size_t)
   [RSP+1C0] 0xFFFFFFFFFFFFFFFE (size_t)
   [RSP+1C8] 0x7FF6BF9C41E0 (SettingT<INISettingCollection>*)
   [RSP+1D0] 0x7FF6BF9C41F8 (SettingT<INISettingCollection>*)
   [RSP+1D8] 0x7FF6BF9C4210 (SettingT<INISettingCollection>*)
   [RSP+1E0] 0x7FF6BF9C4228 (SettingT<INISettingCollection>*)
   [RSP+1E8] 0x7FF6BF9C4240 (SettingT<INISettingCollection>*)
   [RSP+1F0] 0x7FF6BF9C4258 (SettingT<INISettingCollection>*)
   [RSP+1F8] 0x7FF6BF9C4270 (SettingT<INISettingCollection>*)
   [RSP+200] 0x7FF6BF9C4288 (SettingT<INISettingCollection>*)
   [RSP+208] 0x7FF6BF9C42A0 (SettingT<INISettingCollection>*)
   [RSP+210] 0x7FF6BF9C42B8 (SettingT<INISettingCollection>*)
   [RSP+218] 0x0 (size_t)
   [RSP+220] 0x0 (size_t)
   [RSP+228] 0x0 (size_t)
   [RSP+230] 0x0 (size_t)
   [RSP+238] 0x0 (size_t)
   [RSP+240] 0x7FF6BE1212FC (void* -> SkyrimSE.exe+05E12FC)
   [RSP+248] 0x53832FF780 (InitTESThread*)
   [RSP+250] 0x0 (size_t)
   [RSP+258] 0x2 (size_t)
   [RSP+260] 0x1D400000002 (size_t)
   [RSP+268] 0x53832FF780 (InitTESThread*)
   [RSP+270] 0x7FF6BE77426D (void* -> SkyrimSE.exe+0C3426D)
   [RSP+278] 0x7FF6C0B477F0 (void* -> SkyrimSE.exe+30077F0)
   [RSP+280] 0x53832FF780 (InitTESThread*)
   [RSP+288] 0x0 (size_t)
   [RSP+290] 0x0 (size_t)
   [RSP+298] 0x53832FF780 (InitTESThread*)
   [RSP+2A0] 0x0 (size_t)
   [RSP+2A8] 0x0 (size_t)
   [RSP+2B0] 0x7FFBFDEE7034 (void* -> KERNEL32.DLL+0017034)
   [RSP+2B8] 0x0 (size_t)
   [RSP+2C0] 0x0 (size_t)
   [RSP+2C8] 0x0 (size_t)
   [RSP+2D0] 0x0 (size_t)
   [RSP+2D8] 0x0 (size_t)
   [RSP+2E0] 0x7FFBFE9C2651 (void* -> ntdll.dll+0052651)
   [RSP+2E8] 0x0 (size_t)
   [RSP+2F0] 0x0 (size_t)
   [RSP+2F8] 0x0 (size_t)
   [RSP+300] 0x0 (size_t)
   [RSP+308] 0x0 (size_t)
   [RSP+310] 0x0 (size_t)
   [RSP+318] 0xD12FB30100000000 (size_t)
   [RSP+320] 0x0 (size_t)
   [RSP+328] 0x0 (size_t)
   [RSP+330] 0x7FFBFC18FD40 (void* -> KERNELBASE.dll+010FD40)
   [RSP+338] 0x5384DFE700 (void*)
   [RSP+340] 0x80003FFD969BA720 (size_t)
   [RSP+348] 0x7FFB2D374E41 (size_t)
   [RSP+350] 0x5384DFE700 (void*)
   [RSP+358] 0x0 (size_t)
   [RSP+360] 0x0 (size_t)
   [RSP+368] 0x0 (size_t)
   [RSP+370] 0x0 (size_t)
   [RSP+378] 0x0 (size_t)
   [RSP+380] 0x0 (size_t)
   [RSP+388] 0x0 (size_t)
   [RSP+390] 0x0 (size_t)
   [RSP+398] 0x0 (size_t)
   [RSP+3A0] 0x0 (size_t)
   [RSP+3A8] 0x0 (size_t)
   [RSP+3B0] 0x0 (size_t)
   [RSP+3B8] 0x0 (size_t)
   [RSP+3C0] 0x0 (size_t)
   [RSP+3C8] 0x0 (size_t)
   [RSP+3D0] 0x0 (size_t)
   [RSP+3D8] 0x0 (size_t)
   [RSP+3E0] 0x0 (size_t)
   [RSP+3E8] 0x0 (size_t)
   [RSP+3F0] 0x0 (size_t)
   [RSP+3F8] 0x0 (size_t)
   [RSP+400] 0x0 (size_t)
   [RSP+408] 0x0 (size_t)
   [RSP+410] 0x0 (size_t)
   [RSP+418] 0x0 (size_t)
   [RSP+420] 0x0 (size_t)
   [RSP+428] 0x0 (size_t)
   [RSP+430] 0x0 (size_t)
   [RSP+438] 0x0 (size_t)
   [RSP+440] 0x0 (size_t)
   [RSP+448] 0x0 (size_t)
   [RSP+450] 0x0 (size_t)
   [RSP+458] 0x0 (size_t)
   [RSP+460] 0x0 (size_t)
   [RSP+468] 0x0 (size_t)
   [RSP+470] 0x0 (size_t)
   [RSP+478] 0x0 (size_t)
   [RSP+480] 0x0 (size_t)
   [RSP+488] 0x0 (size_t)
   [RSP+490] 0x0 (size_t)
   [RSP+498] 0x0 (size_t)
   [RSP+4A0] 0x0 (size_t)
   [RSP+4A8] 0x0 (size_t)
   [RSP+4B0] 0x0 (size_t)
   [RSP+4B8] 0x0 (size_t)
   [RSP+4C0] 0x0 (size_t)
   [RSP+4C8] 0x0 (size_t)
   [RSP+4D0] 0x0 (size_t)
   [RSP+4D8] 0x0 (size_t)
   [RSP+4E0] 0x0 (size_t)
   [RSP+4E8] 0x0 (size_t)
   [RSP+4F0] 0x0 (size_t)
   [RSP+4F8] 0x0 (size_t)
   [RSP+500] 0x0 (size_t)
   [RSP+508] 0x0 (size_t)
   [RSP+510] 0x0 (size_t)
   [RSP+518] 0x0 (size_t)
   [RSP+520] 0x0 (size_t)
   [RSP+528] 0x0 (size_t)
   [RSP+530] 0x0 (size_t)
   [RSP+538] 0x0 (size_t)
   [RSP+540] 0x0 (size_t)
   [RSP+548] 0x0 (size_t)
   [RSP+550] 0x0 (size_t)
   [RSP+558] 0x0 (size_t)
   [RSP+560] 0x0 (size_t)
   [RSP+568] 0x0 (size_t)
   [RSP+570] 0x0 (size_t)
   [RSP+578] 0x0 (size_t)
   [RSP+580] 0x0 (size_t)
   [RSP+588] 0x0 (size_t)
   [RSP+590] 0x0 (size_t)
   [RSP+598] 0x0 (size_t)
   [RSP+5A0] 0x0 (size_t)
   [RSP+5A8] 0x0 (size_t)
   [RSP+5B0] 0x0 (size_t)
   [RSP+5B8] 0x0 (size_t)
   [RSP+5C0] 0x0 (size_t)
   [RSP+5C8] 0x0 (size_t)
   [RSP+5D0] 0x0 (size_t)
   [RSP+5D8] 0x0 (size_t)
   [RSP+5E0] 0x0 (size_t)
   [RSP+5E8] 0x0 (size_t)
   [RSP+5F0] 0x0 (size_t)
   [RSP+5F8] 0x0 (size_t)
   [RSP+600] 0x0 (size_t)
   [RSP+608] 0x0 (size_t)
   [RSP+610] 0x0 (size_t)
   [RSP+618] 0x0 (size_t)
   [RSP+620] 0x0 (size_t)
   [RSP+628] 0x0 (size_t)
   [RSP+630] 0x0 (size_t)
   [RSP+638] 0x0 (size_t)
   [RSP+640] 0x0 (size_t)
   [RSP+648] 0x0 (size_t)
   [RSP+650] 0x0 (size_t)
   [RSP+658] 0x0 (size_t)
   [RSP+660] 0x0 (size_t)
   [RSP+668] 0x0 (size_t)
   [RSP+670] 0x0 (size_t)
   [RSP+678] 0x0 (size_t)
   [RSP+680] 0x0 (size_t)
   [RSP+688] 0x0 (size_t)
   [RSP+690] 0x0 (size_t)
   [RSP+698] 0x0 (size_t)
   [RSP+6A0] 0x0 (size_t)
   [RSP+6A8] 0x0 (size_t)
   [RSP+6B0] 0x0 (size_t)
   [RSP+6B8] 0x0 (size_t)
   [RSP+6C0] 0x0 (size_t)
   [RSP+6C8] 0x0 (size_t)
   [RSP+6D0] 0x0 (size_t)
   [RSP+6D8] 0x0 (size_t)
   [RSP+6E0] 0x0 (size_t)
   [RSP+6E8] 0x0 (size_t)
   [RSP+6F0] 0x0 (size_t)
   [RSP+6F8] 0x0 (size_t)
   [RSP+700] 0x0 (size_t)
   [RSP+708] 0x0 (size_t)
   [RSP+710] 0x0 (size_t)
   [RSP+718] 0x0 (size_t)
   [RSP+720] 0x0 (size_t)
   [RSP+728] 0x0 (size_t)
   [RSP+730] 0x0 (size_t)
   [RSP+738] 0x0 (size_t)
   [RSP+740] 0x0 (size_t)
   [RSP+748] 0x0 (size_t)
   [RSP+750] 0x0 (size_t)
   [RSP+758] 0x0 (size_t)
   [RSP+760] 0x0 (size_t)
   [RSP+768] 0x0 (size_t)
   [RSP+770] 0x0 (size_t)
   [RSP+778] 0x0 (size_t)
   [RSP+780] 0x0 (size_t)
   [RSP+788] 0x0 (size_t)
   [RSP+790] 0x0 (size_t)
   [RSP+798] 0x0 (size_t)
   [RSP+7A0] 0x0 (size_t)
   [RSP+7A8] 0x0 (size_t)
   [RSP+7B0] 0x0 (size_t)
   [RSP+7B8] 0x0 (size_t)
   [RSP+7C0] 0x0 (size_t)
   [RSP+7C8] 0x0 (size_t)
   [RSP+7D0] 0x0 (size_t)
   [RSP+7D8] 0x0 (size_t)
   [RSP+7E0] 0x0 (size_t)
   [RSP+7E8] 0x0 (size_t)
   [RSP+7F0] 0x0 (size_t)
   [RSP+7F8] 0x0 (size_t)
   [RSP+800] 0x0 (size_t)
   [RSP+808] 0x0 (size_t)
   [RSP+810] 0x0 (size_t)
   [RSP+818] 0x0 (size_t)
   [RSP+820] 0x0 (size_t)
   [RSP+828] 0x0 (size_t)
   [RSP+830] 0x0 (size_t)
   [RSP+838] 0x0 (size_t)
   [RSP+840] 0x0 (size_t)
   [RSP+848] 0x0 (size_t)
   [RSP+850] 0x0 (size_t)
   [RSP+858] 0x0 (size_t)
   [RSP+860] 0x0 (size_t)
   [RSP+868] 0x0 (size_t)
   [RSP+870] 0x0 (size_t)
   [RSP+878] 0x0 (size_t)
   [RSP+880] 0x0 (size_t)
   [RSP+888] 0x0 (size_t)
   [RSP+890] 0x0 (size_t)
   [RSP+898] 0x0 (size_t)
   [RSP+8A0] 0x0 (size_t)
   [RSP+8A8] 0x0 (size_t)
   [RSP+8B0] 0x0 (size_t)
   [RSP+8B8] 0x0 (size_t)
   [RSP+8C0] 0x0 (size_t)
   [RSP+8C8] 0x0 (size_t)
   [RSP+8D0] 0x0 (size_t)
   [RSP+8D8] 0x0 (size_t)
   [RSP+8E0] 0x0 (size_t)
   [RSP+8E8] 0x0 (size_t)
   [RSP+8F0] 0x0 (size_t)
   [RSP+8F8] 0x0 (size_t)
   [RSP+900] 0x0 (size_t)
   [RSP+908] 0x0 (size_t)
   [RSP+910] 0x0 (size_t)
   [RSP+918] 0x0 (size_t)
   [RSP+920] 0x0 (size_t)
   [RSP+928] 0x0 (size_t)
   [RSP+930] 0x0 (size_t)
   [RSP+938] 0x0 (size_t)
   [RSP+940] 0x0 (size_t)
   [RSP+948] 0x0 (size_t)
   [RSP+950] 0x0 (size_t)
   [RSP+958] 0x0 (size_t)
   [RSP+960] 0x0 (size_t)
   [RSP+968] 0x0 (size_t)
   [RSP+970] 0x0 (size_t)
   [RSP+978] 0x0 (size_t)
   [RSP+980] 0x0 (size_t)
   [RSP+988] 0x0 (size_t)
   [RSP+990] 0x0 (size_t)
   [RSP+998] 0x0 (size_t)
   [RSP+9A0] 0x0 (size_t)
   [RSP+9A8] 0x0 (size_t)
   [RSP+9B0] 0x0 (size_t)
   [RSP+9B8] 0x0 (size_t)
   [RSP+9C0] 0x0 (size_t)

MODULES:
   XINPUT1_3.dll 0x000000400000
   steam_api64.dll 0x00005E1F0000
   X3DAudio1_7.dll 0x00005E230000
   AHZmoreHUDPlugin.dll 0x01D4BDBD0000
   po3_SimpleOffenceSuppression.dll 0x01D4C4550000
   SkyrimSE.exe 0x7FF6BDB40000
   gameoverlayrenderer64.dll 0x7FFB6D210000
   YesImSure.dll 0x7FFB6D3F0000
   UniqueMapWeatherFramework.dll 0x7FFB6D480000
   UnequipQuiverSE.dll 0x7FFB6D540000
   StormLightning.dll 0x7FFB6D5C0000
   SSEDisplayTweaks.dll 0x7FFB6D610000
   skee64.dll 0x7FFB6D730000
   po3_Tweaks.dll 0x7FFB6D930000
   po3_SpellPerkItemDistributor.dll 0x7FFB6D9F0000
   PapyrusUtil.dll 0x7FFB6DB90000
   No Lockpick Activate.dll 0x7FFB6DD00000
   MoreInformativeConsole.dll 0x7FFB6DD50000
   MCMHelper.dll 0x7FFB6DE30000
   MapMarkerFramework.dll 0x7FFB6DF60000
   HorseStaminaHUD.dll 0x7FFB6E040000
   Fuz Ro D'oh.dll 0x7FFB6E0E0000
   CrashLogger.dll 0x7FFB6E150000
   steamclient64.dll 0x7FFB6E320000
   MagExtender.dll 0x7FFB981A0000
   FixNotesForSkyUI.dll 0x7FFB981E0000
   fiss.dll 0x7FFB98240000
   skse64_1_6_353.dll 0x7FFB98310000
   EngineFixes.dll 0x7FFB984B0000
   tier0_s64.dll 0x7FFB985B0000
   AHZmoreHUDInventory.dll 0x7FFB98870000
   tbbmalloc.dll 0x7FFB988E0000
   vstdlib_s64.dll 0x7FFB98950000
   bink2w64.dll 0x7FFB9B320000
   DP_Extender.dll 0x7FFBA6E00000
   tbb.dll 0x7FFBAF6E0000
   nvspcap64.dll 0x7FFBB06A0000
   skse64_steam_loader.dll 0x7FFBB2950000
   nvwgf2umx.dll 0x7FFBBA6E0000
   DSOUND.DLL 0x7FFBC2160000
   ExATKDataPlugin.dll 0x7FFBC43B0000
   EVLaS.dll 0x7FFBC5580000
   DINPUT8.dll 0x7FFBC6A80000
   MSVCP140_ATOMIC_WAIT.dll 0x7FFBC8060000
   d3dx9_42.dll 0x7FFBC8080000
   usvfs_x64.dll 0x7FFBCB130000
   winmmbase.dll 0x7FFBDA790000
   aswhook.dll 0x7FFBDC660000
   MSVCP140.dll 0x7FFBDED80000
   VCRUNTIME140_1.dll 0x7FFBDFEA0000
   VCRUNTIME140.dll 0x7FFBDFEB0000
   Secur32.dll 0x7FFBE48C0000
   inputhost.dll 0x7FFBEA0A0000
   Windows.UI.dll 0x7FFBEA200000
   textinputframework.dll 0x7FFBECA90000
   XAudio2_7.dll 0x7FFBEDA00000
   nvldumdx.dll 0x7FFBF0EF0000
   dxcore.dll 0x7FFBF2B00000
   dbghelp.dll 0x7FFBF3D80000
   WINMM.dll 0x7FFBF49E0000
   WINHTTP.dll 0x7FFBF4A10000
   drvstore.dll 0x7FFBF5650000
   MMDevApi.dll 0x7FFBF5B70000
   AUDIOSES.DLL 0x7FFBF5E30000
   cryptnet.dll 0x7FFBF6350000
   VERSION.dll 0x7FFBF6580000
   twinapi.appcore.dll 0x7FFBF6B40000
   WindowManagementAPI.dll 0x7FFBF6DA0000
   avrt.dll 0x7FFBF7360000
   PROPSYS.dll 0x7FFBF7C50000
   d3d11.dll 0x7FFBF7DE0000
   wintypes.dll 0x7FFBF8BE0000
   dcomp.dll 0x7FFBF8D40000
   CoreUIComponents.dll 0x7FFBF9300000
   CoreMessaging.dll 0x7FFBF96B0000
   uxtheme.dll 0x7FFBF9AC0000
   resourcepolicyclient.dll 0x7FFBF9BB0000
   dwmapi.dll 0x7FFBF9CB0000
   kernel.appcore.dll 0x7FFBF9FA0000
   windows.storage.dll 0x7FFBFA1A0000
   HID.DLL 0x7FFBFA940000
   dxgi.dll 0x7FFBFA980000
   ntmarta.dll 0x7FFBFAF00000
   rsaenh.dll 0x7FFBFB150000
   UMPDC.dll 0x7FFBFB4C0000
   IPHLPAPI.DLL 0x7FFBFB4E0000
   powrprof.dll 0x7FFBFB5F0000
   MSWSOCK.dll 0x7FFBFB840000
   CRYPTSP.dll 0x7FFBFBA30000
   CRYPTBASE.DLL 0x7FFBFBA50000
   Wldp.dll 0x7FFBFBAE0000
   msasn1.dll 0x7FFBFBC70000
   devobj.dll 0x7FFBFBE50000
   SSPICLI.DLL 0x7FFBFBF70000
   profapi.dll 0x7FFBFBFC0000
   KERNELBASE.dll 0x7FFBFC080000
   gdi32full.dll 0x7FFBFC350000
   ucrtbase.dll 0x7FFBFC460000
   CRYPT32.dll 0x7FFBFC560000
   cfgmgr32.dll 0x7FFBFC6C0000
   bcrypt.dll 0x7FFBFC710000
   win32u.dll 0x7FFBFC740000
   WINTRUST.DLL 0x7FFBFC820000
   bcryptPrimitives.dll 0x7FFBFC890000
   msvcp_win.dll 0x7FFBFC920000
   ADVAPI32.dll 0x7FFBFC9C0000
   combase.dll 0x7FFBFCA70000
   sechost.dll 0x7FFBFCE30000
   SHLWAPI.dll 0x7FFBFCED0000
   SHELL32.dll 0x7FFBFCFB0000
   USER32.dll 0x7FFBFD760000
   imagehlp.dll 0x7FFBFD960000
   msvcrt.dll 0x7FFBFD9A0000
   ole32.dll 0x7FFBFDA40000
   GDI32.dll 0x7FFBFDB70000
   RPCRT4.dll 0x7FFBFDC80000
   MSCTF.dll 0x7FFBFDDB0000
   KERNEL32.DLL 0x7FFBFDED0000
   IMM32.DLL 0x7FFBFDF90000
   SETUPAPI.dll 0x7FFBFDFC0000
   PSAPI.DLL 0x7FFBFE440000
   shcore.dll 0x7FFBFE4E0000
   WS2_32.dll 0x7FFBFE740000
   OLEAUT32.dll 0x7FFBFE7B0000
   clbcatq.dll 0x7FFBFE880000
   ntdll.dll 0x7FFBFE970000

SKSE PLUGINS:
   AHZmoreHUDInventory.dll v2.0.4
   AHZmoreHUDPlugin.dll v5.1.1
   CrashLogger.dll v1
   DP_Extender.dll
   EngineFixes.dll v6.0.2
   EVLaS.dll v1.2
   ExATKDataPlugin.dll
   fiss.dll
   FixNotesForSkyUI.dll v1.2.5
   Fuz Ro D'oh.dll v2.1.6.108
   HorseStaminaHUD.dll v1.0.3
   MagExtender.dll
   MapMarkerFramework.dll v2.0.4
   MCMHelper.dll v1.3.2
   MoreInformativeConsole.dll v1.0.1
   No Lockpick Activate.dll
   PapyrusUtil.dll
   po3_SimpleOffenceSuppression.dll v2.1.1
   po3_SpellPerkItemDistributor.dll v5.2.1
   po3_Tweaks.dll v1.6.0.1
   skee64.dll
   SSEDisplayTweaks.dll v0.5.9
   StormLightning.dll
   UnequipQuiverSE.dll
   UniqueMapWeatherFramework.dll v1
   YesImSure.dll v1.6

PLUGINS:

Mousetick · June 3, 2022

So the game crashes while the gear is spinning in the lower right corner, before displaying the main menu? Or does it crash even before displaying its (initially black) window and spinning the gear?

Crashes at startup are typically caused by:

Missing masters
Incorrect sort order
Corrupt/faulty plugins
Old LE plugins or LE plugins incorrectly ported to SE
Too many plugins
Corrupt/faulty SKSE plugins or DLLs
Failure to initialize DirectX graphics or audio
Interference from 3rd-party software

That Cathedral Weather mod is unlikely to cause crashes on its own, so it must be an interaction with something else which is broken.

Did you perform the Game Launch Test earlier in the guide?
Ensure all plugins are enabled in the right pane of MO2.
Ensure there are no errors reported by MO2 (warning sign in upper right corner).
Ensure you have sorted with LOOT before launching the game.
Ensure there are no errors reported by LOOT.
Load up your entire load order in xEdit, right-click on the Cathedral Weathers plugin and select 'Check for Errors'. Errors found, if any, are displayed in the Messages tab.
If there are no errors, repeat with each plugin, including the 'vanilla masters' that were cleaned at the beginning of the guide.
Examine the log files in Documents/My Games/Skyrim Special Edition/SKSE. Their contents are usually cryptic informational messages but error messages are easier to identify, and would likely appear towards the end of a log file.

7 hours ago, SuperOwen said:

As soon as I disabled Cathedral Weathers and Seasons, the game booted fine.

Ok. But strictly speaking you can't simply disable Cathedral Weathers, as the STEP Lighting & Weather patch depends on it. So I assume you disabled it too, right?

SuperOwen · June 3, 2022

Sorry, I guess I was a bit vague in my initial post!

The game crashes while the gear is spinning in the corner with the Skyrim logo showing in the centre, before displaying the main menu.

Everything was cleaned, as per instruction, and any "dirty" downloaded mods were cleaned also.

I performed the Game Launch Test earlier in the guide, and it all went smoothly.

I've sorted with LOOT multiple times.

The step where it says to enable all plugins had a me a little confused. Does that mean I enable the ones I'd specifically disabled according to the mod install instructions, or just make sure everything apart from those are enabled?

There are 2x errors listed in MO2, one is "there are files in your overwrite directory" and the other is "missing masters" (Elemental_Staffs.esp + Landscape Fixes For Grass Mods.esp + Oakwood.esp + WACCF_Armor and Clothing Extension.esp)

The errors on LOOT are all referring to the missing masters above, which the guide says to ignore?

I loaded Cathedral Weathers in xEdit, and there were no errors

I didn't have the stomach to load all the other plugins in xEdit right now, after checking "Skyrim.esm" and finding 323 errors, but would LOOT point to something being amiss without the need to manually go through each one? If you think it might be the cause, I guess I'd be up for going through them all. If an error is found, what steps would I take to fix them? Are any errors "purposeful", as the guide suggests to ignore LOOT errors. Would the same thing apply here?

Quote

16 hours ago, SuperOwen said:

As soon as I disabled Cathedral Weathers and Seasons, the game booted fine.

Ok. But strictly speaking you can't simply disable Cathedral Weathers, as the STEP Lighting & Weather patch depends on it. So I assume you disabled it too, right?

I admit, I just disabled Cathedral to try and find a reason for the CTD, and didn't disable anything else. I didn't attempt to start a new save or anything either.

If it comes to it, what would be the best method for going through all the steps again? Is it a simple case of going through my downloads list and reinstalling everything? Or am I best off purging everything and starting from scratch?

I appreciate your input!

Mousetick · June 3, 2022

1 hour ago, SuperOwen said:

The step where it says to enable all plugins had a me a little confused. Does that mean I enable the ones I'd specifically disabled according to the mod install instructions, or just make sure everything apart from those are enabled?

It means to make sure every plugin that is listed in the right pane is enabled (checked), and just these ones. Don't enable those which were specifically skipped or excluded on the left pane, during the mods installation.

1 hour ago, SuperOwen said:

There are 2x errors listed in MO2, one is "there are files in your overwrite directory" and the other is "missing masters" (Elemental_Staffs.esp + Landscape Fixes For Grass Mods.esp + Oakwood.esp + WACCF_Armor and Clothing Extension.esp)

These "missing masters" errors are a serious problem and are likely the cause of your crash. As I mentioned before at the top of my previous post, missing masters are the main cause of crashes at startup. A missing master means that a plugin depends on another plugin which is not enabled in the right pane of MO2. It may not be enabled in the right pane of MO2 because its checkbox is not ticked in the list on the right pane, or because it's not enabled in the list on the left pane, or because it's excluded (moved to optional) on the left pane, or simply because it's not installed at all (on the left pane).

So your first order of priority is to fix that problem. You can use MO2 or LOOT to figure out which master(s) is(are) missing. I'd suggest LOOT as it may be a little easier to read. Make note of the name of the plugin master(s) that are reported by LOOT as missing and report them back here so we can tell you how to correct them if you can't figure it out. You probably forgot to install one or more mods on your way through the guide.

Example:

1 hour ago, SuperOwen said:

The errors on LOOT are all referring to the missing masters above, which the guide says to ignore?

The guide specifically says "Ignore any reported missing compatibility patches or other warnings." It doesn't say "Ignore any errors".

BAD, BAD, BAD:

The error count in LOOT should be zero at all times, and the warning sign icon in the upper-right corner of MO2 should be greyed out at all times. If not, you need to stop and correct those errors before continuing or doing anything else.

1 hour ago, SuperOwen said:

I didn't have the stomach to load all the other plugins in xEdit right now, after checking "Skyrim.esm" and finding 323 errors, but would LOOT point to something being amiss without the need to manually go through each one? If you think it might be the cause, I guess I'd be up for going through them all. If an error is found, what steps would I take to fix them? Are any errors "purposeful", as the guide suggests to ignore LOOT errors. Would the same thing apply here?

1 hour ago, SuperOwen said:

If it comes to it, what would be the best method for going through all the steps again? Is it a simple case of going through my downloads list and reinstalling everything? Or am I best off purging everything and starting from scratch?

Please try to be patient and stay focused. We have no way of knowing what's causing your crashes based on the information you provided. The list of tasks I gave you previously was a troubleshooting checklist to try and narrow down the possible causes and perhaps identify the culprit.

Ensure there are no errors reported by MO2 (warning sign in upper right corner).

You could have stopped right there at that step, since there were errors. There was no need to proceed further down the checklist. Sorry I didn't explain this earlier.

Hope this helps. Don't hesitate to ask if something isn't clear.

z929669 · June 4, 2022

3 hours ago, SuperOwen said:

There are 2x errors listed in MO2, one is "there are files in your overwrite directory" and the other is "missing masters" (Elemental_Staffs.esp + Landscape Fixes For Grass Mods.esp + Oakwood.esp + WACCF_Armor and Clothing Extension.esp)

Ditto everything Mousetick has mentioned in great detail.

If you have this MO warning flag, then you did not follow the guide instructions carefully enough to avoid this and the missing masters issues.

Revisit the Tools setup instructions. Be certain to expand all + Spoilers in orange text and follow those instructions. Revisit the mods related to the missing masters and reinstall according to the instructions.

Be certain to 'hide' plugins per mod instructions for "Optional ESPs/plugins", and enable mods (left pane) as instructed (default is to always enable a mod in left pane after installing it). Always enable all plugins (right pane) before sorting with LOOT ... always check that none are disabled. Sometimes, reenabling a mod on left doesn't enable the mod's plugin on right.

Lastly, click "Expand" in mod tables at right of each row where you see it to view mod install instructions.

SuperOwen · June 4, 2022

Thank you both!

It appears that I must have missed a couple of things during the install process, as I'd downloaded the mods in question but hadn't installed them. After actually installing the missing mods ( :blush: ), Skyrim boots up fine with everything activated! I put my error down to the stop-start nature of how I've been doing it, I've obviously rushed to install everything since I only have limited time each night. Plus, I wasn't taking the specific wording of the guide literally enough, which is my own fault

The last thing that stumps me now is the files in overwrite directory. The only thing in there appears to be "SKSE/Plugins/Fuz Ro D'oh.ini", which appears to have been created a couple nights ago when I first booted the game after disabling Cathedral. As far as I understand, files are created when booting the game by certain mods? Is Fuz Ro D'oh one of them?

If it has something to do with my tool setup, I was a little unsure about the directions it gives.

Quote

All tools installed in the System Setup Guide should already be configured in MO. Some tools will have been auto-detected and added; nevertheless, ensure the settings below are set correctly for all tools. xEdit is used in this example:

It then proceeds to provide instructions on how to set up xEdit specifically, and then only lists what arguments to supply for the other 3 tools and doesn't make mention of what boxes to tick (like "Create files in mod instead of overwrite") I realise I might be overthinking it, but since I've already made one error, this could be another one! If it doesn't say anything needs ticking, then I don't tick anything? Or do I do as the quote implies and set up each tool exactly the same as xEdit?

Hopefully though, those missing masters were the sole cause for concern, and I can carry on with benchmarking process.

You have both saved me countless nights of trial and error, and I am forever grateful! I apologise for my own ineptitude, ubt please let me know if my tool setup worries are with or without merit.

:bow:

Edited June 4, 2022 by SuperOwen

Greg · June 5, 2022

I think what you are seeing here is standard behavior that also happens in my profile. The first time you run the game after completing the setup, some mods may create new files that go into the Overwrite folder. If it's only "SKSE/Plugins/Fuz Ro D'oh.ini" in Overwrite, you might open Overwrite and drag the SKSE folder to the "Fuz Ro D-oh - Silent Voice" mod. This is easier if you collapse all separators except 09 - Fixes so you don't have to scroll to find "Fuz Ro D-oh - Silent Voice".

I usually check Overwrite every so often and try to move these to the mod they belong to.

z929669 · June 5, 2022

If SKSE and xEdit are set up properly, any xEdit-written files will go into xEdit Output mod (which should always be enabled) or SKSE mod. I never get anything in overwrite under any circumstances.

I think we should add this to the SKSE mod install instructions. I believe I had this in the SKSE64 instructions, but I removed it last Oct at the behest of @TechAngel85 or @DoubleYou or @Greg for some reason. Part of this conversation is the use case for recommending it.

My guess is that some people want notification that files are written out related to SKSE by virtue of getting them in overwrite. Great for people who know what to do with them, but alarming for the less experienced (alarming MO warning icon at top right of MO).

DoubleYou · June 5, 2022

Making them all go into a "SKSE64" mod is worse than having them in Overwrite, IMHO. It isn't intuitive that all game created files be associated with SKSE, and then not know where the files went. Less warnings are not always better. Far better for users to see the warning and learn the reason for them and how to manage them then to have no idea what is going on.

Greg · June 5, 2022

I agree with DoubleYou and I think he worded it much better than what I was trying to write.

SuperOwen · June 5, 2022

Gentlemen, you've been so great in helping me get this sorted, I cannot thank you enough.

I guess I'll stick with my current tool setup then?

I did get started on the benchmarking process last night, and everything seemed fine, so hopefully I'm good to go. I might even be able to push my meagre system to go for the milk-drinker ENB settings after it hit well over 95+ average frames on medium BethINI settings!!

I'll be sure to let you know if I'm successful in the end. This has all been very informative at least, sorry for not paying greater attention to the instructions.

Thank you all for your input!

Mousetick · June 6, 2022

I can't help but throw in my 2 cents on the Overwrite issue Please take a chair... are you sitting comfortably?

The OP's experience is typical and an indication that something is amiss with the guide in its current form. "After completing the guide and launching the game, I've got a MO2 warning and stuff in my Overwrite folder. I've no clue what it is: is it normal, did I do something wrong, what am I supposed to do with it?" is a recurring question. It's a FAQ that I'm fairly certain no one here enjoys answering for the umpteenth time. It's also a bad first-time experience for users.

This particular experience is guaranteed to happen in the guide's current state. It's not an "accident". Don't you think something should be done about it?

DY's and Greg's position, while understandable from an expert user point of view, fails to acknowledge the issue to begin with, and doesn't provide any solution to address it. "Git gud" is not a solution

I think Z's suggestion could be a simple and effective solution, with a touch of tweaking. Using an existing mod (SKSE) as a repository for game files generated at runtime should be avoided. It mixes SKSE with unrelated configuration files. Furthermore, it's "dangerous": in case SKSE is updated/reinstalled by the user, all configuration settings that were stored there are lost. So I'd suggest creating a separate, dedicated (initially empty) mod for that. It could be named "MCM Configuration Settings" to simplify, or something like that. And then configure MO2 for the SKSE launcher to create files in this mod.

I'd bet most users don't care what "Fuz Ro D'oh.ini" is, what its purpose is, or where it should go. Same for all the configuration files dynamically created by MCMs or SKSE plugins at runtime. They don't need to know or be bothered by useless Overwrite "noise": Z's solution takes care of that.

Such a setup makes the Overwrite folder and the MO2 warning sign truly unexpected, unusual, and alarming. Some indication that something is truly wrong. As it should be.

The alternative is to leave everything in the Overwrite folder and let the users sort it out. Fine, why not, but then the guide should explain what the user should expect, what this Overwrite stuff is, and how to manage it. Currently the guide does none of that.

Either way, the current status quo is not acceptable IMO. It's easy to lose track of the end goals. For the vast majority of the guide users, "modding" is a means to an end, which is to play the game, it's not an end by itself. So the more that is done to ease them into reaching their goal while skipping all the technical minutiae, the better - in my book.

6 hours ago, SuperOwen said:

Gentlemen, you've been so great in helping me get this sorted, I cannot thank you enough.

I'm glad you were able to sort out your issues in the end. Sorry for hijacking your topic with our Overwrite "debate"

DoubleYou · June 6, 2022

https://stepmodifications.org/wiki/Guide:Mod_Organizer#Maintaining_a_Clean_Overwrite

I suppose we can just link to this relevant portion of the Mod Organizer guide somewhere near the end.

z929669 · June 6, 2022

17 hours ago, DoubleYou said:

Making them all go into a "SKSE64" mod is worse than having them in Overwrite, IMHO. It isn't intuitive that all game created files be associated with SKSE, and then not know where the files went. Less warnings are not always better. Far better for users to see the warning and learn the reason for them and how to manage them then to have no idea what is going on.

True, but they go to SKSE mod only if they are SKSE-mediated files (they wouls still go into overwrite if not mediated by SKSE). As I said, I suspected this is the reason why you want them in overwrite: so you know when and SKSE-mediated mod produces output. That's fair.

15 hours ago, SuperOwen said:

Gentlemen, you've been so great in helping me get this sorted, I cannot thank you enough.

I guess I'll stick with my current tool setup then?

I did get started on the benchmarking process last night, and everything seemed fine, so hopefully I'm good to go. I might even be able to push my meagre system to go for the milk-drinker ENB settings after it hit well over 95+ average frames on medium BethINI settings!!

I'll be sure to let you know if I'm successful in the end. This has all been very informative at least, sorry for not paying greater attention to the instructions.

Thank you all for your input!

Just stick to the current instructions, and you won't go wrong.

9 hours ago, Mousetick said:

I can't help but throw in my 2 cents on the Overwrite issue Please take a chair... are you sitting comfortably?

The OP's experience is typical and an indication that something is amiss with the guide in its current form. "After completing the guide and launching the game, I've got a MO2 warning and stuff in my Overwrite folder. I've no clue what it is: is it normal, did I do something wrong, what am I supposed to do with it?" is a recurring question. It's a FAQ that I'm fairly certain no one here enjoys answering for the umpteenth time. It's also a bad first-time experience for users.

This particular experience is guaranteed to happen in the guide's current state. It's not an "accident". Don't you think something should be done about it?

DY's and Greg's position, while understandable from an expert user point of view, fails to acknowledge the issue to begin with, and doesn't provide any solution to address it. "Git gud" is not a solution

I think Z's suggestion could be a simple and effective solution, with a touch of tweaking. Using an existing mod (SKSE) as a repository for game files generated at runtime should be avoided. It mixes SKSE with unrelated configuration files. Furthermore, it's "dangerous": in case SKSE is updated/reinstalled by the user, all configuration settings that were stored there are lost. So I'd suggest creating a separate, dedicated (initially empty) mod for that. It could be named "MCM Configuration Settings" to simplify, or something like that. And then configure MO2 for the SKSE launcher to create files in this mod.

I'd bet most users don't care what "Fuz Ro D'oh.ini" is, what its purpose is, or where it should go. Same for all the configuration files dynamically created by MCMs or SKSE plugins at runtime. They don't need to know or be bothered by useless Overwrite "noise": Z's solution takes care of that.

Such a setup makes the Overwrite folder and the MO2 warning sign truly unexpected, unusual, and alarming. Some indication that something is truly wrong. As it should be.

The alternative is to leave everything in the Overwrite folder and let the users sort it out. Fine, why not, but then the guide should explain what the user should expect, what this Overwrite stuff is, and how to manage it. Currently the guide does none of that.

Either way, the current status quo is not acceptable IMO. It's easy to lose track of the end goals. For the vast majority of the guide users, "modding" is a means to an end, which is to play the game, it's not an end by itself. So the more that is done to ease them into reaching their goal while skipping all the technical minutiae, the better - in my book.

I'm glad you were able to sort out your issues in the end. Sorry for hijacking your topic with our Overwrite "debate"

... an even better solution. I agree and will be altering my own setup likewise. "SKSE Plugin Output" is what I'll be calling it, and I will place it right after xEdit Output early in my mod's pane.

Mousetick · June 6, 2022

5 hours ago, z929669 said:

As I said, I suspected this is the reason why you want them in overwrite: so you know when and SKSE-mediated mod produces output. That's fair.

I don't understand. What exactly among the output produced by SKSE-mediated mod would require special attention by the average user?

Please provide a concrete example, based on the guide, that makes redirecting to a mod a bad option compared to Overwrite. I haven't seen a compelling argument. Just a matter of personal preference, old habits, and "RTFM", which don't seem to consider the general experience of common users.

A separate mod for SKSE launcher output is actually more convenient and cleaner, as it separates all these configuration files and doesn't clump them together with Overwrite. Sending them to Overwrite is worse for multiple reasons:

This triggers a warning by MO2 for something that is completely normal and expected.
It creates unnecessary busywork for every single user to repeat the same meaningless menial tasks of sorting out its contents.
It's another opportunity for users to mess up by performing manual tasks.
It forces novice users (and old timers who just forgot how) to RTFM on something they will rarely, if ever, encounter or need, when following the guide.
Most of the files are INI configuration files generated by MCMs. They're not meant to be user-editable.
Most users don't care one bit what these files are, and they don't need to be aware of them.

A case could have been made that .Net Script Framework crash logs would better go into Overwrite, triggering a MO2 warning in the process, than being silently shoved into a mod folder. Or that the NGIO grass cache would better go into Overwrite for "easier" finding and sorting. Neither applies today, so this is moot.

CTD with Cathedral Weathers and Seasons - Help?

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Create an account or sign in to comment

Create an account

Sign in

Similar Content

Recently Browsing 0 members

Important Information