Greg

Troubleshooting this issue with 185+ mods will be extremely difficult. Assuming you have all of your mods installed in Mod Organizer, run Mod Organizer and create a new profile and ensure everything except the base game files and SKSE are unchecked in the left pane. This is a new profile so this won't affect anything in your original profile so you can switch back later. If Mod Organizer is in instance mode, it should come up completely empty so you may need to install SKSE to get the scripts. Once this is done and you have a good clean baseline with only the game files and SKSE, try running SKSE from Mod Organizer to see if it works. If this doesn't work, you may want to run BethINI to establish known good INI files to rule out this as a possible cause. If you're still having problems, open the Mod Organizer folder in File Explorer, right click ModOrganizer.exe and click Properties. If you see an Unblock checkbox, check it and click OK. You'll need to do repeat this for all the *.dll files in Mod Organizer folder as well or Windows 10 gets really cranky. If you have any mods installed in the game's Data folder, you should remove them from the Data folder and install them in Mod Organizer

It looks as if you've installed MO2 in the Fallout New Vegas folder and this won't work properly. The virtual file system is known to break when MO2 is installed in the game folder and possibly anywhere in the Steam folder. You should create a separate folder outside the Steam/game paths and outside any folders controlled by UAC (say something like C:\Tools). You may also run into issues with permissions or antivirus software if you have the game installed in the C:\Program Files or C:\Program Files (x86) folder so you might consider moving Fallout NV somewhere else (say C:\Steam).

Have you tried disabling all the mods (except NVSE) to see if you can start the game this way? Assuming this works fine, enable the mods in batches until it crashes to desktop again and then disable a few mods to narrow down the cause.

You may want to report this to the Mod Organizer devs on Discord or Github to see if they can reproduce and fix this issue.

Wrye Bash 307 Beta 3 on Nexus should work fine, but be sure you extract the files from the stand-alone executable download to an empty folder instead of trying to overwrite an existing install. I've had issues with some of the newer versions not working correctly so I'm sticking with the one on Nexus for now.

If you installed Windows 10 fresh, you need to install the June 2010 DirectX 9 runtime using the link in the "Install" section of the ENBoost guide: https://wiki.step-project.com/ENBoost You can also find some instructions for installing DirectX in the LOTD guide: https://wiki.step-project.com/User:Darth_mathias/SRLE_Extended_Legacy_of_The_Dragonborn_Prerequisites Check the properties of TESV.exe, SkyrimLauncher.exe and skse_loader.exe (File Explorer, select the file, right click, Properties) and disable Compatibility mode if it is enabled. Enabling compatibility mode for any of these three executables is known to cause a CTD with this error code so you need to ensure compatibility mode is disabled for all of them.

This is a Steam error so you'll need to figure out why Steam isn't working properly. If you have Steam running on multiple computers (say a desktop and a laptop) using the same account, you might close Steam on all but one to see if it starts working again. You might also try rebooting.

Did you get 307.2018.731.1531 from Nexus or github? The 307 Beta 3 version I downloaded from Nexus (307.2018.704.57) seems to be working fine, but one of the builds I downloaded from github had much the same issue.

I think one of the mods in STEP:Extended already sets the crime alarm distance, so you don't need to do it in the bashed patch as well.

This happens on my system as well, although in my case it usually opens and sorts the load order on the second or third run from Mod Organizer 2. I don't remember if I had this issue with Mod Organizer 1 and it's been probably a year or two since I used this one.

Note that where Mod Organizer stores downloaded files depends on how you configure Mod Organizer. If you install Med Organizer and select Instance mode, the files may be downloaded to C:\Users\[username]\AppData\Local\ModOrganizer. You can open Settings to select pretty much any path you want to use for Downloads (but keep it away from UAC controlled folders, Steam folder, and the game folders). If you install Mod Organizer in portable mode, downloaded files are stored in the ModOrganizer\Downloads folder. If you installed Mod Organizer in say D:\Tools\ModOrganizer, the downloads folder should be D:\Tools\ModOrganizer\Downloads. You can also open Settings to select pretty much any path you want to use for Downloads. Also note that you may find some older guides or videos floating around that direct you to install Mod Organizer in the Steam or game folder. This is obsolete information and should be ignored because Mod Organizer's virtual file system does not work correctly if Mod Organizer is installed in the game folder and may not work correctly if it's installed in the Steam folder.

I think the confusing aspect of the coloring is that red indicates a conflict, but it does not indicate whether this is a breaking conflict or an intentional conflict. For example, SkyFalls/SkyMills sets the Is Full LOD flag on SFarmhouseWindMillDirt02Whiteruntest [MSTT:2D01037F] and DynDOLOD removes this flag. This is intentional because DynDOLOD uses a better dynamic LOD algorithm for this object. It is a conflict because some mod in the middle changed something that wasn't forwarded to the last mod in the load order, but the difficulty can be determining whether the conflict is intentional or a breaking change. When cleaning mods, you want to load only the mod to be cleaned and the masters of this mod. If you load the entire load order in an attempt to clean all mods in one session, you may find that mods further down the load order override "identical to master" records in the mods to be cleaned so these are now seen as "overridden" instead of "identical to master" and won't get cleaned properly.

I updated the link in the original post.

Locked... duplicate post

Is D/:skyrim special edition/skse64_loader.exe the correct path for the executable?

The manual cleaning method documented in Gamer Poet's video is out of date. Follow the Cleaning Vanilla Master Files section in the guide https://wiki.step-project.com/STEP:2.10.0

Yes, you should open the Skyrim Legendary Edition folder. I think TechAngel85 updated this recently to document the new cleaning method used by Wrye Bash.

If you are starting over from scratch, select the option to create a new instance and select the game you want to use (say Skyrim SE). When you want to switch to Fallout 4, click the first button at the top left), create a new instance, and select Fallout 4. You can then use this same button to switch between Skyrim SE and Fallout 4 without getting the mods mixed up.

I don't understand why you renamed all these folders? Mod Organizer runs in one of two modes: In portable mode, you can install as many "copies" of Mod Organizer as desired. For example, you might have MO-FO4 for Fallout 4 or MO-SSE for Skyrim SE. In this mode, all of your files are stored in %ModOrganizer%\profiles, %ModOrganizer%\mods, etc. and are kept separate for each game. If instance mode (the default unless you explicitly select Portable mode), you can create as many instances as you want. In this mode you might have one or more instances for Fallout 4 and one or more instances for SKyrim SE. All of your files are stored in %AppData%\Local\ModOrganizer\[instance] and are kept separate for each game.

[spoiler] ...paste your text here... [/spoiler]

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.

Sorry, but I'm having the same issue so I'm afraid I'm not much help. In my case I'm getting a crash dump when I try to run Wrye Bash from a command line and haven't even tried running it from Mod Organizer yet. I then went back to the version of Wrye Bash that was working previously and it's crashing as well. I'm wondering if my issue might be caused by a recent install of Visual Studio 2019 since that's the only thing that's changed on my system.

In Mod Organizer, double click the SKSE mod in the left pane, go to the INI Files tab, and verify your skse.ini file. It should be like this: [General] ClearInvalidRegistrations=1 [Display] iTintTextureResolution=2048 If this looks good, can you start SkyrimSE.exe (without using SKSE) from Mod Organizer and get into the game without crashing?

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.

See the instructions at https://wiki.step-project.com/TES5Edit#Recommendations for configuring the latest version of TES5Edit (or SSEEdit) to quickly clean plugins.