Shadriss

It can be safely deleted or ignored. It's only used by WB and not Skyrim itself. If you delete it, it obviously will be recreated next time you use it, but otherwise, there's no reason to mess with it.

On the correct folder:
 
Right-Click
Set as Data Folder

On the correct folder:
 
Right-Click
Set as Data Folder

You haven't linked MO2 to Nexus. Go into the Settings on MO2, click on the Nexus tab, and there will be a big button that will link the two. Click it and follow the directions.

You haven't linked MO2 to Nexus. Go into the Settings on MO2, click on the Nexus tab, and there will be a big button that will link the two. Click it and follow the directions.

The dummy ESPs should be handled by LOOT sorting. No need to worry.

The dummy ESPs should be handled by LOOT sorting. No need to worry.

The thread he was trying to link to is here... though I'm not sure which specific post, and it's a LONG thread. A search within that thread might help you find what you are looking for.

The thread he was trying to link to is here... though I'm not sure which specific post, and it's a LONG thread. A search within that thread might help you find what you are looking for.

Move-ing? I'm pretty sure it's long since mov-ed at this point... I honestly can't think of any reason not to be on SSE now instead of SLE... the memory allocation problems that SSE solved makes it a clear choice, but to each their own, I guess.

Move-ing? I'm pretty sure it's long since mov-ed at this point... I honestly can't think of any reason not to be on SSE now instead of SLE... the memory allocation problems that SSE solved makes it a clear choice, but to each their own, I guess.

Sounds like something related to those mods then, if SKSE ran the game fine without any installed.
 
Try this as a troubleshooting effort:
 
1) Deactivate all mods in MO2. Attempt running SKSE through MO2. If this works, go to 2, otherwise, verify that SKSE is properly installed. Those instructions can be seen in the main build guide for STEP 2.10.0 (though it uses MO1 in that guide, the instructions are identical).
 
2) Activate one or two mods at a time, and start though MO2/SKSE. If it works, great - add one or two more in and repeat. If it doesn't, figure out which of the ones you turned on is causing the problem and replace/repair/edit it as needed to get it working.
 
My guess right now is an SKSE install problem, but there is also a feel of a possible missing master mod as well if the game is dropping before hitting the menu... I've seen it happen a few times so quickly that the screen never even went black from MO, so it's not entirely out of the realm of possibility.

Sounds like something related to those mods then, if SKSE ran the game fine without any installed.
 
Try this as a troubleshooting effort:
 
1) Deactivate all mods in MO2. Attempt running SKSE through MO2. If this works, go to 2, otherwise, verify that SKSE is properly installed. Those instructions can be seen in the main build guide for STEP 2.10.0 (though it uses MO1 in that guide, the instructions are identical).
 
2) Activate one or two mods at a time, and start though MO2/SKSE. If it works, great - add one or two more in and repeat. If it doesn't, figure out which of the ones you turned on is causing the problem and replace/repair/edit it as needed to get it working.
 
My guess right now is an SKSE install problem, but there is also a feel of a possible missing master mod as well if the game is dropping before hitting the menu... I've seen it happen a few times so quickly that the screen never even went black from MO, so it's not entirely out of the realm of possibility.

Take a look in the MO2 profile's INI files - there is a setting there to set to full screen. I wonder if you've redone your INI's since you moved to MO2? If you did it from scratch, likely not - if you dragged your old profile and modlist over from MO1 (as I did), the settings should have been the same.

Take a look in the MO2 profile's INI files - there is a setting there to set to full screen. I wonder if you've redone your INI's since you moved to MO2? If you did it from scratch, likely not - if you dragged your old profile and modlist over from MO1 (as I did), the settings should have been the same.

No specials, other to insure that you run the SkyProc patcher after you are done fiddling with your load order. As to the exact placement of the produced patch file, in my load order it was:
 
Bashed Patch
DualSheathRedux
ASIS
DYNDOLOD
 
You can run LOOT again after patch generation to ensure it goes to the right place.

Solution Found:
 
Mod conflict. Specifically, LAL and an overhaul of the opening Helgen scene were fighting each other... which may explain the Nord singing, now that I think on it. The second mod updated since the last time I used it, and that update ended up causing the conflict. Warn Skyrim - I have returned. Again. For the Upteenth time. OK, maybe htey aren't so much warned as resigned...

A) Yes. Yes it is. And thank heavens for it - I hate torches period. I know that STEP has a mod or two to make managing them more user friendly, but I really can't stand them in any shape or form, so... yeah.
 
B) No, it isn't, and isn't likely to, I would guess.

Realistic Water to be loaded after HearthfiresChimneys, so your #2. Read that as "Mod X should be LOADED AFTER: Mod Y."

OK - apparently the solution is just to get rid of OBIS and SIC. Between those two, problem seems to go away. SOLVED.
 
Now to find a way to make the interior a small migde brighter... :)
 
Thanks all for the assist.