Common CTDs, Freezes, ILS and memory issues

[hishutup]

 

  Reveal hidden contents

 

Basic requirements to follow this FAQ

Use the following utilities and have some idea of what they do.

• ENBoost: This extension moves the DX9 texture cache to a different 64 bit process. This reduces the chance of filling up the 32 bit process with textures causing random CTDs.
• Crash Fixes: This is an SKSE plugin that helps catch some issues that cause skyrim to CTD, freeze or hang. 
• Some form of memory fix:
  • SSME: Made redundant by SKSE memory tweaks.
  • SKSE memory tweaks: This changes the initial heap size to make it larger. This avoids the issue where skyrim will not increase the heap causing it to CTD, freeze or hang. This method requires some input for the correct size. This can be found by using Memory Blocks Log. This is a workaround to an issue.
  • Crash Fixes OSAllocators: This is a fix for the same issue that SKSE memory tweaks workarounds. This is a true fix but has its share of issues.
  • Crash Fixes CustomMemoryBlocks: This is a fix to some of the issues caused by OSAllocators. By breaking the heap into smaller blocks, the memory can be allocated and freed as needed. This method requires some input by observing how high you need to set the blocks size. This can be viewed in the console if the toggle is enabled.

 

Info that is typically useless:

• Papyrus logs: These are NOT crash logs. Typically, the last entry could be several minutes before you even experience a crash. Any useful info is typically debugging code in scripts, this is usually removed/disabled before a mod is released. This is a very helpful tool to modders, but not to users.
• Windows logs: These are rarely of any use to a user.

 

Issues caused by SKSE memory tweaks:

Problem: I randomly CTD.

Solution: Check the size against the memory blocks log. If the last element is close to the max size then you may need to increase heap 1 by some amount(~128 MB increments is accurate enough). Heap 2 doesnt need to be increased as it spawns more like it should.

 

Issues caused by Crash Fixes OSAllocators:

Problem: I get "Skyrim has failed to allocate memory"

Solution: This is caused by memory fragmentation and there isn't really a solution for this. Its suggest to use the custom memory blocks instead.

 

Issues caused by Crash Fixes CustomMemoryBlocks:

Problem: Stuff isn't loading in as expected.

Solution: Check to make sure the size is appropriate.

 

How to read and interpret Crash Fixes crash log:

I don't know, I'm curious myself. The hex given isn't a formid, its a memory location by my understanding.

 

 

 

 

 

This is the easiest solution to the memory issue.

 

Install this manually into the "Skyrim" folder(with the TESV.exe)

SKSE Plugin Preloader

Install this manually by moving the SKSE folder into the "Skyrim\Data\" folder

Crash fixes

 

Then open the "Skyrim\Data\SKSE\Plugins\CrashFixPlugin.ini"

Modify the "UseOSAllocators=0" to "UseOSAllocators=1"

Save.

 

You should be good now.

 

I'd recommend removing the old methods of heap modification, ENBoost is fine.

 

[spoiler=Old Post]

I made this sticky because there is a sudden up-rise in CTD relating to the memory tweaks not working. It is flooding The General forum and has kind of spread to the memory blocks log mod topic. 

 

If you are curious how the memory tweaks work, there is an amazing post by keith over here.

 

There are several reasons for one to CTD or freeze but the most common one is that the SSME/Memory Patch 3.0/SKSE memory tweaks are not applying for some reason.

NOTE: SSME is no longer needed and should be removed and replaced with the SKSE Memory Tweaks.

Safety load is also not needed anymore and may cause unexpected issues.

 

 

First, please copy and paste the following into your SKSE.ini file

Make sure your ini is located as such ...\Skyrim\Data\SKSE\SKSE.ini

If you follow STEP check this out.

[General]
ClearInvalidRegistrations=1

[Memory]
DefaultHeapInitialAllocMB=768
ScrapHeapSizeMB=256

To find out if your memory tweaks are working correctly, download and install Memory Blocks Log.

Run the game through MO, I would recommend fully loading into the game but the main menu will suffice. After which close out of the game and open MO again if it closed on you. Go to the overwrite folder and navigate to the "SKSE\plugins\" folder and open up the memoryblockslog.log.

 

Your log should look similar to this:

logging of blocks enabled
logging max values only
Timer disabled
Block1 Block2
512MB 256MB

However, people that experience a lot of crashing will have something like the following:

logging of blocks enabled
logging max values only
Timer disabled
Block1 Block2
256MB 256MB

