Crash fixes

Skyrim Mods |

Crash fixes

Fixes some of the crashes in Skyrim.

Made a plugin to help try and fix some of the crashes. You can turn each individual fix on / off in the SKSE/Plugins/CrashFixPlugin.ini, default settings recommended but if you have problems with something and you know what you’re doing you can change. If you want to see exactly what crashes are fixed (with addresses) and a small explanation of my best understanding of the crash then check the INI file or readme on the nexus mod page.

This plugin is meant to fix some common crashes AFTER you have followed STEP guides and sensible modding rules! It does not fix problems that come from modding irresponsibly or conflicts between mods.

How to use the memory allocator patch?
1. Open CrashFixPlugin.ini and find “UseOSAllocators=0”
2. Change it to “UseOSAllocators=1”
3. Download and install SKSE Plugin Preloader
4. Start game, if you get an error saying that memory patch could not be applied read the message for help, otherwise you’re good to go.
(5.) Causes game to crash and you use ENB? Set ExpandSystemMemoryX64=false in enblocal.ini
(6.) Causes game to crash more frequently (especially with UNP RaceMenu sliders)? Try AlignHeapAllocate=1 in CrashFixPlugin.ini

Tips for additional stability:
(These are things I’ve observed and Not 100% fact!)

If you don’t have some lines listed below in your INI it means they are set to default value.

Data/SKSE/SKSE.ini (not needed if UseOSAllocators=1 in CrashFixPlugin.ini):

Set DefaultHeapInitialAllocMB:Memory to 768. If you are using a lot of mods or higher uGrid than 5 then set 1024. Helps with CTD during save load, especially if you can load the save after qasmoke. Max value is 1280. If you are using ENB you may get CTD on startup with higher value than 768 and ExpandSystemMemoryX64 true in enblocal.ini!
Set ScrapHeapSizeMB:Memory to 256. Game can’t use more than 256 of this and setting higher serves no purpose.

Skyrim.ini:
uExterior Cell Buffer:General – setting this too high causes crashes more, especially when game wants to unload many cells at once. If you set 0 or just remove it from your INI then game decides this and that’s the best way.
bPreemptivelyUnloadCells:General – setting this 1 will mean game purges cell buffers and unload cell whenever it is possible. Default is 0 which means keep cell in memory until we need the space for other cells. I find 0 to be better, there’s no reason to unload cell immediately, the buffer was implemented for a reason.
fPostLoadUpdateTimeMS:Papyrus – setting higher will cause longer loading. Mine is 500, seems to work well for me. You can try 750 or even 1000+ if you have a lot of script-heavy mods.
fUpdateBudgetMS:Papyrus – remove (this sets to default 1.2). If you have a lot of script heavy mods and a good PC you can set higher for example 2.0, however this can reduce your FPS when a lot of things are happening.
fExtraTaskletBudgetMS:Papyrus – remove (this sets to default 1.2). See above.
bEnableLogging:Papyrus – set 0. There’s no reason to log papyrus unless you are developing a mod. Writing to file constantly is not good for performance. Papyrus logs have nothing to do with finding causes for crashes, although you can use this to find misbehaving mod scripts which can be helpful, I’d recommend to disable it for normal gameplay though.
bEnableTrace:Papyrus – set 0. See above.
Any other papyrus setting – delete. Changing the papyrus from default will just cause instability or lagged scripts.
iPresentInterval:Display – VSync enabled or disabled. You shouldn’t need to change this as default value is 1 and that’s good.

Safety Load (not needed if UseOSAllocators=1 in CrashFixPlugin.ini):
Install Safety Load if you have a infinite loading screen or freeze at any point. It fixes a bug in memory allocation that causes deadlock. Yes you still need this if you have SKSE memory patch, no they don’t do the same thing. SKSE memory patch hides the problem of deadlock for longer because it allocates a larger memory block. If you don’t have freeze or infinite loading screen at all then you don’t need this!

Stable uGridsToLoad:
Don’t use this. It causes memory corruption and does nothing unless you are changing your uGridsToLoad setting in INI often (I don’t know why you would).

ENB:
I’m not an expert in ENB, but these two I recommend in enblocal.ini:
ExpandSystemMemoryX64=false
ReduceSystemMemoryUsage=true

Bashed Patch:
You should make this. It helps resolve a lot of conflicts between mods, especially related to leveled lists which can be a big problem. If there are no conflicts this doesn’t really do any harm but even a small mod list usually has some.

LOOT:
LOOT can be a good tool to help resolve issues with ordering, but it is not perfect, sometimes it places mods incorrectly, use your best judgement. LOOT can also warn you about other potential problems with mods.

TES5Edit cleaning:
Do this! LOOT can tell you which mods need cleaning.

Playthrough:
Don’t install or uninstall mods (with ESP files) in the middle of playthrough. Even changing the order can be very bad, especially if you use bashed patch or anything with SkyProc (requiem, perkus maximus). This of course applies to ESP files! Graphics mods and pure SKSE plugins are fine most of the time.

Common issues:
UseOSAllocators=1 and crashing when touching sliders in character creation or otherwise.
Set AlignHeapAllocate=1 in CrashFixPlugin.ini, downside is increased load time and increased memory usage.

UseOSAllocators=1 and crashing on game startup or loading save or shortly after.
Set ExpandSystemMemoryX64=false in enblocal.ini

Game says message box “running out of memory” and crashes.
Set ReduceSystemMemoryUsage=true in enblocal.ini

Ground textures flickering weird.
Set ExpandSystemMemoryX64=false in enblocal.ini


Author: meh321
This content was uploaded by website visitors. If you notice any mistake, please let us know.



Useful Information:

You may also like...

Leave a Reply

Your email address will not be published. Required fields are marked *