Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Event ID: 19 occurs on Windows Server 2008 or Windows Vista Service Pack 1-based computers that use Intel Nehalem processors


View products that this article applies to.

Symptoms

The Windows Hardware Error Architecture (WHEA) feature is enabled on Windows Server 2008 or Windows Vista Service Pack 1 (SP1) systems that are installed on computers that use Intel� Core� i7 (Nehalem) Processors.

In the following event in the System event log, the WHEA handler incorrectly reports that corrected memory errors are processor translation lookaside buffer (TLB) errors:

Log Name: System
Source: Microsoft-Windows-WHEA-Logger
Event ID: 19
Task Category: None
Level: Warning
Error Source: Corrected Machine Check
Error Type: TLB Error
Description:
A corrected hardware error occurred.

Therefore, customers incorrectly assume that the system's processors have to be replaced. In fact, customers may have to replace failing memory DIMMs.

Regardless of how many times the customer replaces the processors, the errors in the event log persist.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix on a Windows Vista-based computer, you must have Windows Vista SP1 installed. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
935791 How to obtain the latest Windows Vista service pack
No prerequisites are required for Windows Server 2008-based computers.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Vista and Windows Server 2008 file information notes

The .manifest files and the .mum files that are installed in each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. These files and their associated .cat (security catalog) files are critical to maintaining the state of the updated component. The .cat files are signed with a Microsoft digital signature. The attributes of these security files are not listed.
For all supported 32-bit versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Whealogr.dll6.0.6001.2238631,23226-Feb-200904:32x86
For all supported 64-bit versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Hal.dll6.0.6001.22386231,90426-Feb-200904:55x64
Hal.infNot Applicable2,92625-Feb-200923:34Not Applicable
Whealogr.dll6.0.6001.2238633,28026-Feb-200904:52x64
For all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Hal.dll6.0.6001.22386428,01626-Feb-200904:48IA-64
Hal.infNot Applicable2,60025-Feb-200923:32Not Applicable
Whealogr.dll6.0.6001.2238654,27226-Feb-200904:45IA-64

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products. For more information about the Intel Nehalem processors, visit the following Web site:

↑ Back to the top


More information

Additional file information for Windows Server 2008 and Windows Vista

Additional files for all supported 32-bit versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Package_for_kb961080_client_1~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable13,74926-Feb-200922:57Not Applicable
Package_for_kb961080_client~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43226-Feb-200922:57Not Applicable
Package_for_kb961080_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable15,35626-Feb-200922:57Not Applicable
Package_for_kb961080_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42426-Feb-200922:57Not Applicable
Package_for_kb961080_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable15,83326-Feb-200922:57Not Applicable
Package_for_kb961080_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43226-Feb-200922:57Not Applicable
X86_microsoft-windows-whea-troubleshooter_31bf3856ad364e35_6.0.6001.22386_none_b69230a064ccbdab.manifestNot Applicable55,85526-Feb-200904:59Not Applicable
Additional files for all supported 64-bit versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Amd64_hal.inf_31bf3856ad364e35_6.0.6001.22386_none_5f73cea1d9a5e670.manifestNot Applicable1,65626-Feb-200923:06Not Applicable
Amd64_microsoft-windows-whea-troubleshooter_31bf3856ad364e35_6.0.6001.22386_none_12b0cc241d2a2ee1.manifestNot Applicable55,87126-Feb-200905:16Not Applicable
Package_for_kb961080_client_1~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable14,15626-Feb-200922:57Not Applicable
Package_for_kb961080_client~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,44026-Feb-200922:57Not Applicable
Package_for_kb961080_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable15,98126-Feb-200922:57Not Applicable
Package_for_kb961080_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43226-Feb-200922:57Not Applicable
Package_for_kb961080_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable15,96626-Feb-200922:57Not Applicable
Package_for_kb961080_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,44026-Feb-200922:57Not Applicable
Package_for_kb961080_winpesrv_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43026-Feb-200922:57Not Applicable
Package_for_kb961080_winpesrv~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43926-Feb-200922:57Not Applicable
Additional files for all supported Itanium-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Ia64_hal.inf_31bf3856ad364e35_6.0.6001.22386_none_0356d71421467e36.manifestNot Applicable1,65526-Feb-200922:57Not Applicable
Package_for_kb961080_sc_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable4,88526-Feb-200922:57Not Applicable
Package_for_kb961080_sc~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42726-Feb-200922:57Not Applicable
Package_for_kb961080_server_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable4,88126-Feb-200922:57Not Applicable
Package_for_kb961080_server~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43526-Feb-200922:57Not Applicable
Package_for_kb961080_winpesrv_0~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,42626-Feb-200922:57Not Applicable
Package_for_kb961080_winpesrv~31bf3856ad364e35~ia64~~6.0.1.0.mumNot Applicable1,43426-Feb-200922:57Not Applicable

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseinter, kbfix, kbbug, kbqfe, KB961080

↑ Back to the top

Article Info
Article ID : 961080
Revision : 2
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 415