Skyrim
0 of 0

File information

Last updated

Original upload

Created by

Me

Uploaded by

CurseOfTheYears

Virus scan

Safe to use

Tags for this mod

Documentation

Readme

View as plain text

the foolproof method is at the bottom of the guide if that's what your looking for and your CTD is not near Honingbrew meadery and or Whiterun hold.

PROLOUGE :

i have just finally managed to fix a CTD that has been occuring in the vicinity of whiterun particularly near the Honningbrew meadery that has been consistant , it took me more than 10 hours to diagnose the error and i will share with you what i had to do to fix the issue and how you can follow in my footsteps without making the mistakes i did in order to cleanly diagnose the problem and also how to fix it, this is a general guide and will help you overcome most CTDs in the game but more specifically the more complicated issues that arise from having many mods or mods that are specifically problem causing.

in order to solve issues with your mods you need to follow a specific set of steps in order to cover all grounds for potential issues and as there are many you need to do so in an orderly fashion. i will explain everything but i will not go into too much detail, i will keep the steps simple and explain the reasoning behind everything that i recommend in this guide.

i have over 1500 mods compiled in over 20 merges and the entirety of my skyrim installation including the game itself + mods + tools is over 200gbs in size , so you can rest assured that most problems you could be having is more or less covered in this guide , if they are not , at the very least following this guide will narrow down the potential cause for your CTD so that you at the very minimum know what the root of the problem is and can go on from there and try to find a fix even if its not included in this guide.

BEFORE YOU BEGIN :

you must first understand that in order to save time and avoid frustration, you need to be well rested and of sound judgment , if you have been trying to fix a problem for the past 3 hours and you have had no luck but you are hell bent on fixing it , that is not the way , you must take a break , rest your body and your mind , nourish it with food and hydrate yourself before you continue , if you are not in a suitable state of awareness you might miss something that you could have easily noticed otherwise and add easily 10hours+ to the time it takes for you to fix the problem, keep and open mind and remember that the price of modding is non other than your sweat , blood and tears , that is assuming you have already sacrificed your firstborn.

also in my experiance theres no such thing as ''Too many mods crashing my game'' if you are not going above the 255 esp limit and are using the NitPick tool for overcoming the total esp count (hidden+activated) mods and are using Crash fixes and SKSE and ENB memory allocation patches so rest assured the problem most likely is caused by a specific mod in your load order.

GATHERING INFORMATION , PLANNING , EXECUTING THE PLAN :

Common causes of this issue are listed below , do not waste time trying to apply fixes for them before knowing for sure that one of them is causing you the problem , a good mechanic does not apply general repairs before he knows what the problem is , firstly, install CRASH FIXES MOD from nexus as well as SKSE preloader and Apply the settings recommended by Crash fix ENBoost ,specially the part about DataSync options, then ENABLE LOGGING for Crash Fixes , RECREATE your CTD , Check the CRASH FIXES LOG , if it says you ran out of memory , Apply Memory Patches provided by Crash Fixes and SKSE and configure your ENBlocal.ini as recommend in the S.T.E.P guide , in my experiance you CANNOT run out of memory in skyrim unless you don't actually have the physical RAM and VRAM availble on your system provided that you have all the availble memory patches for skyrim installed and working , as of the publication of this guide you DO NOT NEED SSME but you do need to enable the memory allocation patches in SKSE and Crash Fixes, you also DO NOT NEED SAFETY LOAD if you enabled memory patches in the aforementioned, if the error provided in the crash fixes log is not about memory and its something along the lines of ''Address Exception Blah Blah Blah Some Codes" proceed to disable the mods listed below if any of them are in your load order or included in one of your batches or merges ,
PLEASE NOTE that you must disable them completely not just the ESP , if you are using mod organizer then Deactivate them , the point is to make sure none of the files in these mods are not only loaded by the game , but also not availble to the game at all , if you are not using a mod manager , you must completely move the files associated with these mods out of your install directory and move them back later once you have resolved the issue. now start up your game and from the main menu open the console and write Coc Whiterun and walk towards honingbrew meadery and go past it until you reach the whiterun gate using only the ROAD until you eighter crash or get to the gates, if this step did not fix your issue and you still had a CTD , you will know to skip the fixes for the mods below , if however this step DOES fix your issue , then enable them one by one until you figure out which one exactly is causing the issue, then proceed to apply fix for it or simply leave it disabled or remove it if you don't really need it.

