Message from crash fixes skyrim ошибка

Описание
Файлы
История версий

К комментариям (168)

ExpandSystemMemoryX64=false
ReduceSystemMemoryUsage=true

➔ SKSE.ini (в папке Data/SKSE) (если его нет, можете скачать с Nexus’а)

DefaultHeapInitialAllocMB=768
ScrapHeapSizeMB=256

➔ Skyrim.ini (в папке Документы/My Games/Skyrim)

uExterior Cell Buffer=36
bPreemptivelyUnloadCells=0

fPostLoadUpdateTimeMS=500 (можно поднять до 1000+)*
fUpdateBudgetMS=1.2 (можно поднять до 2.0)*
fExtraTaskletBudgetMS=1.2 (можно поднять до 2.0)*
bEnableLogging=0
bEnableTrace=0

[Patch]

; Info: Completely disable Skyrim’s memory allocator and use regular C malloc. That means memory blocks will not exist anymore

;       and game will not crash at some arbitrary limit. Theoretically it should also be faster (especially loading screens)

;       and eliminate most ILS or freezing issues.

; IMPORTANT!!: You NEED custom plugin loader to run this so CrashFixPlugin.dll gets loaded before the game initializes!

; When this is enabled then Safety Load and SSME/SKSE memory patch are not needed, but they don’t cause any trouble if you do have them.

UseOSAllocators=1

; Info: When the game crashes unexpectedly then write the relevant information from crash to Data/SKSE/Plugins/CrashLog/crash_time.txt

;       If game crashes when running out of memory or has other issues it’s possible for the file to not appear or become empty!

;       If the game crashes in SKSE dll or a SKSE plugin dll then it’s possible for the crash information to not appear.

;       This setting’s value is treated as flags where:

;       1 — enabled (TL;DR set this for normal enable)

;       2 — don’t write timestamp into file name but instead always write to crash_last.txt (overwritten by default)

;       4 — don’t ignore already known crashes, usually ones that display a message box are ignored

;       8 — append file if it already exists instead of replacing

;       16 — when the game crashes CTD without a message box about game stopped responding

RecordCrashInfo=1

; Write messages that appear in error box also to file in «Data/SKSE/Plugins/CrashFixPluginLog.txt»

LogMessageToFile=1

; Info: Warn user on startup if ENB settings are incorrect.

WarnBadENB=1

; Info: Crash happens unknown constructor (TESObjectLAND::unk_24 object), movaps instruction is used

;       but heap allocate did not allocate this object to have 16 align. Crash happens more frequently

;       with high Ugrids because more cells are loaded and greater chance to misalign.

; Solution: Could align only this object or align all objects. Trying with all to see what happens since

;       same error could be elsewhere as well and I think I have seen it elsewhere.

; Result: Fixes these type of crashes. Some people report longer loading times and higher memory usage with this enabled!

; Update: Disabled by default since it’s incompatible with some ENB settings, higher memory usage and longer loading times.

;         It’s safe and probably good to enable if you are ok with those downsides. I have not personally experienced

;         any incompatibility with ENB, some people say it messes up their game that’s why I wrote it here.

AlignHeapAllocate=0

; Info: Game crashes when strcmp is passed NULL char*

; Address: D573A8

; Cause: Most frequently happens in TthkbClipGenerator::activate (0xBF2FB3),

;        tracked issue to skeleton was deleted in another thread while

;        this function is attempting to use it. Have seen in other places

;        too.

; Solution: Unknown. This doesn’t really fix it for BF2FB3 because it just pops up in foot IK.

;        If patched in foot IK it pops up in hand IK, the problem is larger than just this.

;        Still enabled because it may fix crashes in other places too this is a very common function.

;        There’s really no reason not to have it since the game would crash certainly with this off.

; Enable one. NoTry may be slightly faster but catches less crashes.

StrCmp=1

;StrCmpNoTry=1

; Info: Game crashes when strlen is used on NULL char*

; Address: 46EDF0

; Cause: NiNode names are compared, one of the NiNode’s name is NULL.

; Code:

; NiNode ** v72 = NiNode::children.data — this is iterated until count

; NiNode * v69 = …

; const char * v56 = v69->name;

; if ( v56 )

; {

; const char * v57 = v72[v49]->name; // <- v57 name is not checked for NULL for some reason ?

; _strnicmp(v56, v57, strlen(v57)); <- strlen on NULL, also result is not even used anywhere!

; }

; Solution: Unknown, temporarily bypass whole strcmp since it’s unused.

; Result: Seems to have stopped the crash for me.

StrLen=1

; Info: Unknown, reported as loading save game.

; Address: 8B437C — vtable seems to be 0 or wrong pointer is used.

; Solution: Skip since this is the last part of the function and already has a check anyway

UnkUniqueId=1

; Info: Unknown, reported as loading save game. Possibly related to rendering. First

