Nothing is gobbling up hard drive resources,..so that's good but i was hoping for a clue. :-/Before you try anything else, turn your page file back on.
Make it at least like 1Gb. My guess is.... one of your programs has code that says "move this code from the RAM to the Page file, and don't stop moving it until it's all in the page file
"...which is a impossible task for you. It's not showing up in resource monitor OR system explorer, since low level memory mapping/allocation routines are always handled by the windows kernel ( which isn't visible, right?). I'd say it's a pretty good guess as to what's happening. No program should be micromanaging memory like that, it should be left to operating system to handle..........but there are always bad programmers. I've met a few myself.
On embedded systems and really old programs, programmers make a lot of effort to force unnecessary code out of RAM. Sorry, it's the best guess i have.
Originally Posted by allikat
Remember, Windows uses a large pile of memory for its' own cache, and it releases memory from that cache space as it's required. That will frequently show a good few GB of memory as in use, but it will quickly become available as soon as software asks for it.
Yes, but his problem clearly something else. Window's isn't going to cache 6 GB of RAM for Chrome or mspaint.
Originally Posted by borandi
A little known fact is that any GPU in your system actually pins an equivalent amount of CPU memory for itself, to use as needed. So how many GPUs are in your system? I doubt you would be using more than 6GB of memory on your GPUs, but it's worth asking in case you're on a tri-fire/SLI setup across several screens. Ideally you want the minimum amount of CPU memory in your system to be the sum of your GPU memory + 2 GB (or +4 GB). Usually this memory doesn't show up as used, but something may be showing it in your system.
I think your have a terrible misunderstanding about how memory allocation and mapping works....but i could be wrong. I would like to see your source/proof on this. Memory reserved for hardware DOES show up, it show's up at "hardware reserved" in the resource manager.
The CPU builds a internal memory map of the items in GPU memory. The CPU doesn't need to copy GPU memory, it's just need to know where to look to find stuff. This memory map takes a very small about of CPU RAM, because it's basically a look up table, like the "table of contents" in a book (as opposed to copying the whole book).
If guess if you had a tripple SLi system with 6GB of video memory, and your had a CPU with 2Gb of RAM....the CPU might have a hard time keeping this table in RAM amongst the other things going on in RAM. I don't think that's our problem.Edited by crimsontears809739 - 3/21/12 at 9:12am