Sign in with Microsoft
Sign in or create an account.
Hello,
Select a different account.
You have multiple accounts
Choose the account you want to sign in with.

Summary

This article provides a fix for an issue in which computers that use AMD central processing units hang or restart during the Hyper-V Live Migration process. This issue is caused by caused by AMD erratum 383. For detailed information, see the “Symptoms,” “Cause,” and “Resolution” sections of this article.

To download the fix for this issue, click the View and request hotfix downloads link that is located on the upper-left of the screen.

Symptoms

When you run Windows Server 2008 R2 Hyper-V on a computer that uses AMD Family 10h central processing units (CPUs), the host computer may restart or stop responding unexpectedly. When this issue occurs, you receive no error messages.

This issue may occur when the Live Migration feature is used to move a virtual machine (VM) from one Windows Server 2008 R2 Hyper-V-based node to another node. This problem usually affects the source node that is the original location of the VM and usually does not affect the target node that is the new location where the VM will be moved.

Note This issue may occur in other scenarios and does not occur only in Live Migration scenarios.

Cause

This issue occurs because of erratum 383 in AMD Family 10h processors. This erratum generates a machine check exception. This machine check exception causes the hardware to restart or to stop responding.

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:

http://support.microsoft.com/contactus/?ws=supportNote 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, your computer must be running Windows Server 2008 R2.

Restart requirement

You may 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 (United States) version of this hotfix 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


  • 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.1.760
    0.16xxx

    Windows Server 2008 R2

    RTM

    GDR

    6.1.760
    0.20xxx

    Windows Server 2008 R2

    RTM

    LDR

  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.

  • 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 name

File version

File size

Date

Time

Platform

Hvax64.exe

6.1.7600.16561

643,584

27-Mar-2010

02:26

x64

Hvix64.exe

6.1.7600.16561

707,072

27-Mar-2010

02:26

x64

Hvax64.exe

6.1.7600.20678

643,584

27-Mar-2010

02:26

x64

Hvix64.exe

6.1.7600.20678

707,072

27-Mar-2010

02:26

x64

Status

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

More Information

More information about erratum 383 in AMD Family 10h processors, see the following document:

The revision guide for AMD Family 10h processorsMicrosoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.


As documented in the revision guide for AMD Family 10h processors, there is no hardware based fix for this erratum. This hotfix implements a workaround that prevents this problem from occurring on an affected processor.


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

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 name

File version

File size

Date

Time

Platform

Amd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7600.16561_none_8c57e7847f29ab6e.manifest

Not Applicable

3,985

27-Mar-2010

10:32

Not Applicable

Amd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7600.20678_none_8cddb6699849188a.manifest

Not Applicable

3,985

27-Mar-2010

10:32

Not Applicable

Package_for_kb981618_rtm_bf~31bf3856ad364e35~amd64~~6.1.1.0.mum

Not Applicable

1,436

27-Mar-2010

10:32

Not Applicable

Package_for_kb981618_rtm~31bf3856ad364e35~amd64~~6.1.1.0.mum

Not Applicable

1,455

27-Mar-2010

10:31

Not Applicable

Update-bf.mum

Not Applicable

1,434

27-Mar-2010

10:32

Not Applicable

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

Was this information helpful?

What affected your experience?
By pressing submit, your feedback will be used to improve Microsoft products and services. Your IT admin will be able to collect this data. Privacy Statement.

Thank you for your feedback!

×