Windows 10: nslookup.exe Commit 2.5 GB of my RAM

Hi everyone, I'm Junior Web Developer who code in windows 10. lately, I got front-end project using vue as main framework.Everything seems to be fine, until lately my pc felt slowing down. Turn out, there is a program that commit aprox 2.5GB from my 8GB of RAM. It is called "nslookup.exe". At first, I just killed the program, and I got my 2.5GB space RAM back and everything just run normally, no crash or anything. Only for 5-10 minutes, the program start to run again for some reason and took the same amount of my space RAM, 2.5GBI search about it, asked why this program keep running and do

:)

 

More than 6 GB of RAM of 16 GB missing

I have a fast W10 64bit 16GB RAM pc.

Task Manager shows me around 900 MB used for Me as as user, no other user accounts on the pc, the list I can see also adds up to around that, "Everything" taking around 470 MB, Antimalware 140 MB, Windows Explorer 42 MB, etc., it quickly goes down to processes
not using more than 5 MB, than 1 MB, and the list is not endless, I can clearly see (without adding one-by-one) that the about 870 MB my user account takes, according to the Task Manager, are more or less correct, certainly not above 1 GB, from 16.

According to the Task Manager, just 45 % of memory is free though:

182 Processes, 2680 Thread, 70,000 Handlers, CPU 1 %.

Available memory 7.3 GB of 15.9 GB = 45 %, this remains stable, before I start any other program.

In use (compressed) 6,9 GB (0 MB)

Committed 7.7 GB of 18.3 GB (my graphics card also has 2 GB, so this might explain the difference between 16 and 18.3).

Pages pool 184 MB

Non-pages pool 176 MB.

So does W10 64 bit really need, above the user account's less than 1 GB, another almost 7 GB, so that from my 16 GB, just 7.7 GB remain usable for my software (except for "Everything"'s 470 MB)?

I had installed, and de-installed (!), 2 RAM-Disks some weeks ago, and I don't see any residuals from them, but could them be the culprits? Wouldn't that be shown in the above numbers?

Is Windows really that bad, or might I have non-Windows problems on my pc?

 

16GB of committed memory on a 8GB RAM system

You do not have 16 GB of committed memory. Your task manager screen snap shows that you have 2.2 GB of committed memory, aka "commit charge", with a commit limit of 16 GB.

Committed memory is virtual address space, specifically process-private virtual address space, and it is pageable. So n GB of commit charge is not necessarily using n GB of RAM. And on the other hand, there are other uses of RAM besides committed memory.

See the numbers on your first Task Manager screen snapshot under "Committed"? The first shows how much is currently committed (the "commit charge") and the second shows the commit limit. (Running into the commit limit brings you the "Windows is low on memory" pop-up.)

The graph on the memory page shows physical (RAM) memory usage and it shows only 30% of RAM in use. So disabling your page file will not address your performance problems.

Committed memory is created when processes allocate it. You don't really have a problem with your commit charge, but for reference, I'll add: Each process's contribution to this is shown in TM's "Details" tab, "Commit size" column (which is not displayed by default; you'll likely have to add it). The paged and nonpaged pool also are part of the system-wide commit charge.

You mention that another view of Task Manager (which we can't see) seems to show that your disk 0 is busy a high percentage of the time. Try using the Disk tab in Resource Monitor to see what's accessing the disk so much.

btw, an often-overlooked cause of slow disk activity is disk errors, which result in retries. Check the event log for this.

 

AMD FX OC'ers Club

That's what the auto setting will do since you're over the 1333 mark it jumps to the next step which isn't listed or officially supported I assume by that ram.

At this point though I would suggest dropping the multi one step or .5 so that we can get something stable and possibly take the heat issue out of the picture for now.