Computer Does Not Boot When Tracking Memory Usage with Pool Tags

ID: Q217140

The information in this article applies to:

Microsoft Windows NT Server, Enterprise Edition versions 4.0, 4.0 SP4

SYMPTOMS

After you install Windows NT 4.0 Service Pack 4 on a computer running Windows NT 4.0 that already has the Microsoft Windows NT 4.0 Hardware Compatibility Test (HCT) tool (version 8.1) installed, the computer may stop responding (hang).

CAUSE

The HCT tool automatically enables the use of pool tags to track thread memory usage, and this feature may cause a conflict with the Ntoskrnl.exe file.

RESOLUTION

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/

Q152734 How 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://www.microsoft.com/support/supportnet/overview/overview.asp

NOTE: If this product was already installed on your computer when you purchased it from the Original Equipment Manufacturer (OEM) and you need this fix, please call the Pay Per Incident number listed on the above Web site. If you contact Microsoft to obtain this fix, a fee may be charged. This fee is refundable if it is determined that you only require the fix you requested. However, this fee is non-refundable if you request additional technical support, if your no-charge technical support period has expired, or if you are not eligible for standard no-charge technical support.

For more information about eligibility for no-charge technical support, see the following article in the Microsoft Knowledge Base:

Q154871 Determining If You Are Eligible for No-Charge Technical Support

STATUS

Microsoft has confirmed this to be a problem in Microsoft Windows NT 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

Additional query words:

Keywords : kbenv ntstart ntsp nt4sp5fix
Version : winnt:4.0,4.0 SP4
Platform : winnt
Issue type : kbbug