Thanks, Carl and James. This is great. I didn't know that you could add
those extra columns to Task Manager.
Here are my readings:
Commit Charge:
Total 437,296
Limit 2,043,568
Peak 440,916
Physical Memory:
Total 1,047,924
Available 478216
System Cache 480,728
As for processes, I think the problem must be my anti-spy stuff. Eudora is
a biggie, but I've been using it for years. What's new on this computer is
the McAfee suite, which came with it. That takes up 83,500 in the VM
column. Counterspy takes up almost 50,000. Yahoo desktop search is next in
line with 21,000. SpySweeper comes in at around 14,000.
I can't do without Eudora. I can do without having YDS open, but that means
that when you need it it isn't indexed. I guess I have too much anti-spy
stuff, but I had a spyware catastrophe last year and it took three
different programs to sort it out. La la.
Maybe I'll take off Counterspy and just run it when I need a scan. At least
I'll try it, and see if the problem resolves. I don't like the McAfee suite
very much. Oh, well.
Thanks again. This was extremely helpful.
-- Eve
At 11:56 AM 2006-03-15, you wrote:
Your settings sound fine, but a new computer comes with a lot of add-on
widgets and other software that you weren't running on your old computer.
Some of that software may be buggy leading to this error.
Within seconds after the error message is seen, start/run taskmgr.exe, click
on Performance tab, look at Physical Memory and Commit Charge information.
According to what you said below, your Commit Charge Limit should be 3072000
(or thereabouts). If you see a number greater than 2048000 for Commit
Charge Total, switch to the Processes tab. At the top of the table click on
Mem Usage to sort the list by large memory consumers. Scroll to the bottom
to see the major memory consumers.
Report all of the numbers from the Physical Memory and Commit Charge and
what you found under Processes for further advice.
Carl
-----Original Message-----
From: Windows Home/SOHO [mailto:[EMAIL PROTECTED] On Behalf Of
Eve Golden
Sent: Wednesday, March 15, 2006 11:44 AM
To: [email protected]
Subject: Virtual Memory error
Hi, folks --
I keep getting "virtual memory is too low" errors on my four-month-old Dell
Latitude D610 running Win XP. I'm running the same stuff as I did on my old
computer, where I never had any problems, even though I had less memory
(512, I think) than on this one (1 GB). I've set it as you all advised a
couple of months ago -- Recommended setting is 1534 MB, and it's set so
that the initial and maximum sizes are 2048MB. But the errors are becoming
more frequent. Any idea what's going on?
Thanks --
-- Eve
--
----------------------------------------
To unsubscribe, mailto: [EMAIL PROTECTED]
Is your picture included in the Official Win-Home List Members Profiles
Page?
http://www.besteffort.com/winhome/Profiles.html
If not, write to: [EMAIL PROTECTED]
--
----------------------------------------
To unsubscribe, mailto: [EMAIL PROTECTED]
Is your picture included in the Official Win-Home List Members Profiles Page?
http://www.besteffort.com/winhome/Profiles.html
If not, write to: [EMAIL PROTECTED]
--
----------------------------------------
To unsubscribe, mailto: [EMAIL PROTECTED]
Is your picture included in the Official Win-Home List Members Profiles Page?
http://www.besteffort.com/winhome/Profiles.html
If not, write to: [EMAIL PROTECTED]