View Single Post
  #8   Report Post  
Posted to sci.electronics.repair
Arfa Daily Arfa Daily is offline
external usenet poster
 
Posts: 6,772
Default Any Windoze experts on here ? Bit OT ...



"martinmarty" wrote in message
...
What are you using to see the amount of memory in use, like 35% then
eventually 90%?

I agree with the guy who said go into Task Mgr / Processes and see
which tasks are using the memory.

Another couple ideas to narrow it down, if you think you know what the
culprit is, to test the theory:

- Go into MSCONFIG and under the Services & Startup tabs, disable all
non-essential non-MS startups and services, then see if PC can idle
for a few days without gobbling up all mem.

- Along the same lines, try booting into Safe Mode and see if it can
idle a few days without gobbling up the mem.

Or if you don't know what the culprit is perhaps you can use those
techniques to determine by process of elimination.

Perhaps some program or even OS component has a debug trace or log
turned on which is stored in mem and the longer you run the more it
consumes.


Some good steers there, and also from others who have replied. Thanks all
for your input. I am using two things to monitor the memory usage. The first
is the built-in Windoze memory and processor usage graphic desktop widget.
The second is the memory usage monitoring tool in the memory cleaner program
that I have been using. It agrees exactly with the Windoze one, which would
suggest that they are right. As you see the memory clogging up over a couple
of days, the system performance degrades very noticeably, to the point where
it becomes unusable for all practical purposes. If you then run the cleaner,
it will recover perhaps 20% at best, and there is a corresponding
improvement in performance, which again, would suggest to me that what the
widget is reporting as being the case, actually *is* the case. Ultimately,
the only way to get the system back to full normal performance, is to either
soft or hard restart, after which, low memory usage is again reported.

When I get time, I'll do a restart, and then note what all of the background
applications and the system, are using. When it has started to clog
noticeably, I'll recheck, and see what is using it all ...

Arfa