Lanceor

I've only tried the patch briefly, but I managed to fast travel from Whiterun to Markarth to Raven Rock to Windhelm to Riften... without CTD or ILS. Before the patch, this chain of fast travel was guaranteed to cause problems, and in fact, I wasn't able to get out of Solstheim without using Safety Load.

I tried it and found that it removed more immersion than it added. - When looking to the side, the character's actual head clipped into view. (This was at the default FOV setting.) - In the cut scene parts of "Unbound" the camera position was wrong most of the time. I was able to analyse Lokir's skin pores while riding the cart, and the camera was pointed at the ground for much of the execution scene (including the bit where Alduin attacks). However, I really do like the concept and if the mod author does release another version, I'll definitely be trying it again.

I think that it is beyond reasonable doubt that Safety Load does get rid of the ILS problem. What needs to be evaluated are its CTDs - the number of CTD reports are too many to be coincidental. My current playthrough is quite stable in terms of CTDs but ILS's are rather frequent. The plugin flipped that around - no ILS but frequent CTD (including a reproducible one in Wolfskull ruins with which I was able to conduct testing). As such, I would not give Safety Load an unconditional recommendation. I'd say to users that they try if they are having ILS problems, and to keep using it if it helps more than harms. It is also a plugin that I would keep it on hand in case I get stuck - loading a stubborn savegame or getting out of Solstheim for example.

Just want to add my 2 cents worth. One of the versions is Dual Wield Parry Left Hand - it used to be a bit buggy but I actually fixed it for Borgut1337 and it should be very reliable now. Things to consider for Dual Wield Parry Left Hand: - It uses no scripts at all. - It uses the same default button setup as sword and shield or two handed weapons. i.e. Left click to attack, right click to block. Not having to learn a new button setup makes switching equipment/characters a lot easier. - Its only disadvantage is that left attacks are disabled while dual wielding. This is usually not an issue if a dagger is being wielded in the left hand as is popular. - Right-hand attacks and dual attacks, both normal and power versions, are as vanilla. The first two points are what swayed me towards the Left Hand version instead of the more popular SKSE and Scriptdragon versions.

I use either GPU-Z or MSI Afterburner on a second monitor to keep an eye on things like GPU load, VRAM usage and temperatures. Likewise, I use Task Manager to keep an eye on the CPU load and CPU-Z to monitor temperatures. If you don't have a second monitor, MSI Afterburner has a useful on-screen display function though you may have to tab out or exit the game to check the CPU usage. (Someone may know of a mod or software that can monitor CPU usage in-game). Usually, you'll find out what part of your system is maxing out this way.

Got a bit of a breakthrough today. My earlier hunch about the combat CTDs due to Vilja is correct. If she somehow gets an invalid item in her inventory, combat will make her tear the fabric of Skyrim's space-time and cause a CTD. The fix is to use the console to find and remove these glitched items. Those "corrupted savegames" were probably due to this glitch. One source of CTDs eliminated, 99 to go. :P The memory errors are very weird - no other combination of software has been able to produce these errors. At least I know that rebooting the computer fixes it for a few hours. Perhaps it has something to do with that rumoured Skyrim memory leak. As for autosaves... I stopped using them ages ago. ;)

If you've already done that, the only other way I know of is to reload a previous save, and to avoid saving outdoors. My suspicion is that if the script is running when you save, exiting and reloading will cause that script to go buggy from that point onwards, corrupting future savegames as well. I take the cart ride to Helgen every time I start a new game as I'm wary of exterior saves having this problem!

Yah, turning off the GPU overclock sounds prudent - I'll do that. This is proving really hard to diagnose as sometimes it'll go for hours without a CTD, sometimes it will cause memory errors (requiring a reboot) and sometimes the savegame will corrupt itself (requiring a rollback).

I'd be happy to help out with Oblivion. TBH, I was more involved on the mod-making side of things than the mod-installing side, though I did use a full suite of graphics enhancement mods that worked well for my machine.