;       argument is gNiDX9Renderer->unk_650 which is a pointer.

; Address: CEC5EC — null pointer is passed as second argument to function, this function does not expect it

; Solution: Bypass using argument if it’s null. Maybe doesn’t fix.

Render650=1

; Info: Unknown, no info was provided. // char __thiscall TESObjectREFR::unk_4D4EB0(TESObjectREFR *this)

; Address: 4D4EB9 — vtable of base form is 0

; Solution: Bypass and pretend that base form is 0 since the function does this check itself already

UnkObjRef4D4EB0=1

; Info: Game is saving location’s seen data to save game. The data is NULL.

; Address: 4C6031

; Cause: Game doesn’t check for null pointer

; Code:

; TESObjectCELL * v3 = …

; v5 = BaseExtraList::GetSeenData_40D980(&v3->extraData);

; result = (void *)(*((int (__thiscall **)(_DWORD, _DWORD))*v5 + 1))(v5, v2); // <— v5 can be null! but not checked

; v5 is IntSeenData, size is known.

; Solution: Only solution seems to be temporarily creating an empty IntSeenData and writing this to stream instead.

NullSeenData=1

; Info: BSFixedString::Set is called with NULL argument.

; Address: A51285

; Solution: Ignore call when NULL argument. Not really a solution probably better than crashing though.

StringRefSetNull=1

; Info: This crash happens because StrLen crash was prevented.

; Address: 46EE1D

; Solution: Skip over it.

; Result: See StrLen.

SkipStrLenCrash=1

; Info: This crash happens because unknown reasons during loading. Something to do with behavior graph.

;       One of the more common crashes I get.

; Address: C27A8F

; Solution: Don’t know, trying to let game think the value is 0 and see what happens.

; Result: Haven’t had this crash since.

bhvGraphUpdateLoad=1

; Info: Crash happens during loading, no idea. Might be related to rendering.

; Address: D822D8

; Solution: Tried patch something but it probably doesn’t work.

Unk11=1

; Info: Incompatible skeleton, but could be something else too.

; Address: 46ECF5 — NiNode children access

; Solution: No solution from here, but since it’s going to crash anyway we could at least

;           warn user about possible incompatible skeleton and let them fix it. Shows messagebox

MissingNode=1

; Info: Crash, it’s function array and index goes out of bounds which causes it to call invalid address.

; Address: 6F3A31

; Solution: Check index before calling.

; Result: Haven’t had this crash since.

IndexError1=1

; Info: Crash happens in «MovementPlannerAgentWarp» function, unknown what it does. LookupFormById returns

;       NULL and game does not check or expect this to happen.

; Address: 76E358

; Solution: Game has a check for if returned isn’t actor it sets 0 as value, we will do same if NULL is returned.

MovementPlannerAgentWarp=1

; Info: Crash happens in DDB0A0, seems to be used in some havok animated object’s vtables.

;       Normally these crashes are fixed by aligning allocated memory with 16 bytes. But

;       this one isn’t because it can be used on static memory locations which aren’t using

;       Skyrim’s allocator at all, this means that memory isn’t guaranteed to be 16 byte aligned.

; Address: DDB0B2

; Solution: Use movups instruction instead of movaps.

UnallocatedMovaps=1

; Info: Weird crash with NULL ptr in TESWorldSpace::GetCellByCoordMask_4375D0, don’t know why it happens.

; Address: 437604

; Solution: return 0 if this crash would happen.

; Result: Haven’t had this crash since, but it’s rare anyway so it could be coincidence.

CellNullCrash=1

; Info: Crash when trying to do: v14 = MagicItem::unk_406C70(a3)->properties.projectile;

;       This 406C70 function is something like «GetMainMagicEffect». Sometimes though it may return

;       NULL and in 90% of places the game expects this and checks for NULL result, this patch will

;       fix the remaining locations.

; Address: 7E39EC, 657677, 6577D5, 65FEEC, 8127CF

; Solution: Check for NULL and skip (depends on location) if it is.

GetMainMagicEffect=1

; Info: Crash when game searches node «NPC COM [COM ]» on actor but the node was not found. This is unexpected

;       for game because it uses the result without checking for NULL. This whole thing has something to do

;       with mounting. The function that does this whole thing is present in «StopMountCameraHandler» and

;       «MountInteraction» vtable. Also it seems that this has something to do with updating position.

; More info: Was reported that this could happen if non-humanoid tries to mount a horse. This is a rather specific

;            error with a mod. Instead we will show error message to user when this happens so they can

;            fix or uninstall that mod.

; Address: 6E7F85

; Solution: Check for NULL and if it is NULL then use base node of actor instead of this. It’s fine because

;           we only take X and Y position from it.

; Solution2: Show error message and crash after.

MountNodeCrash=0

MountNodeWarn=1

