Windows 10: Why is my maximum commited memory shrinking after restarting and is there a way to retrieve it?

I have been noticing that when playing my game world of tanks that it sometimes states that "not enough memory, please restart the game". When I did that, I still received the message. When I looked in my task manager, i saw that my commited memory was 128/128gb. I thought that shouldn't be right and restarted my computer. After restarting and checking my task manager again i saw that it came down to 9.4/77.6gb have no screenshot of it unfortunately, cause i thought it wasn't a big problem. After playing world of tanks for a few more times and turning my computer off and on again, I saw th

:)

 

Windows Commit memory leaks away at about 8GB/Hour

System is 32GBRam, from reboot I show commit memory of approx 6GB commted over the following 30 mins this ramps up to say 13.3/65.8 Gb

after a number of hours and the end of the days the system becomes unstable as commit memory hits maximum, and I have to reboot

I have ensured all updates are applied and monitored commit memory by process (in resource monitor) this shows no change in committed memory by process so the no suspect process is in the list.

What steps of diagnosis would anyone recommend....

 

How does memory/commit charge work in Windows 10?

This question is prompted by the following regularly observed phenomena I'd like to find an explanation for:

1. Current commit is regularly higher than Physical usage + Pagefile size. What's up with that? Shouldn't that be impossible? [This it seems might be because of compression. Which transforms the question to: Why doesn't commit limit then go up or something? I.e. what's the point of compression if it doesn't help with memory usage?]
   
2. Sometimes this reaches extreme levels where Current commit is more than double physical memory usage!
   
3. When commit charge fills up and windows starts asking me to close things, most of the time physical memory is at around 60%. This seems horribly inefficient.
   

This is on windows 10, as reported by Process Explorer.

The ultimate question I'd like to answer, is: Can I forego artificially inflating my page file to levels my starved-for-space SSD is ill-equipped to handle just so I can actually effectively utilize my physical memory? (Or even if it wasn't as full. That is, I'd like to avoid suggestions like "Do X/Y/Z to your page file".)

 

Committed Memory full but RAM has empty space?

I thought that Windows performance recorder capture is more than enought, but okay. Here you can see, when i opened 1 more tab in chrome, it's crashed. The commited memory was 19.6 GB, and after i closed one app, because i couldn't create a screenshot, the commited memory decreased to 17.7 GB. As I said earlier, physical ram utilization is not even close to maximum. Aida64 showed that's virtual memory utilization is ~100%, that's why i connected it to commited memory stats.