Windows 10 eating memory

[Torna]

I have seen memory leaks before....today was the worst I have ever seen.  I had hardly anything open and was watching youtube and memory usage went to 99%  the thing (when I finally got the task manager open) was called system and compressed memory.  Help.

[Enderman]

did you try turning it off and on again?

[Torna]

Thanks....I hadn't thought of that.  I want to keep the problem from coming back not postpone it.

[ZLoren]

hi,

do you have an installed bluestacks???

i am always encountering memory leak when i have that...

if yes, then tried to terminate/kill the running process of blustacks...its always have an "HD-" at the beginning of the  process name ^^

just sharing

[spellmanuk]

not had memory leaks on windows 10 so much but have had a couple of cases where i get 99% disk usage with just a few idle applications open

[Torna]

No bluestacks and good for you I would take a screenshot to show you one if could move my mouse to open chrome.

[asterix1001]

i suggest looking for any new or sispissues programs that shoud not be there might have something running in the background taking up all your RAM. also look at programs that are set to run on start up see if theres anything there bud.

[Torna]

Considering the fact that I had been sitting there for hours and it just started happening I doubt startup had anything to do with it.

[TrifectaIII]

So what system and compressed memory is... is exactly what it sounds like, oddly enough. It is data being used by a process that your OS doesn't want to keep in RAM in its uncompressed form, but also doesn't want to copy to your harddrive. So it compresses it and leaves it in your RAM, where it takes up less space, but is still faster to access than if it had been copied to your hard drive.

 

If task manager is showing 99% ram usage primarily due to this process, then either you have some other processes that are causing the actual leak (and then getting their leftover data compressed) or your windows install is borked. Either way, a fresh windows install should help this problem, assuming you can't find a process that could be the culprit.