Windows 10: Excessive Commited Memory caused huge Lag

I was browsing the web normally when I suddenly gained a huge lag, after some struggling to get into task manager because of the lag I was able to see that the committed memory was automatically ramped up to 30.1Gb and 28.7GB was being used out of it; please note I only have 8Gbs of RAM and this is the first time this is happening… Any help would be appreciated please.

:)

 

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".)

 

Investigating huge windows commit size

The program that was faulty is "runSW.exe". After killing it, 6GB of commit memory was released!