falcon_x Aug 23, 2014 @ 10:27am
Frustrating memory issues
My game is pure vanilla with no mods but I have all the DLC. The high-res texture pack makes it so I cannot fast travel more than a few times before it starts caching and stuttering. A simple exit to desktop use to fix this but now it requires a reboot.

How are you guys getting past the absolutely horrific memory management code within Skyrim? This thing must leak thousands of objects every time a grid cell is unloaded in order for it to start stuttering so fast. I suspect high-res textures reveal the core issue sooner since they require more memory.

I am very surprised this was never fixed as it tends to ruin the whole experience.
Last edited by falcon_x; Aug 23, 2014 @ 10:27am
Showing 1-14 of 14 comments
< >
Panda Aug 23, 2014 @ 10:32am 
If you're confident that your specs should be able to handle the high resolution textures without any issues, then you can perhaps try ENBoost.
falcon_x Aug 23, 2014 @ 8:17pm 
The issues are not indiv systems if the game leaks memory. There is no way to fix that...only slow its progression over time. Leaked memory is essentially invisible to the OS during the game since it is allocated but never unallocated or given back to the OS. No mod and no utility can fix that unless it can allocate raw memory without using the OS.

I have found that the more I transition from inside to outside the quicker it happens. I have 6GB of RAM but according to my data the game is not using it and will still begin to have issues around the 4GB mark.

The reboot that I initially thought was required didn't make sense b/c the OS should clean up any allocated memory when the program terminates. I have since found the problem and it is not related to the memory not being cleaned up at exit. The issue was actually related to being in an area or zone that didn't perform very well. Once I went back to White Run the game was fine. So I can remedy the memory issue by simply exiting the game back to the OS and restarting.

I would imagine the more mods and texture packs one has the quicker this issue occurs. I'm very surprised a memory leak of this magnitude was left in at release.
Last edited by falcon_x; Aug 23, 2014 @ 8:17pm
Tibbers Aug 23, 2014 @ 8:23pm 
Originally posted by falcon_x:
The issues are not indiv systems if the game leaks memory. There is no way to fix that...only slow its progression over time. Leaked memory is essentially invisible to the OS during the game since it is allocated but never unallocated or given back to the OS. No mod and no utility can fix that unless it can allocate raw memory without using the OS.

I have found that the more I transition from inside to outside the quicker it happens. I have 6GB of RAM but according to my data the game is not using it and will still begin to have issues around the 4GB mark.

The reboot that I initially thought was required didn't make sense b/c the OS should clean up any allocated memory when the program terminates. I have since found the problem and it is not related to the memory not being cleaned up at exit. The issue was actually related to being in an area or zone that didn't perform very well. Once I went back to White Run the game was fine. So I can remedy the memory issue by simply exiting the game back to the OS and restarting.

I would imagine the more mods and texture packs one has the quicker this issue occurs. I'm very surprised a memory leak of this magnitude was left in at release.
The game can't even use 4gb of ram, the engine is limited to 3.1gb. ENBoost give it more ram to play with, and it includes the ability to free up ram in-game. And the latest version of SKSE will clear up any issues you are having with the memory cache filling up and causing the game to crash when it switches to the 2nd block(if you are having that issue).

I don't experience any memory leak myself, but that could be ENBoost doing it's job.
Last edited by Tibbers; Aug 23, 2014 @ 8:23pm
falcon_x Aug 23, 2014 @ 8:41pm 
The game can't even use 4gb of ram, the engine is limited to 3.1gb.
I used Task manager private working set to estimate this rather than Process Manager so my estimates were likely off a bit.

ENBoost give it more ram to play with, and it includes the ability to free up ram in-game.

This might help prolong the issue but it cannot prevent it. If a pointer to memory is lost without being unallocated and that pointer goes out of scope somehow then that memory is lost forever and no mod can change that unless it goes into Skyrim's memory and finds an orphaned pointer and then releases the memory it points to.

That being said I will look into this a bit more. Anything to prolong the inevitable is going to at least improve the experience. I will not use SKSE since it uses dll-injection.
Last edited by falcon_x; Aug 23, 2014 @ 8:53pm
Another Aug 23, 2014 @ 8:51pm 
Skyrim will eventually chug and face plant. That can't be avoided. The game will also CTD if you somehow (aka mods) push it beyond its silly memory limits. Bethesda being Bethesda.

I use ssme rather than the memory feature of SKSE.
http://www.nexusmods.com/skyrim/mods/50305/

