Hello:

No, not THAT memory...

Uhhh. Where was I?? Oh, yeah... I've been getting memory warnings about "excessive" memory use, or something like that. I installed a meter, and it DOES show, with NOTHING running except Firefox, 35% usage. It goes up as I add a few internet connections, and Google.. But, NONE of that should make my usage go up to as high as 75% with NO memory hog apps running.. I installed a "what's running" program, but it LOOKS like nothing unusual is running in the background... But, I really can't tell...

What's up with this beast?

excon

The Windows task manager shows running processes and the amount of memory each process uses. If their sum isn't near to the total memory in use, you may be infected with something hidden.

What was the exact memory message and your total memory amount?

Excessive memory usage can be a sign of malware infection. Update everything, run a virus scan and then you can use MSConfig to stop loading as many programs and services on boot.

Hello you guys:

Thanks for you help so far... I haven't seen the message since I posted, so I can't tell you exactly what it says.. But, it's a Firefox message, not a windows one.

I keep my PC pristine. I run anti-virus every night, have a strong firewall, and I run Ace Utilities all the time.. I don't think I have a virus. z

In MSconfig, I wouldn't know WHAT programs NOT to load upon start.

Frankly, I don't think it's my startup programs, because my memory usage right after I reboot isn't high. It's after a few hours of using Firefox, and NOTHING ELSE, do I see my memory usage go way up and get that dreaded message...

It's JUST a message. Nothing bad happens. I don't run out of memory. I guess it's a good thing that I seldom run memory hog apps.. Nonetheless, the memory thing is curious. I just want to guard against somebody USING my memory online for some nefarious deed...

excon

I just wanna guard against somebody USING my memory online for some nefarious deed...
That wouldn't be the case. Firefox did indeed have a memory leek issue a few versions back but it was resolved... mostly. You could try using Chrome.