Modding & Load Order / The Elder Scrolls V: Skyrim Special Edition / Creation Engine

Skyrim SE: Fixing Plugin Load Order, SKSE, and CTDs

A modern load-order and SKSE checklist for Skyrim Special Edition crashes at the main menu and during a save load.

Official Steam Store header artwork for The Elder Scrolls V: Skyrim Special Edition.

Skyrim crashes are often blamed on the load order when the actual mismatch is an SKSE version, a missing master, or a plugin that requires a different game build.

Fixing Plugin Load Order, SKSE, and CTDs

Verified field fix

The shortest safe order for this issue:

  1. Launch the vanilla game once with no SKSE and no mods to establish a clean baseline.
  2. Match the SKSE build to the exact Skyrim runtime version.
  3. Sort plugins with a conflict-aware tool, not the game’s default order.

The runtime comes first

SKSE is built against a specific Skyrim executable. A mismatch can close the game before a save loads. Check the runtime version and the SKSE build before touching plugins. Then verify that every framework mod supports that same runtime.

%USERPROFILE%/AppData/Local/Skyrim Special Edition/plugins.txt
# Enable only the masters you actually have.
*Skyrim.esm
*Update.esm
*Dawnguard.esm
*HearthFires.esm
*Dragonborn.esm
*Unofficial Skyrim Special Edition Patch.esp
The mod manager writes this file. Do not hand-edit while the manager is open; a missing master causes a startup crash.

A load order is a dependency graph

Missing masters should be fixed, not sorted around. Use a mod manager that shows conflicts and master requirements. Do not use thirty mods as the first test after a patch; add content in small batches and test a save that is not your only copy.

Field notes before you change the build

A The Elder Scrolls V: Skyrim Special Edition mod list is a dependency graph, not a popularity ranking. Confirm that the loader and shared frameworks match the current game build before sorting content mods. A missing dependency can look exactly like a bad load order.

Back up the active profile and a save before disabling anything. If the game starts cleanly with frameworks only, add content back in small batches and test the same menu, dialogue, or world load after each one.

  • Do not mix two mod-manager deployments over the same game folder.
  • Do not delete a content mod without testing a copied save first.
  • Do not paste a load order from a different game build and expect it to be stable.

Check it before you keep it

Launch through SKSE with only the core masters enabled

0 / 5 complete

Keep a known-good profile

Export the working mod list before the next patch. A short, documented stack is easier to repair than a folder full of files whose versions nobody recorded.

The line to keep

Runtime, masters, then content. That order prevents the classic Skyrim CTD before you even reach the title screen.

Did this fix work on Patch 1.6.1179 — Creations runtime?

One click. No account. Your vote is stored in this browser and de-duplicated per file.

Verified against 1.6.1179 — Creations runtime. Votes are local-only telemetry.

The Elder Scrolls V: Skyrim Special Edition: bench questions

2 answers
Why does Skyrim crash before the main menu?
Common causes are an SKSE/runtime mismatch, a missing master, or a bad plugin. Disable mods and test the base runtime first.
Does LOOT fix every load order?
It sorts plugins sensibly, but it does not resolve every script conflict or missing dependency. Read the messages.
Filed under

Modding & Load Order

Patch tested: 1.6.1179 — Creations runtime

This field file was tested against the patch context above. If a launcher update changed your menu labels, include the exact build number in a report to the desk.

Continue the file stack Game hub ↗
Index: Pagefind Type a game, symptom, or tool

    ↑↓ navigate ↵ open GPH / COMMAND SEARCH
    Local profile / hardware telemetry

    My rig

    Stored only in this browser. Game hubs use it to estimate whether your build clears the recommended specification — nothing is uploaded.

    No profile yet. Save once and the masthead, spec pages, and tool prefills follow.

    Telemetry never leaves this browser.