Physical Memory Going Nuts!!

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

My available physical memory can go from 210mb right down to 5. I have 512mb
memory altogether. What's going on and how can I fix this?
 
gwynaz said:
My available physical memory can go from 210mb right down to 5. I have
512mb
memory altogether. What's going on and how can I fix this?
Some memory intensive program is using the physical memory.
As for what is going on, I have no idea because you gave no information
about which program is using the memory.
The easy way would be to install more memory.
Another way would be to determine which programs are the memory hogs and
whether these programs have been infected or not.

Jim
 
you can use this freeware
to manage the memory:
http://www.amsn.ro/

i don't suggest to keep
it running all the time.

instead you can run it then
quit it, before or after
running any program.

My available physical memory can go from 210mb right down to 5. I have 512mb
memory altogether. What's going on and how can I fix this?
 
How do I find out which program is using all the memory?

Open the Task Manager...
Ctrl + Shift + Esc | Click on the Processes tab |
Click the CPU header twice to bring the highest user to the top of the list

If CPU isn't available, Click View, then click Select Columns. Place a
check mark in the box by CPU Usage.

The Processes tab shows information about the processes running on your
computer.

For example, you can display information on CPU and memory usage, page
faults, handle count, and a number of other parameters.

To sort the list of processes
* On the Processes tab, click the column heading you want to sort by.
Note
* To reverse the sort order, click the column heading a second time.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In gwynaz <[email protected]> hunted and pecked:
 
db said:
you can use this freeware
to manage the memory:
http://www.amsn.ro/

i don't suggest to keep
it running all the time.

instead you can run it then
quit it, before or after
running any program.

That product is pure unadulterated crapware that is totally incapable
of performing any useful function with respect to memory usage.
Period.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
gwynaz said:
My available physical memory can go from 210mb right down to 5. I have 512mb
memory altogether. What's going on and how can I fix this?

By design Windows will always attempt to find some use, anything
whatever that might potentially be of some benefit, for every bit of
the installed RAM. Unused memory should perhaps more accurately be
referred to as "useless memory" because that is what it actually
represents - memory for which Windows has so far been totally unable
to find any beneficial use for.

Hope this explains the situation.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
maybe for you it is.

i use it and it's benefits
outwieghs your opinion.


db said:
you can use this freeware
to manage the memory:
http://www.amsn.ro/

i don't suggest to keep
it running all the time.

instead you can run it then
quit it, before or after
running any program.

That product is pure unadulterated crapware that is totally incapable
of performing any useful function with respect to memory usage.
Period.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
no,
this is inaccurate...

there are a number of
dll's that cannot get
unloaded by windows
when the memory is
running low...

where exactly do you
get your opinions...?


gwynaz said:
My available physical memory can go from 210mb right down to 5. I have 512mb
memory altogether. What's going on and how can I fix this?

By design Windows will always attempt to find some use, anything
whatever that might potentially be of some benefit, for every bit of
the installed RAM. Unused memory should perhaps more accurately be
referred to as "useless memory" because that is what it actually
represents - memory for which Windows has so far been totally unable
to find any beneficial use for.

Hope this explains the situation.

Good luck

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
db said:
maybe for you it is.

i use it and it's benefits
outwieghs your opinion.

Defragmenting memory is pure hokum.

All addresses in RAM are equally accessible with the same access time.
Period. Not an opinion. An absolute and undeniable fact.

Any program that purports to optimize performance by defragmenting
memory is crapware.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
db said:
no,
this is inaccurate...

there are a number of
dll's that cannot get
unloaded by windows
when the memory is
running low...

That much is correct, but I didn't say anything about that in my
response.
where exactly do you
get your opinions...?
From 37 years of experience with computers, among others.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
maybe you overlooked
the fact i provided because
you were too busy preaching
to the o.p. with unhelpful
rhetoric.

unloading dll's is only one
aspect that can attribute
to the subject at hand.

it is hoped that we do not
tread on each others sub threads
as i prefer only to respond to
the o.p. with helpful suggestions
rather than debate the issues
with others.

detente is better than taunting...


db said:
no,
this is inaccurate...

there are a number of
dll's that cannot get
unloaded by windows
when the memory is
running low...

That much is correct, but I didn't say anything about that in my
response.
where exactly do you
get your opinions...?
From 37 years of experience with computers, among others.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
db said:
maybe you overlooked
the fact i provided because
you were too busy preaching
to the o.p. with unhelpful
rhetoric.

Balderdash.



unloading dll's is only one
aspect that can attribute
to the subject at hand.

Artificially forcing Windows to unload DLLs (which is your idea, I
never mentioned it) is often a bad idea because all too often the DLL
will have to be reloaded again. And reloading a DLL from the hard
drive will take approximately 1,000 times longer to access than it
would if that DLL had been left in RAM, as Windows wanted to.
it is hoped that we do not
tread on each others sub threads
as i prefer only to respond to
the o.p. with helpful suggestions
rather than debate the issues
with others.

Whenever I seem people recommending "snake oil" type products I will
always intervene with the truth. And the truth is that any product
that purports to improve performance by defragging RAM is pure
unadulterated crapware.
detente is better than taunting...

And honest accurate information is better than misinformation and
deception.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
well, if you are positive
that memory management
is snake oil, you should
take your complaint to
Microsoft.

microsoft wrote the programming
codes for managing memory but
only left minimal options for use
by the customers.

however people much smarter than
yourself, have combined the
multitude of codes for managing
memory into little programs.

the coding is available at
Microsoft.com

in conclusion, issues also arise
with large memory as well

unfortunately, i believe that your perception
and rationalization of windows
capability to manage memory
is just as flawed for larger memory
configurations...

