#Enbhost for enbseries keeps opening driver
#Enbhost for enbseries keeps opening Patch
#Enbhost for enbseries keeps opening code
#Enbhost for enbseries keeps opening Pc
#Enbhost for enbseries keeps opening free

The values here are measured in megabytes. This means that increasing this parameter's value will result in equal increases in both VRAM and system RAM usage. The buffer will be set in VRAM and this portion of VRAM will not be used for ENBoost's dynamic memory allocation however, it will also be duplicated in the system memory used by TESV.exe as well. This parameter sets the size of a buffer used for swapping geometry and textures between VRAM and system memory. Set to false if ExpandSystemMemoryX64 is enabled (see above). A known bug is that Alt+tab will not work in fullscreen when this is enabled. When enabled, it does not use memory reallocation, compression, or enbhost.exe and will only work when ReduceSystemMemoryUsage is also enabled. This is a workaround for users experiencing large amount of stuttering, typically on systems with large amount of VRAM (4GB+).

#Enbhost for enbseries keeps opening free

If experiencing extended cell load times, before enabling this feature, it is recommended to first try using the ' free VRAM' key (see section) to clean video memory before entering a new location or fast traveling.Д®nabling this parameter is generally not safe. If this works, users are encouraged to go to a small interior, save the game, and then disable this again before trying to load the problem savegame. Enabling this parameter could potentially help load a save game which fails to load otherwise.

#Enbhost for enbseries keeps opening Pc

This may cause stuttering since more data must be dynamically loaded into memory during gameplay as the PC looks and moves around. When enabled this parameter can give faster cell-load times as geometry/textures are not loaded into video memory until they are visible. Routinely running Skyrim with this enabled is not recommended.

#Enbhost for enbseries keeps opening driver

If experiencing CTDs even while ENBoost features are enabled, users can try enabling this parameter to see if it resolves (helps to confirm video driver issues) otherwise, it is best to leave it disabled (false). When enabled this parameter can cause lower than optimal performance and/or long pauses. The parameter forces the ENBSeries driver libraries to manage video memory resources for cached textures (rather than the video drivers) and will ignore more of the errors reported by the video drivers. This was mainly implemented as a fix for AMD video card users however, it can also be useful for others. Set to true if ExpandSystemMemoryX64 is enabled (see above). 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.

#Enbhost for enbseries keeps opening code

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.

#Enbhost for enbseries keeps opening 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.