Windows 10: Committed Memory full but RAM has empty space?

Can someone check what's wrong. I installed 8gb more, and it's still not enough. I don't want to destroy my ssd and want to disable page file. I recordered info by Windows performance recorder and opened a few tabs in chrome. Can someone check this info and tell me what's wrong, thanks.The link to the recording: https://drive.google.com/file/d/1px0HDTrYsxyJV13z2UUCqnxIMw1Vj5SV/view?usp=sharing

:)

 

Committed Memory full but RAM has empty space?

I'm running modded Cities: Skylines (as very memory using game when modded). I have an SSD, so I don't want a massive paging file size (at the moment its disabled to see if it will fix by problem but it doesn't seem like it). During the loading process the
committed memory maxes out, yet there is a lot of space on the RAM (image below):



I don't understand how the committed memory is full yet the RAM has almost 5GB empty? After the committed memory maxes out, the game crashes, crashes some random running programs too and sometimes black screens my PC and then spams me with errors.

 

Committed Memory full but RAM has empty space?

Surely if the total committed memory is 16GB with no paging file and I have 16GB RAM, then all the committed memory is RAM? And that memory works the same on all machines running Windows? I don't understand how the committed memory can be full but RAM is not.
I will the performance toolkit next time I try run the game, but I'm not sure when to run it, while the game is loading and RAM usage is increasing or at a different time?

 

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.