db said:
maybe you overlooked
the fact i provided because
you were too busy preaching
to the o.p. with unhelpful
rhetoric.

Balderdash.


unloading dll's is only one
aspect that can attribute
to the subject at hand.

Artificially forcing Windows to unload DLLs (which is your idea, I
never mentioned it) is often a bad idea because all too often the DLL
will have to be reloaded again. And reloading a DLL from the hard
drive will take approximately 1,000 times longer to access than it
would if that DLL had been left in RAM, as Windows wanted to.
it is hoped that we do not
tread on each others sub threads
as i prefer only to respond to
the o.p. with helpful suggestions
rather than debate the issues
with others.

Whenever I seem people recommending "snake oil" type products I will
always intervene with the truth. And the truth is that any product
that purports to improve performance by defragging RAM is pure
unadulterated crapware.
detente is better than taunting...

And honest accurate information is better than misinformation and
deception.

Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
incidentally, this will be my
final response.

it should be noted that
the windows operating system
confirms and validates the
results from using the program
i suggested and disproving
your "snake oil" assessment.

although i appreciate the
challenge to a certain extent;
there is no need for me to further
this conversation and waste my
valuable time on this issue.
 
db said:
well, if you are positive
that memory management
is snake oil, you should
take your complaint to
Microsoft.

If you can show me any credible reference to where Microsoft has ever
advocated defragmenting of RAM memory then I will gladly do so. But
you can't and won't because it simply doesn't exist. Microsoft
knows, as does anyone who really understands computers, that
defragmenting of RAM memory is a total waste as there is nothing that
can possibly be gained. All addresses in RAM are equally accessible
with the same access time. It takes no longer to go from an address
at the beginning of RAM to one at the far end than it does to go from
an address to the immediately adjacent address.

The product you advocate purports to defragment RAM as a performance
matter. That is pure and absolute drivel and serves only to prove
that the creators of that product have absolutely no real knowledge
about the subject.


microsoft wrote the programming
codes for managing memory but
only left minimal options for use
by the customers.

Yes.


however people much smarter than
yourself, have combined the
multitude of codes for managing
memory into little programs.

the coding is available at
Microsoft.com

Where? URL or other citation please.
in conclusion, issues also arise
with large memory as well

Issues do arise regarding memory, that is true. But fragmentation is
not one of them.
unfortunately, i believe that your perception
and rationalization of windows
capability to manage memory
is just as flawed for larger memory
configurations...

What are you talking about? The only issue I have raised in our
discussion is your advocacy of a product that promotes itself on the
basis of defragmenting RAM. You have not, in fact cannot, provide
any credible reference (e.g. a Microsoft document) that mentions this
subject.


Ron Martell Duncan B.C. Canada
--
Microsoft MVP (1997 - 2008)
On-Line Help Computer Service
http://onlinehelp.bc.ca
Syberfix Remote Computer Repair

"Anyone who thinks that they are too small to make a difference
has never been in bed with a mosquito."
 
I have issues putting faith in posts by people that don't even know
how to post to Usenet (pardon my top posting in this message). I'm
quoting your entire reply so you can look for yourself at areas you
quoted and areas where you posted 'new' data. It's quite confusing
because you don't really know what you are doing with your replies and
quoting. Plus, your lines are too damn narrow. Set your line length to
60 or 70 characters and let the software do the work of wrapping.
After all, you are the one touting that the programmers know more than
the users. Try following your own advice before criticizing others.
Have a nice day, assuming you haven't already killfiled me. :)
 
Ron said:
If you can show me any credible reference to where Microsoft has ever
advocated defragmenting of RAM memory then I will gladly do so. But
you can't and won't because it simply doesn't exist.

I don't believe Microsoft has ever advocated defragging RAM memory, but
apparently they feature an article written by Future Publishing Limited,
which does just that:
Memory optimisation tools make it easier for you to optimise
memory quickly, without delving into the Control panels. If you
want to run software that requires a large chunk of memory, such
as image or sound editors that load the whole file into memory to
work on it, or if you don't often turn your PC off, then memory
optimisers will help you reclaim memory from other applications.
They will also defragment free memory so Windows doesn't spend
time and effort keeping track of several smaller chunks of memory.

(from http://support.microsoft.com/kb/835645/en-gb )

Of course, there is a disclaimer at the top of this page:
The articles set out below are articles created and/or produced by
Future Publishing Limited. Microsoft is not responsible for the content,
accuracy or opinions expressed in these articles.

So, although Microsoft doesn't advocate this procedure, they apparently
have no problem presenting it. Maybe a complaint to them *would* be
useful...
 
http://support.microsoft.com/kb/835645/en-gb would apply if running Windows
98.

You cannot defrag the pagefile (C:\pagefile.sys) in XP without a 3rd party
tool or a lot of hassle.

<quote>
Defragmenting the Paging File
To defragment, or reduce the amount of fragmentation in the paging file:
1. Click Start, point to Settings, click Control Panel, and then
double-click System.
2. On the Advanced tab, click Performance Options.
3. Click Change to open the Virtual Memory dialog box.
4. Change the paging file to another drive.
5. Reduce the minimum and maximum size of the original paging file on the
drive you want to defragment to 0 MB.
6. Restart your computer to have the system use the new paging file.
7. Run Disk Defragmenter on the original drive to consolidate the free space
segments created by moving the paging file.
8. Re-create the paging file on the original drive.
9. Reduce the minimum and maximum size of the temporary paging file to 0 MB.
10. Restart your computer.
<quote>
from...
Files Excluded by the Disk Defragmenter Tool
http://support.microsoft.com/kb/227350

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Back
Top