The most common "fix" is to open the "Modify Executables" window by clicking the gears on  the top part of MO and select the SKSE executable and add the Argument 

-forcesteamloader

It should then look something like this.

After which, click the modify button and then relaunch the game through MO then close it and make the comparison again. 

 

If your results did not change then make a post below, otherwise search for topics that already exist in the General forum. If your particular issue does not already exist then make a new topic and there will be someone to answer your questions.

 

[GrantSP]

So... do you really need the HDT Physics Extension mod installed? I note that that mod also has a version of Sheson's memory patch included, or at least some code that purports to do the same thing. If you are getting fatal exception crashes from that DLL why not remove it?

I'm not even sure if you have the Memory Blocks Log installed, so if you haven't please do so and edit the INI according to the guidelines in this thread.

[PlukovnikPravda]

I have come to the same conclusion. I did some testing but will do some more to make sure that there is where the wheels fall off the apple cart. So far, I think of not a single mod the needs it. I use the mem blocks log to see where the memory patch is running when the CTD happens. So far, the highest is 339 MB; oddly, it has crashed in Whiterun near the blacksmith at 240 but crashed going from Riverwood up the road to Bleak Falls Barrow and pegged at 339.

 

Thanks, Grant.

--Pravda

[PlukovnikPravda]

So, that wasn't the fix, either. Also, I get the infamous purple texture right before a situation where there is a CTD. Different mods, never repeats. Weird that way.

 

Also, I verified my cache using the Properties tab in Steam. I kept getting "1 File did not verify and will be reacquired." No sure which file, nor when it would reacquire.

 

Finally, I changed permissions to all subfolders in my Games folder of the SSD. Before that, I had a problem using Body Slide 2: it kept giving me "Failed to find Game Path or game reg key" error. Now it doesn't.

 

And still getting CTD. Meh...

[GrantSP]

Purple textures mean whichever mod that is supposed to be supplying that texture... isn't. You can bring up the console and click on the item to see which plugin should be providing it and then examine your load order to see where you messed up.

Steam verification ALWAYS says that, it's a file used to see which files are missing and if anything needs to be re-acquired it will do so immediately. You'll see a download happening in your Steam UI.

[PlukovnikPravda]

