Common CTDs, Freezes, ILS and memory issues

[hishutup]

 

 

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.

 

[DoubleYou]

Map menu crashes can happen due to bad INIs as well.

[Amuscaria]

I've redid the inis from scratch following the step guides. Still crashes on startup 50% of the time. 50% it crashes on load. This is a lot better with the ENB disabled, although the game still crashes for reasons I can't tell. 

 

What should I set for "VideoMemorySizeMb="? STEP tells me to use the Memory checker, which gives 16000, and subtract 170. I was told the Max should be 10240. Another tutorial told me to use my maximum video memory and subtract 170, so 7915-170 = 7745. I can't tell if my ENBoost is even working. I tried installing the Skyrim Performance monitor, but the program fails to launch. Tells me I don't have Net Immerse 2.0 (when I have a newer version).

 

I've also extended the SKSE memory patch to 1024 (1280 in skse.ini).

 

Nothing is helping.

 

Disabling all of my mods don't help wither, as the thing crashes on the main menu WITHOUT any mods.

[RhinoW]

Hi, so i was playing skyrim and i got a random ctd.

 

The thing is before i could just load back into the game, now i get a crash message when trying to load the game. Here's what it appears:

 

11 Dec 15:24:37 Game has crashed while reading binary data stream! This could indicate a corrupt NIF file. Here are the last opened files starting from most recent:

 

D:\SteamLibrary\steamapps\common\Skyrim\DATA\TEXTURES\armor\thievesguild\f\thievesguildarmorclothesf_n.dds" 0.000000 seconds ago.

 

D:\SteamLibrary\steamapps\common\Skyrim\DATA\TEXTURES\armor\thievesguild\f\thievesguildarmorclothesf.dds" 0.000000 seconds ago.

 

D:\SteamLibrary\steamapps\common\Skyrim\DATA\TEXTURES\armor\thievesguild\m\thievesguildarmortorsom.dds" 0.016000 seconds ago.

 

D:\SteamLibrary\steamapps\common\Skyrim\DATA\TEXTURES\actors\character\female\femalebody_1_s.dds" 0.250000 seconds ago.

 

D:\SteamLibrary\steamapps\common\Skyrim\DATA\MESHES\actors\character\character assets\skeletonbeast.nif" 0.469000 seconds ago.

 

D:\SteamLibrary\steamapps\common\Skyrim\DATA\TEXTURES\armor\zga_amulet\gauldur_g.dds" 0.469000 seconds ago.

 

D:\SteamLibrary\steamapps\common\Skyrim\DATA\TEXTURES\armor\zga_amulet\gauldur.dds" 0.485000 seconds ago.

 

D:\SteamLibrary\steamapps\common\Skyrim\DATA\MESHES\armor\amuletsandrings\zga_amulet\gauldurmale.nif" 0.485000 seconds ago.

 

Sometimes other files appear, but its usually the gauldur amulet, thieves guild armor, femalebody and skeletonbeast.

I would appreciate any help i can get.

[aragonit]

Playing with the new STEP version and my usual other mods gives me LOTS of CTDs and out of memory crashes. I have another installation still here with the old STEP, and I used to play for days without a single CTD. Could DyndoLod be the reason for the memory problems?

[Cat]

Just wanted to say that I have been experiencing almost always random CTDs and usually just an ILS after a fresh (correct) installation of STEP. the solutions with INI modification didn't help, I installed Safety Load and it solved the problem.