0

I have Windows 10, and nowadays as I use my laptop, my computer uses more and more RAM and CPU. If I don't do anything, happens the same, I left my laptop at home, and after 8-10 hours it uses 99% of my hardwares, and after a while my computer freezes and says, that I have to restart my computer, because I have no more RAM. I don't have any viruses, and yes, I disabled Superfetch also. The top 2, which uses, are always Service Host: Local System (mainly this one) and System.

Here's a picture after 10 minutes of run:

https://postimg.org/image/brggjvoz7/

And here after 2 hours:

https://postimg.cc/image/68nr59azn/

Expanded as requested:

enter image description here

Ƭᴇcʜιᴇ007
  • 111,883
  • 19
  • 201
  • 268
Tibor Sas
  • 21
  • 2
  • 2
    Please expand the entry so that we can see the services the process hosts. – Daniel B Sep 06 '16 at 15:30
  • This is not a duplicate. Windows compressing the memory is just a result of the original problem: a service eating memory. – Daniel B Sep 06 '16 at 15:45
  • https://postimg.org/image/jftexoc69/ – Tibor Sas Sep 06 '16 at 16:30
  • Hm, interesting. Try stopping the Windows Update service. – Daniel B Sep 06 '16 at 17:20
  • Try the process [here](http://www.windowscentral.com/how-use-dism-command-line-utility-repair-windows-10-image). – David Schwartz Sep 06 '16 at 18:46
  • Nothing helped yet :/ – Tibor Sas Sep 06 '16 at 19:24
  • 1
    reboot, open a cmd.exe as admin and run this: **wpr.exe -start CPU -start ReferenceSet && timeout -1 wpr.exe -stop C:\HighCPUAndMemoryUsage.etl**. (Attention, this command must be 1 line without any line breaks) Minimize the cmd Window, let this run a few minutes until you see a memory usage grow. if you captured the grow, go to the cmd again, press a key to stop logging. compress the etl and share it. – magicandre1981 Sep 07 '16 at 04:27
  • ok, I have a mistake in the command. use this on: **wpr.exe -start CPU -start ReferenceSet -filemode && timeout -1 && wpr.exe -stop C:\HighCPUAndMemoryUsage.etl** – magicandre1981 Sep 07 '16 at 15:44
  • 2
    It's ridiculous this is marked as a duplicate. The service host process (`svchost`) is not the System process. – Daniel B Sep 11 '16 at 09:19

2 Answers2

1

While I can't translate what program is taking all the memory, I imagine it's the feature of Windows 10 that puts used files into memory to allow for faster access should you re-start the program that needs them. It's nothing particularly to worry about since Windows will just free the memory if you open something else.

Remember that unused memory is wasted memory. So Windows uses it whenever it can.

Stephen
  • 600
  • 4
  • 10
  • You should quote the relevant information from your link – Ramhound Sep 06 '16 at 15:36
  • Link removed as it only referred to Windows XP and 7 and not Windows 10 to which this question refers. – Stephen Sep 06 '16 at 15:39
  • 1
    I am not sure it makes a difference here. Memory mangement hasn't change that much, only difference between Windows 7 and Windows 10 would be that memory is not compressed. The article is pretty version netural, I see no reason, it wouldn't apply to Windows 10. – Ramhound Sep 06 '16 at 15:53
  • This is not cache or anything. That memory is really used. It’s a memory leak. – Daniel B Sep 06 '16 at 15:55
  • @DanielB How did you reach that conclusion? This looks like normal Windows 10 caching and compression to me. – David Schwartz Sep 06 '16 at 17:33
  • @DavidSchwartz Because no form of caching or whatever results in the Local System service host using that much memory. (It’s at 25 MiB here.) Memory used for cache isn’t attributed to any process but displayed as free. Compressed memory is displayed on the System process. Yet in this case it’s clearly the Local System service host using all memory. – Daniel B Sep 06 '16 at 17:53
  • @DanielB Memory used for cache is *never* displayed as free, since it's not free. There are caches and discardable memory all over the place in modern Windows systems. There's no evidence of a leak here. – David Schwartz Sep 06 '16 at 17:57
  • @DavidSchwartz Okay maybe my wording was bad, but please take a look at Task Manager’s memory view. Cached (aka standby) memory is “available”. Windows has carefully designed it so as not to confuse novice users. The percentage in Task Manager clearly indicates there is (almost) *no* “available” memory left. Task Manager also clearly indicates the process using the memory: The Local System service host. This process is *not* supposed to use that much memory. It *does not* host any cache. It *does not* host compressed memory. – Daniel B Sep 06 '16 at 18:12
1

I don't know how, but now my computer works like nothing happened. The RAM and the CPU as well, don't know how or why. If anybody else has this problem, the Microsoft recommended me the following steps:

  • Delete Avast antivirus https://www.avast.com/uninstall-utility
  • Search for viruses by the windows Defender
  • Delete all the "malware search" programs, including CCleaner
  • If after all these steps you still have the problem, try this:

    • Open Command line as administrator (Win+X)
    • Type these and press Enter after all the lines

      dism /Online /Cleanup-Image /ScanHealth
      dism /Online /Cleanup-Image /CheckHealth
      dism /Online /Cleanup-Image /RestoreHealth
      

I hope I could help you!

Sathyajith Bhat
  • 61,504
  • 38
  • 179
  • 264
Tibor Sas
  • 21
  • 2