ripple

You have a mod in your load order that depends on Frostfall's plugin as a 'master.' Thus, uninstalling Frostfall (and its plugin) causes your game to CTD on start.

1) Do not disable all plugins, make saves, and then re-enable plugins, unless you want to play with corrupted saves. When you have mods utilizing continually updating scripts, doing so is akin to uninstalling those mods without having first halted the running scripts. 2) The Papyrus log should be located at '/My Documents/..../Skyrim/logs/script/' 3) Hothtrooper44_Armor_Ecksstra.esp ActiveLoad this plugin directly above Then uninstall all mods associated with plugins not recognized by BOSS (do not simply disable those plugins, uninstall the mod and all resource files were installed with the mod). Once we figure out what the problem is, we can see about reinstalling them and what to do about them. Until then, let's eliminate them from the equation. Now try starting a new game (do not load an existing save game, especially not one made near Pelagia farm), and see if you can complete the Companions vs. giant scene without a CTD.

I asked for the example. And I clearly asked -specifically- for an example where the US flag was singled out as the one flag that was arbitrarily banned, as implied by all of these "OMG! Can't wear the US flag anymore!", 'news' sources, rather than cases where the institution has adopted an 'all are equally banned' (so you can't wear -any- flags any more, whether it's a US flag on Mexican holiday, A swaztika on a Jewish Holiday, or an Israeli flag on a Palestinian holiday) approach (as is consistent with how these institutions operate, which is basically to preempt any 'problems', and to ensure the institution will be discharged from any legal liabilities), or where the policy they are drafting are 'pending' (which means they do not yet have a policy on this, rather than have implemented a policy that specifically targets the US flag as the one flag that is banned).

Cover or stealth works best for me. I actually felt enemy mages were a bit underpowered so I made a personal mod to boost their level scaling. Once you are able to invest in enchanting and can make some resist magic items, mage-slaying becomes really (almost too) easy.

I know of some companies that have policies regarding not displaying -any- national flags, but I am not aware of any major stories about someone in the US getting offended specifically at the US national flag (but not other national flags). Care to supply a link?

I think what s/he is saying is that there is a mod in her/his load order where the order of the mod's masters is 'out of order' and does not conform to BOSS' latest masterlist. So when s/he runs BOSS, which adjusts the load order to the latest masterlist, the mod in question shows up in Wyre Bash as being dependent on a number of masters whose order does not conform to his load order (wow, that was a mouthful...). This is generally harmless and typically have no detrimental effects. However, if it really bothers you, you can load the mod in question in TES5Edit, right click on the plugin and select 'sort masters', and TES5Edit will sort the order of the mod's masters and alter records appropriately to conform to the new order of the 'masters.' I feel like I just joined the Masons....

Enable Papyrus logging, play for at least 10-15 minutes (avoid doing things that seems to CTD your game), and copy/paste the log here, into a set of spoiler tags so it won't clutter the screen. If it's too big to copy/paste here, upload it to PasteBin and post the link here.

I took a look at some of the logs, and it looks like my suspicions have been confirmed. It seems you uninstalled many, many mods mid-playthrough after making save games with those mods active, which is why your Papyrus log is getting spammed with the 'missing file' messages. A number of mods that were uninstalled also appear to have been 'script intensive', added new properties, or redefined vanilla properties, and have left orphan junk in your save game. In short, your save games are corrupt. Even SKSE's 'clearinvalidregistration' function will not be adequate to salvage your save games (as it only deals with broken onupdate events--although it looks like you have some of that too). At this point, the best thing you can do to stabilize the game is to delete your existing saves and start a new game. Orphan junk baked into save games cannot be cleaned (or rather, all methods of 'cleaning save games' are akin to 'chemotherapy' and is just as likely to further damage those save games, without any assurance of actually salvaging them). A brand new game will ensure you would not have to deal with any orphan junk baked into your save games from mods that you have uninstalled (presuming that you do not uninstall more mods mid-playthrough again). Before starting a new game, you might also want to take the opportunity to trim the mod list a bit, make sure all mods you want to keep are fully updated to the latest version, and just some general mod load order maintenance/tune up (for example, get rid of mods with navmesh errors, which can cause CTDs, unless you want to repair them yourself). You can also reinstall the game and mods (making sure the mods you will reinstall are mods you really want to keep, and won't uninstall mid-playthrough). But if you were very meticulous with mod un/installation, un/installed all of your mods via one mod manager, and did not leave any orphan loose files in your game data folder from mods that were uninstalled, then I would say a complete reinstall is not necessary.

