CTD when loading whiterun exterior from menu screen

[Echo]

If I load any interior cell through a save or any cell (exterior or interior -- even the one I'm trying to load) through coc, I'm able to afterwards load an autosave outside of Whiterun no problem. If I try to load that autosave from the main menu, I CTD. It's a brand new game -- I coc'd into the interior of Whiterun from the main menu (created the default Prisoner character with iron armor and whatnot) and then walked outside the main gate, causing an autosave. I didn't crash when I walked outside at all -- I only started seeing the problem when I tried to load this autosave. I created another autosave outside of whiterun by doing the same thing (coc'ing into whiterun from the main menu and walking outside), and it CTDs too when loaded from the main menu (but again, is fine when loaded while I'm already in-game).

 

I followed STEP Extended but left out the following mods: Improved Closefaced Helments, SKSE-Elys-AltF4, Disease Descriptions, Lore-Based loading screens, Viewable Faction Ranks, A Quality World Map,  NoMaaM Breathing Idles, Wonders of Weather, Smaller Ice Spikes and Spear, Skyrim Enhanced Camera, and Dynamic Distant Objects LOD.

 

No extra non-STEP INI Tweaks

 

Using Mod Organizer

 

System Specs: 16 GB DDR3 RAM, 3.9 GHz quad core CPU, 2 GB Video Card (Radeon HD7800)

 

BOSS load order: Get this error whenever I try to run BOSS through MO, but the load order is sorted by LOOT, so there shouldn't be any issues there

 

I'm getting ~70-80 FPS most places I go in Skyrim, so I'm doubtful that this is an issue with not having enough hardware resources, but maybe it's an issue in Skyrim's programming where there's a bottleneck that crashes when I try to load too many things at once?

Edited February 6, 2016 by Echo

[Nebulous112]

Isn't using coc commands to travel and bypass certain things pretty dangerous on a save you want to keep? I try not to use console commands at all (if I can help it) on saves I plan on keeping.

 

It could also be something like your memory blocks filling up. Try installing Memory Blocks Log, and see from the log if you need to increase your memory settings in skse.ini.

 

Also, for BOSS, you need the 32-bit version, if there is such a thing. MO is a 32-bit program, so it will only run other 32-bit programs. I use LOOT myself, as it is much more up-to-date for Skyrim, not to mention the overall better functionality.

[Echo]

Isn't using coc commands to travel and bypass certain things pretty dangerous on a save you want to keep? I try not to use console commands at all (if I can help it) on saves I plan on keeping.

Is it really? I've never heard anything of the sort before. All it does is move you to a different cell (same thing as walking through a door), so I wouldn't think anything would be wrong with it. I don't use it on a regular basis though -- I use it pretty exclusively to testing. I've had this CTD on save loading from the main menu but not from in-game problem before on a save I hadn't used any console commands in before, so I'm pretty sure it's not related to coc.

It could also be something like your memory blocks filling up. Try installing Memory Blocks Log, and see from the log if you need to increase your memory settings in skse.ini.

Alright I'll try that. I'll post back here with what I find out.

Also, for BOSS, you need the 32-bit version, if there is such a thing. MO is a 32-bit program, so it will only run other 32-bit programs. I use LOOT myself, as it is much more up-to-date for Skyrim, not to mention the overall better functionality.

Well they do two completely different things, so I wouldn't say LOOT is better overall. LOOT tries to automatically detect and resolve issues, but can't detect minor issues (i.e. Mod A patches something better than Mod B so both mod authors recommend putting Mod A after Mod B in the load order). BOSS is entirely user-managed, so it picks up on that kind of stuff since it was manually inputted, but it's flawed in the sense that it doesn't help with new/uncommon mods since they haven't been inputted into the system and that people may have input bad load order settings into BOSS. To my understanding, they work better together than either one does alone. If you run BOSS first and get the little things taken care of and then run LOOT which corrects any human error and new/uncommon mod load order positions, you're better off than running either or.

[GrantSP]

STEP uses LOOT and any issues regarding the use of BOSS should be looked at by either the maintainer of the specific guide or by the user themselves.

 

As to the question of BOSS or LOOT.

• BOSS is no longer in active maintenance, whereas LOOT is in a constant state of improvement.
• The list of mods that need special treatment is likewise being constantly updated and very few mods need special handling, whereas very few people (some estimate as little as 20) ever added to BOSS's lists.
• Those very few mods that do, can be managed by setting meta rules, also easily done with LOOT.
• Most of the contributors to BOSS's code are now working on LOOT.

A good look at the LOOT FAQ may allay any fears you might have about LOOT.

 

I would also echo the counsel to avoid using "coc" to initiate any save that you wish to use. Even using it to test things should be used judiciously as this post by @arthmoor notes. Moving into areas this way can avoid needed scripts from firing, or cause them to fire out of sequence. Saving them into a save will likely cause issues further down the track.