GrantSP

Wow! Just wow!

Welcome to STEP @jc1ward The GitHub issue tracker may look like a "jumbled mess" but is actually a very useful tool in seeing what are current issues. Familiarise yourself with how to search it and you will quickly see all you need to know about the current 'plan of attack'. My advice to you is: just install it and see what hits and what misses. If something looks wrong, search for that issue and add anything you notice that might help.

I just added ICBINE4 == I Can't Believe Its Not ENB version 4, since there was a couple of posts about its meaning, but for some reason I can't see it triggering in the forum. Bam! And there you go, as soon as I wrote this post it worked. Magic. Ahh, so this only applies to newly added or edited posts? It isn't retroactive? Going back through the forum to see if it applies I notice it only comes up if I enter 'Edit' and save the old posts.

I concur.

I too do not see the need to dual-boot. Win10 with an AMD card works very well for me with almost constant 60FPS.

Fair enough. Orphaned scripts is about all it's good for but the best option is to not load/unload scripted mods mid game. Make a new profile, as you have been doing, and try the mod to see if it fits your playstyle and then add it into a new game. At any rate I'm glad you have it all sorted now and welcome to STEP. We try to provide a good stable modding experience so if you come across any issues feel free to ask, you will never be berated for asking, what many consider, basic questions.

We don't delete topics. Even if the 'problem' is minor and the resolution presents itself easily, this forum is for future users to see what went wrong and how to fix it. For this reason we prefer it that posts don't get deleted and all the information remains for everyone to read. Don't worry if you feel your initial post was pointless, its amazing how often the same minor mistakes are made by users, even long-time users.

I think a more pertinent question might be: what have you been doing that makes you think your saves are in need of 'cleaning'? After so little time with the game I'm assuming you haven't been outrageous with your mod choices. Or have you?

Add the switch "-IKnowWhatImDoing". Ps. We have a nice xEdit guide now that includes snippets like this.

If you're referring to your OP, then yes, others see that same thing. The reasons for it are very well described in this guide by @Kesta.

@Kesta, an excellent description of the topic! Kudos to you.

Yeah, that was my line of reasoning also.

In what way? Could you elaborate more?

We have a thread specifically for CTDs & related issues here. Read through that and see if you can pinpoint your issue.

