pyrate999

It worked! A million thanks to you.

Yeah, sorry if you thought I had fewer mods. I've usually been very good at installing them, and my setup worked wonderfully. Immersive Jewelry is probably it, actually. I had just gotten it, and although it ran once fine that was before I tried that bashed patch. Are you saying remove it totally, or just the .mayaSwatches?

On account of the log crashing my web browser when I try to paste it, I've opted to just upload it to dropbox: https://www.dropbox.com/s/u4hhknb3ug2e66l/usvfs-2017-01-15_22-45-57.log?dl=0 It's over 300,000 lines, so fair warning. I skimmed through, and the bit around line 260,000 was different than the rest.

Check your AV software and if possible add MO2 as an exclusion, or if needed disable it to test. Many poorer AV packages get confused by MO's 'hooking' mechanism and view it as a bad thing. Malware and viruses sometimes use similar tricks to gain access to processes in your system. Added exclusion, didn't work, disabled it, didn't work, uninstalled it, again, exactly the same. However if what you are describing is SkyrimSE actually starting and then CTDing then perhaps the issue is to do with missing masters or similar issue. AFAIK there are no missing masters. I've checked with MO, Wrye Bash, LOOT, SSEEdit. There aren't any issues with mods that I know of. STEP recommends not installing anything into UAC folders like 'Program Files (x86)' as this allows Windows to interfere in processes. Likewise it is suggested to install MO and any other tools like WB or LOOT away from the game folder, perhaps into a dedicated utility folder: C:\Games\Tools\. Also running admin is not recommended unless specifically instructed to by a tool author. Especially is this true with MO. Processes running with higher privileges calling processes with user access only, or vice versa, are causes of untold problems. I've ran it from Program Files (x86), normal program files, Games, even the desktop. Every single time I get the same result. And I only ran it from admin once in desperation. That was about 3 delete-everything-and-reinstalls ago. It didn't have any effect except to make MO crash every second time I tried to run the game.

So, I'm at my wit's end here. I've tried everything I possibly can: Running as admin, reinstalling both the game and MO, in different locations every time, and all I get is the same result. I try to run SkyrimSE through MO, the process runs for a minute or so and MO locks for that time, and then it suddenly stops. It runs just fine through steam, doesn't run through MO with all mods disabled, and the launcher (through MO) crashes when I press any buttons. Paths are right, I've installed all windows updates, no antivirus or firewall or what have you, and it's always the same. LOOT and other third-party plugins run, my mods are all compatible, etc. This is constant across all versions of MO as well. 2.0.7, 2.0.5, hell, I've even tried 2.0.8. I've installed MO into the same folder as skyrimSE.exe. I am at my wits end here. Closest thing I can find to a solution is this, from the Mod Organizer guide on this site: Problem: Launching an application fails. Mod Organizer locks for a few seconds, but then simply unlocks and does nothing. Probable cause: The application is installed as a mod in Mod Organizer, but is unchecked in the Left Pane modlist. General Solution: Check the application's mod in the Left Pane modlist. Left pane is vacant of any official files. Only thing I've done between functioning and non-functioning was uninstall some other games on steam to clear up hard drive space. Oh, and I made a bashed patch, which had always worked before and there were no issues with.