i would leave it on auto, win 10 doesn't use the page file unless it needs to swap things out of ram to put other things in, like when you playing a game.
windows doesn't have an out of ram error, what it sees as memory is page file + ram so you can run out of memory and still have ram, I have seen people run out who had 21 out of 24gb of ram free. So starving the page file isn't ideal
you might have a memory leak as windows should not run out like this
Download
Process explorer and run it as admin (it comes from Microsoft so its safe)
the default view is tree structure meaning like your task manager screen, it will show what processes are underservice, but unlike task manager, it shows the ram usage of each part so you can see what is eating your ram
Private bytes = actual ram usage
Working set = Ram + page file usage - this might be where you find problem
This page shows what all the colours and headings mean, link at bottom of it shows how to use it to find problems. You can right click headers and run an av scan from within the program.
see if you can identify anything using large amounts of working set as this is likely where the problem is.