Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
An update rollup package for the Hyper-V role in Windows Server 2008 R2: August 24, 2010
Article ID: 2264080 - View products that this article applies to.
This article describes an update rollup package that resolves some issues for the Hyper-V role on a computer that is running Windows Server 2008 R2 and that is dated August 24, 2010.
Issue 1When a computer has one or more Intel CPUs code-named Nehalem installed, you receive the following Stop error message:
Note The Nehalem CPU for a server is from the Intel Xeon processor 5500 series and for a client computer is from the Intel Core-i processor series.
0x00000101 ( parameter1 , 0000000000000000, parameter3 , 000000000000000c) CLOCK_WATCHDOG_TIMEOUT
Issue 2Consider the following scenario:
Note You have to restart the VM to recover from this issue.
Issue 3When a computer has an Intel Westmere processor, you receive an error message that resembles the following:
STOP: 0x0000001a ( Parameter1 , Parameter2 , Parameter3 , Parameter4 ) MEMORY_MANAGEMENT
Cause of Issue 1This issue occurs because of a known erratum of the Intel code-named Nehalem processors.
The known erratum creates some spurious interrupts. Therefore, you receive the Stop code error that is mentioned in the "Symptoms" section.
For more information about the known erratum, see the following Intel documents:
Intel Xeon Processor 5500 Series Specification Update, July 2010
Intel Core i7-800 and Intel Core i5-700 Desktop Processor Series Specification Update, July 2010
Cause of Issue 2This issue occurs because of a race condition in the hypervisor.
Cause of Issue 3This issue occurs because the hypervisor does not handle the caching from the Virtual Machine Control Block (VMCB) feature correctly. Therefore, some memory is corrupted, and the Stop error occurs.
Note The new VMCB feature of the Intel Westmere processors increases the performance of the hypervisor by improving virtualization. However, the VMCB feature was introduced after Windows Server 2008 Service Pack 2 (SP2) and Windows 2008 R2 were released. Therefore, this issue occurs.
How to obtain this updateThis update is available from the Microsoft Update website:
http://update.microsoft.comNote: You can use the "Windows Update" control panel applet to download the hotfix package in Windows Server 2008 R2.
PrerequisitesTo apply this update, you must be running Windows Server 2008 R2. Additionally, you must have the Hyper-V role installed on the computer.
Restart requirementYou must restart the computer after you apply this update.
Update replacement informationThis update replaces the hotfixes that are described in the Microsoft Knowledge Base articles 975530, 974909, and 981791.
File informationThe global version of this update installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notesImportant
For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
Workaround of Issue 1To work around issue 1, disable the Advance Configuration and Power Interface (ACPI) C-states by using a BIOS firmware option on the computer.
If the BIOS firmware does not include an option to disable the ACPI C-states, disable the ACPI C2-state and ACPI C3-state by setting a registry key. To do this, follow these steps:
To continue to benefit from these energy saving states, remove the registry key after you install this hotfix. To remove this registry key, follow these steps:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
975530For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/975530/ )Stop error message on an Intel Xeon 5500 series processor-based computer that is running Windows Server 2008 R2 and that has the Hyper-V role installed: "0x00000101 - CLOCK_WATCHDOG_TIMEOUT"
974909For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/974909/ )The network connection of a running Hyper-V virtual machine is lost under heavy outgoing network traffic on a Windows Server 2008 R2-based computer
981791For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/981791/LN/ )"STOP: 0x0000001a" error message on a computer that has an Intel Westmere processor together with the Hyper-V role installed on Windows Server 2008 or on Windows Server 2008 R2
824684The Intel Westmere processor has a microarchitecture that is a 32-nanometer (nm) variant of the Nehalem microarchitecture. The models of the Intel Westmere processor that are affected by this issue include the Xeon Processor 5600 series.
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
For more information about the Xeon Processor 5600 series, visit the following website:
General information about the Intel Xeon Processor 5600 seriesThe 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.
Additional file information
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
Article ID: 2264080 - Last Review: November 22, 2010 - Revision: 2.1