Huge memory leak (23gb+)

Jayden_8

Commendable
Jun 29, 2016
16
0
1,510
Hey I am new to this so cut me some slack.

EDIT: I am such an idiot sorry. Here is my specs

windows 10
32gb ram
i7 6700 (non K)
MSI b150 gaming
MSI rx 480
240gb SSD
2TB HDD
(I bought some parts and then got better funds then excepted explains the odd setup)

Link to memory usage:

https://s15.postimg.org/c5amv328r/wwwwwwwwwasd.png

I have no idea what is going on. It seems like none of my closed programs are freeing up memory...

I play battlefield 1 >doesnt free up memory
I play dragon age >doesnt free up memory
I use cheat engine to cheat dragon age >doesnt free up memory

etc.....

Note: I do have a hidden keylogger that I used once to steal my brothers password... I forgot how to access it (it is hidden) but that is the only abnormal thing I have.

(LIke no anti virus has ever picked it up LOL I.E can't delete it ohwell)
 
Solution
What happens when you start using your keyboard? If you end up getting more leaked memory the more you use your keyboard, that would point to that being the issue; i.e. What happens when you decide to... Write a paper? Go surf the forums and post a fair bit? Search for a slew of things on the internet? compared to... What happens when you... Don't do anything on it for an extended period (already stated)? Decide to actually do something with the machine, such as watch Netflix or YouTube, but allow them to auto continue without any human interaction?

If you suffer more of a memory leak with one route than another, that can make it for a fairly easy diagnosis. But, yes the fact that your machine starts normally and accumulates used...

genthug

Honorable
If you can't delete something, can't see if it's running, and presuming it is always running... then that points to that being your memory leak, assuming your antiviral software has not picked up on anything else harmful.

Does this issue persist if you restart your machine, or does it only occur when you have left your machine running for an extended period? Because those would point to two very different issues.
 

Jayden_8

Commendable
Jun 29, 2016
16
0
1,510
OK

The memory is normal when it first starts up.
If I leave in on overnight it will slowly gain nonpaged memory (up to 5 - 6 gbs)
But when I start using it, it skyrockets to the point where I have to restart withen hours.

Anytime I close ANY program the memory stays......
The memory gains even if I dont open anything.....

NOTE: Somthing else that is interesting that it will decrease and stabilize at about 5 - 6 gbs. when idle Then after an hour it will go back to what it was (if the system have reached 20gbs unpaged)
 

genthug

Honorable
What happens when you start using your keyboard? If you end up getting more leaked memory the more you use your keyboard, that would point to that being the issue; i.e. What happens when you decide to... Write a paper? Go surf the forums and post a fair bit? Search for a slew of things on the internet? compared to... What happens when you... Don't do anything on it for an extended period (already stated)? Decide to actually do something with the machine, such as watch Netflix or YouTube, but allow them to auto continue without any human interaction?

If you suffer more of a memory leak with one route than another, that can make it for a fairly easy diagnosis. But, yes the fact that your machine starts normally and accumulates used memory over time points to a memory leak, you were correct in that.
 
Solution

Jayden_8

Commendable
Jun 29, 2016
16
0
1,510
I am going to assume it is the keylogger so I am going to remove it as I have no need for it.
Also leaving the computer on overnight and see if it makes a difference.

TBH google turned up nothing to do with any memory leak with 10gbs+ I am going to presume this is pretty abnormal.
 

genthug

Honorable
Memory leaks in this day and age are abnormal, as people typically go bonkers over them. Anything that has a notable memory leak these days gets patched fairly quickly, and anything that used to have memory leaks has since been fixed. *cough* FireFox *cough*