New
#1
SuperFetch & Standby Memory Not Working Properly?
Updated October 2018:
From Wagnard:
Intelligent standby list cleaner v1.0.0.7 Released | WagnardsoftHi everyone.
Some of you may know me already as the maker of DDU (Display driver Uninstaller).
I decided to revive this old thread to let you know that I have made a little tool that can help you with gaming by purging the Standby list automatically when needed.
Feel free to try it out. It is available on my website @ wagnardsoft
It is named "Intelligent standby list cleaner" ISLC" in short.
Updated February 2018:
Just a small update on this. It is a Windows bug. I called Microsoft and got hold to a higher tier engineer working for tech support and he told me it's indeed an issue with how the os retrieves data on certain hardware configurations from standby memory. At least they acknowledge it, but he couldn't say anything about a fix or how long I need to wait for a new update... He only mentioned that I can use the feedback app and give sys info. Yup... I need to wait until April - May then for a new feature update in hopes that it resolves itself. If it doesn't then I need to live with turning off SuperFetch and clear my standby memory once in a while, or revert my os.
__________________________________________________________
So there's a task called Superfetch in Windows that's supposedly should improve performance because it preloads applications in RAM. I read an article that games installed on a PC with 4GB or less memory may suffer from this due to its excessive load in/out behavior. My issue seems to stem from this service causing stuttering and overall bad performance in games, however I have 16GB of RAM... I can confirm this by either disabling the service or emptying my standby memory to free using empty standby list command. It looks like the task of fetching data from standby memory is more demanding than it should be for some reason. This can take a while depending on the game and how much free RAM I have, but usually the performance is good until Windows starts this bull.
I found the culprit in Windows 10, or more specifically the Creators Update - as Windows 7 and regular 10 didn't show the same symptom, even with SuperFetch running. I tried to reinstall the OS, do a complete rundown of clean drivers etc and the issue was still there. So, is this service broken in the Creators Update or what? I don't get it. Oh, and I have also tried diferent memory sticks, aswell as both dual and quad channels. More RAM will only postpone the issue.
Last edited by Faith; 12 Oct 2018 at 08:03.