A hotfix is available that addresses several problems on a Windows Vista-based or Windows Server 2008-based computer that supports the Intelligent Platform Management Interface

You may experience the following problems on a Windows Vista-based or Windows Server 2008-based computer that supports the Intelligent Platform Management Interface (IPMI).

Problem 1

You want the system to perform standard software error-processing when a hardware error generates a nonmaskable interrupt (NMI). To do this, you set the NMICrashDump registry entry to "1" under the following registry subkey:However, after a nonmaskable interrupt (NMI) is caused by the IPMI Watchdog Timer, and the system restarts, the Operating System Boot System Event Log (SEL) messages are not saved in the baseboard management controller (BMC) as expected. Therefore, your IPMI-compliant management software does not capture the correct computer state. This symptom occurs only if the BMC interrupt is enabled.

Note The NMICrashDump registry entry is an NMI switch that specifies whether the system performs standard software error-processing when a hardware error generates an NMI. When the NMICrashDump registry entry is set to "1," the system should perform standard software error-processing. For example, in this situation, the system might display a "Stop error" message. Additionally, Itanium-Based systems can generate a memory dump without this registry entry. This registry entry is only effective on x86 and x64 platforms.

Problem 2

The IPMI driver uses an Add SEL command to capture the log header when it tries to log the following SEL messages:

• Operating System Stop
• Operating System Boot
• Operating System Shutdown

However, if the SEL message is compliant with IPMI event message formats, the IPMI driver should use a Platform Event command to capture log headers instead of an Add SEL command. Add SEL commands should only be used to store OEM-format SEL messages.

Problem 3

When Keyboard Controller Style (KCS) communication interrupts are enabled in the BMC, interrupt service routines (ISRs) may be invoked before the IPMI driver finishes the initialization of BMC interrupts. This behavior may cause unnecessary execution of ISRs.

Note KCS communication interrupts are enabled when the "byte 1 bit 0" of the BMC Global Enables data is set.

Hotfix information

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.

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems 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.

Prerequisites

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

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

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 files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

  Version	Product	Milestone	Service branch
  6.0.6000.16xxx	Windows Vista	RTM	GDR
  6.0.6000.20xxx	Windows Vista	RTM	LDR
  6.0.6001.18xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	GDR
  6.0.6001.22xxx	Windows Vista SP1 and Windows Server 2008 SP1	SP1	LDR

• Service Pack 1 is integrated into Windows Server 2008.
• The MANIFEST files (.manifest) and MUM files (.mum) installed for each environment are listed separately. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.

For all supported 32-bit versions of Windows Server 2008 and of Windows Vista

For all supported 64-bit versions of Windows Server 2008 and of Windows Vista

For all supported Itanium-based versions of Windows Server 2008

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information for Windows Server 2008 and for Windows Vista

Additional files for all supported 32-bit versions of Windows Server 2008 and of Windows Vista

Additional files for all supported 64-bit versions of Windows Server 2008 and of Windows Vista

Additional files for all supported Itanium-based versions of Windows Server 2008