Windows 10: Standby memory and gaming dilemma

After experiencing frequent crashing with The Sims 2, I applied the standby memory fix, setting the Task Scheduler to clear standby memory every 5 minutes. It solved my crashing, but it seems to come with the price of making the general Windows system hang and lag constantly (good example GIF here). So, while I'm not tech savvy by any stretch, I'm guessing things like folder icons and such are stored as standby memory (which now keeps getting wiped)? The strange thing is I can't find anyone else experiencing this, either through googling or asking fellow players.

Aside from having to disable/enable the task manually as needed, is there anything else I could do instead? Why does this not seem to be an issue for anyone else?

:)

 

[Question] Clearing Standby memory when free memory reaches some level

The situation is:

Why do i want 2gb of Standby memory when the game is paging file because it's lacking of free memory and not using that 'useless' resource?? I didn't pay for a 8gb to see windows locking 2gb for no reason.

There's a in-game graph monitor that shows that when there's no free memory the game runs badly. But when there's free memory (stolen from the useless standby) the game runs smoothly.. With no stuttering (no graph variations)

I'm using a standby cleaner already and the result is brilliant for gaming. I just need a better MODE of cleaning. To clean the standby only when needed (no free memory) and not every 5 minutes (most of the time won't be needed every 5 minutes maybe 10). But if i close the game it will keep cleaning every 5 minutes.

Thousands of Battlefield 1 players with very expensive computers were having problems with stuttering.. Doesn't matter if it was 16gb or a 8gb PC. The ram management on newer versions of windows 10 is badly planned.

On previous versions of windows 10 there were no issue like that. Microsoft failed badly.. It's a clear example of bad ram management..

It happens with tons of games not only BF1.

 

[Question] Clearing Standby memory when free memory reaches some level


Why do you think it necessary to free standby memory?
The normal state for available memory is on the standby list, not free. Windows was designed to function optimally with zero free memory. I have often seen this with no issues of any kind. The ideal would be zero free memory at all times but we are not there yet.

I have tried a number of these memory cleaners (just for experimental purposes) and have been thoroughly unimpressed.

 

SuperFetch & Standby Memory Not Working Properly?


Updated Febraury 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.