; Info: Crash when game is trying to setup foot IK but there’s a problem. Real cause is unknown but for me.

;       So we will display a message box when this crash happens. Seems related to the

;       StrCmp crash in BF2FB3, maybe. Try reducing the amount of installed animations.

; Address: BFECC1

; Solution: No solution from here, display warning with helpful tips.

IKCrashWarn=1

; Info: Crash happens when rendering and saving. I think this is when it renders the save game image.

; if ( v8 ) // <- not null

; {

;  if ( v8 )

;    v9 = *(v8 + ; // <- *(v8 + is null

;  else

;    v9 = 0;

;  v10 = *(v9 + 140) * *(a2 + 4) // <- crash because null

;    + *(v9 + 136) * *a2

;    + *(v9 + 144) * *(a2 + ;

;  v21 = v10 — *(*(v8 + + 148) * a3;

; }

; Address: CB051A

; Solution: We will skip this if block when *(v8 + is null, as if v8 was null.

RenderSave=1

; Info: Crash was reported as casting spell. Only happens sometimes. Happens in movement controller.

;       Seems like vtable is NULL.

; Address: 76636B

; Solution: This happens in a for loop and it happens in if clause. We can skip if this crash would happen.

MoveControllerCast=1

; Info: Crash when saving game and trying to render (possibly save game image again?). It’s trying to get

;       vtable of NULL pointer which will crash.

;   if ((*a2 + 76)(a2, a1)) // a2 is null

;   {

;     *(0x1BA9344) = a1;

;     *(0x1BA9340) = a2;

;   }

;   else

;   {

;     *(0x1BA9340) = 0;

;     *(0x1BA9344) = 0;

;   }

; Address: CAF9F7

; Solution: Skip function call and set return value to false so we don’t have to use the NULL value.

SaveRenderCrash=1

; Info: Crash when game tries to get loaded node but it is set to NULL. Only ever seen this on two people.

;       It is most likely actually related to corrupted mesh being unable to be loaded and game does not expect it.

;       NiNode * node = a->GetLoadedStateNiNode();

;       v2 = node->(*(vtable+0x14))(); // <- node is NULL

;       if(v2) { *((int*)(v2 + 212)) = 0; } // <- we can skip this part since it has a check anyway

; Address: 4C119E

; Solution: Real solution would be to find the broken mesh and remove it. So lets notify user instead of ignoring this part.

; Enable one of the following, ignore problem and try to continue or show message box with object reference form ID and form Type.

NullLoadedNodeIgnore=0

NullLoadedNodeNotify=1

; Info: Crash in GarbageCollector::Add when actor argument’s base form is NULL. Game does not check this, when in

;       some other places it does check for this possibility.

; Address: 690A69

NullActorBaseForm=1

; Info: Crash when modifying actor value but the pointer is bad, possibly due to actor being invalid. This happens often

;       when script engine is lagged and spells want to modify actor values a lot.

; Address: 6E07C6

AVSetCrash=1

; Info: If your scripts use more than 65535 different strings then the save game will be corrupt and not possible to load.

;       This fixes it by changing the save file format slightly if string count is higher than 65520. That means if you

;       have this option enabled and your save game would have become corrupt it changes format instead and vanilla game

;       or save game tools will not be able to open it! Opposite is true as well, if the count goes below 65520 after

;       and you save again then the format reverts to vanilla.

; Address: Around 30 different parts of code had to be patched.

StringCount32=1

; Info: Warn if SKSE memory patch is not active. This checks if default heap size is 256 or less and warns if you try to

;       click New, Continue or Load in main menu. Still lets you play the game, just shows a warning.

WarnSKSEMemoryPatch=1

; Info: If AlignHeapAllocate is disabled by user then fix that one movaps crash manually. There’s no downside to having this enabled.

; Address: 4BD832

FixMovApsManuallyIfAlignedAllocateIsDisabled=1

; Info: Overwrite array allocator directly when UseOSAllocators is set to 1. Don’t understand the code enough yet to

;       say if it’s safe or not. At this point it’s just here for testing.

OverwriteArrayAllocator=0

; Info: Player’s NiNode (not necessarily same as loaded node) is NULL while drawing world.

; Address: 69B84B

NullPlayerNode=1

; Info: Function TESObjectREFR::CanBeMoved_4D9CF0 is called on an object reference that has NULL base form. This is not expected

;       and will crash. We will instead return false from that function if that’s the case. The problem is most likely larger than

;       just this, if you prefer to crash instead disable it.

; Address: 4D9D09

NullBaseFormMove=1

; Info: Game tries to iterate child nodes of a NiAVObject but it’s possible that the target is not a NiNode and can’t have child nodes.

;       This ends up in a NULL pointer crash.

;  v26 = v22->vtable->sub_5EADD0(v22); // Returns «this» if v22 is a NiNode and returns «NULL» if not.

;  for ( i = 0; i < v26->children.emptyRunStart; ++i ) // crash because v26 is NULL.

; Address: 46CA06

NullRefNode=1

; Info: Something is done with outfit of NPC, but one or more entry is NULL and game crashes.

; Address: 561FF7

NullOutfitEntry=1

; Info: Actor is being deleted and base form is NULL.

; Address: 6BAC9A

ActorDeleteNullBase=1

; Info: Does two things:

;    1. Tracks the last X files opened by game.

;    2. If the game crashes while reading binary data stream (e.g. NIF file but could be others too) then show message box listing

;       those files.

; This can be helpful to track down a corrupted NIF file.

DebugStream=1

; Info: When the game fails to create texture in memory should we display a warning and exit game? Recommended yes because you will

;       see purple textures couple of seconds and then the game will crash anyway since it’s not expected for this to be a NULL value.

WarnTextureFailure=1

; Info: Something is done with face gen animation on BSFaceGenNiNode but the parent node is NULL which is unexpected.

; Address: 5A8808

NullParentNode=1

; Info: For debugging purposes, on game startup run allocator benchmark and write results to «AllocatorBenchmark.txt» in Skyrim root

;       directory. This compares vanilla, aligned vanilla, malloc, aligned_malloc and custom memory block implementation. When you reach

;       main menu the game will start the test, wait for a message box to say the test is completed, then close game and disable this option.

RunAllocatorBenchmark=0

; Info: How many objects to allocate and free for each size (8, 12 and 16).

CountAllocatorBenchmark=1000000

; Info: How many times to run each test.

TimesAllocatorBenchmark=2

; Info: How many threads to run concurrently. Most accurate is only running one thread, although you can also try 2 to see the performance

;       of thread-safe code.

ThreadsAllocatorBenchmark=1

; Info: Enable custom block allocator for small sizes. May help with memory fragmentation problem. This option does nothing if UseOSAllocators

;       is not enabled.

CustomMemoryBlock=1

; Info: Set total megabytes allocated for the custom block allocators. This amount is sensibly divided between each block.

;       Has no effect if CustomMemoryBlock is not enabled. The more you allocate here the less memory you have for other stuff!

CustomMemoryBlockTotalSizeMb=64

; Info: Show usage of each memory block in per cent when you open console. Has no effect if CustomMemoryBlock is not enabled.

;       This can help you tweak the CustomMemoryBlockTotalSizeMb value.

MemoryInfoConsole=1

; Info: Fixes two crashes specific to Enderal mod. Seems like something to do with havok.

; Address: EBC0A6 and ECD92E

EnderalSpecific=1

; Info: Active effect list of actors is not thread safe but accessed and modified from multiple threads, this will add mutex to each actor’s

;       effect list.

FixUnsafeEffectList=1

; Info: Game crashes when actor’s combat style form is NULL for some reason. Warn the user and try to display the actor’s reference and base ID.

; Address: 8368B1

WarnNullCombatStyle=1

; Info: Set OS update frequency to 1 millisecond (regular is around 16) and replace GetTickCount with timeGetTime. This is for debug only! Don’t use.

;       May reduce performance.

HighFrequencyOSTimer=0

; Info: Make game’s update timer more accurate. This is for debug only! Don’t use.

HighFrequencyGameTimer=0

Skyrim came out a long time ago but the game still has a massive player base due to its sheer size and the number of different side quests. However, users who either installed too many mods or simply regular users encounter this weird error while playing Skyrim regularly.

(Проблема решена) Skyrim продолжает вылетать (легко)

Если ваш Skyrim вылетает на вашем компьютере, не волнуйтесь! Вы можете исправить сбой Skyrim с помощью решений, описанных в этой статье. Проверить это!

Было бы так неприятно, если бы Skyrim вылетает на вашем ПК. Но не волнуйтесь. Вы можете исправить сбой Skyrim и улучшите свой игровой опыт.

Как исправить Skyrim Crash?

Вот решения, которые вы можете попробовать исправить. Нет необходимости пробовать их все; просто двигайтесь вниз, пока проблема сбоя не будет решена.

Способ 1. Установите последний патч

Разработчики программ обычно продолжают выпускать патчи для улучшения программы и исправления некоторых ошибок, как и Skyrim. Вам следует установите последние патчи Skyrim и держите игру в курсе . Затем перезагрузите компьютер. Это должно исправить сбой Skyrim.

Skyrim обычно дает сбой, когда драйверы вашего устройства отсутствуют или устарели, особенно драйвер видеокарты. Поэтому вам следует проверить драйверы устройств на своем компьютере, убедиться, что все драйверы верны и обновлены, а также обновить те, которые не установлены.

Обновление драйверов вручную — Вы можете обновить драйверы вручную, перейдя в сайт производителя и ищу самые последний правильный драйвер для ваших устройств. Если у вас нет времени, терпения или навыков работы с компьютером для обновления драйверов вручную, вместо этого вы можете сделать это автоматически с помощью Водитель Easy .

Автоматическое обновление драйверов — Driver Easy автоматически распознает вашу систему и найдет для нее подходящие драйверы. Вам не нужно беспокоиться об ошибке при установке.

Вы можете автоматически обновлять драйверы с помощью СВОБОДНЫЙ или За версия Driver Easy. Но с версией Pro это займет всего 2 клика (и вы получите полную поддержку и 30-дневная гарантия возврата денег ):

1) Скачать и установите Driver Easy.

2) Запустите Driver Easy и нажмите Сканировать сейчас кнопка. Driver Easy просканирует ваш компьютер и обнаружит проблемы с драйверами.

3) Щелкните значок Обновить рядом со всеми отмеченными устройствами, чтобы автоматически загрузить и установить правильную версию своего драйвера (это можно сделать с помощью СВОБОДНЫЙ версия).

Или нажмите Обновить все для автоматической загрузки и установки правильной версии всех драйверов, которые отсутствуют или устарели в вашей системе (для этого требуется Pro версия — вам будет предложено выполнить обновление, когда вы нажмете Обновить все ).

4) После обновления драйверов перезагрузите компьютер и снова попробуйте Skyrim, чтобы проверить, работает ли он.