Since I had read that SKSE's memory feature isn't quite as reliable as ssme, and ssme is working fine for me (edit: skse's situation may have changed since I last checked). This gives Skyrim enough memory to run ENBs, several mods, HD texture packs, multiple extra NPCs (ex: Immersive Patrols, 3DNPC). It's really quite impressive what the modders have managed to do. I swear they're like the mechanics on an old starship that should have went derelict ages ago.

...it still eventually chugs and face plants though, and Bethesda stopped patching Skyrim quite a long time ago. So get those unofficial patches or your game will simply stop working eventually anyway.
Last edited by Another; Aug 23, 2014 @ 8:53pm
Enigma Aug 23, 2014 @ 10:38pm 
X:\...\Steam\SteamApps\common\skyrim\Data\SKSE (if you dont have it, just make a new folder and named it SKSE).
Open this folder, right click and open a text file that you will name SKSE.ini and type the following:
[Memory]
DefaultHeapInitialAllocMB=768
ScrapHeapSizeMB=256

That will allow you to play Skyrim fluid and with no memory_related_freezes/crashes (at least when you dont spam 1000+ guards in that sector).

hope it helps, have fun
Panda Aug 23, 2014 @ 10:51pm 
Originally posted by falcon_x:
The issues are not indiv systems if the game leaks memory. There is no way to fix that...only slow its progression over time. Leaked memory is essentially invisible to the OS during the game since it is allocated but never unallocated or given back to the OS. No mod and no utility can fix that unless it can allocate raw memory without using the OS.

I have found that the more I transition from inside to outside the quicker it happens. I have 6GB of RAM but according to my data the game is not using it and will still begin to have issues around the 4GB mark.

The reboot that I initially thought was required didn't make sense b/c the OS should clean up any allocated memory when the program terminates. I have since found the problem and it is not related to the memory not being cleaned up at exit. The issue was actually related to being in an area or zone that didn't perform very well. Once I went back to White Run the game was fine. So I can remedy the memory issue by simply exiting the game back to the OS and restarting.

I would imagine the more mods and texture packs one has the quicker this issue occurs. I'm very surprised a memory leak of this magnitude was left in at release.

Donno. I have 8GBs of RAM and 2GBs of VRAM. Textures mostly use VRAM. Again, I'll assume you have a powerful machine because people who know they have older specs won't complain about game peformance.

Now, I have a lot of HD texture replacers for everything. A lot of mods, and a taxing ENB. My computer gets hot but I once played 8 hours without any issues whatsoever. No CTDs and stuttering apart from the few odd framedrops.

You may be right that Skyrim has it's issues. Myself, I never ran vanilla Skyrim and like Goyo, I have the unofficial patches, SKSE, and ENBoost and never got any issues so I'll assume these things fixed the game so it works well.

So we could all lament and bash how bad the optimizations for Skyrim are but after that's all said and done, I'll go back to what I was trying to do on my first post and try to actually help you make your game play better. I assumed that was the point of this thread or are we just here to diss on Skyrim?
falcon_x Aug 23, 2014 @ 11:31pm 
[Memory]
DefaultHeapInitialAllocMB=768
ScrapHeapSizeMB=256
I see so this will make the first allocation 768MB and consecutive allocations at 256MB. Seems that Skyrim has issue when allocating new chunks. I will try this and see if it works.

Textures mostly use VRAM. Again, I'll assume you have a powerful machine because people who know they have older specs won't complain about game peformance.
That depends on how it is implemented. Without seeing the code I cannot comment one way or another. I understand how Gamebryo does it but I assume the version Skyrim uses has been heavily modified. Skyrim does not appear to have the FPS issue that all other Gamebryo games have (Guild 2, Oblivion, Fallout 3 and Fallout NV, and Divinity 2) so it has been modified in that regard and I expect it has been modified heavily in other areas.

I assumed that was the point of this thread or are we just here to diss on Skyrim?
Why would I 'diss' a game I have over 200 hours in? But if I did want to 'diss' the game this would be the place to do it would it not?
Last edited by falcon_x; Aug 23, 2014 @ 11:38pm
Tibbers Aug 24, 2014 @ 12:49am 
Originally posted by falcon_x:
I see so this will make the first allocation 768MB and consecutive allocations at 256MB. Seems that Skyrim has issue when allocating new chunks. I will try this and see if it works.
If 768 causes it to crash, try 512. For whatever reason 768 caused me to CTD, but 512 works just fine. The default is 256, so even 512 is a huge improvement.
Kelvy Aug 24, 2014 @ 12:57am 
[Papyrus]
iMinMemoryPageSize = 256
iMaxMemoryPageSize = 512
I was looking at this wasn't sure if I was on the right path
Afro_Sama Aug 24, 2014 @ 2:17am 
Originally posted by falcon_x:

I will not use SKSE since it uses dll-injection.

Whats wrong with dll-injection?
Last edited by Afro_Sama; Aug 24, 2014 @ 2:18am
Panda Aug 24, 2014 @ 2:42am 
That depends on how it is implemented. Without seeing the code I cannot comment one way or another. I understand how Gamebryo does it but I assume the version Skyrim uses has been heavily modified. Skyrim does not appear to have the FPS issue that all other Gamebryo games have (Guild 2, Oblivion, Fallout 3 and Fallout NV, and Divinity 2) so it has been modified in that regard and I expect it has been modified heavily in other areas.

As to the VRAM, I am stating that it is so for vanilla. I have not looked closely at how ENBoost works but perhaps it works around this.

Why would I 'diss' a game I have over 200 hours in? But if I did want to 'diss' the game this would be the place to do it would it not?

I didn't say that you couldn't talk smack of Skyrim here. I wanted to clarify the purpose of the thread since your answer to my first attempt to help you was a long rant without any comment on ENBoost.

You could try to tweak INI files, I guess, since you seem to be hesitant to use mods and see if that works well enough for you. I believe the patches are still pretty much essential, ENBoost not too much if you're not going to mod anyway but again, if your system chokes on just the HD textures DLC, it's either you need a better video card, or perhaps it's time to consider ENBoost.

Now, if you do find a solution that works for you, it would be great if you could post back what it was so other people may benefit as well.
Last edited by Panda; Aug 24, 2014 @ 2:43am
pedantic_roc Aug 24, 2014 @ 2:52am 
Originally posted by Afro_Sama:
Originally posted by falcon_x:

I will not use SKSE since it uses dll-injection.

Whats wrong with dll-injection?

Make your own mind up. :-)

http://securityxploded.com/dll-injection-and-hooking.php
Enigma Aug 24, 2014 @ 8:43am 
That for [Papyrus] is for those who work with CreationKit.
if you work with it, you may notice that you work and work and work, till, at a given time you cannot open any file and cannot work further and have to save and close and restart again ... (this is becouse the "sack is full" in the CK).
With that line you give your "sack" a bigger/greater size, so you can work longer w/out having to restart it again.
Showing 1-14 of 14 comments
< >
Per page: 15 30 50
Date Posted: Aug 23, 2014 @ 10:27am
Posts: 14