there is a memory leak in nMvA pool tag. running findstr /m /l tag *.sys resolves it as aswmon2.sys or aswmon.sys.
I can absolutely confirm this under Windows XP SP3.
Using the methods described here, here and here, I’m getting
Memory: 2096124K Avail: 1090788K PageFlts: 186 InRam Krnl: 228K P:118524K
Commit: 940764K Limit:4037644K Peak: 953912K Pool N:32840K P:125572K
Tag Type Allocs Frees Diff Bytes Per Alloc
THCN Paged 15 ( 0) 9 ( 0) 6 27591264 ( 0) 4598544
nMvA Paged 926577 ( 77) 919362 ( 75) 7215 15410312 ( 4112) 2135
MmSt Paged 18163 ( 0) 4598 ( 0) 13565 14379880 ( 0) 1060
CM35 Paged 350 ( 0) 203 ( 0) 147 11718656 ( 0) 79718
NV_x Paged 5 ( 0) 0 ( 0) 5 7307264 ( 0) 1461452
...
and after a while (~45min, running and closing several programs)
Memory: 2096124K Avail: 943956K PageFlts: 788 InRam Krnl: 256K P:163516K
Commit:1070884K Limit:4037644K Peak:1227344K Pool N:32916K P:170336K
Tag Type Allocs Frees Diff Bytes Per Alloc
nMvA Paged 2225163 (1015) 2206052 (1008) 19111 40124216 ( 14392) 2099
THCN Paged 20 ( 0) 12 ( 0) 8 27746912 ( 0) 3468364
CM35 Paged 373 ( 0) 226 ( 0) 147 11718656 ( 0) 79718
MmSt Paged 31411 ( 0) 21999 ( 0) 9412 11716352 ( 0) 1244
NV_x Paged 5 ( 0) 0 ( 0) 5 7307264 ( 0) 1461452
...
After running for several hours, messages in the error log start showing.
Event ID 2020
Event Type: Error
Event Source: Srv
Event Category: None
Event ID: 2020
Description:
The server was unable to allocate from the system paged pool because the pool was empty.
The system then becomes unusable and has to be rebooted.
The tag ‘THCN’, btw, resolves to ‘aswSP.sys’.
Hope this helps!
Not to thread Hijack, but I’d like to know if this may be affecting me too.
Windows XP SP3 Avast version 7.0.1451
I lack an programs to find memory leaks, but I’ve noticed that my Commit charge is growing at a very fast rate! Generally, with firefox running it averages 350-400 commit charge…I’m over 550 now.
Also, when I turned on my monitor after leaving my computer on all night, I noticed I was logged out of Skype, the skype screen was entirely black save the drop down and login info. Half the names on Trillian were blank or missing letters, my desktop had multiple icons blacked out and I could do nothing except start menu - restart. When I did, I noticed a popup beneath the busted skype window saying “There is not enough memory to complete this operation.”
Well ,I’m a little more reassured about my (memory leak?) problem like have more and more guys with WXP SP3 and new version ais 7.0.1451
After 2 or 3 hours (with browser activity) , popups appear to say programs didn’t be found , not enough memory , … some others programs closed , windows half blank , icons blacked
So , pending an update or a solution , where/how can I downgrade ais to version 7.0.1426 , please ?
Thanks
- Uninstall avast from Control Panel first.
- Boot.
- Use Avast Uninstall for complete uninstallation.
- Boot.
- Stay off-line (not connected to Internet)
- Install again the old version: http://filehippo.com/download_avast_antivirus/ or http://www.oldapps.com/avast_antivirus.php?old_avast=6918
- Boot.
- Register avast (insert the registration key).
- Uncheck the programs updates (set to manual).
- Only then connect to Internet (go on-line).
- Check and post the results.
Thanks for this “How/Where” I will try and post results
I downgraded to 7.0.1426 PRO (I still got my old setup file), and everything’s back to normal 
BTW, I don’t see the memory leak on Win7 SP1…
Well , all right with 7.0.1426 (total memory kernel = 85 000 ko , it was to 400 000 ko when crash with 7.0.1451)
I have to do it with 2nd PC but the problem is that I lose personal config when I apply aswclear.exe utility :-[
I am having the exact same symptoms listed by the users above. Really hoping this critical error will be fixed asap as it renders my computer unuseable after a few hours (parts of gui missing, error messages, programs unable to start - fixed with a reboot until memory runs out again). Also using WinXP SP3.
It was enough for me to switch over to MSE. Sorry Avast, You’ve been great to me over the years, but…
Ditto for me! I’m suffering exactly the same symptoms with 7.0.1451 and WinXP Pro + SP3.
I did what Tech suggested and downgraded to version 7.0.1426. Now I’m back to a working avast!Pro again.
Suggestion: avast should perform a better betatest phase… I already learned such horror stories with e.g. ESET NOD32 (the reason why I switched to avast, they never fixed it)… 
:o
An update to the .1451 update is severely needed, and in a hurry! >:(
Are the developers aware of the issue? I’m asking because I read on the forum they are going to release a new program update at some time next week.
I don’t appear to be suffering the issues on my XP Pro SP3 system that others are reporting here, not that means they aren’t which is clearly the case.
Whilst I don’t have the memory leak tools to check it in the way that others have done, only the task manager data on usage and I’m not seeing anything overly different to normal, running out of memory and no errors as mentioned by others.
No problems here either. (See screenshot)
System up and running since very early morning.
The memory leaks described above appear in the kernel memory pool, which is not visible in task manager!
You have to use at least Process Explorer’s “System Information”. There it shows as “Kernel Memory”.
Whilst that is true, but the consuming of your memory resulting in memory errors is a very rough and ready indication if you have the problem.
I have received some information on this:
By all accounts this is only present in win2k/winXP and I’m told the bug is fixed (and relates to rename operations). Now I don’t know if that fix, means an internal program build awaiting release, I have asked that and awaiting confirmation.
Like I said before with v7.0.1451 Kernel memory grow to 400 000 ko , now no more than 85 000 ko (1 day opened with v7.0.1426) . (Win xp INTEL PIV hypethreading)
On the other hand , for my 2nd Pc (win xp AMD Athlon) , no trouble anymore with new update . It confirm it’s not a general problem.
For the future, you can backup/export your settings and restore later, avastUI, Settings, Maintenance, Settings Backup.
DavidR, +1
Seems if some of those who wish to run systems 24/7 are the ones experiencing this problem.
XP Pro SP3 Avast! 7.0.1451 2GB RAM no problems seen so far, but then again only run system when actually using it.
Great thread! Great diagnostics. Should be a standard part of the beta testing process, it is likely those who have lesser memory (256-512 MB) might display this issue sooner, rather than later.
@ Herrminator,
Is problem now resolved? It was an update that fixed it?