Метод 3: отключить моды

Моды, которые вы устанавливаете для Skyrim, также могут вызывать сбой, поэтому, если вы установили моды в Skyrim, вы можете попробовать следующее:

1) Отключить моды в вашем Skyrim.

2) Попробуйте свой Skyrim, чтобы убедиться, что он работает правильно.

3) Если Skyrim перестает давать сбой, скорее всего, проблема связана с модами, и вам следует удалить моды .

Если Skyrim по-прежнему вылетает, вы можете попробовать следующий метод.

Never clean your «Skyrim.esm» file or you risk bricking your game. Some mods also have the same issue and need their .esp files cleaned through the same process, but always read the mod page before deciding to clean a mod’s .esp file.

Anniversary Edition Is Running Scripts Too Quickly

The Anniversary Edition of Skyrim has updated the Papyrus Engine, Skyrim’s scripting engine. If you have modded Skyrim with multiple scripting mods, there’s a chance that your game can immediately crash since Payprus scripts run much faster now. While a great step forward for the modding community long-term, it does mean that some mods are unstable as of writing.

The Solution

Reddit user u/SailingRebel has created an update to Skyrim’s PapyrusUtil file that should fix most of these issues. Download the file and extract it to your Skyrim directory. Say «yes» to any overrides the file needs to make. Alternatively, you can revert the version of Skyrim you’re using to bypass the Anniversary Edition’s changes. You can do this with the Unofficial Skyrim Special Edition Downgrade Patcher mod created by halgari.

