MO2 Save Load Crash

[Vilverin]

Okeydokey, so I've had a pretty much hassle free run with MO2, but recently decided to upgrade from the current release of MO2 2.16 to the brand spanking new 2.20beta8 because I wanted to use MO2 with Oblivion and I found out it could force OBSE to load, which I don't think 2.16 could.

 

Well, Oblivion is an awful game and was uncooperative so I had to stick back to dealing with Wrye in order to install mods and such. But after I was done with Oblivion, I decided to load Skyrim SE back up and join the modern world, only for the game to immediately CTD when I attempted to load a save. I hadn't touched SSE since I fuddled around trying to stabilise Oblivion in order to get it to work. Also, every other game I had set up to be managed with MO2 was not making it past the load screen before it CTD'd.

 

Other steam games are still working, as well as non steam games such as Minecraft; so I don't think it could be a memory problem (although I ran a diagnostic to be sure) and I don't think it is DirectX (although I downloaded the runtime again).

 

In order to get Oblivion to run with Wrye, I had downloaded python, and in an attempt to get ENBs to work I had installed an older version of DirectX, which was uninstalled shortly after. Curiously, SSE runs fine through steam itself, as I could start a new game and the game remained stable.

 

I have attempted to run the game through MO2 using a new profile with no mods, reverted back to 2.16, verified the game cache, deleted the ini files, ran mo2 as an admin, removed mods one by one, prayed, installed windows updates, disabled overlays upon overlays, sorted with LOOT over and over, searched the issue for at least three 3 google pages,; but to no avail.

 

I am at my wits end, and I have no idea what could possibly causing this. The only thing I can think of is possibly a problem with the OS but I don't want to think about that yet. If anyone could help me, I will be extremely grateful. Anything you need I will do my best to help.

[Greg]

I guess the first question is can you run SkyrimSE.exe on its own without any mods? You can do this by running Skyrim SE from the start menu or from File Explorer by browsing to Steam/SteamApps/common/Skyrim Special Edition and double clicking on Skyrim.exe. If this crashes, run SkyrimSELauncher.exe, set your video settings again, and then try to run Skyrim SE. What we want to do here is to get the vanilla game running on its own before throwing other complexities into the mix.

 

If this works, try running Skyrim SE from Mod Organizer. Use a vanilla profile without any mods and don't run SKSE at this step. Just verify that the game loads and seems to be working find.

 

If you're good to this point, verify the version of Skyrim SE you have installed is compatible with the version of SKSE you have. It's probably best to just download the latest version, but verify your version is Skyrim matches the one listed on the SKSE page. This is critical because it may crash if you have a different version of Skyim SE.

[Vilverin]

Hiya greg,

Vanilla game, launched through Steam, works fine. New game starts perfectly, this is with SKSE both not running and running alongside.

Vanilla Skyrim, launched through MO2 without SKSE running, gets to the splash screen but a few seconds into starting a new game, it CTDs. No missing masters either, and SKSE version I'm running is the one for my version of Skyrim (the latest version)

[Vilverin]

Does anyone know what could be possibly causing this? The crashes only occur when I run SkyrimSE with MO2.

[Greg]

You might run LOOT to verify all the plugins in the right pane are in the correct order.

 

You may have bad INI files in your profile. You can remedy this by deleting Skyrim.ini and SkyrimPrefs.ini in your profile folder (something like C:\ModOrganizer\profiles\[profile name] in Portable mode or C:\Users\[username]\AppData\Local\ModOrganizer\[instance name] in Instance mode). You might also consider using BethINI the INI files after you get the game working with Mod Organizer.

 

You can try to add an exception for ModOrganizer.exe to your AntiVirus software in case it is interfering with Mod Organizer's virtual file system.

 

If you are on Windows 10, Windows interferes with Mod Organizer's virtual file system if ModOrganizer.exe or any of the *.dll files are blocked. This one is cumbersome because you'll need to open the Mod Organizer folder with File Explorer, right click ModOrganizer.exe, click Properties, click Unblock, and click OK. You'll also need to repeat this for all *.dll files in the Mod Organizer folder and subfolders. The easiest way to handle this is to download Mod Organizer from Nexus and unblock the file you downloaded before installing it.