z929669

The latest LE guide is 3.0.0 ... it has been months since that post
https://stepmodifications.org/wiki/SkyrimLE:3.0.0

Install these two mods:
https://www.nexusmods.com/skyrimspecialedition/mods/108618
https://www.nexusmods.com/skyrimspecialedition/mods/30379 (also read the third sticky on this one's Posts)
 

Attached is my MO sorted LO in my dev build. Keep in mind that some mods will be sorted arbitrarily by LOOT where order of one or more mods doesn't matter. This applies to some of these. Just check records in xEdit if you don't trust that.loadorder.txt

Thos instructions are redundant. I will fix it

This is fixed

There won't be any performance improvement, because at game runtime, all plugins are effectively being merged anyway (in load order). The advantage of merging them yourself is that you will have presumably made better decisions by doing it yourself. But that's a lot of work. The only reason to merge would be to avoid the plugin cap, which is largely alleviated anyway with many mods being ESL format.
Merging plugins doesn't resolve conflicts, BTW. Merging and resolving conflicts are two different actions. You would first resolve conflicts and then merge the remainder in order of load priority.

Well, we got a response, and current behavior is expected due to the explanation that we evidently hadn't considered:
https://invisioncommunity.com/forums/topic/471314-adding-new-quote-when-editing-a-previous-post/?do=findComment&comment=2920714
 

They PM'd me and I took care of it.

MO installs and keeps it's files and mods in a default location as indicated. The VFS uses this location. If you type %localappdata%\Modorganizer into your Explorer address bar or via the 'Run' menu, you will be taken to the MO files location.
See https://stepmodifications.org/wiki/Guide:Mod_Organizer#Updates
Just follow the guide instructions and don't go further than this by changing MO's internal file org. All is as it should be.

As has been mentioned on another topic, some engine-level mods are not updated to the latest game. You need to disable those mods for now.

You can change those as well or leave them at defaults. It usually doesn't matter much for these unless you have visual glitching in those interfaces.

The Step patches and possibly a couple other mods. We just don't support anything but the latest game + all DLC or keep track of such details for this reason. It's too much maintenance for us to tailor our guides and processes to support multiple flavors of any single game.
You will need to install the complete guide and check issues in xEdit to determine what is dependent on the latest DLC ... or simply purchase the AU content.

The only rule of thumb for interpreting these crash logs that I can thin of is to pay attention to the "Possible relevant objects" part at the top and begin looking at those formIds in xEdit. From what I can see, you are running Simplicity of Snow along with BDS, and they likely aren't compatible. I would drop Simplicity of Snow and use BDS unless there is some requirement that you have the former.

The latest version of SKSE no longer requires this file as indicated in the Changelog on this page. I will update our instructions.

The skin issue is related to ENB. These settings resolves that in the Step ENB:
[SUBSURFACESCATTERING] IgnoreWeatherSystem=false IgnoreWeatherSystemInterior=true Amount=0.5 AmountInterior=0.5 EnableOldSSS=false EnableSeparateInteriorParameters=true EpidermalAmount=1.5 EpidermalAmountInterior=1.2 EpidermalDiffuseSaturation=0.15 EpidermalDiffuseSaturationInterior=0.05 EpidermalMix=0.1 EpidermalMixInterior=0.05 Quality=1 Radius=5.0 RadiusInterior=3.0 SubdermalAmount=1.0 SubdermalAmountInterior=1.0 SubdermalDiffuseSaturation=0.85 SubdermalDiffuseSaturationInterior=0.85 SubdermalMix=0.05 SubdermalMixInterior=0.02 SubdermalPhase=0.0 SubdermalPhaseInterior=0.0 SubdermalTranslucency=0.5 SubdermalTranslucencyInterior=0.5 SurfaceBrightness=1.6 SurfaceBrightnessInterior=1.1 The eyes may be the [EYE] SSS ENB settings.
I also see what looks like stuck LOD.
The other stuff is very likely due to OCS compatibility problems with the Step mod list.

Improper command-line string in MO: C : instead of C:

As Butch mentions, try verifying game files using this instruction. Then read through that whole page for tips on configuring tools like xLODGen and you modding environment in general.

If all is fine and your stuttering only coincides with your use of DynDOLOD 3, then you will need to post for help in the DynDOLOD support forums using instructions in the OP and the forum.

Try setting UseOriginalPostProcessing=false in enbseries.ini. Then set in:
\Steam\steamapps\common\Skyrim Special Edition\enbseries\enbeffect.fx.ini
Test things in the GUI in game to see how things work ... it's quite complex to get things looking right, but lots of the more complex ENBs (e.g., Truth) configure ENB this way to open up another universe of configuration options. We don't do it, because we want to retain the vanilla colors and image space lighting (and it very complicated as I mentioned with many more additional degrees of freedom).

I've no idea about the auto-signature, but I went into your profile and enabled your ability to view signatures. The hide sig feature must be available for everyone from another user's sig, which makes sense.
After your 20th post, you will be able to set your sig and see other settings for that in you Account Settings. This prevents spammers from doing stupid things like setting ads in sigs. Most spammers won't be able to post 20 times before we notice something's up.

You must have figured it out? I see your sig, but you should get rid of the blank lines. New paragraphs always include white space so blank lines are not needed.

You can use the wiki to add your system specs.
https://stepmodifications.org/wiki/STEP:Main
Then you can link that as I have done in my sig.

Answered in OP final edit

I find Merged Plugin Guidelines for Personal Use to be a very good and practical reference for doing what you want using a couple of approaches, but also review The Method.
We usually do patching and merging manually rather than using tools like Mator Smash and the like. These tools are handy for people that are experienced, but I find that it's just as much work and possibly even more, since you can never rely on any batch process to handle everything correctly. You still need to set things up properly and carefully review the results. I feel much better knowing what I have done myself and maybe comparing my own results with the results from a batch-processing tool.
We also have several relevant guides on our wiki, but they are in need of updates:
https://stepmodifications.org/wiki/Guide:Merging_Plugins https://stepmodifications.org/wiki/Guide:XEdit https://stepmodifications.org/wiki/Guide:Basics_of_Resolving_Conflicts  

See OP edit
@Arel You should mark "best answer" in all topics you create if your questions get answered.
Thanks

I am almost certain that it's an OS-level or display-level issue and not an application issue (although certain apps may be sensitive to it).
Since you have multiple monitors, I would test display settings and basically make your OS think that you only have one monitor (the 4K). Make sure taht this monitor is the only one plugged into your box and ensure you are using your optimal display port on your card. Reboot once the OS is displaying your desktop and Windows apps correctly. Update your display drivers (keeping the one-monitor system in place). Verify your display driver settings for the 4k display (these may have different requirements/optimizations).
Then check MO and xEdit once all seems kosher (after reboot). Once all is well in this config, THEN plug in your old monitor and troubleshoot the multi-display issues if they persist (hopefully, they will not).