Vista - Using only 1/3 page file, but unable to load application

I'm not able to load even another tab on the browser unless I exit an
application. Why am I not using my entire page file? Below are the
statistics from Task Manager. Any ideas? TIA

Physical Memory (MB) System
Total 2037 Handles 27701
Cached 1037 Threads 1032
Free 0 Processes 81

Kernel Memory (MB) Page File 1610M/5956M
Total 151
Paged 87
Nonpaged 64

On the bottom: Physical Memory 58%

Resource monitor also shows Physical memory use at 58%

'David' wrote, in part:_____

Your problem is not a lack of memory. Task Manager is showing half your
physical memory is being used as cache to speed disk operations; if the
operating required more memory for applications, it would just reduce the
memory devoted to cache. As long as applications don't need the memory, it
is more efficient to use it as cache rather than let it sit idle. The
number of handles, threads, and processes reported is not out of line
either. My guess is that you have a application that is not well behaved
(either not completely compatible with Vista or ill-programmed) or Vista
still has some hidden problems that only crop up in particular
circumstances; the first suggestion is more likely the problem. The only
thing I see that is exceptional is your excessively large page file. Since
you would have had to manually set a page file to be so large with 2 GBytes
of physical memory, is it possible that you may have made other 'tweaks',
perhaps in the 'Advanced System Settings' where you changed the page file
size?

At any rate, the Vista Home Premium / Intel T7300 platform I am using to
post has Internet Explorer with a half dozen tabs, Microsoft Mail, Windows
Media Player, and Task Manager running (plus the usual services, etc.) Task
Manager reports, for this system:
Physical Memory (MB) System
Total 2045 Handles 72764
Cached 1366 Threads 1018
Free 14 Processes 86

Kernel Memory (MB) Page File 1970M/4312M
Total 191
Paged 83
Nonpaged 107

Physical Memory: 41% (848 MBytes)

You've not provided much information on WHEN the problem occurs. After
rebooting does the problem go away for a while, then recur?

Phil Weldon



"David" <dfumento@xxxxxx> wrote in message
news:3EECDC9B-7B17-450E-AB88-E08ECC81D82A@xxxxxx