Installation instructions for Engine Fixes 5.3.3+:
BEFORE YOU START: This is a SKSE64 plugin. Therefore, you need to have the correct version of SKSE64 installed for your game version in order for this mod to function. If you don't have SKSE64 installed or don't know what SKSE64 is, do not attempt to install this mod. Learn what SKSE64 is and why you might want it here. SKSE+SkyUI installation instructions here. Once SKSE64 is properly installed, follow the Engine Fixes install steps below:
(1) RECOMMENDED: Completely remove all files and uninstall any previous installations of SSE Engine Fixes prior to starting.
(2) Download, install and enable/deploy the required all-in-one Address Library for SKSE Plugins with your mod manager. You will need to install the latest 1.5.x or 1.6.x version of the Address Library depending on which version of the game you are playing. If you're getting error 1114 or 617, it's probably because the Address Library isn't installed or properly enabled.
(3) Download and install the latest x64 version of the required Microsoft Visual Redistributable for Visual Studio 2019. On the linked page, it's the download that reads x64: vc_redist.x64.exe. Yes, it's a Windows install. Double-click the downloaded exe, follow the prompts, and reboot. If you're getting error 126, it's probably because the C++ Redistributable isn't installed.
(4) From the Files page, download, install and enable Part 1 of Engine Fixes with your mod manager. You will need to install the correct version of Part 1 for your game version. For those playing the latest version of Skyrim (1.6.1170+), be sure to download Part 1 version 6.2 from the Files page. EngineFixes.ini has been replaced with EngineFixes.toml in 5.3.3+. Open the UTF-8 encoded .toml file in Notepad to make your setting changes. You can delete the old EngineFixes.ini.
(5) From the Files page, download Part 2 manually. Do not install Part 2 of SSE Engine Fixes with your mod manager. Instead, extract the Part 2 archive, then copy and paste the three dll files from the archive directly into the root game directory (the folder containing SkyrimSE.exe). Do not simply place the archive file in that directory. Do not create a folder with the 3 files in that directory. Do not place the extracted files in the /Data directory. Part 2 is compatible with all versions of the game. OPTIONAL: If you are using Vortex, you can download and install Part 2 using the Mod Manager Download, but before deploying, double click the item in Vortex and change the Mod Type to Engine Injector. Then enable/deploy Part 2.
Do not rename your skse64 executables. If you have already done so, you will need to change the file names back to the original skse executable names. That means skse64_loader.exe and SkryimSE.exe. Skyrim.exe and adding an INI, as several obsolete guides tell you to do to get skse launching from Steam will not work. SSE Engine Fixes needs the original skse64_loader.exe and SkyrimSE.exe file names and files.
If you want to launch from Steam, add skse64_loader.exe as a Non-Steam Game. If Steam is open you can also launch skse64_loader.exe from a shortcut or from the mod manager and still get achievements in your Steam SSE Library and the overlay. The original Steam SSE page will always execute the standard launcher, but you can still see your achievements and screenshots there if you launch via skse64 using one of these other methods.
If you are getting Error 193, you are running an Oldrim plugin and need to uninstall it and find the SE version.
If you want to verify that Engine Fixes is running ok, open your d3dx9_42.log in your SSE game folder. It should look something like below when Engine Fixes is running properly. Don't worry about the line reading "failed to search dll plugin directory" - this just means you don't have other plugins that use the \Data\DLLPlugins directory installed.
Spoiler:
Show
skse64 plugin preloader - d3dx9_42exe path: X:\SteamLibrary\steamapps\common\Skyrim Special Edition\SkyrimSE.exe loaded into SkyrimSE.exe or SkyrimVR.exe, proxying SkyrimSE d3dx9_42 funcs and registering preload hook successhook triggered, loading dll plugins (meh's loader) failed to search dll plugin directoryDLLPlugin loader finished hook triggered, loading skse pluginsfound plugin "EngineFixes" for preloading attempting to load found pluginsattempting to load "X:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\EngineFixes.dll" loaded successfully and Initialize() calledloader finished
This mod seems to not work with (Part 1) SSE Engine Fixes for 1.6.1170 and newer (6.2): https://www.nexusmods.com/skyrimspecialedition/mods/9670?tab=files
Using GOG version AE 1.6.1179. That mod was working with an older GOG version and an older version of Engine Fixes, but it no longer works with the current version of Engine Fixes enabled. Works fine if I disable it.
"Testing: I included a neat little trick for testing...open the console (~) then type:
help "random dragon" player.placeatme xxxxxx
Replace the x's with the code that shows up after the first command."
That command and the mod doesn't work with SSE Engine Fixes enabled, and trying to type that command gives "VIEWER STRINGS NOT AVAILABLE". When it works, it's supposed to give a random code like it did with previous versions of SSE Engine Fixes.
Engine Fixes is running fine. I have no idea what that little console trick buys you, but the log says EF is running as it should. You can test to see if the F5 setting in the toml file is allowing you to do regular sales when pressing the F5 key:
Then Engine Fixes is running as it should. Running an obscure console command someone randomly recommended on the web somewhere is not a requirement for this mod. The log file is the true test for a correctly running EF.
That console command is from the mod page's description, not from some random person. Both it and the mod worked with an earlier version of this mod, so i'm not sure what changed.
How to act and post pretentious on a video game mod :)
If you can't help him resolve his issue, without insulting him, why post? His issue isn;t GLARING, so it's not a "right in front of you" answer, so why s#*! all over him? You that tired of "helping"? I know people make modding unbearable with the benality, redundancy, inept searching skills, and entitlement...but your reply ranks right up there with their questions.
Embarassing, really it is. And yes " You don't care, blah, blah", but you do, so step back, reflect, and try to be less of "that". or continue and keep acting like an angry child.
Hello! I just installed the mod, but after doing so the game isn't reading the majority of my other mods. I tried uninstalling and reinstalling a few of them with no luck, and from a few online forums people seem to think this is the mod that may have caused it. I tried completely uninstalling parts 1 and 2 of the mod, but the issue is still persisting. Could anyone give any advice on how to best handle this issue?
I did install those, both parts one and two, but that seems to be what broke my mods since the only other thing I installed was a sky texture mod this is the culprit. Regardless, I don't see why this has left my game unable to read the majority of my mods.
Feel like an idiot, after you mentioned the version I realize I downloaded the wrong part 1. Sorry, downloading this came at the tail end of four days of downloading mods. For anyone else having this issue, make sure sure you grabbed the up to date AE Part 1.
I installed them both from the files page, not from the download at the top. I've managed to fix my mods not loading, but now my mod config menu won't work as when I click it it is empty of any mods that use it; as well as most UI mods like A Matter of Time. At this point I would just like to uninstall the mod but deleting it and the archive (plus removing the overwritten part 2 files) does not seem to do anything and the issues still persist.
Hello! I wonder if you can help me: I have a crash every time I try to begin the dawnguard dlc campaing when you have to go to castle Dawnguard. I've downloaded this mod but won't help. Any way to fix that?
Part 1 is version 6.2, and Part 2 is version 6.1.1. Both parts are required in order for this mod to function, but Part 1 needs to match your Skyrim game version.
Thanks, I understand that. But what I'm asking is if the EngineFixes DLL for 1.6.1170+ is supposed to have version 6.1.1. Because there also is a Part 1 with the same number, but for the older version. I would expect the newer DLL to also have file version 6.2. Just want to be sure.
Yeah, the actual properties of the EngineFixes.dll may have a different version number, but it won't hurt anything as long as you installed the Part 1 archive with the correct version number (6.2). The author has retired, and it's unlikely he'll be back to make any version number changes to the dll properties.
Engine Fixes has started to just unceremoniously crash on save. I can play for a while, save just fine, but after about 10 hours give or take a few saving becomes a russian roulette with all chambers loaded.
Yes, all the fixes are enabled in the .toml. Yes, I am using the correct version. Yes, I have tried disabling certain settings.
Yes, it is set to 8192. I even tried doubling it, does nothing.
Weirdly, the crash stopped happening but I am sure it will occur again - for the record, I changed nothing about my plugins or load order. Other saves had the same issue; problem would occur after a while, then magically stop occurring, then occur later on again and not go away, bricking the character.
Every save is a damocles sword above my characters heads.
Edit: save size can't be the issue, it happened with saves between 20 and 30 MB, but also on fresh characters lvl 5-6 with a 10 MB save.
Same thing At a certain point, the game starts to crash (CTD) with autosaves and normal saves. When I restart the game, it saves perfectly for a while, and then... CTD on autosave. GOG 1.6.1179
Yes, and it started out of nowhere... Now, when installing: https://www.nexusmods.com/skyrimspecialedition/mods/146873 and https://www.nexusmods.com/skyrimspecialedition/mods/147847 the problem gets worse: when trying to exit Volkinar Castle, I had two consecutive CTDs in the autosave, and when I uninstalled them, I was able to exit perfectly on the next attempt. But when I uninstalled them, the problem recurs later. Every 2-3 normal autosaves, I have CTDs. Following several threads, I came across this mod.
I'm seeing similar issues, and seeing what you are saying, have you tried disabling auto saves altogether? I'm attempting these changes to the TOML file: RegularQuicksaves = true # Makes quick saves into regular saves CleanSKSECosaves = true # Delete SKSE cosaves that have no matching save SaveGameMaxSize = true # Expands the maximum uncompressed size of a save game from 64 MB to 128 MB
I'll post if it works for me or no. :)
UPDATE: Didn't work :(
But it makes me curious: Can someone tell me where this line is: UseTBBMalloc (default: true) - If you enable the memory manager patch, this will also replace standard malloc with tbbmalloc? Because that's the error I feel I'm getting when it returns void pointers, Pastebin, and I'm curious if I can just add the line under fixes or if it is there just typed differently from the description page.
Yeah, at this point I think you can rule out Engine Fixes and start debugging your load order and testing older saves, maybe your Skyrim install. You may have some save corruption going on. Use the standard mod debugging techniques posted all over the web. Good luck.
The problem is that they are random CTDs, after x saves/autosaves, and so it's very difficult to "find a culprit." Considering that other times it worked fine and from one day to the next...
Going to ask you a seemingly dumb question: Are you on windows 10 or 11?
If you are on either, when was the last time you ran DISM and sfc on your machine? I was getting a ton of random CTDs after a few hours play, tried everything with the mods. Spent weeks on it but nothing got much better. Ran DISM and sfc on the computer for something unrelated, and the CTDs stopped.
Those Win10 update forced restarts will bork important system files. Had one the other week that left me unable to start a bunch of programs, including MO2. Couldn't launch anything in admin mode, not even cmd.exe. Took the best part of a week & a lot of pulled out hair to get everything running again.
what I did was to deactivate the autosave, from that moment I did not have CTD again, in the last days I have not been able to play to confirm it, but that day I played a lot without CTD. I noticed the following: when exiting whiterun it took a long time to load the game (I have many graphic mods and a card with only 2Gb of VRAM), a black screen appeared and I thought “I'm going to have CTD”, but no, the game loaded perfectly outside whiterun. However in this process a window appeared to update/load shaders, which led me to think if the autosave process was given at the same time as the process of updating shaders and if this was what caused CTD. In my humble opinion it should not be the problem but....
I'm running into an error with getting this running and I'm not sure where to go from here.
I followed all the install instructions to the T, confirmed I have the 1.6 version of Address library installed, confirmed I have the 1.611... version of Skyrim through steam, confirmed my SKSE is the matching version, have both part 1 & 2 of sse installed (part 2 done manually)
I also can confirm my C++ visualizer is the correct one, and my d3dx9_42.lo log matches the example one exactly
But the issue I'm running into is that when I try to load my game, all the mods I have requiring SKSE are disabled and my game quickly crashes.
When I dont have SSE Engine fixes installed though SKSE works just fine
tbbmalloc.dll on skyrim 1.6.1170 skse 2.2.6 is incompatible with "Papyrus Extender" it causes CTD have to disable one or the other. just a heads up for others.
Not sure if anyone else experiences this, but after updating this yesterday (and only updating this mod), I now have a peculiar issue: When I get back into a game (start up SSE, choose my latest save, the game loads), the first time, (and ONLY the first time AND only when I'm in an interior cell), I open the game map, I CTD. If I open the map for the first time outside, no problem, and if I open the map the second time (whether outside or in an interior cell), it works just fine. However, this happens every time now, after updating from 4.11 to 4.13. I do use map-altering mods, but after this happened, I removed all of them, plus removing/reinstalling SSEEF 4.13, and it ONLY happens when I add 4.13. Unfortunately, I deleted 4.11 when I upgraded, so I can't test whether this also now happens on 4.11, but it didn't happen at all when I was using this before. Note that I use Vortex, have no file conflicts/rules set for SSEEF, and don't use SSE Fixes. Kinda at a loss as to why this particular (and screwy) situation would be related to an upgrade, and suspect pretty strongly that it's not SSEEF per se, but can't figure out what else would be causing this.
Any ideas come to mind? (Oh, and before someone suggests the historic fix to map CTDs, I don't have bBloodSplatter in my skyrim.ini, so don't bother with that one.)
14702 comments
BEFORE YOU START: This is a SKSE64 plugin. Therefore, you need to have the correct version of SKSE64 installed for your game version in order for this mod to function. If you don't have SKSE64 installed or don't know what SKSE64 is, do not attempt to install this mod. Learn what SKSE64 is and why you might want it here. SKSE+SkyUI installation instructions here. Once SKSE64 is properly installed, follow the Engine Fixes install steps below:
(1) RECOMMENDED: Completely remove all files and uninstall any previous installations of SSE Engine Fixes prior to starting.
(2) Download, install and enable/deploy the required all-in-one Address Library for SKSE Plugins with your mod manager. You will need to install the latest 1.5.x or 1.6.x version of the Address Library depending on which version of the game you are playing. If you're getting error 1114 or 617, it's probably because the Address Library isn't installed or properly enabled.
(3) Download and install the latest x64 version of the required Microsoft Visual Redistributable for Visual Studio 2019. On the linked page, it's the download that reads x64: vc_redist.x64.exe. Yes, it's a Windows install. Double-click the downloaded exe, follow the prompts, and reboot. If you're getting error 126, it's probably because the C++ Redistributable isn't installed.
(4) From the Files page, download, install and enable Part 1 of Engine Fixes with your mod manager. You will need to install the correct version of Part 1 for your game version. For those playing the latest version of Skyrim (1.6.1170+), be sure to download Part 1 version 6.2 from the Files page. EngineFixes.ini has been replaced with EngineFixes.toml in 5.3.3+. Open the UTF-8 encoded .toml file in Notepad to make your setting changes. You can delete the old EngineFixes.ini.
(5) From the Files page, download Part 2 manually. Do not install Part 2 of SSE Engine Fixes with your mod manager. Instead, extract the Part 2 archive, then copy and paste the three dll files from the archive directly into the root game directory (the folder containing SkyrimSE.exe). Do not simply place the archive file in that directory. Do not create a folder with the 3 files in that directory. Do not place the extracted files in the /Data directory. Part 2 is compatible with all versions of the game.
OPTIONAL: If you are using Vortex, you can download and install Part 2 using the Mod Manager Download, but before deploying, double click the item in Vortex and change the Mod Type to Engine Injector. Then enable/deploy Part 2.
Do not rename your skse64 executables. If you have already done so, you will need to change the file names back to the original skse executable names. That means skse64_loader.exe and SkryimSE.exe. Skyrim.exe and adding an INI, as several obsolete guides tell you to do to get skse launching from Steam will not work. SSE Engine Fixes needs the original skse64_loader.exe and SkyrimSE.exe file names and files.
If you want to launch from Steam, add skse64_loader.exe as a Non-Steam Game. If Steam is open you can also launch skse64_loader.exe from a shortcut or from the mod manager and still get achievements in your Steam SSE Library and the overlay. The original Steam SSE page will always execute the standard launcher, but you can still see your achievements and screenshots there if you launch via skse64 using one of these other methods.
If you are getting Error 193, you are running an Oldrim plugin and need to uninstall it and find the SE version.
That is all.
skse64 plugin preloader - d3dx9_42exe path: X:\SteamLibrary\steamapps\common\Skyrim Special Edition\SkyrimSE.exeloaded into SkyrimSE.exe or SkyrimVR.exe, proxying SkyrimSE d3dx9_42 funcs and registering preload hook
successhook triggered, loading dll plugins (meh's loader)
failed to search dll plugin directoryDLLPlugin loader finished
hook triggered, loading skse pluginsfound plugin "EngineFixes" for preloading
attempting to load found pluginsattempting to load "X:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\EngineFixes.dll"
loaded successfully and Initialize() calledloader finished
Using GOG version AE 1.6.1179. That mod was working with an older GOG version and an older version of Engine Fixes, but it no longer works with the current version of Engine Fixes enabled. Works fine if I disable it.
"Testing:
I included a neat little trick for testing...open the console (~) then type:
help "random dragon"
player.placeatme xxxxxx
Replace the x's with the code that shows up after the first command."
That command and the mod doesn't work with SSE Engine Fixes enabled, and trying to type that command gives "VIEWER STRINGS NOT AVAILABLE". When it works, it's supposed to give a random code like it did with previous versions of SSE Engine Fixes.
exe path: E:\GOG Games\Skyrim Anniversary Edition\SkyrimSE.exe
loaded into SkyrimSE.exe or SkyrimVR.exe, proxying SkyrimSE d3dx9_42 funcs and registering preload hook
success
hook triggered, loading dll plugins (meh's loader)
failed to search dll plugin directory
DLLPlugin loader finished
hook triggered, loading skse plugins
found plugin "EngineFixes" for preloading
attempting to load found plugins
attempting to load "E:\GOG Games\Skyrim Anniversary Edition\Data\SKSE\Plugins\EngineFixes.dll"
loaded successfully and Initialize() called
loader finished"
Just like that.
RegularQuicksaves = true
If you can't help him resolve his issue, without insulting him, why post? His issue isn;t GLARING, so it's not a "right in front of you" answer, so why s#*! all over him? You that tired of "helping"? I know people make modding unbearable with the benality, redundancy, inept searching skills, and entitlement...but your reply ranks right up there with their questions.
Embarassing, really it is. And yes " You don't care, blah, blah", but you do, so step back, reflect, and try to be less of "that". or continue and keep acting like an angry child.
Because there also is a Part 1 with the same number, but for the older version.
I would expect the newer DLL to also have file version 6.2. Just want to be sure.
I can play for a while, save just fine, but after about 10 hours give or take a few saving becomes a russian roulette with all chambers loaded.
Yes, all the fixes are enabled in the .toml.
Yes, I am using the correct version.
Yes, I have tried disabling certain settings.
The crashlog is always the same.
Here is an example:
crashlog pastebin
If anyone knows how to fix it or mb the author/current curator sees this and can fix it, that would be great. Otherwise GG.
I even tried doubling it, does nothing.
Weirdly, the crash stopped happening but I am sure it will occur again - for the record, I changed nothing about my plugins or load order.
Other saves had the same issue; problem would occur after a while, then magically stop occurring, then occur later on again and not go away, bricking the character.
Every save is a damocles sword above my characters heads.
Edit: save size can't be the issue, it happened with saves between 20 and 30 MB, but also on fresh characters lvl 5-6 with a 10 MB save.
https://www.skyrimcrashdecoder.com/
At a certain point, the game starts to crash (CTD) with autosaves and normal saves. When I restart the game, it saves perfectly for a while, and then... CTD on autosave.
GOG 1.6.1179
No clear culprit could be found - from none of my logs :/
Problem started appearing again after playing for a while and saving with no issues. This is maddening.
Now, when installing:
https://www.nexusmods.com/skyrimspecialedition/mods/146873 and
https://www.nexusmods.com/skyrimspecialedition/mods/147847
the problem gets worse: when trying to exit Volkinar Castle, I had two consecutive CTDs in the autosave, and when I uninstalled them, I was able to exit perfectly on the next attempt. But when I uninstalled them, the problem recurs later. Every 2-3 normal autosaves, I have CTDs.
Following several threads, I came across this mod.
I'm attempting these changes to the TOML file:
RegularQuicksaves = true # Makes quick saves into regular saves
CleanSKSECosaves = true # Delete SKSE cosaves that have no matching save
SaveGameMaxSize = true # Expands the maximum uncompressed size of a save game from 64 MB to 128 MB
I'll post if it works for me or no. :)
UPDATE: Didn't work :(
But it makes me curious: Can someone tell me where this line is:
UseTBBMalloc (default: true) - If you enable the memory manager patch, this will also replace standard malloc with tbbmalloc?
Because that's the error I feel I'm getting when it returns void pointers, Pastebin, and I'm curious if I can just add the line under fixes or if it is there just typed differently from the description page.
To reiterate, I have ALL fixes enabled. There is nothing I could enable to "fix" anymore.
I have already tried disabling some of them like the memory management, but it just lead to a straight up CTD when trying to load a save.
Am already doing that, so far with no success.
The problem is that they are random CTDs, after x saves/autosaves, and so it's very difficult to "find a culprit." Considering that other times it worked fine and from one day to the next...
Unhandled exception "EXCEPTION_ACCESS_VIOLATION" at 0x7FFC376BF6D6 skse64_1_6_1179.dll+005F6D6
[RSP+6C8 ] 0x1F409B401F1 (char*) "aving SKSEPersistentObjectStorage data...... Grass Mods Patch.esppor.espPatch.espanced.espave2_E2A5A610_0_416E746F6E696F_WhiterunWorld_000412_20250503080534_2_1.skse_1.skse3109_2_1.skse"
[RSP+6D0 ] 0x7FFC37738A18 (char*) "SKSE"
[RSP+6D8 ] 0x1F64EDB52B8 (BSTCommonStaticMessageQueue<BSTSmartPointer<bgs::saveload::Request,BSTSmartPointerIntrusiveRefCount>,8>*)
[RSP+6E0 ] 0x1F64EDB4F00 (BGSSaveLoadManager*)
[RSP+6E8 ] 0x1 (size_t)
[RSP+6F0 ] 0x5F682FF190 (char*) "Autosave2_E2A5A610_0_416E746F6E696F_WhiterunWorld_000412_20250503080534_2_1"
[RSP+6F8 ] 0x1F6B44C8100 (`anonymous namespace'::Win32FileType*)
[RSP+700 ] 0x1F64EAEC800 (void*)
[RSP+708 ] 0x1F6B44C8BB0 (char*) "Autosave2_E2A5A610_0_416E746F6E696F_WhiterunWorld_000412_20250503080534_2_1"
[RSP+710 ] 0x5F682FF1A0 (char*) "10_0_416E746F6E696F_WhiterunWorld_000412_20250503080534_2_1"
[RSP+718 ] 0x7FFC37670A3E (void* -> skse64_1_6_1179.dll+0010A3E)
If you are on either, when was the last time you ran DISM and sfc on your machine?
I was getting a ton of random CTDs after a few hours play, tried everything with the mods. Spent weeks on it but nothing got much better.
Ran DISM and sfc on the computer for something unrelated, and the CTDs stopped.
Worth a try, anyway.
i'll try...
Had one the other week that left me unable to start a bunch of programs, including MO2. Couldn't launch anything in admin mode, not even cmd.exe.
Took the best part of a week & a lot of pulled out hair to get everything running again.
I noticed the following: when exiting whiterun it took a long time to load the game (I have many graphic mods and a card with only 2Gb of VRAM), a black screen appeared and I thought “I'm going to have CTD”, but no, the game loaded perfectly outside whiterun. However in this process a window appeared to update/load shaders, which led me to think if the autosave process was given at the same time as the process of updating shaders and if this was what caused CTD. In my humble opinion it should not be the problem but....
I followed all the install instructions to the T, confirmed I have the 1.6 version of Address library installed, confirmed I have the 1.611... version of Skyrim through steam, confirmed my SKSE is the matching version, have both part 1 & 2 of sse installed (part 2 done manually)
I also can confirm my C++ visualizer is the correct one, and my d3dx9_42.lo log matches the example one exactly
But the issue I'm running into is that when I try to load my game, all the mods I have requiring SKSE are disabled and my game quickly crashes.
When I dont have SSE Engine fixes installed though SKSE works just fine
Any ideas come to mind? (Oh, and before someone suggests the historic fix to map CTDs, I don't have bBloodSplatter in my skyrim.ini, so don't bother with that one.)