Game crashing as soon as the main menu appears

[Deleted18816929User]

I've only installed a few mods from Nexus (37 mods)and now my game crashes instantly, I recently disabled all of my

steam workshop mods I used to have installed (except 1). My game can't even be on the main screen for more than a

second without crashing (yes, I actually timed this and took me way to long to get the time). Mod list below.

 

Aemer's Refuge

360 Walk and Run Plus

Fores New Idles in Skyrim - FNIS - FNIS Behavior V6_3

XP32 Maximum Skeleton Extended

Digitigrade Beast Races Full DLC Edition - Digitigrade Beast Race Feet v1_1

Open Cities Skyrim

VioLens

Realistic Water Two

Vivid Weathers

Alternate Start

Hearthfire multiple adoptions

Realistic Ragdolls and Force

Campfire - Complete Camping System

ELFX

Immersive Citizens

Point The Way

The Joy of Perspective

The Joy of Perspective - Joy of Perspective v2 - Female - Compatible Skeleton - CBBE - UNPB - CHSBHC - Beta

Wet and Cold

NetImmerse Override

CBBE

Feminine Argonian and Khajiit Textures

Masculine Argonian and Khajiit Textures (SoS Full Edition)

SMIM

USLEP (Unofficial Skyrim Legendary Edition Patch

The Paarthurnax Dilemma

Imperious - Races of Skyrim

Racial Body Morphs

Racial Body Morphs for Imperious

SoS (Yes, I'm shameless)

RaceMenu

SkyUI

Enhanced Blood Textures

Zim's Immersive Artifacts

 

I have a feeling that the reason why my game crashes is that I either have a bunch of incompatible mods or I'm missing

some required mods. If you're wondering, yes I used LOOT. Help anyone?! (No, this is not the load order LOOT set)

Edited September 15, 2017 by Guest

[Shadeybladey]

Crashing before load screen usually means you have references in your setup to mods that no longer exist on your system, such as the Workshop mods or others you removed. When the engine tries and fails to find them, it crashes to desktop.

 

It could also be due to mod dependencies being missing (IE, a mod you have requires another mod to run).

 

 

There is a hidden folder (under Windows 7 Home Premium 64 bit):

 

C:\Users\UserName\AppData\Local\Skyrim

 

This contains (usually) four text files:

 

* SteamModList.txt (empty, as we never download mods from Steam Workshop)

* DLCList.txt (an unsorted list of all the mods you have, but not Skyrim.esm or Update.esm)

* plugins.txt (a sorted list on my machine, including Update.esm but not Skyrim.esm)

* loadorder.txt (a sorted list, including both Update.esm and Skyrim.esm)

 

 

 

Your problem is most often due to one or more of the above files still having a mod listed that is not on your machine. Say, you removed a mod and did not re-run Loot.

 

Or it may have the same mod listed twice.

 

Search for the AppData folder

mark it as not hidden

make a shortcut on your desktop so you can find it again

delete those four files

re-run the Vanilla launcher

tick the mods you want to use to recreate DLCList.txt (IIRC)

close down the launcher

run LOOT

launch the game with the SKSE Launcher.

 

Alternatively, you could manually read through the files and delete one instance of anything that is listed twice, or delete anything that you know you have removed and don't want to run.

 

Don't run the Vanilla launcher ever again as it will reorder things. I have a separate desktop shortcut called SKSE Skyrim to avoid this.

 

I do not use Mod Managers (so I can't help with NMM or MO) and I still prefer BOSS plus manual sorting as I find LOOT to be error-prone.

 

 

 

Then, make sure that you have:

 

* Skyrim Legendary Edition installed

* Latest version of USLEP

* Latest version of all Arthmoor's mods for LE (Alternate Start, Paarthurnax etc. I'd also highly recommend Run for Your Lives and When Vampires Attack)

* Latest version of SkyUI for Skyrim LE

* Latest version of SKSE for Skyrim LE

 

Checking the versions of your other mods won't hurt, either, and you could check for any dependencies while you are at it, although Nexus always tells you any required mods when you download one.

 

 

You cannot use the Unofficial patches for one version of the game with a different version (Vanilla, Vanilla+DLC, LE or SE) and, similarly, many mods are designed for one version of the other.

 

EG, If you have Skyrim LE then you are fine with USLEP.

 

If you have Vanilla, you need USKP, not USLEP.

 

If you have Vanilla + Dragonborn + Dawnguard but not Hearthfire, you'd need USKP + UDBP + UDGP

 

If you have Skyrim Second Edition, you'd need USSEP.

 

 

Good Luck.

 

 

:smile:

[Deleted18816929User]

Crashing before load screen usually means you have references in your setup to mods that no longer exist on your system, such as the Workshop mods or others you removed. When the engine tries and fails to find them, it crashes to desktop.

 

It could also be due to mod dependencies being missing (IE, a mod you have requires another mod to run).

 

 

There is a hidden folder (under Windows 7 Home Premium 64 bit):[/size]

 

C:\Users\UserName\AppData\Local\Skyrim

 

This contains (usually) four text files:

 

* SteamModList.txt (empty, as we never download mods from Steam Workshop)[/size]

* DLCList.txt (an unsorted list of all the mods you have, but not Skyrim.esm or Update.esm)

* plugins.txt (a sorted list on my machine, including Update.esm but not Skyrim.esm)

* loadorder.txt (a sorted list, including both Update.esm and Skyrim.esm)

 

 

 

Your problem is most often due to one or more of the above files still having a mod listed that is not on your machine. Say, you removed a mod and did not re-run Loot.[/size]

 

Or it may have the same mod listed twice.[/size]

 

Search for the AppData folder[/size]

mark it as not hidden[/size]

make a shortcut on your desktop so you can find it again[/size]

delete those four files[/size]

re-run the Vanilla launcher[/size]

tick the mods you want to use to recreate DLCList.txt (IIRC)[/size]

close down the launcher[/size]

run LOOT[/size]

launch the game with the SKSE Launcher.[/size]

 

Alternatively, you could manually read through the files and delete one instance of anything that is listed twice, or delete anything that you know you have removed and don't want to run.

 

Don't run the Vanilla launcher ever again as it will reorder things. [/size]I have a separate desktop shortcut called SKSE Skyrim to avoid this.[/size]

 

I do not use Mod Managers (so I can't help with NMM or MO) and I still prefer BOSS plus manual sorting as I find LOOT to be error-prone.[/size]

 

 

 

Then, make sure that you have:

 

* Skyrim Legendary Edition installed

* Latest version of USLEP

* Latest version of all Arthmoor's mods for LE (Alternate Start, Paarthurnax etc. I'd also highly recommend Run for Your Lives and When Vampires Attack)

* Latest version of SkyUI for Skyrim LE

* Latest version of SKSE for Skyrim LE

 

Checking the versions of your other mods won't hurt, either, and you could check for any dependencies while you are at it, although Nexus always tells you any required mods when you download one.

 

 

You cannot use the Unofficial patches for one version of the game with a different version (Vanilla, Vanilla+DLC, LE or SE) and, similarly, many mods are designed for one version of the other.

 

EG, If you have Skyrim LE then you are fine with USLEP.

 

If you have Vanilla, you need USKP, not USLEP.

 

If you have Vanilla + Dragonborn + Dawnguard but not Hearthfire, you'd need USKP + UDBP + UDGP

 

If you have Skyrim Second Edition, you'd need USSEP.

 

 

Good Luck.

 

 

:smile:

Ihave more than those 4 files, I actually have 8 files, I have the 4 files you listed but then I have other files called

 

loadorder.backup.nmm

loadorder.nmm.bak

plugins.backup.nmm

plugins.nmm.bak

 

What do I do with these?

[Shadeybladey]

Those look like they are part of the Nexus Mod Manager setup.

 

I never use Mod Managers as I prefer to install manually, but the presence of those files could possibly cause all the issues I have seen people complain of, such as NMM re-downloading mods they have removed, insisting on re-installing things etc.

 

In your case, they may still be pointing to mods that you have removed, or possibly have no effect on your CTD at all if the mods they include are correct.

 

 

First, I would suggest proceeding as in my first post and see if that works (I'm assuming you will not have to let NMM actually download and install them all again - I would hate that).

 

 

If you still CTD, I would suggest moving them to a separate folder, such as NMMBAK, in a separate location and see if NMM creates correct versions.

 

Alternatively, you could copy them to a separate folder as a backup, examine the contents of the originals for duplicates or errant mods and then either delete the contents or delete the files. NMM should then recreate them according to the mods you choose to have.

 

But, as I say, I have no real experience of using NMM, so you might want input from someone who does.

 

 

To read the files, you'll have to make Windows open *.nmm and *.bak files with Notepad or similar text editor.

 

:smile:

 

 

 

 

[Kapteyn]

It could also be due to a load order discrepancy. For example, if you have a patch for a mod then it needs to go below the master in the load order, otherwise you are very likely to get an insta-desktop. The same can apply to any mod which requires a separate one, usually the mod page will tell you and ideally the download prompt will as well.

 

I'm going to assume you have Legendary Edition because you have stuff which needs the DLC. Now, if that is your actual load order (as opposed to being a randomly ordered list) then you need to place the unofficial patch immediately after the DLC (or at least after any ESM files which a mod manager might force to the top).

 

As for those backup files, you can just ignore those because they won't be loaded. Or you can delete them, it doesn't really matter. Also, "bak" literally means "backup", lots of programs will use that extension when it overwrites a configuration file - they're there to fall back on if needed, they don't do anything just by sitting there.