The size of your save game does not provide a clear indication of bloating, but the size of the Papyrus log indicates your save game *might* be corrupted. I'd still have to see the content of the log to confirm. If you can cut it up and post it to PasteBin in separate chunks. Download 'NotePad+' if you don't have it, and copy/paste sections of your Papyrus log there so you can save the Papyrus in parts for upload. It's a very good utility and will preserve the original formatting. In the event your save games are 'corrupted', reinstallation of the game may not be necessary if you have not fubarred the installation of existing mods. But starting a brand new game (and not uninstalling mods mid-playthrough) will most likely be necessary.

If a mod is listed as 'obsolete', I would advise uninstalling it, because it means the mod is no longer supported, even if the mod author still made it available for download. Depending on how old the mod is, it may not have been properly updated for the latest patch and the records may not conform. You should temporarily turn off auto-update of everything in your system, including Windows update if you have that set on auto. Make sure nothing is going to interfere with your gaming at all for the next couple of nights. This way, you can confirm whether external utilities are involved. Also, start keeping a log or journal of some sort that details your CTDs, including the time of the CTD, where your character was in game location wise, and what were you doing/what was going on.

I can't seem to download the log without having to install their spyware downloader... What is the length of time for the log you accumulated? If it's just 10-15 minutes and too big to upload to PasteBin, then it's definitely not a good sign. Have you, by chance, uninstalled a lot of mods in the past and continued with same save games after uninstalling those mods? Incidentally, what is the size of your current save games and how many accumulated hours are those save games?

Still a bit messed up but enough to work with. 1) Download TES5Edit from the link in the BOSS log, follow the instructions on the same page, and clean the plugins flagged by BOSS as containing 'dirty edits' (except where BOSS explicitly states it is not necessary), including the update and any DLC esm's flagged as such. You will need to remove identical to master entries as well as undelete/disable deleted references. 2) For now, uninstall all the mods associated with plugins not recognized by BOSS (uninstall via the mod manager you used to install not, not just disable the plugins). It's too much of a hassle right now to deal with them as they require additional procedures and could very well be implicated in your game instability.

Hmmm....the formatting for your BOSS log is messed up and spreading....'eastward.' Copy/paste it to NotePad first, then copy/paste from NotePad into the spoiler tag. See if that fixes it. Turn off your scheduled defrag and anti-virus completely for now, during this period of Skyrim troubleshooting. This should be the quickest way to determine if they are implicated.

Just a couple of things: 1) 'Immersive Patrol' is not 'script intensive.' In fact, I am not sure if it uses any scripts. And it comes in modular form so that users can pick and choose just how much they want to add until they hit the threshold of their modded setup. Performance-wise, it's actually less taxing than 'Populated....' 2) The average users should not be using a TES5Edit merged patch. Aside from the fact that the merged patch function is no longer supported by the TES5Edit team, the merged patch function is not as 'intelligent' as the Bashed Patch, and often requires the user to manually edit unwanted merges post-generation. It is not a 'fire and forget' all purpose compatibility patch and unless the user knows exactly which records they want to merge (and thus, which needs to be deleted post-generation), I advise you not to use it.

You can use the 'BOSS Userlist Manager' to set custom rules for plugins so their load order positions will not be reset every time you run BOSS.

Enable Papyrus logging. Edit Skyrim.ini and added the following to the bottom: [Papyrus] bEnableLogging=1 bEnableTrace=1 bLoadDebugInformation = 1Play for at least 10 to 15 minutes (anything shorter is going to be of less help), avoid doing the stuff that normally triggers your CTDs. Then copy/paste the entire Papyrus log here (you will find the Papyrus logs stored at '/Documents/..../Skyrim/logs/scripts/'), inside a set of spoiler tags (so it would clutter the screen). If it's too big to post here, upload the Papyrus log to PasteBin, and post the link here.

