Memory Leak in Perfmon.exe Occurs Monitoring WINS Counters
Article ID: 154162
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q154162
SYMPTOMS
After several days of monitoring your WINS server over the network with
Performance Monitor, your server may stop responding. The only way to
reclaim the lost memory is to restart your WINS server.
If you monitor your WINS server by running Performance Monitor locally, you
may experience a memory leak in Perfmon.exe. You can reclaim the lost
memory by quitting Performance Monitor.
RESOLUTION
Perform one of the following to work around this problem:
- Do not monitor WINS counters.
- Run Performance Monitor locally rather than across the network. While
you experience a memory leak in this scenario, the memory is returned
when you exit Performance Monitor.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the
Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Additional query words: 4.00
Keywords: kbhotfixserver kbqfe kbbug kbfix KB154162