MMMMZZZZWWW Posted February 24 Share Posted February 24 My last requiem playthrough was almost over. It was a smooth 100+ hours of gameplay without any major issues/bugs/crashes. Solstheim was the last destination. Sadly, I was probably missing some meshes or had issue with Dyndolod (not sure) that caused crashes when I approached Miraak's temple. So here's what I did. Downloaded the latest Requiem and Dyndolod resources and dlls. Reinstalled the Soltheim AIO mod. Disabled the Simple Snow Improvement - Solstheim Ruins mod. Regenerated Dyndolods. Now, my old save CTD immediately after loading (which isn't too bad considering I was about to start a new game anyway.) But the new game also crashes after around 10 seconds after I made the Alternate Life choices. Everything's normal if I don't leave that prison cell. I'd appreciate some help with pinpointing the culprit. Cheers! 2025-02-24-21-22-00.log Link to comment Share on other sites More sharing options...
ZeroOblivion27 Posted February 24 Share Posted February 24 (edited) the error happened around memory address 0x7FF61EF50DCF The specific cause isn’t clear from this log, but i can see some memory operations and function calls happening just before the crash. It’s likely that there was an issue related to some in-game objects (TESObjectREFR and TESQuest are mentioned), which may have caused an invalid memory access or unhandled operation. The registers show the values that were being held in memory at the time of the crash. In this case, several pointers (addresses in memory) are stored in the registers (TESObjectREFR, TESQuest, etc.), which point to game objects or structures. The stack trace is a sequence of function calls (mov and lea instructions are mentioned), which shows how the program was executing leading up to the crash. It includes functions responsible for managing quests and possibly in-game references (TESQuest, TESObjectREFR). What happened was Skyrim was performing an operation related to quests or objects in the game (like referencing an object or handling a quest), but it hit an error while doing so. The game tried to access memory that it shouldn't have, causing the crash. Edited February 24 by ZeroOblivion27 1 Link to comment Share on other sites More sharing options...
Hietanen Posted February 24 Share Posted February 24 You need to install Crash Logger SSE for this one, since Trainwreck is not detailed enough to give any specific crash details. https://www.nexusmods.com/skyrimspecialedition/mods/59818 1 Link to comment Share on other sites More sharing options...
MMMMZZZZWWW Posted February 25 Author Share Posted February 25 6 hours ago, Hietanen said: You need to install Crash Logger SSE for this one, since Trainwreck is not detailed enough to give any specific crash details. https://www.nexusmods.com/skyrimspecialedition/mods/59818 Here you go. Hope this is clearer. Thank you. https://pastebin.com/1gNhWtce Link to comment Share on other sites More sharing options...
MMMMZZZZWWW Posted February 25 Author Share Posted February 25 9 hours ago, ZeroOblivion27 said: the error happened around memory address 0x7FF61EF50DCF The specific cause isn’t clear from this log, but i can see some memory operations and function calls happening just before the crash. It’s likely that there was an issue related to some in-game objects (TESObjectREFR and TESQuest are mentioned), which may have caused an invalid memory access or unhandled operation. The registers show the values that were being held in memory at the time of the crash. In this case, several pointers (addresses in memory) are stored in the registers (TESObjectREFR, TESQuest, etc.), which point to game objects or structures. The stack trace is a sequence of function calls (mov and lea instructions are mentioned), which shows how the program was executing leading up to the crash. It includes functions responsible for managing quests and possibly in-game references (TESQuest, TESObjectREFR). What happened was Skyrim was performing an operation related to quests or objects in the game (like referencing an object or handling a quest), but it hit an error while doing so. The game tried to access memory that it shouldn't have, causing the crash. Thank you for the detailed reply. I'm still at loss what my next step is to fix the issue though. But thanks for the help! 1 Link to comment Share on other sites More sharing options...
Hietanen Posted February 25 Share Posted February 25 Yes the Crash Logger SSE log was a lot clearer, and it shows that the mod "cctwbsse001-puzzledungeon.esm" is crashing with an object reference none. This can happen if you use an outdated version of this mod, so time to update your creation club content and download the newest versions. Link to comment Share on other sites More sharing options...
ZeroOblivion27 Posted February 25 Share Posted February 25 (edited) 28 minutes ago, Hietanen said: Yes the Crash Logger SSE log was a lot clearer, and it shows that the mod "cctwbsse001-puzzledungeon.esm" is crashing with an object reference none. This can happen if you use an outdated version of this mod, so time to update your creation club content and download the newest versions. The puzzle dungeon has always been a bit tricky for me, even with the latest versions, so I tend to avoid it. Edited February 25 by ZeroOblivion27 Link to comment Share on other sites More sharing options...
Recommended Posts