ENBoost is able to initialize multiple instances of the enbhost process, each able to use up to 4GB of system RAM up to a maximum of 128GB (capped by the kilobyte value set in VideoMemorySizeMb below. It is highly recommended to enable and keep this feature enabled! For this feature to work properly, users should have a minimum of 4GB system RAM. It does this by launching the enbhost.exe process to handle dynamic memory allocations. This parameter will enable the ENBoost features to dramatically reduce CTDs and other issues caused from reaching Skyrim's memory limit. More of an explanation by Boris can be found here and by keithinhanoi here and here. Please read these posts before posting support questions in the forums about this parameter! Don't be lazy! Note:' for this parameter to work, ReduceSystemMemoryUsage must be set to true and EnableUnsafeMemoryHacks must be set to false (see below). According to Boris, this can reduce memory fragmentation and make better use of Skyrim's available memory, especially when running on 64-bit Windows Vista or newer.
When set to true, this parameter changes some of Skyrim's memory allocation code to cache data at the 'top' of Skyrim's memory space (Windows default caches to bottom of memory space). While this warning does not apply to everyone under all circumstances ( me for example, running DefaultHeapInitialAllocMB=768), credible testing here on STEP supports the notion that setting EnableUnsafeMemoryHacks=true can contribute to Skyrim CTD at startup when using sheson's memory patch.
Reserved memory size enb Patch#
Therefore, if using the Sheson Memory Patch fix (either standalone or with SKSE), it is recommended to set ExpandSystemMemoryX64 to false. It has been reported that this feature can conflict with "Sheson's Memory Patch 3.0" (now included with SKSE) by causing Skyrim to crash if the memory patch fix is used to increase Skyrim's initial heap allocation ( Block 1 or DefaultHeapInitialAllocMB in skse.ini) higher than 512 in Sheson's Memory Patch or 768MB in SKSE.