Where does Committed Memory working from?

Hello everyone, sorry for if there is any forum already exist (which i have n't found yet). Windows 10 brick since it release. I am added two screen shots and i can't comprehend yet how windows 10 memory work. In some forum, It claimed that

"The whole point of virtual memory is that it can be much larger than physical (RAM), no?btw... you appear to have a pagefile of about 24 GB, since you have 8 GB RAM and the commit limit is 32 GB. So your "committed" could be as high as 32 GB. (And at the moment it almost is that high, so reducing or eliminating the pagefile would be a bad idea.)"

this is from 3rd paragraph of best selected answer. windows 10 - Why is my "Committed" memory so much higher than my actual RAM space? - Super User "24GB since u have 8GB and the commit limit 32 GB"

My question is, where is that committed memory (in memory? or in c: ? which i disable),according to screenshots shows that memory usage is 2.2/8 GB and 3.4/GB committed Memory while i have disabled page file from all drives. sorry for messy thanks

Committed memory isn't something that physically exists. It isn't RAM usage, or pagefile usage, or any combination of them. It isn't actually stored anywhere. It is just a number. But it is an important number.

Committed memory (often referred to as the commit charge) is a somewhat difficult concept. Many Internet articles have tried to describe it, and got it wrong. It is difficult to describe something complex in a way that is both easy to understand and technically accurate. Microsoft user level documentation tends to err on the side of easy to understand, but at the expense of technical accuracy. Technical documentation is good, but of course it assumes the reader has the knowledge to understand it.

As simple as I can describe it:

When an application or the OS required a place to store data it must ask the memory manger for it. This is generally referred to as allocating memory. This data storage can be in RAM or the pagefile. When the request is mode the application may not need it immediately or know how much it will actually need. But it needs to know it is immediately available when it is needed. In fulfilling the request the memory manager promises or makes the commitment that it will be available. To do this it keeps a running total of all such requests by all applications. This is the commit charge.

The commit limit, the maximum level that the commit charge can reach, is RAM size plus pagefile size, minus a small overhead. With no pagefile it will simply be RAM size.

Windows will not allow the commit charge to exceed the commit limit. Otherwise it would be making a promise it may not be able to keep. That could lead to all kinds of bad things.

The memory manager will refuse a request if it would exceed the commit limit. Some applications will handle this gracefully but it is hard to do. Many will simply give up and silently terminate without warning. To avoid this it is important that the commit charge does not get too high.

It is not normally recommended to disable the pagefile. When disabled there is a hard limit on the commit limit, the size of RAM. With a pagefile with default configuration the commit limit will be RAM size plus pagefile size. And that is a soft limit. It can be increased by enlarging the pagefile if needed. Not that this doesn't imply the pagefile will actually be used. It just has to be there.

Well, I don’t disable page file usually. I just love to mess things with exceed of my curiosity. I appreciate your time and effort. I posted this forum to determine if I need to add more ram or not. So if I can’t tell which is by actual memory usage which could be “2.2/8 GB or 3.4/8 GB. Because if almost half of memory in use with no application running, then where would memory usage would go or make pc lag/slow. I am very picky since I built my own pc

The Task Manager display is typical of a 8 GB system with relatively light usage. The actual RAM usage is 2.1 GB. The commit charge does not represent RAM usage at all. It isn't a value of particular importance unless it approaches the commit limit, which it is not.

Without knowing the circumstances under which the screenshot was taken it really doesn't mean much. The important thing is what is the memory usage when under a heavy workload.