Note: The Papyrus solution is temporary. Mod authors will need to update their mods to support AE’s improved scripting for this issue to truly go away.

Skyrim Runs Out Of Memory

The original release of Skyrim on PC doesn’t utilize your memory as well as the Special Edition. If you’re still using the original version of Skyrim, the game can only use up to 4GB of RAM at a time. Going over that value will crash your game.

The Solution

Skyrim: Special Edition has a far higher memory limit that is impossible to reach with current hardware. If you play on the Special Edition, memory-related crashes are not a concern. If you’re still concerned about memory, install the SSE Engine Fixes mod from authors aers, Nukem, and Ryan.

ENBoost is an external piece of software intended to be used alongside an ENB, although ENBoost can be used without an ENB active. This app essentially lets Skyrim use your video card’s VRAM as additional RAM to bypass the 4GB restriction. An in-depth guide on how to install and use ENBoost can be found on the S.T.E.P. wiki. Special Edition users do not need ENBoost nor benefit from it in any way.

SKSE’s Memory Fix is a line you can add to your Skyrim Script Extender’s .ini file to improve Skyrim’s memory allocation to prevent certain crashes from occurring. You’ll need Skyrim Script Extender, an external executable file, for this to work. Special Edition users do not need to enable a memory fix. Once installed, head to «SKSE.ini» and replace the contents of that file with the following:

Display

iTintTextureResolution=2048

General

ClearInvalidRegistrations=1

Memory

DefaultHeapInitialAllocMB=768

ScrapHeapSizeMB=256

ИНФОРМАЦИЯ : Если вам нужно включить эту службу, щелкните службу правой кнопкой мыши и выберите Начало чтобы включить его.

Что делать если скайрим вылетает в меню и на рабочий стол

Если игра начала вылетать просто так, демонстрируя серый экран или показывая главное меню прямо посреди игры, то причина ― в поврежденных файлах сохранения. Скачайте чужие сейвы из интернета и попробуйте запустить скайрим с ними.

