"Lewisd42" <> wrote:
|>I am struggling with a stubborn memory leak IRT afd.sys. Server is a
|>Windows 2003
|>Enterprise with 2GB RAM. The problem is in Non-Paged memory, so I know
|>the total system RAM is irrelevant. The system will run for about 3-4
|>days then hang with the event log showing 2091 and 1053 errors.
|>Monitoring Poolmon shows that Afdb is growing to the point of sucking
|>up all the non-paged memory so the system will quit accepting any
|>connections except local log on and oddly enough, Remote Desktop
|>connection. The killer of it all is that restarting the Print Spooler
|>releases ALL the excess memory. I did one restart of the Spooler and
|>recovered over 11MB of Non-Paged Pool. I am trying to use the driver
|>verifier to see if it is an HP print driver. I have read that some
|>possibilities include the HP TCP/IP port being a problem, but I have
|>run those on this server for a couple years without a glitch.
|>
|>The logical question now is, "Ok, what did you install recently that
|>caused this to start up??" Therein lies the rub. The only thing RECENT
|>is a new version of Symantec AV corp (10.1.0.394) and I have noticed
|>that the problem seems to occur after the Nightly AV scan runs. I would
|>
|>normally disable the scan, except that after a reboot, the AfdB tag
|>continues to grow and there is no "scan" running other than the
|>Real-Time scanner....and why in the world would a Print Spooler restart
|>
|>affect something being leaked by an AV? I just am not sure that the AV
|>thing is anything more that coincidence, but I am throwing it out there
|>
|>as part of the facts.
|>
|>
|>I guess I am not sure of what to look for using verifier, but it sure
|>makes a nice display of information. Here is a snapshot of what it says
|>
|>for afd.sys:
|>
|>
|>Name: afd.sys, loads: 1, unloads: 0
|>CurrentPagedPoolAllocations: 390
|>CurrentNonPagedPoolAllocations: 2301
|>PeakPagedPoolAllocations: 410
|>PeakNonPagedPoolAllocations: 2325
|>PagedPoolUsageInBytes: 102728
|>NonPagedPoolUsageInBytes: 399136
|>PeakPagedPoolUsageInBytes: 108008
|>PeakNonPagedPoolUsageInBytes: 936532
|>
|>
|>And then 30 seconds later:
|>
|>
|>Name: afd.sys, loads: 1, unloads: 0
|>CurrentPagedPoolAllocations: 389
|>CurrentNonPagedPoolAllocations: 2316
|>PeakPagedPoolAllocations: 410
|>PeakNonPagedPoolAllocations: 2339
|>PagedPoolUsageInBytes: 102464
|>NonPagedPoolUsageInBytes: 413440
|>PeakPagedPoolUsageInBytes: 108008
|>PeakNonPagedPoolUsageInBytes: 936532
|>
|>
|>And so on....so I am wondering if I am looking in the right place. Any
|>insight into this would be greatly appreciated since my users (About
|>150 of them) routinely get held up from work first thing in the morning
|>
|>if I don't get the server rebooted in time. I am now stuck with
|>restarting the Print Spooler every day, but that's simply not workable.
Post this again to: microsoft.public.windowsxp.general
might even ping David Candy, he's got this drive verifier down.
If all else fails you might email him
your dump files
verifier generates.
--
*..· ´¨¨)) -:¦:-
¸.·´ .·´¨¨))
((¸¸.·´ .·´ -:¦:-
http://www.nasa.gov/mov/148112main_pia08118-320-cc.mov
-:¦:- ((¸¸.·´* NASA and Partners Release New Movies Of Titan -16megs
Similar Threads
