SKSE "Memory Block Tweaks" problem

[sinomagic]

Hello everyone,

 

i have recently decided to return to skyrim and re-installed everything, however i am unable to tweaks my memory block (1,2) like i used to.

 

My game crashes everytime in the main menu, after i raise the DefaultHeapInitialAllocMB=768 to 1024 or higher in SKSE.ini.

 

Here is a setting which works fine(No crashes/problem) of my SKSE.ini:

[Display]

iTintTextureResolution=2048

 

[General]

ClearInvalidRegistrations=1

EnableDiagnostics=1

 

[Memory]

DefaultHeapInitialAllocMB=1024

ScrapHeapSizeMB=256

 

Unfortunately i am not able to configure DefaultHeapInitialAllocMB and ScrapHeapSizeMB anymore. ! 

 

Please help ;( Would really appreciate it    

 

Thanks!

 

 

 

 

 

[Nazzzgul666]

I suggest using crash fixes instead. It has a function that afaik doesn't copy the SKSE memory patch but maes it unecessary using another method and as far as i can say, works much better. Besides that, values above 1024 were never recommended, 768 was always the suggested value.

[Alpia]

 

Hello everyone,

 

i have recently decided to return to skyrim and re-installed everything, however i am unable to tweaks my memory block (1,2) like i used to.

 

My game crashes everytime in the main menu, after i raise the DefaultHeapInitialAllocMB=768 to 1024 or higher in SKSE.ini.

 

Here is a setting which works fine(No crashes/problem) of my SKSE.ini:

[Display]

iTintTextureResolution=2048

 

[General]

ClearInvalidRegistrations=1

EnableDiagnostics=1

 

[Memory]

DefaultHeapInitialAllocMB=1024

ScrapHeapSizeMB=256

 

Unfortunately i am not able to configure DefaultHeapInitialAllocMB and ScrapHeapSizeMB anymore. ! 

 

Please help ;( Would really appreciate it    

 

Thanks!

 

 

If you have ENB and change the DefaultHeapInitialAllocMB size to 1024 you will allways crash you either have to just let it be 512 or set in the enblocal.ini ExpandSystemMemoryX64=false to false (for me 768 still works just crashes at 1024 just try it)

 

You shouldnt change ScrapHeapSizeMB anyway btw since you said you cant change both you as said shouldnt even try to change ScrapHeapSizeMB

 

 

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. Therefore, if using the Sheson Memory Patch fix (either standalone or with SKSE), it is recommended to set ExpandSystemMemoryX64 to false.

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. ~z929669 Talk 23:19, January 17, 2015 (EST)

 

There is also a mod to test if you even need it set to 768 or higher http://www.nexusmods.com/skyrim/mods/50471/? (memory blocks log) it provides a log in which you can see how high you need to set it, test it like he recommends it.

[sinomagic]

I suggest using crash fixes instead. It has a function that afaik doesn't copy the SKSE memory patch but maes it unecessary using another method and as far as i can say, works much better. Besides that, values above 1024 were never recommended, 768 was always the suggested value.

 

 

 

 

Hello everyone,

 

i have recently decided to return to skyrim and re-installed everything, however i am unable to tweaks my memory block (1,2) like i used to.

 

My game crashes everytime in the main menu, after i raise the DefaultHeapInitialAllocMB=768 to 1024 or higher in SKSE.ini.

 

Here is a setting which works fine(No crashes/problem) of my SKSE.ini:

[Display]

iTintTextureResolution=2048

 

[General]

ClearInvalidRegistrations=1

EnableDiagnostics=1

 

[Memory]

DefaultHeapInitialAllocMB=1024

ScrapHeapSizeMB=256

 

Unfortunately i am not able to configure DefaultHeapInitialAllocMB and ScrapHeapSizeMB anymore. ! 

 

Please help ;( Would really appreciate it    

 

Thanks!

 

 

If you have ENB and change the DefaultHeapInitialAllocMB size to 1024 you will allways crash you either have to just let it be 512 or set in the enblocal.ini ExpandSystemMemoryX64=false to false (for me 768 still works just crashes at 1024 just try it)

 

You shouldnt change ScrapHeapSizeMB anyway btw since you said you cant change both you as said shouldnt even try to change ScrapHeapSizeMB

 

 

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. Therefore, if using the Sheson Memory Patch fix (either standalone or with SKSE), it is recommended to set ExpandSystemMemoryX64 to false.

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. ~z929669 Talk 23:19, January 17, 2015 (EST)

 

There is also a mod to test if you even need it set to 768 or higher http://www.nexusmods.com/skyrim/mods/50471/? (memory blocks log) it provides a log in which you can see how high you need to set it, test it like he recommends it.

 

Thank you guys:) Really helpful, Any idea what ExpandSystemMemoryX64 do?

[Alpia]

 

 

 

I suggest using crash fixes instead. It has a function that afaik doesn't copy the SKSE memory patch but maes it unecessary using another method and as far as i can say, works much better. Besides that, values above 1024 were never recommended, 768 was always the suggested value.

 

 

 

 

Hello everyone,

 

i have recently decided to return to skyrim and re-installed everything, however i am unable to tweaks my memory block (1,2) like i used to.

 

My game crashes everytime in the main menu, after i raise the DefaultHeapInitialAllocMB=768 to 1024 or higher in SKSE.ini.

 

Here is a setting which works fine(No crashes/problem) of my SKSE.ini:

[Display]

iTintTextureResolution=2048

 

[General]

ClearInvalidRegistrations=1

EnableDiagnostics=1

 

[Memory]

DefaultHeapInitialAllocMB=1024

ScrapHeapSizeMB=256

 

Unfortunately i am not able to configure DefaultHeapInitialAllocMB and ScrapHeapSizeMB anymore. ! 

 

Please help ;( Would really appreciate it    

 

Thanks!

 

 

If you have ENB and change the DefaultHeapInitialAllocMB size to 1024 you will allways crash you either have to just let it be 512 or set in the enblocal.ini ExpandSystemMemoryX64=false to false (for me 768 still works just crashes at 1024 just try it)

 

You shouldnt change ScrapHeapSizeMB anyway btw since you said you cant change both you as said shouldnt even try to change ScrapHeapSizeMB

 

 

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. Therefore, if using the Sheson Memory Patch fix (either standalone or with SKSE), it is recommended to set ExpandSystemMemoryX64 to false.

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. ~z929669 Talk 23:19, January 17, 2015 (EST)

 

There is also a mod to test if you even need it set to 768 or higher http://www.nexusmods.com/skyrim/mods/50471/? (memory blocks log) it provides a log in which you can see how high you need to set it, test it like he recommends it.

 

 

Thank you guys:) Really helpful, Any idea what ExpandSystemMemoryX64 do?

 

 

 

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). 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. Note:' for this parameter to work, ReduceSystemMemoryUsage must be set to true and EnableUnsafeMemoryHacks must be set to false (see below).

 

http://wiki.step-project.com/Guide:ENBlocal_INI/Memory

 

Like I said use memory blocks log test how big you even need it set and then think about changing settings that may not even be need a change. In fact you dont have to change either setting I have a heavy setup and I rarely get over 512, so I have it on 768. I have the expandsystemmemory on false as its the default setting for the enblocal.ini I use and I have no reason to change it, as I dont have problems even tough I could enable it.
 

[sinomagic]

 

 

 

I suggest using crash fixes instead. It has a function that afaik doesn't copy the SKSE memory patch but maes it unecessary using another method and as far as i can say, works much better. Besides that, values above 1024 were never recommended, 768 was always the suggested value.

 

 

 

 

Hello everyone,

 

i have recently decided to return to skyrim and re-installed everything, however i am unable to tweaks my memory block (1,2) like i used to.

 

My game crashes everytime in the main menu, after i raise the DefaultHeapInitialAllocMB=768 to 1024 or higher in SKSE.ini.

 

Here is a setting which works fine(No crashes/problem) of my SKSE.ini:

[Display]

iTintTextureResolution=2048

 

[General]

ClearInvalidRegistrations=1

EnableDiagnostics=1

 

[Memory]

DefaultHeapInitialAllocMB=1024

ScrapHeapSizeMB=256

 

Unfortunately i am not able to configure DefaultHeapInitialAllocMB and ScrapHeapSizeMB anymore. ! 

 

Please help ;( Would really appreciate it    

 

Thanks!

 

 

If you have ENB and change the DefaultHeapInitialAllocMB size to 1024 you will allways crash you either have to just let it be 512 or set in the enblocal.ini ExpandSystemMemoryX64=false to false (for me 768 still works just crashes at 1024 just try it)

 

You shouldnt change ScrapHeapSizeMB anyway btw since you said you cant change both you as said shouldnt even try to change ScrapHeapSizeMB

 

 

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. Therefore, if using the Sheson Memory Patch fix (either standalone or with SKSE), it is recommended to set ExpandSystemMemoryX64 to false.

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. ~z929669 Talk 23:19, January 17, 2015 (EST)

 

There is also a mod to test if you even need it set to 768 or higher http://www.nexusmods.com/skyrim/mods/50471/? (memory blocks log) it provides a log in which you can see how high you need to set it, test it like he recommends it.

 

 

Thank you guys:) Really helpful, Any idea what ExpandSystemMemoryX64 do?

 

 

 

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). 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. Note:' for this parameter to work, ReduceSystemMemoryUsage must be set to true and EnableUnsafeMemoryHacks must be set to false (see below).

 

http://wiki.step-project.com/Guide:ENBlocal_INI/Memory

 

Like I said use memory blocks log test how big you even need it set and then think about changing settings that may not even be need a change. In fact you dont have to change either setting I have a heavy setup and I rarely get over 512, so I have it on 768. I have the expandsystemmemory on false as its the default setting for the enblocal.ini I use and I have no reason to change it, as I dont have problems even tough I could enable it.

 

Thank you )