The paging file you disabled has nothing to do with VRAM it's merely when the system runs out of system RAM it uses the HDD for 'virtual memory'. A GPU using system RAM used to be known as 'AGP Aperture' back in the AGP days and it's a completely different animal to the Windows paging file.
If anything all that your tests show is that either you have insufficient system RAM or Windows is poor when it comes to system memory management.
I'd also like to know how you managed to run these tests fairly? what benchmark did you use to ensure both runs were identical?
Did you read the whole thread?
It basically answers all of the questions you have. Most notably -
1. Until the GTX 680 it seems that cards could not use physical memory when they ran out of vram. So, as Nvidia call it they "texture stream".
The tests I ran show that when the paging file is disabled the physical ram usage does not change. Therefore it is "texture streaming" from somewhere, and that somewhere is not system memory.
2. When you disable the paging file the game can crash. Why? And why doesn't it crash for me? Put simply the game must be using the paging file. We already knew this, however, and this is why we celebrated the 680 using system ram. Even though it's still a million miles from being ideal it's got to be better than using the page file.
As for insufficient system ram? it didn't change. I know it's been pointed out that windows memory monitor isn't very accurate, but the results were identical.
3. If you had read the opening post you would have seen how I ran the tests. However, as I pointed out a few times they are not accurate benchmarks and should not be taken as so. They are simply there to show what happened when I disabled my paging file and ran the game on the same level.
No BF3 benchmark is ever going to be completely accurate. Any one can work that out. There is no "set routine" benchmark that does exactly the same things during the FPS recording.
What I mean is when some one benchmarks BF3 they have to play it. And when they play it each benchmark is going to offer a multitude of scenarios and differences as it's not a set benchmark.
Metro 2033 would probably have been better. But, this whole thread was not about Metro 2033. So I simply benchmarked it using the only method available to me, which is to play the game.
In other words I am trying to make people understand that sometimes what you see isn't exactly what you get. All it takes is one spike in FPS or one extra explosion and you have millions of people declaring one product better than the other.
Stupid really.