0
I upgraded to Win10 from Win7, been having horrid memory leaks. Basically I can't run my computer for more than 7 days, my virtual memory would reach 55GB+ and make my computer non-responding. It's on "system managed" setting, though I tried giving it more manually and it would just fill up too.
My old Win7(before the Win10 upgrade) on this same computer was fine, could run for 3 months+ without issue. My laptop that has Win10 is also fine, it's now on for 2 months and memory use is minimal.
This is my MEMMAP, poolmon and ProcessHacker info:
This is how long my PC been on for the above screenshot:
This is my PC specs:
Please let me know if there's any other info needed to diagnose the issue.
Btw I have tried poolmon/WPA to diagnose the issue according to various guides found here, but for some reason I'm still unable to determine the cause of the memory leak. So you'll have to tell me exactly what to do differently with poolmon/WPA to find the cause. Thanks!!
KoKo
Posted 2016-12-28T23:42:03.717
Reputation: 1 498
I already tried the solution in that thread and couldn't find the leak, you can see I commented under the accept answer. – KoKo – 2016-12-29T00:28:29.313
Doesn't mean this still isn't a duplicate. – Ramhound – 2016-12-29T00:34:11.490
It's not a duplicate because my issue is specifically with the virtual memory or "commit charge" growing, which might not be related to driver memory leak. So the method describe in finding the leak may not be suitable for my case, or at least no in the way he described, there's something I might need to do differently. – KoKo – 2016-12-29T00:36:52.607
It does appear that neither your paged or nonpaged pool sizes account for the excessive commit charge, so I wouldn't expect the poolmon/WPA guides usually posted to help in this case. – Jamie Hanrahan – 2016-12-29T01:20:37.557
You need to look at each process's contribution to the commit charge. Please post a screenshot of Task Manager's "Details" tab. In that, include the "Commit size" column and sort by that column. (Right-click on the column headings, click "Select columns", check the one for "Commit size", OK, then click the "Commit size" column header once or twice as needed, to sort in descending order.) If you'd prefer to use Process Explorer, that tool calls the same counter "Private bytes". – Jamie Hanrahan – 2016-12-29T01:25:00.120
MMxx are memory managment related usage. CM16 = registry. you have to use WPA to trace which processes cause high memory allocations. See my answer in the duplicate link on how to do it. – magicandre1981 – 2016-12-29T15:57:53.477
ok I only found MmSt, but then I don't know what I'm looking at just like last time: http://imgur.com/a/uTFTL
– KoKo – 2016-12-30T02:22:40.800activate stack column (do a rightclick on column), load symbols and expand stack – magicandre1981 – 2016-12-30T12:43:36.617
Thanks. Is the "impacting size" column indicating which symbol is memory leak? http://imgur.com/a/jaNZ0
– KoKo – 2016-12-30T14:45:11.083you need to load symbols to see more: https://msdn.microsoft.com/de-de/windows/hardware/commercialize/test/wpt/load-symbols-or-configure-symbol-paths and expand the stacks with large values
– magicandre1981 – 2016-12-30T16:22:58.267ok symbols loaded, now it looks like this: http://imgur.com/a/ru8Fb
– KoKo – 2016-12-30T20:37:58.550MMxx tag usage comes from a torrent script which download files and does IO activity. so this is expected usage. Cm is used to load registry hives, this is also expected. – magicandre1981 – 2016-12-31T14:18:27.613
So how do I find out what is growing my virtual memory to 55GB+? My physical memory seems fine as you can see in the 1st screenshot – KoKo – 2016-12-31T15:29:36.883
also use WPT/WPA to see pagefile access and memory allocations: https://aloiskraus.wordpress.com/2016/10/09/how-buffered-io-can-ruin-performance/
– magicandre1981 – 2017-01-01T11:31:56.350Thanks Magicandre, I actually figured it out, I'm so excited. I actually followed the advice of this question: http://superuser.com/questions/519731/huge-memory-usage-in-nonpaged-pool, specifically looking at the task manager's "paged pool" column, I found it was the realtek audio driver that was using the most memory. I killed that process and my virtual memory usage went from 40GB to 6GB... so that's definitely the culprit. Thanks for making me understand what I needed to look for though.
– KoKo – 2017-01-02T03:05:24.603