Ooh, someone got up grumpy.
The facts of this issue have not changed between Windows Vista->7->8, specifically the x64 editions.
Windows does not "want" to use more than 80% of available memory. There's one person who wants to argue this point for the sake of arguing. He doesn't even argue whether or not it's a major issue but if this happens at all. It's inane as anyone can see from
their resource monitor how windows allocates memory and can observe the magic 80% number in action.
If you have NO page file, then
Windows will issue low memory warning immediately upon reaching the 80% threshold.
If you HAVE page file then
Windows will happily allocate SOME of that remaining 20% of RAM but will start to move it to page file immediately until you're back at max 80% allocated.
It's stupid but there's nothing you can do about it as Microsoft does not want to cap the buffer/reserver amount in absolute megabytes for some reason. At 8GB machines that's 1.6GB memory doing nothing much, perhaps it'll finally be patched when 16GB becomes
commonplace as 3.2GB is fairly obvious overhead.
Workarounds: Get more RAM. More the better. Yes, you only get 4/5 of it actually used but RAM is cheap and do you think the amount used is being allocated efficiently? Use the page file. Yes it's annoying but it adds some flexibility to the system at least.
For HDD pagefile should not exceed more than 3-4GB, your machine will be already rather sluggish at such amount. Allocating 1.5x RAM is old obsolete and completely wrong in 2014. If you have SDD you can have larger pagefile if you want but you'd better buy
more RAM instead.
Chrome leaks memory like crazy, deal with it. You can see the actual amount used by opening url about://memory (which goes to chrome://memory-redirect/). Using adblock makes the memory leak much worse but not using adblock makes life worse. If you want even
more nitpicking detail you can check chrome://memory-internals/
There's also chrome task manager available from shift-esc
You can try "the great suspender" extension for chrome. At least for firefox similar extensions which (try to) unload tabs do not work as firefox does not actually release the memory when tab is suspended. But it's worth a shot..