Когда вылет в главное меню или на рабочий стол происходит сразу же после нажатия на кнопку «Играть», вам необходимо скачать новую версию DirectX. Необновленный драйвер способен загрузить главное окно, но не может прогрузить локацию .

Иногда подобный баг единоразовый. В таком случае переживать не стоит.

Почему skyrim вылетает с модами

Многие люди жалуются, что их игра постоянно закрывается после установки модификаций. Это частая проблема, но решить ее не так просто. Какая-то из программ конфликтует с другими. Чтобы это проверить, поставьте софт Loot и отсортируйте модификации.

Если это не помогло, скачайте Nexus Mod Manager и отключите все моды. Включайте их поочередно и проверяйте, после чего именно игра начинает самопроизвольно закрываться. Проверьте наличие «модов для модов» вроде SkyUI.

Pinpointing how this occurred is typically difficult and changes on a case-by-case basis. However, even those who have never modded their game might suffer from a corrupt version of Skyrim out of the blue. Unfortunately, your best bet to fix this type of error is to reinstall the game entirely or validate the integrity of your game files.

Fix 3: Install the latest version of DirectX

Apparently, most players were installing a version of DirectX that wasn’t stable and causing the game to crash on startup. We recommend that you download and install the latest version of DirectX from the official Microsoft website. Select Repair and Install if the software is present on your computer and wait for the process to complete.

The Skyrim crashing could be caused by a missing or outdated graphics driver on your computer. You can update your GPU driver to the latest version to solve the problem. To update your driver:

1. Press Win+X keys and select Device Manager from the menu list.
2. Expand the Display adapters option.
3. Right-click on your graphics device and select Update driver.
4. In the pop-up window, click Search automatically for updated driver software.
5. If Windows couldn’t update it, then download and install the latest driver version from your graphics card manufacturer’s website.

Once the update is complete, restart your computer and launch Skyrim to see if it works correctly.

Вы можете автоматически обновлять драйверы с помощью СВОБОДНЫЙ или За версия Driver Easy. Но с версией Pro это займет всего 2 клика (и вы получите полную поддержку и 30-дневная гарантия возврата денег ):

Solution 4: Turn Off ffdshow Audio And Video Decoders

Users suggested turning off these audio and video decoders if you have them installed on your computer, which can be done easily by settings these programs as exceptions in the game itself. If you are not able to locate these programs on your computer, that means that you don’t have them installed and you can simply skip this solution.

1. Click either on the Start menu or the Search button located next to it and type ffdshow in the search bar.

1. Click on either the audio or the video decoder (you will need to repeat the same process for both of them) and wait for them to open.
2. You will be able to see a menu on the right which consists of several options. Navigate to the DirectShow control section.
3. Check the box next to the “Don’t use ffdshow in:” option and click on Edit.

1. Locate Skyrim.exe either from the list which will open up or click on the Add button and locate Skyrim’s executable file on your computer.
2. Repeat the process for the other decoder you haven’t opened and check to see if the error appears again.

Solution 5: Verify Integrity of Game Cache

Verifying the integrity of game cache is an option available solely to Steam users who have downloaded the game from there. This is quite a good fix since this option will search through your Skyrim files in search of a broken one and it will also automatically download any missing or corrupt files. Follow the steps below to achieve this.

Changing the sound settings in Control Panel on your PC is an official fix by Bethesda which seems to have helped plenty of people in dealing with random crashes to the Desktop. This will, however, change the sound settings on your PC but the change will probably go unnoticed and the error will be gone forever. Sound problems in Skyrim is a known problem.

1. Right-click on the Volume icon located at the bottom right part of your desktop screen (system tray) and choose the Playback devices option.
2. In the Playback tab of the Sound window (which just opened up), select your default playback device (Speakers).

1. Right-click on the device and choose the Properties option. When the Properties window opens, navigate to the Advanced tab.
2. Under the Default Format section, click the arrow button next to the quality mode and choose this option:

Skyrim developers release new patches to troubleshoot existing/known bugs of the game. If the crash you are facing is a result of a known bug that is already patched in the latest version, then installing the latest patch will solve the problem. Make sure that you have your credentials at hand so you can log back in after the update.

Solution 1: Loading Old Save Game in Skyrim

What always seems to work for the users is to just load an older save game. You cannot get a corrupted savegame back and the progress stored in that savegame has been lost. In most cases, loading an older save game fixes the issue and the game starts to work properly. We recommend that during gameplay, always remember to perform a quicksave every now and then.

Also, we strongly suggest that you create a new savegame through the Pause Menu as soon as you get a chance.

Solution 2: Using Player Kill Command

What seems to be a common workaround for this predicament, players use the self kill command to trigger an auto-reload which seems to load the game up just fine. Below, we have listed the method to trigger an auto-reload.

Common Workaround:

1. Load the game that had the crashing bug in it.
2. Use the “Player.kill” command as instructed above.
3. Try to save and check if it works.

