Archived from groups: microsoft.public.windowsxp.general (More info?)
I am running XP Pro with 1Gb of RAM on a Dell box. The paging file is fixed
at an additional 1Gb of virtual memory. My typical usage is not very
taxing - Outlook, a few windows of MSIE, paint.net, MS Streets & Trips, etc.
A couple of times a week my system acts as if it is running out of memory:
new windows won't open up until I close existing windows. I go into Control
Panel and various applets will open to a blank screen. I'll hit a button in
Outlook and get a 'plunk' sound. A reboot will correct the problem every
time.
When I check the performance tab in task manager I never see my commit
charge go much higher than 600,000 and the peak never much higher than that
so I should have lots of system resources free. CPU usage is always low and
the available system memory always shows plenty of wiggle room. The only
thing I can see that is consitent is that when the system starts wigging out
the number of handles always seems to be around 17,000 or so as opposed to
the 14,000 that I usually see.
Currently I have 57 processes, 626 threads and 14336 handles, about an hour
and a half after last reboot and everything is working well.
Any pointers on how to figure out what is happening would be greatly
appreciated.
I am running XP Pro with 1Gb of RAM on a Dell box. The paging file is fixed
at an additional 1Gb of virtual memory. My typical usage is not very
taxing - Outlook, a few windows of MSIE, paint.net, MS Streets & Trips, etc.
A couple of times a week my system acts as if it is running out of memory:
new windows won't open up until I close existing windows. I go into Control
Panel and various applets will open to a blank screen. I'll hit a button in
Outlook and get a 'plunk' sound. A reboot will correct the problem every
time.
When I check the performance tab in task manager I never see my commit
charge go much higher than 600,000 and the peak never much higher than that
so I should have lots of system resources free. CPU usage is always low and
the available system memory always shows plenty of wiggle room. The only
thing I can see that is consitent is that when the system starts wigging out
the number of handles always seems to be around 17,000 or so as opposed to
the 14,000 that I usually see.
Currently I have 57 processes, 626 threads and 14336 handles, about an hour
and a half after last reboot and everything is working well.
Any pointers on how to figure out what is happening would be greatly
appreciated.