-Skyrim Flora Overhaul
Fix : remove the nif file named ''vurt_greenyelplant.nif" that is included in this mod.

-IHSS / Improved horse steps sound (a Skyrim Special edition mod)
Fix : remove the mod.

-All Female Body Mods With Physics
Fix If Bodyslide Output Meshes : Rebuild Bodyslide Meshes , try rebuilding differently as in with different presets
Fix if HDT extention : " Provide if you know one " but note that HDT extention itself has not been known to cause this particular CTD
Fix if Skeleton : Put your Skeleton as the last loaded file in your load order and in your active mods list if using mod managers
Fix if Armor for specific body type : Remove Armor or build the specific bodyslide for the armor again / try building a different preset

-Running out of memory
apply the memory fixes mentioned above, this is just a reminder for you if you didn't read that part.

-Verdant
Fix : remove , '' provide if you know one ''

-JK's Skyrim
Fix : remove and install again , remove permenantly if needed.

-People of skyrim
Fix : reinstall the mod and if it doesn't work , remove it.

-HD trees mod
Fix : reinstall or remove.

-Enchanced Vannila Trees
Fix : reinstall or remove.

-Qaxes Questoriom :
Fix : reinstall or remove.

-safety load :
Fix : enable the OnlyWhenLoading command in the .ini file in safetyload.

-Open Cities :
Fix : reinstall or remove.

-Immersive world encounters :
fix : fix your load order. its a mod conflict issue.

-I Love Cleavage
fix : remove

IF THE ABOVE STEPS DID NOT HELP SOLVE YOUR ISSUE HERE IS A FOOLPROOF method for fixing any possible issue caused by a mod regardless of weather it has to do with honingbrew meadery and whiterun hold or not :

create a text file for yourself , this is your checklist, sort your mods by priority in your mod manager, go to the bottom of your mod manager files load order (P.S : i am not referring to your ESP load order where it says ''plugins'') , now click your last mod (highest number priority which should be at the bottom) , once its highlighted , hold shift , go up 100 mods and click, this will select your last 100 mods , now right click and disable selected , now check the mod manager for missing masters errors that it may give you , now disable the mods that are missing masters (because you just disabled those masters) AND MOVE THEM TO THE BOTTOM OF YOUR LIST (if mod organizer , right click them and Send To Bottom) , run your game and see if the CTD happens , if it does , exit , if the ctd does not occur , run your game a second time to double check if the ctd is resolved , once you do a double check and the ctd does not occur at any point in this procedure , record in the text file you created , the range of the mods by priority number which were causing the CTD for example i recorded my checklist like this :

''1500-1400 CTD'
''1400-1300 CTD"
"1300-1200 CTD"
"1200-1100 CTD STOPPED" ------> CTD is caused by a mod between priority 1200 to 1100

next disable half of those 100 mods and check for CTD , twice.
next disable half of those, and half , and half , and so on until you find the exact mod causing the issue, next eighter remove that mod or search for a fix to its CTD.

Note that if at any point you stopped crashing BUT your CTD was NOT caused by ANY of the 100 mods in the range of mod priority that you stopped crashing in then your CTD is caused by one of the mods you disabled because it required one of the mods you were disabling in batches of 100 as a master, therefor you must go to the bottom of your load order which you send those mods to and start testing those mods in batches of half to see which one was causing the issue.

this is time consuming but it is foolproof.