Microsoft KB Archive/235425

= CreateFile Can Cause Leak in Paged Pool Memory =

Article ID: 235425

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
 * Microsoft Windows NT Server 4.0 Enterprise Edition
 * Microsoft Windows NT Workstation 4.0 Developer Edition

-



This article was previously published under Q235425



SYMPTOMS
Your computer running Windows NT may become unresponsive and may display an error message indicating that the computer is running low on virtual memory.

In addition, Performance Monitor shows a rise in paged pool memory usage that never declines.



CAUSE
This behavior may occur if a program makes a call to the Win32 application programming interface (API) function CreateFile, and passes a drive letter that is mapped to a remote file system using the Windows NT redirector (this results in an error value of ERROR_INVALID_NAME). The Windows NT redirector did not release memory allocated to attempt this operation.



Windows NT Server or Workstation 4.0
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:


 * http://www.microsoft.com/windows/servicepacks/ -or-


 * 152734how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp

Windows NT Server 4.0, Terminal Server Edition
To resolve this problem, obtain the latest service pack for 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 Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.

Keywords: kbhotfixserver kbqfe kbbug kbnofix KB235425

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.