Hi there, I’ve recently started to install some mods in my Skyrim LE, after lots and lots of reading in guides, forums and watching videos about how to mod correctly your game, then I thought I did everything correctly when I started to install my mods, but when I started my playthough, right after leaving the cave from Helgen, this message from the mod Crash Fixes has appeared:

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:

C:Program Files (x86)SteamsteamappscommonSkyrimDATASOUNDfxmag_isfiremag_fire_ready_lp.wav» 0.110000 seconds ago.

C:Program Files (x86)SteamsteamappscommonSkyrimDATASOUNDfxmag_isfiremag_fire_charge_050.wav» 0.141000 seconds ago.

C:Program Files (x86)SteamsteamappscommonSkyrimDATASOUNDfxfst_isstonelightrunlfst_stone_light_run_001.wav» 0.594000 seconds ago.

C:Program Files (x86)SteamsteamappscommonSkyrimDATASOUNDfxfst_isstonelightrunrfst_stone_light_run005.wav» 0.891000 seconds ago.

C:Program Files (x86)SteamsteamappscommonSkyrimDATASOUNDfxfst_isfst_npcstoneheavywalkfstnpc_stone_heavy_walk_003.wav» 1.375 seconds ago.

C: Program Files (x86)SteamsteamappscommonzSkyrimDATASOUNDfxmag_isfrostmag_frost_bolt_001.wav» 1.594 seconds ago.

C:Program Files (x86)SteamsteamappscommonSkyrimDATASOUNDfxfst_isfst_npcstoneheavywalkfstnpc_stone_heavy_walk_004.wav» 1.688 seconds ago.

C:Program Files (x86)SteamsteamappscommonSkyrimDATASkyrim — Sounds.bsa» 1.703 seconds ago.

I’m not an expert when modding my games, so I came here to see if anyone could help me to solve this issue. I already tried to find my answer in some other forums and videos on yt, but without luck. Here’s my load order from LOOT if that can help in any way:

0 0 Skyrim.esm

1 1 Update.esm

2 2 Dawnguard.esm

3 3 HearthFires.esm

4 4 Dragonborn.esm

5 5 RSkyrimChildren.esm

6 6 ClimatesOfTamriel.esm

7 7 hdtHighHeel.esm

8 8 Diverse Random NormalAttack.esp

9 9 HighResTexturePack01.esp

10 a HighResTexturePack02.esp

11 b HighResTexturePack03.esp

12 c Unofficial High Resolution Patch.esp

13 d FMS_FemaleMakeupSuite.esp

14 e SaturationBoost.esp

15 f The Dance of Death — Ultimate Edition.esp

16 10 VioLens.esp

17 11 RLO — Interiors.esp

18 12 JKs Skyrim.esp

19 13 Skyrim Immersive Creatures.esp

20 14 RLO — Exteriors.esp

21 15 OBIS.esp

22 16 OBISDB.esp

23 17 Immersive Sounds — Compendium.esp

24 18 Thunderchild — Epic Shout Package.esp

25 19 Skyrim Immersive Creatures — DLC2.esp

26 1a Hothtrooper44_ArmorCompilation.esp

27 1b SMIM-Merged-All.esp

28 1c Immersive Patrols II.esp

29 1d Hothtrooper44_Armor_Ecksstra.esp

30 1e Immersive Weapons.esp

31 1f 12FemaleBrows.esp

32 20 SGEyebrows.esp

33 21 MBO Pack by Team TAL.esp

34 22 XPMSE.esp

35 23 RaceMenuMorphsCBBE.esp

36 24 UIExtensions.esp

37 25 AddItemMenuLE.esp

38 26 FNIS.esp

39 27 FISS.esp

40 28 AMatterOfTime.esp

41 29 Vivid Weathers.esp

42 2a Vivid Weathers — Extended Snow.esp

43 2b Vivid Weathers — Extended Rain.esp

44 2c Apocalypse — The Spell Package.esp

45 2d TheEyesOfBeauty.esp

46 2e ClimatesOfTamriel-Dawnguard-Patch.esp

47 2f Critical Hit.esp

48 30 DeadlySpellImpacts.esp

49 31 ISC DeadlySpellImpacts Patch.esp

50 32 Deadly Destruction.esp

51 33 EnchantmentPower.esp

52 34 dD — Enhanced Blood Main.esp

53 35 ISCompendium Enhanced Blood Patch.esp

54 36 Eyes of Aber.esp

55 37 towConversation.esp

56 38 HDT Capes.esp

57 39 HDTPhysicsWeaponSling.esp

58 3a HDT Female Hairstyles.esp

59 3b HorseCloak.esp

60 3c KJ Tattoos 4K.esp

61 3d LFox Pickpocketing Chance Caps at 100.esp

62 3e RSChildren.esp

63 3f RLO — Effects.esp

