For those complaining about stuttering while gaming

[BlackManINC]

Or about not being able to open up applications for instance, the images below speaks for itself. This is EXACTLY why I always tell people to keep an eye on that damn standby memory. You see, I always check it before I get to gaming. I was getting ready to play Halo: Infinite, and lo and behold, this is what I run into.   So much for the claim that the O.S will clear the standby memory out. If it does, it sure as shit ain't that reliable, like, at all. ....Shit chewed up and swallowed ALL my memory, even though I have 32 gbs of ram. And no, as you'll see, I didn't have a ton of applications open either. This is one of the main reasons why stuttering is so common while gaming. This one dude couldn't even open up Radeon because of this. He didn't have enough space in the ram for it. This needs to be pinned to the top of the sub forum in my opinion, but that's up to the mods. 

 

 

 

 

 

Also, take note of the time between the two images on the clock bottom right. STILL hasn't cleared out by the way. 

 

 

[BlackManINC]

 You have got to be fucking kidding me with this dude. It STILL hasn't cleared. This is not an issue that actually needed to be addressed in an update or in Win 11 according to Microsoft, but Microsoft is retarded so I already have a low opinion of them anyway folks. Look at this shit. 

 

[Alex Atkin UK]

21 minutes ago, BlackManINC said:

 You have got to be fucking kidding me with this dude. It STILL hasn't cleared. This is not an issue that actually needed to be addressed in an update or in Win 11 according to Microsoft, but Microsoft is retarded so I already have a low opinion of them anyway folks. Look at this shit. 

 

You seem to be missing the point, its not SUPPOSED to clear it, unless it needs it.  Look at the cached amount, look at the standby amount, its data in memory in case you need it again that can be INSTANTLY reclaimed, it wont cause stutter when doing so as it wont page out that data, its basically free RAM when required.  You can see this reflected in task manager where it says 24% RAM used.

 

If anything having that cache reduces stutter as it will quickly be full of game assets that might need re-loading otherwise.  Its why even on a HDD, fast traveling to somewhere and back again can be REALLY fast, as the previous locations assets are still in the cache. Plus its not constantly wasting cycles clearing out memory that is no longer used, until its needed.

Modern OS by design keep RAM as full as possible, because there is no logical reason not to.  Linux did this for decades, Windows probably also did but it didn't used to tell you, instead just showing it as free memory so as not to confuse the user.

[BlackManINC]

12 minutes ago, Alex Atkin UK said:

You seem to be missing the point, its not SUPPOSED to clear it, unless it needs it.  Look at the cached amount, look at the standby amount, its data in memory in case you need it again that can be INSTANTLY reclaimed, it wont cause stutter when doing so as it wont page out that data,

STOP right there. Hitman 3 was stuttering like a cheap whore until I personally cleared the standby memory myself using Process Lasso. This has happened to me multiple times. Now if this retarded ass operating system was half as smart as you are claiming it is, it would have cleared it right then, because it would have noticed that Hitman 3 NEEDED all that memory. Simple logic. The shit don't work as well as you believe it does. 

[Mark Kaine]

If there only was a program to fix this well known longstanding bug...

 

Btw, framedrops also happen with badly programmed games, poor drivers and terrible engines (such as "unity" on Nvidia...)

 

Nothing to do with standby/memory at all in those cases. 

 

I think you should reformulate your post, because as it is, its just not accurate or helpful...

 

 

[Mark Kaine]

4 hours ago, Alex Atkin UK said:

You seem to be missing the point, its not SUPPOSED to clear it, unless it needs it.  Look at the cached amount, look at the standby amount,

Exactly, its simply "cached" data...

 

However sometimes windows has an issue with this (either hw or sw related im not sure) and that can lead to games dropping frames. In which case a standby list cleaner is a simple fix - and if that doesn't help its something else, there's thousands of reasons why a game might not run stable after all. 

 

4 hours ago, BlackManINC said:

-snip-

This is an issue with your setup,  either it's hw or sw, it is fixable (for me a bios update did it iirc)

[BlackManINC]

8 hours ago, Mark Kaine said:

Exactly, its simply "cached" data...

 

However sometimes windows has an issue with this (either hw or sw related im not sure) and that can lead to games dropping frames. In which case a standby list cleaner is a simple fix - and if that doesn't help its something else, there's thousands of reasons why a game might not run stable after all. 

 

This is an issue with your setup,  either it's hw or sw, it is fixable (for me a bios update did it iirc)

Its an issue with the O.S being a half wit, simple. Only thing the user can do about it is use apps like process lasso, or Microsoft's ranmap to clear it, which was their half assed attempt at addressing it.

