The information in this article applies to:
SYMPTOMSIn Windows NT 4.0, a non-paged pool memory leak may occur when functions like IoReadPartitionTable() or DeviceIoControl() attempt to read a partition table. The Microsoft Developer Network explains these functions at: http://msdn.microsoft.com CAUSEThis problem occurs because memory allocated when reading the partition table may not be freed in the event that an error, such as STATUS_DEVICE_BUSY, is returned. RESOLUTIONA supported fix that corrects this problem is now available from Microsoft, but
it has not been fully regression tested and should be applied only to systems
experiencing this specific problem. If you are not severely affected by this
specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack
that contains this fix. http://www.microsoft.com/support/supportnet/overview/overview.aspThe English version of the Windows NT Server and Windows NT Workstation fix should have the following file attributes or later:
STATUSMicrosoft has confirmed this to be a problem in Windows NT 4.0. MORE INFORMATIONAdditional query words:
Keywords : kbenv kbbug4.00 kbfix4.00 |
Last Reviewed: December 9, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |