MemoryBlocksLog writes data to a logfile. Nothing else.
MemoryBlocksLog is a plugin for Skyrim Script Extender SKSE, so SKSE is required for it work.
Install MemoryBlocksLog.dll and MemoryBlocksLog.ini from the download archive into the SKSE plugin folder ../data/skse/plugins/
Edit ../data/skse/plugins/MemoryBlocksLog.ini in notepad to set log location. If using MO and DefaultLogLocation=true in the MemoryBlocksLog.ini, check overwrite folder for the logfile.
If there is ILS (Inifinite Loading Screen) or CTD (Crash To Desktop) and the block1 log reaches the max setting, increase the block1 / default heap setting in SKSE.ini. If SKSE.ini doesn't exist create it according to the guides:
In SKSE.ini the default heap setting always needs to be + 256 higher than the real block1 / default heap size actually is.
There is no need to set block1 / default heap to specific numbers, it just needs to be high enough by a small amount, like 60MB or so. Any memory allocated for block1 / default heap that is not used is unavailable to the other processes of the game.
Do not change block2 / scrap heap settings. It is fine and never causes CTD regardless of the logged values.
With a brand-new gaming computer with 16gb of Ram, I was sure I wouldn't have any more problems with Skyrim! Of course, I was wrong. Then, I struggled to remember the name of that program that saved me, years ago, on a seven-year old computer. And then .... BINGO ...Memory Blocks Log.
No more problems. Simple solutions. I like that. However, my 42-year old firstborn, who is a full-bird colonel in the US Army, would not take kindly to my giving him, to you ...
Are you using Mod Organizer? Mine is doing the same thing as I don't clear out my overwrite by making it a plugin.
Check GamerPoets video on how to change the Path on which the log is created and try setting a new path https://youtu.be/EnmkloC905Q
I haven't tried this yet but you could also try deleting the log from the overwrite folder and let this plugin create a new one.
Also take a look at Sheson's comment below
"As already posted in these comments: If default heap memory allocation is replaced by the preloader + crash fixes setting UseOSAllocators=1 than there is nothing for Memory Blocks Log to log after the game started, because default heap memory is disabled. If default heap memory is disabled it can not cause crashes anymore. If default heap memory is disabled there is no need to use Memory Blocks Log to verify if the default heap setting needs to be adjusted."
If you want to see the log though all you need to do is open the crashfixplugin.ini and set UseOSAllocators= from 1 to 0.
Crash fix appears to show identical information in the console while in game ? ( may be wrong here but I no longer see the memory usage in console after changing the above setting ) The only difference is the memory blocks log is a bit more detailed showing you exact values instead of percentages
@Krob7675Mine is doing the same thing as I don't clear out my overwrite by making it a plugin.
i might not understand what your saying, but i will say. I installed mod initial like any other mod. Activated, Went into game to test. When i exited game the log was generated into my overwrite folder and i then placed that log inside of Memory Blocks Log mod. I then went onto MO/MODS/Memory Blocks Log folder and had a fully generated log. If your not getting a full log read out whilst inside overwrite folder it didn't hurt anything on my end having had placed log inside overwrite to the Memory Blocks Log mod, further i did another test and 2nd time nothing was put into overwrite folder, but when i checked log in my MO/Mods/Memory Blocks Log folder new log had generated there.
Hello sheson, i hope my 1st born is doing well whatever the hell you've done with him.
I have a silly question : if i set UseOSAllocator to 1 in my crashfix.ini, the game don't use his own memory alloc system ? So this is the reason why your memory blocks log shows me a heapsize of 256mb under block 1 ? Or the log should be blank ?
Memory Blogs log shows the default and scrap heap initial and current settings. If it shows 256MB for block1 (default heap) then it is still at the default setting. Memory Blocks Log will report the initial values and then logging will stop because nothing is increasing the default and scrap heaps, because the memory allocation was replaced.
As already posted in these comments: If default heap memory allocation is replaced by the preloader + crash fixes setting UseOSAllocators=1 than there is nothing for Memory Blocks Log to log after the game started, because default heap memory is disabled. If default heap memory is disabled it can not cause crashes anymore. If default heap memory is disabled there is no need to use Memory Blocks Log to verify if the default heap setting needs to be adjusted.
Hi, I have some odd behavior showing up in my memory blocks log. The following data comes from the end of a recent session. I have left out most of the list so I don't take up an entire page. Here is the relevant "weird" behavior:
That pattern block 1 switching between a high number (591) and 7 is repeated until block 1 caps out. I have my block 1 set to 1280 but I have seen MBL reporting Block 1 as high as 1012. The alternating 591 / 7 pattern begins when the scrap heap reaches 256. I have my .ini set to show both increasing number and decreasing ones, but this pattern also correlates to when my gameplay begins to stutter, which is why I'm trying to figure out what's going on.
For system specs, I am running a GTX 1080 / i7 7700k / 16gb system ram / Samsung 960 pro (OS & Skyrim) / 1440p monitor. I have 229 mods running, but the most script intensive one is frostfall, the rest are textures, interface, fixes, and addons (I didn't want to list 229 mods here to save you guys wall o' text).
What's also odd is that Skyrim Performance monitor is showing my GPU dropping to 0% usage intermittently around the time this pattern starts up. The GPU usage most notably drops to 0 (and takes my framerate to 1) when I attempt to go into the skills menu. I CTD 3 out of 4 times I try to access the skills menu unless i first switch Frostfall off in the MCM.
Any thoughts about this data pattern in MBL? Is this normal behavior?
Give Feedback
587 comments
Comments locked
The author has locked this comment topic for the time beingMemoryBlocksLog is a plugin for Skyrim Script Extender SKSE, so SKSE is required for it work.
Install MemoryBlocksLog.dll and MemoryBlocksLog.ini from the download archive into the SKSE plugin folder ../data/skse/plugins/
Edit ../data/skse/plugins/MemoryBlocksLog.ini in notepad to set log location.
If using MO and DefaultLogLocation=true in the MemoryBlocksLog.ini, check overwrite folder for the logfile.
If there is ILS (Inifinite Loading Screen) or CTD (Crash To Desktop) and the block1 log reaches the max setting, increase the block1 / default heap setting in SKSE.ini. If SKSE.ini doesn't exist create it according to the guides:
S.T.E.P. Project
Skyrim Stability Guide
Speed and Stability Guide for ENB
GamerPoets Youtube Channel
Gophers Youtube Channel
In SKSE.ini the default heap setting always needs to be + 256 higher than the real block1 / default heap size actually is.
There is no need to set block1 / default heap to specific numbers, it just needs to be high enough by a small amount, like 60MB or so. Any memory allocated for block1 / default heap that is not used is unavailable to the other processes of the game.
Do not change block2 / scrap heap settings. It is fine and never causes CTD regardless of the logged values.
With a brand-new gaming computer with 16gb of Ram, I was sure I wouldn't have any more problems with Skyrim! Of course, I was wrong. Then, I struggled to remember the name of that program that saved me, years ago, on a seven-year old computer. And then .... BINGO ...Memory Blocks Log.
No more problems. Simple solutions. I like that. However, my 42-year old firstborn, who is a full-bird colonel in the US Army, would not take kindly to my giving him, to you ...
Thanks, once again
:)
Thanks for the mods, I have Memory blocks log installed, and it provides output, but this is always just two actual lines, it never grows or shrinks:
logging of blocks enabled
logging max values only
Timer disabled
Block1 Block2
512MB256MB
858
858
Any ideas?
Check GamerPoets video on how to change the Path on which the log is created and try setting a new path
https://youtu.be/EnmkloC905Q
I haven't tried this yet but you could also try deleting the log from the overwrite folder and let this plugin create a new one.
Also take a look at Sheson's comment below
"As already posted in these comments: If default heap memory allocation is replaced by the preloader + crash fixes setting UseOSAllocators=1 than there is nothing for Memory Blocks Log to log after the game started, because default heap memory is disabled. If default heap memory is disabled it can not cause crashes anymore. If default heap memory is disabled there is no need to use Memory Blocks Log to verify if the default heap setting needs to be adjusted."
Crash fix appears to show identical information in the console while in game ? ( may be wrong here but I no longer see the memory usage in console after changing the above setting ) The only difference is the memory blocks log is a bit more detailed showing you exact values instead of percentages
i might not understand what your saying, but i will say. I installed mod initial like any other mod. Activated, Went into game to test. When i exited game the log was generated into my overwrite folder and i then placed that log inside of Memory Blocks Log mod. I then went onto MO/MODS/Memory Blocks Log folder and had a fully generated log. If your not getting a full log read out whilst inside overwrite folder it didn't hurt anything on my end having had placed log inside overwrite to the Memory Blocks Log mod, further i did another test and 2nd time nothing was put into overwrite folder, but when i checked log in my MO/Mods/Memory Blocks Log folder new log had generated there.
I have a silly question : if i set UseOSAllocator to 1 in my crashfix.ini, the game don't use his own memory alloc system ? So this is the reason why your memory blocks log shows me a heapsize of 256mb under block 1 ? Or the log should be blank ?
Regards
As already posted in these comments: If default heap memory allocation is replaced by the preloader + crash fixes setting UseOSAllocators=1 than there is nothing for Memory Blocks Log to log after the game started, because default heap memory is disabled. If default heap memory is disabled it can not cause crashes anymore. If default heap memory is disabled there is no need to use Memory Blocks Log to verify if the default heap setting needs to be adjusted.
591 || 256
7 || 256
591 || 256
7 || 256
591 || 256
7 || 256
592 || 256
That pattern block 1 switching between a high number (591) and 7 is repeated until block 1 caps out. I have my block 1 set to 1280 but I have seen MBL reporting Block 1 as high as 1012. The alternating 591 / 7 pattern begins when the scrap heap reaches 256. I have my .ini set to show both increasing number and decreasing ones, but this pattern also correlates to when my gameplay begins to stutter, which is why I'm trying to figure out what's going on.
For system specs, I am running a GTX 1080 / i7 7700k / 16gb system ram / Samsung 960 pro (OS & Skyrim) / 1440p monitor. I have 229 mods running, but the most script intensive one is frostfall, the rest are textures, interface, fixes, and addons (I didn't want to list 229 mods here to save you guys wall o' text).
What's also odd is that Skyrim Performance monitor is showing my GPU dropping to 0% usage intermittently around the time this pattern starts up. The GPU usage most notably drops to 0 (and takes my framerate to 1) when I attempt to go into the skills menu. I CTD 3 out of 4 times I try to access the skills menu unless i first switch Frostfall off in the MCM.
Any thoughts about this data pattern in MBL? Is this normal behavior?