[Dedayog]

12 hours ago, BlackManINC said:

STOP right there. Hitman 3 was stuttering like a cheap whore until I personally cleared the standby memory myself using Process Lasso. This has happened to me multiple times. Now if this retarded ass operating system was half as smart as you are claiming it is, it would have cleared it right then, because it would have noticed that Hitman 3 NEEDED all that memory. Simple logic. The shit don't work as well as you believe it does. 

Do cheap whores stutter?  I think you're disrespecting stutterers and cheap whores.

 

 

[Mavendow]

13 hours ago, Alex Atkin UK said:

Modern OS by design keep RAM as full as possible, because there is no logical reason not to.  Linux did this for decades, Windows probably also did but it didn't used to tell you, instead just showing it as free memory so as not to confuse the user.

Nope, Windows did not. That's a common myth but not true. Rather, SuperFetch could mimic the effects of total memory caching but it's not the same; it loaded only commonly used software into cached memory. Prefetch was an older version of the same concept. Nowadays I believe it's called SysMain and it does aggressively consume memory regardless of your usage patterns. In no case was the memory usage unreported.

 

Anyway, the problem Windows has is that it caches data also using the page file which is typically just duplicating data on the same drive the data came from. This may have been useful on HDD where seek times come into play but it's utterly worthless for flash. It can also lead to precisely the OP's issue if, for example, the page file is on a secondary storage HDD where the drive has to spin up and seek before that cache can be accessed. Some storage drives are actually much slower than older HDDs which lack data shingling. In which case it's many orders of magnitude slower than just re-reading the file from the flash drive. This is why I turn off the page file on all secondary HDDs and on my own PC I turn off the page file entirely.

[Alder Lake]

14 hours ago, BlackManINC said:

Or about not being able to open up applications for instance, the images below speaks for itself. This is EXACTLY why I always tell people to keep an eye on that damn standby memory. You see, I always check it before I get to gaming. I was getting ready to play Halo: Infinite, and lo and behold, this is what I run into.   So much for the claim that the O.S will clear the standby memory out. If it does, it sure as shit ain't that reliable, like, at all. ....Shit chewed up and swallowed ALL my memory, even though I have 32 gbs of ram. And no, as you'll see, I didn't have a ton of applications open either. This is one of the main reasons why stuttering is so common while gaming. This one dude couldn't even open up Radeon because of this. He didn't have enough space in the ram for it. This needs to be pinned to the top of the sub forum in my opinion, but that's up to the mods. 

 

 

 

 

 

Also, take note of the time between the two images on the clock bottom right. STILL hasn't cleared out by the way. 

 

 

according to my school, those images are pornography

[Mark Kaine]

10 hours ago, BlackManINC said:

Its an issue with the O.S

and the hardware. Its fixable.  Ever thought about that Microsoft can't make the os work perfectly for every random combination of hw out there?

 

Again,  not saying its not an issue,  im saying instead of complaining (about a very old problem) you could try to fix it yourself-- i recommend ISLC , make it run on startup,  it uses basically zero resources  = problem solved  for good .

 

Ps: also why the hell does your AV have a gazillion processes running? I'd deinstall this trash and use defender instead!

You're welcome = )

 

 

[Mark Kaine]

9 hours ago, Mavendow said:

Anyway, the problem Windows has is that it caches data also using the page file

The problem windows has is that it sometimes doesn't clear out the standby memory,  it just keeps going up,  its called "memory  leak" which then leads to "stutters"

 

But again,  its fixable,  currently my standby memory works as intended,  page file is usually at 0% all is good.

 

All it needed was a BIOS update  (weirdly enough)

 

 

[Mavendow]

45 minutes ago, Mark Kaine said:

The problem windows has is that it sometimes doesn't clear out the standby memory,  it just keeps going up,  its called "memory  leak" which then leads to "stutters"

 

But again,  its fixable,  currently my standby memory works as intended,  page file is usually at 0% all is good.

 

All it needed was a BIOS update  (weirdly enough)

The standby memory was probably leaking from a hardware driver. I was not talking about third party issues but Microsoft's own issues with caching.

[Mark Kaine]

1 hour ago, Mavendow said:

The standby memory was probably leaking from a hardware driver. I was not talking about third party issues but Microsoft's own issues with caching.

Yeah I know, but I don't know much about that, I was just pointing out this specific memory leak can be fixed , and yes its not necessarily Microsoft's fault,  just a combination of things, hw, drivers... (im guessing!)