Dragon_Nexus Posted July 8, 2021 Posted July 8, 2021 I recently gave up trying to fix a previously modded version, removed everything, reinstalled the game and did everything from scratch using pretty much only the mods I knew of that worked. Relatively basic stuff. I'm still getting CTDs. I solved the infinite loading issue with another mod I'd forgotten to reinstall but I'm on a new game in Windhelm, started in the dark elf section, if I go up the left or right set of stairs from there, the game CTDs. Same spot every time. I *think* there's an NPC setting it off? Once I stood at the bottom of the stairs talking to another NPC and it CTD'd during the conversation. Â Looking up on the stability guide, it sounds like it's a missing mesh issue if it keeps happening in the same place. Problem is I don't know how to diagnose that, how to find which mesh might be causing it and how I can fix it. I've included my load order in case anyone can spot a common culpret. Â I've done the cleaning thing on Skyrim's main files, I've done Bodyslide and Fores New Ideas, all the basic stuff. Â Any help appreciated. LOOT Order.txt
Dorabella Posted July 8, 2021 Posted July 8, 2021 31 minutes ago, Dragon_Nexus said: Looking up on the stability guide, it sounds like it's a missing mesh issue if it keeps happening in the same place Both the Papyrus log and the Crash fix could give you some clues  You may find that you miss Babo Dialogue, as it happened to me. Despite any support program (LOOT and / or other) did not detect it, despite the mods, they did not place it in the mandatory reuisiti, I had a CTD always in the same way, babo Dialogue installed, problem solved  Generally, papyrus refers to scripts but, it is not excluded that it may mention the offending mod Crash fix , it might also give you some clues although, very often it refers to codes
Mauserl Posted July 8, 2021 Posted July 8, 2021 Windhelm is notorious for CTDs. So I don't think it's an NPC...  I installed several texture replacers and some beautification mods like JKs and seem to be safe now, but I have no idea what caused my Windhelm CTDs in the first place. UPDATE: you might also want to look at this thread: https://forums.nexusmods.com/index.php?/topic/718451-ctd-when-looking-to-the-east-while-in-windhelm/#entry6081980  Windhelm is superbuggy, it also has a bugged side quest :  Be sure to visit the White Vial shop as early as possible and start the quest there or the shop might just close and the quest will never be able to be finished.
tzenrick Posted July 8, 2021 Posted July 8, 2021 NetScriptFramework has more crash logging. It might help point to to whats causing the issue as well.
Dragon_Nexus Posted July 9, 2021 Author Posted July 9, 2021 I don't have the Archetecture folder to delete meshes from (since I haven't installed any mods that change the graphics). I tried Babo Dialogues but for some reason that made the crash happen faster. So I removed that, Horrible Harassment and Approach entirely. Crash still happens in the same place. Â I tried finding NetScripeFramework but I can only find it for the SE version, and I'm on LE. Â The game is setup to make mini dumps, but I always get an error trying to read them. "It may be corrupt or in a format not understood by the debugger". I probably set it up wrong. I've included my latest one if anyone's able to ready and understand it. 2021-07-09_01.48.53.dmp
Mauserl Posted July 9, 2021 Posted July 9, 2021 My editor says that file is empty, guess it does not have time to dump anything before it crashes.
Elizinator Posted July 10, 2021 Posted July 10, 2021 if youre using MO2, sometimes NetScriptFramework just plain doesnt generate a crash log. its a known issue without a known solution. what ive found often helps with that is simply closing mod organizer and restarting. if it is a mesh issue, .netscriptframework crash log should name and shame it
Dragon_Nexus Posted July 13, 2021 Author Posted July 13, 2021 I'm using Vortex. Is there a version of netscriptframework for LE or is it an SE only thing?
Recommended Posts
Archived
This topic is now archived and is closed to further replies.