Spoiler tags [ s p o i l e r ] (without the spaces) Copy/paste your complete BOSS log here, including SKSE information and plugins not recognized by BOSS if there are any. [ / s p o i l e r ] Do this for any logs or lists that takes up more than a few lines so those reading your post won't be greeted by a huge wall of texts. If you are consistently experiencing CTDs in that time frame, and no CTDs (or noticeably fewer CTDs) when you play outside of that time frame, than it suggests a cause external to Skyrim. Something that only occurs during that time frame, such as a scheduled anti-virus scan (which we've ruled out, but could be other external programs). If it's just an overlap, and you simply cannot find the time to test your playing time outside of that time frame to confirm your suspicions, then it's probably just a coincidence. At the very least, it would not be enough to go on that we could conclusively pin point the issue to an external program (meaning we would have to look for other possible causes of CTDs).

This is...not helping....there can be many, many, many causes of CTDs. Being able to discern some sort of 'common pattern' to CTDs will greatly reduce the possibilities and help narrow down the cause. So think carefully about the details of when/where/what were you doing or what was going on in game when the CTDs occur. If you consistent CTD some time between that time frame you specified (which is very specific), without fail, even if you just played for 10 minutes that happen to fall within that hour, then that's a possible 'pattern.' If it's not consistent, but just that your play time overlaps with that period of time, then it's probably not relevant and can be ruled out as a 'pattern.' This matters. Also, start by posting your complete BOSS log (including the SKSE information). Just copy/paste it here, including the list of plugins not recognized by BOSS if one is generated, and enclose it in a set of spoiler tags so it will not clutter the screen.

What do you base this on? First, there is no real point in using 'tools to clean your saves.' With the exception of SKSE 'clearinvalidregistration' function, which only address orphaned OnUpdate events, there are no 'tools' that can 'clean' saves which are not basically various forms of 'chemotherapy' that are just as likely to destroy the save games they purportedly attempt to salvage. Second, UFO actually comes with an uninstallation function that will allow users to halt running scripts and dispel active effects via the firefly. I've used it, and it works--although I never had the chance to see if there are any long term ramifications (and uninstalling any of these mods will invariably leave a crapload of orphaned junk baked into your save games). AFT, on the other hand, does not. Uninstalling AFT mid-playthrough will necessitate a fresh game.

Those are two very different symptoms. Are you consistently CTDing "Nightly, between the times of 11 PM Mountain Standard Time (That would be midnight, Central) and 12:30 AM Mountain Standard Time (1:30 AM Central)", or is that just so happens to be the time when you get around to playing Skyrim (and it CTDs an hour into your game, no matter what time it is)?

He's using GDO and 'Immersive Weapons.' Both of those mods still require spike.esm as a master.

They will be removed if the mod was installed and uninstalled via a mod manager (which is why everyone is advised to use a mod manager to exclusively handle the un/installation of mods, to ensure loose resource files will not be left behind in the game installation). What I think DownTheDrain is sayin is that there are ophan script data baked into the save game from mods that have been uninstalled, and thus causing the issues the OP is encountering. A Papyrus log will confirm this.

Do you have any external programs scheduled to run during that time, like scheduled regular scan by anti-virus, etc.?

Actually, you should definitely not do this with any of these follower overhaul mods, because they are all 'script intensive.' Disabling, making a save, then re-enabling, is equivalent to uninstalling a mod without first halting any running scripts. This will lead to spamming Papyrus logs and potentially corrupt saves. The only exception is perhaps UFO, as you can disable the mod's functionalities via the Firefly at Riverwood. But the best thing to do is to start a brand new game after uninstalling or disabling any of these follower overhaul mods.

There are issues with both UFO and AFT (the most notable of which is that it breaks one of Karliah's AI packages in 'Trinity Restored'). Right now I am testing EFF, after having tried UFO and AFT extensively. I like EFF's simplicity.