It's possible probable that the old script was baked into your savegame and Skyrim is still using the old one. While ClearInvalidRegistrations will eventually clear out the old script, you could try going to an unmodded interior cell and waiting for 31 days. No Boring Wait Menu will help preserve your sanity if you do this.

Once again, Skyrim has thrown me another curve ball. MemTest on its own - No problems MemTest after 8 hours of Prime95 - No problems MemTest + Prime95 at the same time - No problems MemTest + IntelBurnTest - No problems MemTest + IntelBurnTest + Ungine Heaven - No problems MemTest + IntelBurnTest + Prime95 + Ungine Heaven - Surely you can't be serious... MemTest after an hour of Skyrim - Memory Errors The memory errors still occur after the system is given 10 minutes to cool down and there are no other applications running. They'll persist until a system reboot after which I'll have no further memory errors until I run Skyrim again. What could it be about Skyrim that could mess up memory so badly that not even three torture-testing applications in unison can't match it?

Yes. :facepalm: Editing my post now.

Seriously - run MemTest. Like you, I tried every conceivable combination of mods and tweaks and still couldn't achieve stability. Also like you, I used the same overclock for over a year and my rig could survive 8 hours of Prime95 and pass IntelBurnTest and Ungine Heaven Benchmarks with flying colors. I was 200% sure that my system was completely rock-solid stable... but 5 minutes of MemTest completely shattered that notion. The worst that could happen is that you waste half an hour confirming what you already know. ;)

Has anyone tried turning off Hyperthreading? The theory is that hyperthreading allows a quad-core processor to run up to eight concurrent threads at 50% speed. While great for general computing, Skyrim (and games in general) requires maximum on-demand performance from fewer cores. Having to share a core with another thread will actually worsen its performance. Also, to quote the CPU affinity - two different approaches thread: By turning off hyperthreading, Windows is still managing how the CPU is utilised. However, it ensures that high-usage processes get cores all to themselves. I do have some anecdotal results from my non-scientific "tests". However, I'll spoiler them so that anyone planning to test it can do so with an open mind. :)

Like most, I love simple tweaks that improve stability and/or performance, but I have my reservations on whether the tweaks in Project Stability work or not. HPET Tweaks Summary: Tests inconclusive, but I'm avoiding using it. I've run a battery of fifteen-minute tests that show forcing HPET to be quite stable after a system restart. However, with HPET forced it seems that memory errors start to occur after a few hours of gameplay. The only way I can test this scientifically is to change the HPET settings, play for several hours and then run the memory test... a bit more time consuming than I can afford. Just for the record, these are the HPET settings that were available to me and I've tried all four. Setting 1: HPET: Enabled, HPET Mode: 32 bit, useplatformclock not set (system/BIOS default) Setting 2: HPET: Enabled, HPET Mode: 32 bit, useplatformclock true Setting 3: HPET: Enabled, HPET Mode: 64 bit, useplatformclock not set Setting 4: HPET: Enabled, HPET Mode: 64 bit, useplatformclock true Unparking Cores Summary: No scientific evidence for/against, but I'm using it. All my cores were already unparked due previous registry dabbling. I presume it either helps or does nothing so I'm leaving them unparked. CleanMem Summary: No obvious effect so I'm avoiding this tool. I get a lot of load screen freezes on fast travel or cell transition. CleanMem didn't reduce them in any way. I've tried various "memory optimisers" on occasion since the 1990's and have yet to use one that has had a measurable effect. Given the controversy surrounding memory optimisers in general, I'm avoiding this tool. But wait, there's more! There's one more tweak that I think would have fit in well with Project Stability and I'm surprised that it wasn't included - turning off hyperthreading in the BIOS. I'm going to start a new thread on this so as not to hijack this thread. :) Edit: I'm a doofus and wrote HPET as HDEP.