Papyrus is the name given to a new script language that Bethesda created when they developed Skyrim, or to be more precise for the Creation Kit. (Actually in-house development used different tools than the CK but for the sake of expediency, I'll just say the CK.) Skyrim is a game that was developed to use the same basic structure as games that preceded it such as: Morrowind, Oblivion, Fallout 3 & Fallout New Vegas. These games too had scripts that accomplished tasks in-game, but it was not Papyrus. Note this last phrase! Now when Skyrim, and now Fallout 4, was developed a lot was made of the use of Papyrus and the fact it has an entry in the configuration INI for it to log events and the success or failure of the script functions. This is where new users need to realise that Papyrus logging is not a tool to diagnose CTDs, ILSs or any other issues you might face in your game. It's sole purpose can be told in one short sentence added to the header of every log that one of the Bethesda developers mentions here. (Thanks to @alt3n1ty for this tidbit) (Nb. This is in FO4 logs, not Skyrim, so don't go looking for them in your Skyrim logs and come back and tell me different.) Another point to remember. The mechanism that logs these scripts is part of the game engine and if it, the game engine, crashes it is impossible for it to log what happened because it itself is now... crashed. You will need a process running separately to the game engine to track the calls made by it and to it in the same way as software developers run bugtrackers on their software. e.g. MO's logs can be used for some minor error tracking because MO's 'hooking' code is running separately to the game and does not CTD when the game does. Now let's go back to the point about Skyrim being the next game in a long line of games all designed similarly. When a gamer running Morrowind, Oblivion, Fallout 3 or Fallout New Vegas had a CTD or ILS what did they use to diagnose their issues? Could they enable Papyrus logging to help them? No, they did what all gamers did, they looked at the real issue: memory. The biggest culprit is large texture mods or other such things that tax the system to a point where it just 'throws up its hands and surrenders'. Nowhere did they consider a script logging mechanism would assist them, because one didn't exist. These issues have existed since there were games and the means to diagnose and fix them have also existed. All before the introduction of Papyrus. Long story short: turn off your Papyrus logging and DO NOT USE it to diagnose general game issues. Only enable it if you are assisting a modder to diagnose a script in their mod and they ask you to do so.

I wonder if I my ask for some trouble-shooting from anyone here running MO on a Win 7 machine? A user over on Nexus is experiencing odd graphical glitches that require a soft reboot whenever he mouses over a save in MO's 'Saves' tab. He's got a TTW setup and, from I've managed to find from him, it looks like an issue with Windows Aero. Anyone seen anything remotely similar?

Nothing to worry about with that log entry. Note it is flagged as: INFO, not ERROR. MO's 'hooking' mechanism can't find something that it was expecting and just exited without knowing from where. Unless you are experiencing actual CTDs or other problems, I suggest you just continue on modding/playing.

Papyrus logging is not a worthwhile method to check for CTD causes. CTDs invariably are because memory allocated for something (textures are a large contributor) is now blocked and the game can't load what it needs and falls over. Just because you have a few messages in papyrus logs does not mean the supplying mod is the culprit. We have a dedicated thread setup to help users investigate these issues.

You've left the details a little sparse so I'll give a generalised response. That exception is an "unhandled" exception meaning Windows has no way of figuring out which executable, or a function inside it, caused the error. However since it is in Kernel it is probably due to a driver error, perhaps Windows updated and you are yet to restart to force the changes. Alternatively you may be trying to have some software run in the background, like Steam's overlay, and that is messing with your system. Try the trusted: switch off, let sit for 5 minutes and reboot method. After that examine what you were doing and what software was running and try to replicate the error.

Regardless of the browser you have, if previously you were able to use MO's nxmhandler there will be this registry setting: HKEY_CLASSES_ROOT\nxm\shell\open\commandwhich points to nxmhandler.exe in the location of your MO install. This is the case regardless of the browser you choose to run. If it does not exist, as would be the case on a system where MO or NMM was not installed, you can manually create this registry setting and point it to that executable on your system. If, and I don't know if Tor allows this, file protocols on websites are not passed to 3rd-party applications, such as MO's nxmhandler.exe, then regardless of this registry setting you won't be able to use Tor to initiate a download.

Welcome to STEP @Frighten There are already a few topics started on this matter and currently there is no confirmed method to fix this error. Please go to the GitHub issue created for this matter and follow any instructions provided and also offer any extra information about your system that you feel may help.

Navigate to \Steam\steamapps\common\Skyrim Mods\Bash Installers\Bash\ or where you installed WB on your system and make a copy of Installers.dat. Delete the original and see if the error persists. If not rebuild the installers tab either by answering "yes" when asked or by selecting 'Enabled' from the context menu on the Installers tab. This file is a machine listing of every file seen by WB, and hence the game, and may take some time to generate. I do not believe doing this will adversely affect the already installed status of your mods but that is why you make a backup copy before proceeding.

Just check what's in them. If the 2nd 'overwrite' contains all the same files of the first, there is no point in having them both active, just the last one is needed. If on the other hand only some files are different then you may need both. I'm not sure what Neo has you place in that folder but I can speak for FNIS. Only the FNIS output from the active modlist should be active, disable any from before and do not use it. Stuff like *.json files are configuration files from various mods and the same thing will apply with those. *.logs, usually generated from SKSE plugins, are also not needed and the only reason to keep them in a modfolder is to stop them spawning in the true 'overwrite' after each run.

Yes, if can read hexadecimal on the fly.

@Aristotle unfortunately you are in a sorry situation. Your XP system is going to continue to give you grief into the future if you wish to modify your game extensively, ie. STEP based. Too many important issues were ironed out in the 1.3.x series of MO that you will not get any benefit from. Sadly the only recourse I can offer is to upgrade. Actually I would advise this even if it wasn't an MO matter. Drivers for your hardware, software compatibility, webpage rendering, etc. are all going to become more and more an issue for you if you persist with an out-dated OS.