A swap file question  

You may get a number of varied responses on the topic, but generally speaking, the best course of action is to simply allow Windows to automatically manage this. It is only in rare circumstances that you should need to change this.

... and those questions are what?

reddwarf4ever said:

Ok, even if that’s the best option, there are still questions around this I would like answered....

Here's one you may not have thought of. You MUST have a swapfile on the C: drive if you want to have a complete memory dump after a BSoD so that you can diagnose the cause.

Microsoft said:

If you select the Complete memory dump option, you must have a paging file on the boot volume that is sufficient to hold all the physical RAM plus 1 megabyte (MB)....

...A kernel memory dump records only the kernel memory. This speeds up the process of recording information in a log when your computer stops unexpectedly. You must have a pagefile large enough to accommodate your kernel memory. For 32-bit systems, kernel memory is usually between150MB and 2GB. Additionally, on Windows 2003 and Windows XP, the page file must be on the boot volume. Otherwise, a memory dump cannot be created.

https://support.microsoft.com/en-us/...ns-for-windows

My standard recommendation regarding pagefile configuration: Unless you have specific reason for changing this, and you understand what you are doing, leave the configuration on system managed. If you are at the point of asking questions it is hardly likely you will do better than this.

If you don't have an SSD, get one. It will do far more for performance than anything you could possibly do with the pagefile.If you have the pagefile on an SSD all you need to know about the pagefile is that is be big enough to meet commit charge requirements. The commit charge is essentially RAM size plus pagefile size.

It really shouldn't be necessary to speak of having a pagefile on a conventional drive. For the sake of completeness I will do so.

A great deal of nonsense has been written about the pagefile. And much that was valid when written is now obsolete. Even with a conventional drive most attempts to optimize the pagefile are a waste of time. It typically isn't used enough to make much difference. But probably putting the pagefile on it's own partition is one of the worst things you can do. This solves a problem you almost certainly don't have, and replaces it with one that is very real. #1 factor in conventional drive performance is seek time. To minimize seek time you want the pagefile as close to other OS files as possible. A pagefile on it's own partition maximizes seek time, the exact opposite of what you want. Not that this is likely to male much difference anyway.

Unless you are really low on RAM, just leave it alone and let the system manage it.