Paging file size going crazy

I have posted similar question a while ago when I realized my paging file occupying 32 GBs (Surfaced starting Windows version 1703 ~ 1709) , the recommendations were to set paging file use off then back on .

Now I noticed when I did the new paging is down to 1906 MBs which is fair , surprisingly it booms with the very next system restart to this :

Without me touching anything , now if I started playing games it may well reach the 32 GBs ceiling not only that but may start occupying different partitions as well .

This laptop is 8 GBs of RAMs and has an Nvidia GPU of 4 GBs + 4 GBs shared memory and on latest Nvidia Drivers .

When playing games RAM usage (Monitored by Task Manager with the aid of an additional display) would not exceed even 50~60%

When setting a Maximum size to paging files games may crash reporting insufficient memory issues after a while of use (Despite not less than 40% of RAMs are reported free by Task Manager) .

This now has me in doubt that windows is directing shared memory to paging file some how but I'm still wondering how it still manages to boom it to almost 16 GBs on second restart without me touching anything .

Post a screenshot of Task Manager - Performance tab showing memory info when the problem appears.

I suspect that the large pagefile is simply a symptom of the real problem, a large commit charge. Low memory warnings have nothing to do with a RAM shortage. Windows doesn't even have any messages for that. Such errors are due to the commit charge approaching the commit limit.

@CountMike like I said manual leads to crashing on longer game play .

@LMiller7 The low memory warnings I think are game related / DX / .Net frame work and is game dependent , I had one game reporting not enough texture memory once even .
Here are screen shots taken just as I run a game and then 10 minutes later , so yea the so called commit value keeps increasing , so what's to be done here ?
Game Start :

10 Minutes Later :