Another dumb question (if I were smart, i'd either figure this out or do what you do): I use ENB Injector since I use a laptop. Is the ENBlocal.ini still the same?

 

I'm going thru this one step at a time (pun intended) to see where in the install process I can break it.

Speaking of enbocal...I just changed two hugeazz errors that I shoulda noticed early on.

[cadleo]

  On 12/29/2014 at 11:51 PM, hishutup said:

I made this sticky because there is a sudden up-rise in CTD relating to the memory tweaks not working. It is flooding The General forum and has kind of spread to the memory blocks log mod topic. 

 

If you are curious how the memory tweaks work, there is an amazing post by keith over here.

 

There are several reasons for one to CTD or freeze but the most common one is that the SSME/Memory Patch 3.0/SKSE memory tweaks are not applying for some reason.

NOTE: SSME is no longer needed and should be removed and replaced with the SKSE Memory Tweaks.

Safety load is also not needed anymore and may cause unexpected issues.

 

 

First, please copy and paste the following into your SKSE.ini file

Make sure your ini is located as such ...\Skyrim\Data\SKSE\SKSE.ini

If you follow STEP check this out.

[General]
ClearInvalidRegistrations=1

[Memory]
DefaultHeapInitialAllocMB=768
ScrapHeapSizeMB=256

To find out if your memory tweaks are working correctly, download and install Memory Blocks Log.

Run the game through MO, I would recommend fully loading into the game but the main menu will suffice. After which close out of the game and open MO again if it closed on you. Go to the overwrite folder and navigate to the "SKSE\plugins\" folder and open up the memoryblockslog.log.

 

Your log should look similar to this:

logging of blocks enabled
logging max values only
Timer disabled
Block1 Block2
512MB 256MB

However, people that experience a lot of crashing will have something like the following:

logging of blocks enabled
logging max values only
Timer disabled
Block1 Block2
256MB 256MB

The most common "fix" is to open the "Modify Executables" window by clicking the gears on  the top part of MO and select the SKSE executable and add the Argument 

-forcesteamloader

It should then look something like this.

After which, click the modify button and then relaunch the game through MO then close it and make the comparison again. 

 

If your results did not change then make a post below, otherwise search for topics that already exist in the General forum. If your particular issue does not already exist then make a new topic and there will be someone to answer your questions.

 

This fixed the ILS issue for me. Thank you.

Edited May 7, 2016 by cadleo

[DJenser]

  On 5/7/2016 at 6:44 AM, cadleo said:

This fixed the ILS issue for me. Thank you.

  On 12/29/2014 at 11:51 PM, hishutup said:

I made this sticky because there is a sudden up-rise in CTD relating to the memory tweaks not working. It is flooding The General forum and has kind of spread to the memory blocks log mod topic.

 

If you are curious how the memory tweaks work, there is an amazing post by keith over here.

 

There are several reasons for one to CTD or freeze but the most common one is that the SSME/Memory Patch 3.0/SKSE memory tweaks are not applying for some reason.

NOTE: SSME is no longer needed and should be removed and replaced with the SKSE Memory Tweaks.

Safety load is also not needed anymore and may cause unexpected issues.

 

 

First, please copy and paste the following into your SKSE.ini file

 

 

 

Make sure your ini is located as such ...\Skyrim\Data\SKSE\SKSE.ini

If you follow STEP check this out.

[General]ClearInvalidRegistrations=1[Memory]DefaultHeapInitialAllocMB=768ScrapHeapSizeMB=256

To find out if your memory tweaks are working correctly, download and install Memory Blocks Log.

Run the game through MO, I would recommend fully loading into the game but the main menu will suffice. After which close out of the game and open MO again if it closed on you. Go to the overwrite folder and navigate to the "SKSE\plugins\" folder and open up the memoryblockslog.log.

 

Your log should look similar to this:

logging of blocks enabledlogging max values onlyTimer disabledBlock1 Block2512MB 256MB

However, people that experience a lot of crashing will have something like the following:

logging of blocks enabledlogging max values onlyTimer disabledBlock1 Block2256MB 256MB

The most common "fix" is to open the "Modify Executables" window by clicking the gears on the top part of MO and select the SKSE executable and add the Argument

-forcesteamloader

It should then look something like this.

After which, click the modify button and then relaunch the game through MO then close it and make the comparison again.

 

If your results did not change then make a post below, otherwise search for topics that already exist in the General forum. If your particular issue does not already exist then make a new topic and there will be someone to answer your questions.

After completing my setup of S.T.E.P. Core last night, I have experienced consistent ILS's whenever I attempt to fast travel from my current location near the Windhelm stables to pretty much any other spot on the map. I know they're legit ILS's and not 2 min. LS's because each time, the SPM shows my "disk I/O:" at zero while my RAM & vRAM usage appears to cap out at around their combined 4gb maximum (2gb 750ti/8gb ddr3 system RAM.), and the CPU output locks at a minimum of 25% (Phenom II X4 3.4ghz).

 

All of the textures I've loaded are per recommendations, with none of them higher than 2048, and I have ENBoost running with 768/256 in my Skyrim folder and the latest version of SKSE, which automatically includes Sheson's Memory Patch. I even went in and removed my map mods and deleted several map-related ini tweaks, which many people cited as the culprit in their own ILS's, before finally deleting my Skyrim.ini and SkyrimPrefs.ini (and yes, I have file extensions enabled) and running the launcher to install a fresh set. None of it had any effect. I'll try the block log to see if anything is inexplicably misconfigured, but it's looking like I'm going to have to start uninstalling some of this S.T.E.P. Core eye candy I spent the last several nights setting up, which is a shame, since I was able to run around causing trouble at the docks with a couple followers in tow with only slight frame drops and a single CTD, which is something I've never managed even without a follower. Needless to say, I'll be hanging on to the performance and stability mods, but some of the textures and effects mods may have to go... :-(

Edited May 11, 2016 by DJenser

[Kelmych]

Have you used the spINI application to provide a base set of Skyrim.ini and SkyrimPrefs.ini, and then added the Skyrim ini tweaks in the STEP guide? These can sometimes help reduce problems including ILS.

 

I have several Mod Organizer profiles with different numbers of mods included. At some places like leaving Solitude and leaving the Nightcaller Temple I have found that I get ILS with the profile with the most mods while there is no ILS with the profile that has the fewest (the base set of STEP Extended mods). Users including me have posted that increasing the "DefaultHeapInitialAllocMB=768" parameter in SKSE.ini to a value larger that 768 may help reduce the occurrences of ILS (it has for me). Note that at least for me increasing this value increases random CTDs in the game, so I try to not increase it too much. There are also some discussions in posts about the ILS effects of a few of the INI parameters.

[DJenser]

I suspect it was mostly mod bloat, although I did make sure the [memory] ini tweaks were all in place & that ENBOOST was running (which it was, given that SPM showed my vRAM running consistently around 1400-1900, but my system RAM was sometimes peaking around 2200-2300, indicating that ENBHelper.exe was indeed doing its thing)... I removed the majority of the LOD & flora mods (I tend not to focus on far-off trees & mountains enough to care about those) along with a house mod I no longer use, started from a slightly earlier save in a smaller interior space inside Windhelm proper, and voila, no ILS... And none since. Load times were also reduced to seconds, instead of minutes. I guess I simply needed to prioritize performance over eye candy, so I kept a few nicer textures on the interior spaces, NPCs, weapons, and armor. The rest will have to wait until my cash reserves are up and my spousal aggro is down enough to upgrade my rig again. (Although, I suspect that 4GB cards will be flooding eBay in the coming months, given that the the new GTX 1080's are priced way lower than Titans were last Christmas.)

Edited May 12, 2016 by DJenser

[PlukovnikPravda]

Not to sound stupid or ignorant (oops, too late for me), but how hard is it to swap out GPU in a laptop? When I used a tower, it was easy enough to unscrew the back to access the cards, but the process of removing my old HD from the previous Toshiba was complex. I keep getting the CTD with the Havoc thread as the culprit. But since the previous Toshiba using Win7 and the AMD ran the same load order flawlessly, I have to conclude there's something wrong with Win 10 (yeah! I know - crazy, right?) that I can't fix or optimize.

 

Except with a hammer.

-- Pebcack

[PlukovnikPravda]

Intel HD Graphics Family is pretty well useless for anything other than reading propaganda from Microsoft or Intel. After installing STEP, running LOOT, cleaning mods with TESVEdit, and building a Bashed Patch, the new profile worked...until I left Whiterun for a little quest at Valtheim. Each time it's the graphics adapter failing. Sadly, the solution here is a new rig.

[hishutup]

I thought I posted to your previous comment

...

The integrated graphics is slowly becoming more useful however I'd never use it because I prefer dedicated graphics.

[maedrhos]

I've recently encountered an inability to save my games about 20 hours into play-throughs. I've determined that it isn't being caused by string count or memory block excesses, but I can't determine what is causing it. My install is SRLE plus hunterborn, moonpath and a bunch of follower mods. It works fine off a new install (not a single crash for about 20 hours) until I encounter this. I've been systematically cutting back the mods to find the culprit but since it isn't popping up until well into a game I haven't yet found a smoking gun. There isn't a lot of information on the web or STEP about what causes it but that using the 'player.kill' fix (https://forums.steamp...d.php?t=2994022) does work. I successfully used it about 8 hours ago on my current play-through and it did work....no other problems. My questions are two-fold:....what could be causing it? (or at least what should I be looking for since I've ruled out more obvious things) and why does the 'player.kill' method work? (What is it doing to the game to allow one to continue playing as if the problem never existed?)

[hishutup]

  On 5/22/2016 at 7:07 PM, maedrhos said:

 

I've recently encountered an inability to save my games about 20 hours into play-throughs. I've determined that it isn't being caused by string count or memory block excesses, but I can't determine what is causing it. My install is SRLE plus hunterborn, moonpath and a bunch of follower mods. It works fine off a new install (not a single crash for about 20 hours) until I encounter this. I've been systematically cutting back the mods to find the culprit but since it isn't popping up until well into a game I haven't yet found a smoking gun. There isn't a lot of information on the web or STEP about what causes it but that using the 'player.kill' fix (https://forums.steamp...d.php?t=2994022) does work. I successfully used it about 8 hours ago on my current play-through and it did work....no other problems. My questions are two-fold:....what could be causing it? (or at least what should I be looking for since I've ruled out more obvious things) and why does the 'player.kill' method work? (What is it doing to the game to allow one to continue playing as if the problem never existed?)

 

They is supposedly a proper fix with Crash Fixes

[maedrhos]

  On 5/22/2016 at 9:19 PM, hishutup said:

They is supposedly a proper fix with Crash Fixes

Thanks for giving it some thought. I installed that three weeks ago when Neo put it in the SRLE build hopeful that my problem was the newly discovered string limit. But the problem came up again last week and my string count never reached the former limit which is why I'm sure it's not a string issue. It's something else but I don't know where to look now. I'm hopeful that the 'player.kill' fix is the answer but since I don't know what it is truly doing to the game I can't be sure I'm not just creating more problems. I live in hope of actually finishing the game someday.

Edited May 22, 2016 by maedrhos