Hi Yank, thanks.
Yes, Full System Scan, which would run during idle periods, if my settin was "ON". I knew where to look to check this per the "'book", however, my concern is that it was running regardless in the background .. even though I have no entries in the logs.
The reason for asking is that I experiece from time to time a Commit Charge (XP Pro/Sp3) increase of +/-140mb. The system in question is old, lean and with a total of 512mb, so every mb counts. I normally have a commit charge of around 285-290mb after boot .. so when I start out with circa 430mb after boot it's a problem of sorts. Typically, the higher commit charge stays with me for a week or 10 days or so .. befor the lower commit charge returns for 3-5 days before it goes up again.
If I recall correctly, it all happened after I upgraded to NAV 2011 last May, and, thus my suspicion that NAV has something to do with this. And, yes, I have removed all Norton progs, run the cleaner, and reinstalled. No difference.
I have NAV 2102 19.2.0.10 and no other active (only demand) virus/malware progs installed. Let me add a print-screen of XP's task manager showing a "normal" boot, and, then, ditto one showing an "elevated" boot. The columns differ, but, VM Size is in both. Again, this is a good/normal boot:
And this is what I call a bad/elevated boot! Note the VM Size increase for ccsvchst.exe, explorer.exe and one svchost.exe.
Any ideas here? Also non-NAV culprits or hidden processes which behave like this? Best, CBA
Hello SendOfJive,
This isn't a Norton issue. Your symptoms are exactly those that DaveH and I have experienced, and which Reese Anschultz had indicated were possibly related to a Microsoft memory leak that was introduced in the KB2616676 update.
Thanks, interesting. I'll look into the link provided. But, note that my problems started last May and are intermittent. Some good days followed by several bad ones. In the link below I posted my initial query on this:
At the time I tought I had found the culprit, an orphaned file (qdfsdrv.sys - Norton Filter Driver 7.0.0.15), which was part of Norton CleanSweep (removed a long time ago). But, as it turned out, this file wasn't the the cause of my problems.
DaveH fixed the issue by investigating the problematic crypt.dll file and removing the update, but there is a hotfix for this that Reese mentions. I have not installed the hotfix, so I cannot say if it fixes the issue.
Do you refer to Crypt.dll, Crypt32.dll or CryptSvc.dll? Searching for the Crypt.dll file, I get no hits, but, I have a bunch of the other ones (below).
Do you think the referenced hotfix applies in my case? If so, I may try it next time my "symptons" start show again. Right now I'm fine .. booting up at around 290mb or so. Or, did Reese indicate that a hotfix is in the offing ... in my lifetime? Best, CBA
- �1995 - 2013 Symantec Corporation Legal Notice License Agreement Privacy Policy Cookies Site Map RSS
