The reason for the confusion about DIMM voltages on Sandy Bridge is that Sandy Bridge and most Rev 3.0 motherboards prefer 1.500V DIMM. There are 1.65V DDR3 DIMM but they're not preferred for the new Sandy Bridgemotherboards. So the RAM manufacturer may say "1.65V" and the motherboard manufacturer may say "1.5V".
Some people are running 1.65V DIMMs on their 1.5V motherboards without issues. Other people will tell you that it's a horrible idea and that you can cause problems with your system by doing so. If the DIMM that you bought are 1.65V DIMM and you are only putting 1.5V to them and they're working error-free, then you're fine. If they require 1.65V to work without errors then you're in the "not recommended" area. Again, some users don't mind that and others do. I think that's a call only you can make for yourself. (I personally would make sure that I bought 1.50V DIMM and stick to what the motherboard manufacturers recommend.)
That being said, when you fully populate the DIMM slots on your motherboard, you may need to increase your voltage slightly above what the DIMM are rated at from their manufacturer in order to make them stable. (So that's where things get really dicey, if you're using 1.65V DIMM and they need 1.66V to get stable because of how many you have, but your motherboard recommends only 1.50V you're pushing the limits even harder here.)
The issue of a fully populated set of DIMM slots on your motherboard is completely independent from the issue of 1.50V vs 1.65V DIMM.
I hope that makes a bit more sense now.
Moving along, it sounds like with 3DS Max and Mudbox and Zbrush that you may
indeed have a need for 16GB of RAM and may even have a need for a page file beyond that.
Page file size is not something I would let Windows allocate dynamically allocate in most situations because this leads to fragmentation issues and a fragmented page file sucks
on a standard HDD. What I would do, is run a clean-sweep of my drive (CCleaner is great) and disable the page file. Then I restart my PC and I defragment my HDD. (I like Defraggler, from the same company that makes CCleaner.) Once I have my HDD completely defragged (NOT on SSD, I'm talking traditional HDD here) then I will enable a page file and make the maximum and minimum size identical, not allowing Windows to determine the size. Doing this forces the page file to be contiguous and prevents it from ever becoming fragmented and this improves performance dramatically.
Again, I do not know enough about SSD to know whether or not its best to have a page file on a SSD or on a HDD. Ask the SSD experts here about that.
A page file on a SSD would certainly perform better than on a HDD but I suspect that a page file on a SSD may wear it out quickly due to the many read/write operations inherent with a page file.
As far as what size to make the page file, if I need one, what I do is monitor my RAM use with the page file disabled and run the most memory intensive programs that I have and see what sort of memory warnings come up. (Most programs will tell you how much more they need.) I like to make my system have about 80% of the memory used in a maximum memory load scenario, which allows ample reserves for regular operations like opening and closing windows, saving files, etc.
If you encounter an issue where Windows is running out of memory you can always increase the size of your page file. Note that if you've written more to your HDD that you'll likely cause your page file to become fragmented, so it's a good idea to go back and disable the page file, reboot, sweep the system clean, defragment completely, then set the new pagefile size and verify that it's contiguous.
The pagefile fragmentation issues are one reason that many people recommend that you have your page file somewhere other than the C partition. Another reason folks recommend having it on other drives is that file access is typically faster at the beginning of the disk, so if you have two physical HDD and your OS is on hda then you can put your page file on a clean fdb and it will be not only contiguous, but also at the very beginning of the disk which makes it perform ever so slightly better than if it were at the end of the disk. (The larger the platter size of disk is, the more marked that performance difference will be.)
If you have only one physical HDD with multiple partitions (primary or logical) then ideally, the page file should be at the beginning of the disk. Note that when I say "beginning" of the disk, that means beginning from what the OS sees and it's actually the outer edges of the disk where the angular velocity is highest. The inner areas of the disk are the "end" of the disk and the file performance is slowest there. Since you are using SSD and if you are going to use your HDD as a page file then It would definitely be best to have the HDD formatted into two partitions and have the "first" partition be dedicated to the page file and nothing else. (You can then allow Windows to dynamically allocate page file with the confidence that it will never become fragmented if you do not use it for any other purpose and do not store other files there.)
Unfortunately, I do not know of a way to create profiles that will disable the DIMM slots on your motherboard from within the OS. Physically placing a DIMM into the slot will cause it to draw electrical power and affect the RAM timings and voltage / current draw.
However, as I mentioned above, if you use a dedicated HDD (or partition) for your page file, you can allow Windows to dynamically manage your page file. You may never even use the page file with 16 GB of RAM, even with the 3DS Max. Then again, if you're running large numbers of polygons and using xrefs (external references) you might be using huge amounts of RAM and need far more than the 16 GB your system has. Often, 3DS Max recommends that you have a page file 2x the size of your physical RAM amount.
Fortunately, Windows is fairly good about trying to use physical RAM before it uses virtual RAM so if you are using 16 GB of RAM and a large page file, Windows shouldn't
slow you down in gaming, for example.