Stop error message on a Windows Server 2008 R2-based computer that has the Hyper-V role installed and that uses one or more Intel CPUs that are code-named Nehalem: "0x00000101 - CLOCK_WATCHDOG_TIMEOUT"

Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.

Symptoms

Consider the following scenario:

  • A computer is running Windows Server 2008 R2 and has the Hyper-V role installed.

  • This computer uses one or more Intel CPUs that are code-named Nehalem. For example, the Nehalem CPU for a server is from the Intel Xeon processor 5500 series, and the Nehalem CPU for a client is from the Intel Core-i processor series.

In this scenario, you receive the following Stop error message:



0x00000101 (parameter1, 0000000000000000, parameter3, 000000000000000c)

CLOCK_WATCHDOG_TIMEOUT

Cause

This problem occurs because incorrect interrupts are generated on the computer that uses Intel processors that are code-named Nehalem. These interrupts are caused by a known erratum that is described in the following Intel documents. To view these Intel documents, click the following links:

Intel Xeon Processor 5500 Series Specification Update, September 2009
http://www.intel.com/assets/pdf/specupdate/321324.pdf

Intel Core i7-800 and Intel Core i5-700 Desktop Processor Series Specification Update, October 2009
http://download.intel.com/design/processor/specupdt/322166.pdfMicrosoft 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.

Resolution

This hotfix pertains only to computers that have Intel processors installed.

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 website:

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.

Restart requirement

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

Hotfix replacement information


This hotfix does not replace any other hotfix.

File information

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table.

Windows Server 2008 R2 file information note
  • 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, critical 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 critical to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

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.

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

643,072

13-Dec-2009

05:55

x64

Hvboot.sys

6.1.7600.16385

118,864

14-Jul-2009

01:48

x64

Hvix64.exe

6.1.7600.16485

707,072

13-Dec-2009

05:55

x64

Hvax64.exe

6.1.7600.20595

643,072

13-Dec-2009

07:08

x64

Hvboot.sys

6.1.7600.16385

118,864

14-Jul-2009

01:48

x64

Hvix64.exe

6.1.7600.20595

707,072

13-Dec-2009

07:08

x64

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_6ac22d266d67e0b790ec450bd08df4d7_31bf3856ad364e35_6.1.7600.16485_none_c7ffe3a2bc1847cd.manifest

Not Applicable

710

14-Dec-2009

09:32

Not Applicable

Amd64_82285e6be069dec1e715d87517dd0a29_31bf3856ad364e35_6.1.7600.20595_none_a9d8b55020e8f787.manifest

Not Applicable

710

14-Dec-2009

09:32

Not Applicable

Amd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7600.16485_none_8c4646ee7f364b85.manifest

Not Applicable

3,985

14-Dec-2009

09:32

Not Applicable

Amd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7600.20595_none_8cc513cd985c0740.manifest

Not Applicable

3,985

14-Dec-2009

09:32

Not Applicable

Update.mum

Not Applicable

1,456

14-Dec-2009

09:32

Not Applicable

Workaround

You can disable the Advance Configuration and Power Interface (ACPI) C-states by using a BIOS firmware option on the computer. If the firmware does not include this option, a software workaround is available. You can disable the ACPI C2-state and C3-state by setting a registry key. To do this, follow these steps:

  1. At a command prompt, run the following command:

    reg add HKLM\System\CurrentControlSet\Control\Processor /v Capabilities /t REG_DWORD /d 0x0007e066

  2. Restart the computer.

Note The computer idle power consumption will increase significantly if the deeper ACPI C-states (processor idle sleep states) are disabled. 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 that you set in step 1 after you install the hotfix that this article describes. To do remove the registry key, follow these steps:

  1. At a command prompt, run the following command:

    reg delete HKLM\System\CurrentControlSet\Control\Processor /v Capabilities /f

  2. Restart the computer.

Status

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

References

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

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×