64 40 SkyHUD.esp

65 41 StrangeRunes.esp

66 42 True Master Trainers.esp

67 43 Abundant Enchantments.esp

68 44 Unlimited Training.esp

69 45 WWW.esp

70 46 ClimatesOfTamriel-Dragonborn-Patch.esp

71 47 dD-DG-DB-Immersive Creatures EBT Patch.esp

72 48 RLO — Illuminated Spells.esp

73 49 SkyUI.esp

74 4a perrobs experience choice.esp

75 4b RaceMenu.esp

76 4c RaceMenuPlugin.esp

77 4d aMidianborn_Skyforge_Weapons.esp

78 4e AMB Glass Variants Lore.esp

79 4f Differently Ebony.esp

80 50 Open Cities Skyrim.esp

81 51 Alternate Start — Live Another Life.esp

I think that’s it, any help would be really appreciated. If someone needs more information, feel free to request. Thanks for taking your time until here.

If you are one of those Skyrim players and is coming across the “Skyrim has failed to allocate memory” error message then you have landed at the right place. Here in this fixing guide, I’ll show you how you can get rid of this Elder Scrolls Skyrim memory issue.

Skyrim is an action role-play open-world fantasy game developed by Bethesda Game Studios and published by Bethesda Softworks. The Skyrim Legendary and Classic edition are 32-bit Windows programs and hence they can use only up to 4GB of RAM on a 64-bit Windows 11 or Windows 10 OS. This makes there two Skyrim editions more prone to the Skyrim CTD issues due to running out of memory. One such CTD issue leads to the error message saying “Skyrim has failed to allocate memory! Possibly running out of memory…“

How to fix the “Skyrim has failed to allocate memory” issue

The issue occurs due to the game running out of system memory but it doesn’t mean that increasing the RAM physically will solve the problem. In fact, this not gonna help even a single bit. but what will work, are the fixes that are mentioned below.

Fix 1: Use ENBoost

Usually, most Skyrim users install ENB on their system to improve the screen quality while some don’t even install it. But irrespective of whether you have installed ENB or not, you should consider using ENBoost to solve the Skyrim failed to allocate memory issue from the PC. This is because ENBoost uses the ENB framework to increase the allocated RAM to the Skyrim game.

Hence the situation where Skyrim gets run out of the amount of RAM it can access, using the ENBoost to increase this amount can greatly improve the game performance along with eliminating the Skyrim failed to allocate memory issue. Moreover, there is no need to run an actual ENB graphics preset to benefit from this advantage, eliminating all the downsides of using boost. Here’s how you can use ENBoost and tweak the Enblocal.ini.

• Download the latest version of ENB.
• Now install the d3d9.dll, Enbglobal.ini and Enbhost.exe using the downloaded ENB
• Once done, open the installed Enblocal.ini file.
• Look for the UsePatchSpeedhackWithoutGraphics and set its value to True.
• Also, set the following thing to their respective values as discripted below:
  • Set VideoMemorySizeMB to Vram + Ram – 2048
  • Set ReservedMemorySizeMb to 128 or 256 (for 32-bit system) and 512 or 1024 (for 64-bit system)
• Now, close the Enblocal.ini file and restart the game.

Fix 2: Change the Crash Fix Settings

As per what some Skyrim players have reported, changing the CustomMemoryBlockTotalSizeMb parameter can solve the Skyrim failed to allocate memory issue. The Skyrim players who have changed the parameter to such a value that brings the memory usage to around 50-60 have solved the issue. This is a hit and trial method in which you’ll have to keep increasing the value of the CustomMemoryBlockTotalSizeMb parameter and will have to keep checking the memory usage in the game until the memory usage reaches somewhere around 50-60.

Fix 3: Consider Removing Mods

There are also high chances that using a lot of mods with the game is causing it not able to allocate a sufficient amount of system memory. If you are having a lot of mods that you don’t use very often or if you have unnecessary mods installed then you should lastly consider uninstalling as many of them as possible if nothing works.

Bottom Line

Ok, here comes the end of this fixing guide and I am hoping that after reading this you would be able to fix your issue. The Skyrim has failed to allocate memory issues generally gets fixed by using the ENBoost and changing the Enblocal.ini values as mentioned above. If this doesn’t work then you can try changing the CustomMemoryBlockTotalSizeMb value to make the in-game memory usage value reach 50-60. Lastly, if nothing works, you should better consider decreasing the number of mods that are installed in your Skyrim game.

Also Read:

• Fix 0kb bug in Skyrim Anniversary Edition on PS4
• Auepuf.exe/Auepuc.exe Explained | Is it safe for Windows 11/10?
• Fix The instruction at 0x000000000 referenced memory at 0x00000000. The memory could not be read
• Ducky One 2 Mini Keyboard shortcuts [127 Shortcuts]
• 7 Best FPS Counters for Windows 11/10