INTELLIGENT WORK FORUMS FOR COMPUTER PROFESSIONALS
Come Join Us!
Are you a Computer / IT professional? Join Tek-Tips now!
- Talk With Other Members
- Be Notified Of Responses
To Your Posts
- Keyword Search
- One-Click Access To Your
Favorite Forums
- Automated Signatures
On Your Posts
- Best Of All, It's Free!
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.
Partner With Us!
"Best Of Breed" Forums Add Stickiness To Your Site

(Download This Button Today!)
Member Feedback
"...You have made an incredible site which is truly a great help to me in solving problems. A tip of my hat to you!..."
Geography
Where in the world do Tek-Tips members come from?
|
Pool Non Paged bytes Memory Leak: spoolsv.exe
|
|
shorty545 (IS/IT--Management) |
28 Oct 05 14:48 |
I believe I have a memory leak in "Pool Nonpaged Bytes" for spoolsv.exe. I monitor the pool nonpaged bytes service for spoolsv.exe and the total amount continues to rise. It never goes down.
If I watch the availble memory at the same time, the amount gradually decreases.
Something is causing my server to crash every 9-10 days. I believe this is it.
How can I locate what in the spoolsv.exe is causing the leak? Anyone have any similar experience?
Thanks,
Jeremy |
|
I am having the same problem. I would think that it is one of the print drivers causing the memory leak. However my machine is a print server with over 40 different printers. I can not find a way to pin down which driver is the problem. |
|
shorty545 (IS/IT--Management) |
18 Nov 05 17:16 |
I am still having this problem with no resolve. I've tried updating all print drivers. No change. I've monitored spool services with performance monitor and it continues to consistantly grow.
In Poolmon the only tag that I see rising consistantly with is afdb. If I restart the print spooler the bytes associated with afdb go drasticly down. But after about an hour or two, it is back as the number 1 or 2 spot in when sorted by bytes.
Any HELP PLEASE!!! |
|
shorty545 (IS/IT--Management) |
26 Jan 06 17:25 |
Finally got this issue resolved!!!
The solution was to remove all HP Standard TCP/IP ports. As for the printers that were using these ports, I manually created new ports using the Standard TCP/IP port and assigned the printers to use these ports.
Case closed.
|
|
|
 |
|