The Elder Scrolls V: Skyrim — How to Fix "Crash on startup with mods"
What causes the Crash on startup with mods error in The Elder Scrolls V: Skyrim, and the fixes in the order that works.
Last updated 2026-09-25 · evergreen reference
The "Crash on startup with mods" failure in The Elder Scrolls V: Skyrim has a specific cause, and knowing it saves you from working through a dozen unrelated fixes. This page covers what the error actually looks like, why it happens, and the fixes ranked by how often they work.
What the error looks like
Confirm you are dealing with the same failure.
Recognising "Crash on startup with mods"
Skyrim closes at launch or at the main menu, typically after installing or updating mods.
Why it happens
The cause determines the fix.
Cause 1
An SKSE version mismatch — an engine fix, address library or DLL plugin built for a different game runtime than the one you have installed.
Cause 2
A missing master file or a corrupted texture being loaded at startup.
Cause 3
ENB or ReShade conflicting with each other or with a lighting mod.
Cause 4
Physics instability from an unlocked frame rate, which can crash before the menu on high-refresh displays.
Fixes, in the order that works
Cheapest and most reversible first.
Match SKSE and the address library to your exact version
Check your game version, then install the matching SKSE build, Address Library and every DLL plugin. Launch through SKSE’s executable, not the vanilla launcher.
Install the four stability patches
Unofficial Skyrim Special Edition Patch, SSE Engine Fixes, SSE Display Tweaks and .NET Script Framework. The last one also produces crash logs that name the actual problem.
Disable ENB or ReShade and test
Rename or remove the ENB files and any ReShade DLLs temporarily, then test the same startup. Update them or try a different preset if that is the cause.
Cap the frame rate to 60
Skyrim’s physics engine breaks above roughly 60 FPS. Use your GPU control panel or a display tweak mod, and do not stack several frame limiters at once.
Sort with LOOT and clean dirty edits
LOOT orders your load automatically; SSEEdit cleans dirty edits in older mods. Both prevent a large share of otherwise unexplainable startup crashes.
How to confirm it is fixed
One successful launch is not proof.
Retest properly
Start a new game in addition to loading a save. If a new game works and your save does not, the save has orphaned scripts from a mod you removed — not an installation problem.
If none of this works
What to do after the list is exhausted.
Gather evidence before asking
Collect your crash log, a DxDiag and the list of fixes you already tried. For The Elder Scrolls V: Skyrim, support will ask for all three, and a report with evidence gets a far better response than "it crashes".
Reinstall last, not first
A reinstall is the most time-consuming fix and repairs the same files that verification and cache repair handle in minutes. Try it only after the targeted fixes above have failed.
Related pages
This is an independent player reference and is not official documentation for The Elder Scrolls V: Skyrim. GameRulePro does not host or link to copyrighted assets. Modding guidance is for single-player use only — never use mods in online multiplayer. Verify current requirements, prices and policies with the publisher before acting.
Keep fixing
Can I run it? FPS calculator
Check whether your hardware, not the settings, is the limit.
Open →All fix & optimization guides
Every crash, black-screen and FPS guide we have published.
Open →Game database
System requirements and projected FPS for 335 titles.
Open →Release calendar
Launch dates and platforms for upcoming games.
Open →