Microsoft KB Archive Search

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.

  1. Home
  2. An update rollup package for the Hyper-V role in Windows Server 2008 R2: August 24, 2010

An update rollup package for the Hyper-V role in Windows Server 2008 R2: August 24, 2010

View products that this article applies to.

Symptoms

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 1

When a computer has one or more Intel CPUs code-named Nehalem installed, you receive the following Stop error message:
0x00000101 ( parameter1 , 0000000000000000, parameter3 , 000000000000000c) CLOCK_WATCHDOG_TIMEOUT
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.

Issue 2

Consider the following scenario:
  • You run a virtual machine (VM) on the computer.
  • You use a network adapter on the VM to access a network.
  • You establish many concurrent network connections. Or, there is heavy outgoing network traffic.
In this scenario, the network connection on the VM may be lost. Additionally, the network adapter is disabled.

Note You have to restart the VM to recover from this issue.

Issue 3

When a computer has an Intel Westmere processor, you receive an error message that resembles the following:
STOP: 0x0000001a ( Parameter1 , Parameter2 , Parameter3 , Parameter4 ) MEMORY_MANAGEMENT

↑ Back to the top

Cause

Cause of Issue 1

This 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 2

This issue occurs because of a race condition in the hypervisor.

Cause of Issue 3

This 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.

↑ Back to the top

Resolution

Update information

How to obtain this update

This update is available from the Microsoft Update website:
http://update.microsoft.com

Note: You can use the "Windows Update" control panel applet to download the hotfix package in Windows Server 2008 R2.

Prerequisites

To apply this update, you must be running Windows Server 2008 R2. Additionally, you must have the Hyper-V role installed on the computer.

Restart requirement

You must restart the computer after you apply this update.

Update replacement information

This update replaces the hotfixes that are described in the Microsoft Knowledge Base articles 975530, 974909, and 981791.

File information

The 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 notes
Important
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Hvax64.exe6.1.7600.16622643,07225-Jun-201004:48x64
Hvboot.sys6.1.7600.16385118,86414-Jul-200901:48x64
Hvix64.exe6.1.7600.16622699,39225-Jun-201004:48x64
Hvax64.exe6.1.7600.20742643,07224-Jun-201008:52x64
Hvboot.sys6.1.7600.20742118,65624-Jun-201012:13x64
Hvix64.exe6.1.7600.20742699,39224-Jun-201008:52x64

↑ Back to the top

Workaround

Workaround of Issue 1

To 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:
  1. At a command prompt, type the following command, and then press Enter:
    reg add HKLM\System\CurrentControlSet\Control\Processor /v Capabilities /t REG_DWORD /d 0x0007e066
  2. Restart the computer.
Note If you disable the ACPI C-states, the computer idle power consumption increases significantly. Windows Server 2008 R2 uses these deeper C-states on the Xeon 5500 series as a key energy saving feature.

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:
  1. At a command prompt, type the following command, and then press Enter:
    reg delete HKLM\System\CurrentControlSet\Control\Processor /v Capabilities /f
  2. Restart the computer.

↑ 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

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
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"
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
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
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981791
"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
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

The 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.

For more information about the Xeon Processor 5600 series, visit the following website:
General information about the Intel Xeon Processor 5600 series
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.

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_0bee55f7ac1209d39f01fa922c89010b_31bf3856ad364e35_6.1.7600.20742_none_e0ea7884a932c503.manifest
File versionNot applicable
File size710
Date (UTC)25-Jun-2010
Time (UTC)21:12
PlatformNot applicable
File nameAmd64_2ae933757785df4976ffe8a8b8cf2eca_31bf3856ad364e35_6.1.7600.16622_none_91a6a84af857324c.manifest
File versionNot applicable
File size710
Date (UTC)25-Jun-2010
Time (UTC)21:12
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7600.16622_none_8c8429647f085228.manifest
File versionNot applicable
File size3,985
Date (UTC)25-Jun-2010
Time (UTC)21:12
PlatformNot applicable
File nameAmd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7600.20742_none_8cf82657983629d4.manifest
File versionNot applicable
File size4,163
Date (UTC)24-Jun-2010
Time (UTC)16:11
PlatformNot applicable
File namePackage_1_for_kb2264080_bf~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot applicable
File size1,791
Date (UTC)25-Jun-2010
Time (UTC)21:12
PlatformNot applicable
File namePackage_1_for_kb2264080~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot applicable
File size2,508
Date (UTC)25-Jun-2010
Time (UTC)21:12
PlatformNot applicable
File namePackage_for_kb2264080_rtm_bf~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot applicable
File size1,442
Date (UTC)25-Jun-2010
Time (UTC)21:12
PlatformNot applicable
File namePackage_for_kb2264080_rtm~31bf3856ad364e35~amd64~~6.1.1.0.mum
File versionNot applicable
File size1,461
Date (UTC)25-Jun-2010
Time (UTC)21:12
PlatformNot applicable
File nameUpdate-bf.mum
File versionNot applicable
File size1,440
Date (UTC)25-Jun-2010
Time (UTC)21:12
PlatformNot applicable

↑ Back to the top

Keywords: kb, kbhyperv, kbqfe, kbfix, kbsurveynew, kbexpertiseadvanced, atdownload

↑ Back to the top

Article Info
Article ID : 2264080
Revision : 1
Created on : 1/7/2017
Published on : 11/22/2010
Exists online : False
Views : 524