penguinopus

Skywind is starting to seem like flying cars--part of an imagined future that is and always will be X years away.

That's possible. Here's why it doesn't make sense to me. NOTHING I do with the RAM changes which saves produce the ILS. The saves that work, load no matter what. I can run a bunch of programs in the background (including Crashplan, which is a total resource hog, taking 3 to 4 GB of RAM) and they still load. The saves that cause ILS, do so no matter what. I can kill all background processes, disable ENB, etc. They still won't load. And remember, I have at times loaded a save, RESAVED IMMEDIATELY, and produced a save that causes ILS. Again, the loadable save loads no matter how much I'm taxing my RAM. The immediate resave causes ILS regardless of how much I'm babying it. That leads me to think the ILS isn't being caused by savegame bloat or lack of RAM.

Thanks. I have spent hours researching savegame bloat and trying various recommendations. Nothing works. And as I say, I really doubt this is the cause of the problem.

My most recent saves all cause Infinite Loading Screen (ILS). Earlier saves are fine, BUT the problem comes back. Say I play for half an hour, making five saves along the way (all indoors to be safe). The last two or three will cause ILS. The first two or three will load and be playable. But if I load one of those games and re-save it right away, the new save will often cause ILS. If it doesn't, the next save 5 minutes later will. If I load one of those saves, I can play for several hours, saving along the way. The game will not stutter or freeze or crash. But not a single one of those saves will be loadable. I'll have wasted all that time. There is no particular location or situation that causes this. The Safety Load mod does not help in my case. This happened once before and I "solved" it by restoring a save from 20 hours of gameplay prior. That worked to allow me to replay those 20 hours and add at least another 10. Then the problem came back. Tech Details: - Windows 7 Ultimate 64-bit - 97 GB free space on Skyrim drive - GEForce 560 video card with 2GB RAM - Intel® Core i7-2700K 3.50 GHz CPU - RAM - 8GB (4GBx2) DDR3/1600MHz Dual Channel Memory Skyrim Details - Latest version of Skyrim and skse. - Run game through Mod Organizer using Loot to check the load order and then creating a bashed patch - Cleaned the 3 DLC with TES5edit and checked to make sure the uncleaned versions hadn't resurrected (as they sometimes do) - Load Order I checked one of the bad savegames with TESVESSE. Under Global data table 3 > Papyrus it said I had 38,054 strings. So I'm nowhere near capacity on that. This does not appear to be a memory problem. As I say, the game runs quite smoothly. I'll get an occasional CTD--maybe one per 2 hours of gameplay. And very occasionaly I'll get a 1-second freeze or a short stutter. My saved games have gotten progressively larger over 100 to 200 hours of gameplay (guesstimate). They started out around 5 MB and are now at 32 MB. As far as I can tell, though, there isn't some size threshhold causing the ILS. Still, I wish there were some way to save my quest records, possessions, and discovered places and transfer them to a newly created character. That would get rid of the save bloat without making me start all over. (I've done that so many times, I am SICK of those early quests.)

I found this post because I was searching for a solution to this problem. No luck. But after some digging, I think I've found one all by myself. I'm using Mod Organizer, so my details may be different. But the crucial facts are these: A) Headbomb's original Better Sorting mod can stay around even after you think you've uninstalled it, deleted it, performed an exorcism, and entered Witness Protection. B) It can fight Sharlikan's patch and win. So even if you've installed the patch over the original, or deleted the original and installed the "patch" (which is fully functional on its own and has everything it needs from the original already inside it), you can still end up with the original esp files that BOSS lectures you about. I think the following steps can solve that problem. Worked for me, anyway. 1. Search your hard drive(s) for headbomb*.esp (just like that, with the asterisk. Now might be a good time to download Everything and let it index your hard drive. It'll probably be done before Windows is finished with its search. And then you can use Everything to run the search and watch how it spits back the results faster than you can blink.) 2. Delete them all. (If you think some of them are safely in a backup folder that Skyrim absolutely will not bother with, fine. That's your lookout. Just delete the ones that might be causing the trouble. Wimp.) 3. Reinstall ONLY the Sharlikan patch. There is no need to re-install the original. 4. Run BOSS and see if the problem disappears. 5. If anyone tries this, let me know either way. But if it doesn't work, I'm likely out of ideas. I'm not sure why the original mod behaved this way. And to be fair, it wasn't quite the original mod. I tried to repair the original esp files with TES5Edit before going back and actually reading BOSS' warning message instead of assuming I knew what it said. (Dirty edits. It's ALWAYS dirty edits. Well, I know how to fix THAT....) :wallbash: