I am trying to sort of figure out how to 64-bit Windows deals with memory. The main reason is that I am using Dragon NaturallySpeaking 10.0 preferred which is a voice-recognition package. It is known that this will temporarily freeze when it runs out of memory. Sometimes it returns a report that it is attempting to recover from low system resources.
In Windows, the term "System Resources" does not mean memory, well, it does, but not the systems memory.
Windows contains a number of "pools" of memory called "heaps", these heaps are referred to as "System Resources" and refer to areas of memory reserved for graphics objects, fonts, file handles, and window objects. Some kinds of apps use ridiculous amounts of these resources and leave them low for other apps, and when you have several apps that use ridiculous amounts (or have resource leaks), then you run into trouble.
You can have 8GB of memory free and still run out of system resources. This is one of those "annoyances" about the architecture of Windows that we just have to deal with.
The only real solution is to find out what's using all your resources and not run those apps.