Virtual Memory fills up uncontrollably

February 16, 2011 at 07:26:09
Specs: Windows XP, INTEL CORE2DUO
I have a Dell with a Core2Duo and 2GB of DDR2 667MHz RAM. I have my Virtual memory set to around 1.5 to 2 times that and use my D: drive for additional virutal memory. I don't use my System drive just so my OS doesn't crash.

My memory keeps filling up as my computer stays on longer and longer. It goes upto 11GB. I have never seen any computer let alone mine do this.

I am not sur if it is some setting or a virus of some sort. Any advice will be greatly appreciated.


See More: Virtual Memory fills up uncontrollably

Report •

#1
February 16, 2011 at 07:57:10
How are you determining the page file is getting to 11gig?

If you set it to 1.5/2x ram that is a static setting and can't grow past 2xram.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#2
February 16, 2011 at 08:06:05
One I get a notification at the taskbar saying my virtual memory is filling up.
Also when I pull up the Taskmanager, in the Performance tab, right at the bottom the field which says 'Commit Charge ' says ~11000M.



Report •

#3
February 16, 2011 at 08:31:10
One I get a notification at the taskbar saying my virtual memory is filling up.
Also when I pull up the Taskmanager, in the Performance tab, right at the bottom the field which says 'Commit Charge ' says ~11000M.

Report •

Related Solutions

#4
February 16, 2011 at 09:09:40
Is this a 64 bit OS? It would require multiple processes, each with a very high private bytes usage to rea

Report •

#5
February 16, 2011 at 09:12:34
No its a 32bit OS.

Report •

#6
February 16, 2011 at 09:14:03
Is this a 64 bit OS? It would require multiple processes, each with a very high private bytes usage, to reach a 11000 MB commit charge. With 2 GB RAM it would require a pagefile of at least 9 GB.

Could you provide a screenshot of Task Manager - performance tab?


Report •

#7
February 16, 2011 at 09:50:32
Don't mess with the virtual memory settings, just let Windows handle it.

Report •

#8
February 16, 2011 at 15:18:34
commit charge is not solely related to the pagefile. It is virtual memory but this is cache in RAM as well as pagefile.sys on the hard drive.
http://www.pcmag.com/encyclopedia_t...

"With 2 GB RAM it would require a pagefile of at least 9 GB."

Not following your reasoning here LMiller7. System would/could never use a 9gig pagefile. If that much paging to disk was required you would have already hit the ceiling in hard page faults in memory which requires you to add ram not pagefile.

rajat4108 what you see is usually the result of rouge software like a virus or malware infection. Have you scanned for these?

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#9
February 16, 2011 at 16:07:56
The commit charge represents the size of virtual address space for which storage has been committed. This may be in RAM or the pagefile. Thus, if you have a 11000 MB commit, at least 9000 MB must be committed to the pagefile. This does not mean that there is 9000 MB of data in the pagefile, only that the pagefile must be that large in the event that all committed memory was actually used. You can have a very high commit with very little data in the pagefile.

A 32 bit system could certainly use a 9 GB pagefile or even more and still perform well.


Report •

#10
February 17, 2011 at 08:53:11
Sorry but I belive you have it opposite Lmiller7. 9000mb is in RAM and 2000mb is on the disk in the pagefile. From the OP " 1.5 to 2 times"

If you ever monitored a large pagefile you would see the OS never uses all of it. Never ever.

Like I said if you needed that much paging the system would already be slow/failing due to hard page faults which would compound the disk i/o access issue because you have paging and hard faults requiring the files on the disk to be read back into memory.

http://www.wordiq.com/definition/Pa...

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#11
February 17, 2011 at 09:08:03
Thanks for the detailed replies.
I tend to agree with you that it is a rogue/malware of some sort.

The exact message that I get at the Taskbar is : "Your Sytem is low on virtual memory. Windows is increasing the size of your paging file.During this process, memory requests for some applications maybe denied. "

I tried to pull up the Taskmanager, in the Performance tab, right at the bottom the field which says 'Commit Charge ' says ~11000M and take a screen capture but the computer had slowed down too much.

I currently have AVG 2011 the free version and spybot and they haven't been able to pickout anything. Is there any other free Virus SW that might help with this?

Thanks again.


Report •

#12
February 17, 2011 at 11:28:21
Those should be sufficent to meet your needs.

I would suggest you look at the processes tab in task manager to see what is consuming the most resources.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#13
February 17, 2011 at 21:24:06
Just to make this perfectly clear:
We have a reported commit charge of 11,000 MB. I rather doubt this but we will assume it to be true. Since Windows will not over commit there must be storage available for all 11,000 MB. Since RAM is only 2GB the pagefile must be at least 9,000 MB to provide the necessary storage.

Commit charge refers to the amount of storage that would be required if all committed memory were actually used, not how much data is actually being stored. We could have a pagefile of 9 GB that is required for the current commit charge but contains very little data, or, at least in theory, none at all. RAM usage could also be low. Commit charge has nothing to do with pagefaults.


Report •

#14
February 18, 2011 at 05:17:11
All, thanks for your help. I got the issue fixed. It was a malware of some sort. I used Malware Bytes.

http://download.cnet.com/Malwarebyt...
/3000-8022_4-10804572.html?part=dl-10804572&subj=dl&tag=button

Great software cleaned out whatever was causing it.

Also LMiller7 is right, the reported committed charge was 11GB. When I looked up all the programs running and summed it, it didn't total 11GB though the commit charge said so. The additional 9 GB came from HD space.


Report •

#15
February 18, 2011 at 05:36:57
Glad you have the problem solved.
One of the problems with malware is that it often hides itself from Task Manager and other such utilities. To see a programs contribution to the commit charge you must look at the "Virtual Memory size" column which will display as "VM Size". This is not displayed by default. Of course in the case of malware it may not be displayed at all.

Report •

#16
February 18, 2011 at 09:03:03
"Since RAM is only 2GB "

You are missing a key issue in memory management of ram.

After all if, as you say, 2gig of physical ram was included in the commit charge where would be no room for anything else.

There maybe only 2gig of physical memory but ram is virtualized and is always under any system reported to apps as 4gig. The OS literally lies to everyone while it juggles virtual space within ram space.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#17
February 18, 2011 at 11:07:22
Committed virtual address space requires that there be sufficient physical storage available. This can be in either RAM or the pagefile. 11,000 MB committed memory requires that at least that much physical storage be available. Since RAM is 2 GB the remainder must be in the pagefile. This does not mean that this much storage is actually in use. It only means that this must storage must be available somewhere.

Report •

#18
February 19, 2011 at 08:05:57
sorry but that is not correct. If we were limited by physical memory the folks trying to run xp on 256meg of memory wouldn't even be able to boot.
Perhaps this will help
http://en.wikipedia.org/wiki/Virtua...

Notice in the following link the 4GB limits which I mentioned previously

http://en.wikipedia.org/wiki/Virtua...

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

#19
February 19, 2011 at 09:25:38
It appears that you have some misconceptions about the commit charge but I don't have sufficient time to deal with this. I see little point in continuing this.

I have read the articles above and many more.


Report •

#20
February 19, 2011 at 11:31:36
I would agree there is some misunderstanding on how ram is utilized and how memory is virtualized. Best of luck.

Answers are only as good as the information you provide.
How to properly post a question:
Sorry no tech support via PM's


Report •

Ask Question