Hyper-V Hotfix for "0x00000101 - CLOCK_WATCHDOG_TIMEOUT" on Nehalem systems

Hyper-V Hotfix for "0x00000101 - CLOCK_WATCHDOG_TIMEOUT" on Nehalem systems

  • Comments 27

We have just released a new hotfix for Windows Server 2008 R2 that address the issue that users were getting a bluescreen of death on Intel Xeon 5500 series processor-based computers with the following text:

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

You can download the hotfix from here: http://support.microsoft.com/kb/975530

For the curious, this issue is actually caused by a bug (or in Intel terms “erratum”) that causes these processors to generate spurious interrupts.  You can read about this in the latest Intel documentation for this process series: http://www.intel.com/assets/pdf/specupdate/321324.pdf

Cheers,
Ben

Leave a Comment
  • Please add 5 and 2 and type the answer here:
  • Post
  • Thank God! That error was stopping us from moving all 50 or so of our VMs to R2 on our new R710s.  You made my day!

  • Is this the same problem that could be avoided with the BIOS change of:

    Disable the C1E setting in the BIOS?

  • Robert -

    Yes

    Cheers,

    Ben

  • When we first saw this issue a month ago we escalated it through our MS Partner Support and Dell support and they never mentioned the CIE fix until I posted to Expert's Exchange.  Thanks for the further insight from Intel, Ben. Will this eventually get pushed as an update rather than a hotfix?

  • Is this hotfix also applicable to Hyper-V Server R2?

  • Do you know if there is a fix for the same issue on AMD Turion X2 processors?  My development laptop has been plagued by this problem for as long as I can remember, and I'd love to get that resolved.

  • Thanks for posting this.  Just had my Dell R610 with production VM bugcheck this morning.  Will be installing this tomorrow night.

  • Grant Dawson -

    I do not know what the plans are here.

    Joris -

    Yes, it is applicable to Hyper-V Server R2.

    Scott -

    No, it is not applicable there.  Note that this bug check can also be caused by problematic drivers.

    Cheers,

    Ben

  • Hello, after the installation of hotfix KB975530 there is no difference to before. We use Windows Server 2008 R2 - Cluster with role  Hyper-V and SQL Server 2008. We have the bluescreen in both combinations.

    The file versions didn't changed:

    Hvax64.exe 6.1.7600.16431

    Hvboot.sys 6.1.7600.16385

    Hvix64.exe 6.1.7600.16431

    Greetings from germany

  • I have been having the same BSOD running Hyper-V Server R2 on a R710 with dual E5520, 2.26Ghz quad core processors, and have been seeing the following output below when I analyze the dump file. I am getting a different bug check then listed in the kb article though.

    0x00000019 (0x0000000000000020, 0xfffffa8027506000, 0xfffffa8027506340, 0x000000000c340000)

    I successfully installed the hotfix a few minutes ago and rebooted, but the file versions for Hvax64.exe and Hvix64.exe both still show 6.1.7600.16431, and I do not have Hvboot.sys in my system32 directory.

    What is the ETA for a hotfix that correctly installed on Hyper-V Server R2, and any idea why my bugcheck is different?

    CLOCK_WATCHDOG_TIMEOUT (101)

    An expected clock interrupt was not received on a secondary processor in an

    MP system within the allocated interval. This indicates that the specified

    processor is hung and not processing interrupts.

    Arguments:

    Arg1: 000000000000000d, Clock interrupt time out interval in nominal clock ticks.

    Arg2: 0000000000000000, 0.

    Arg3: fffff88002064180, The PRCB address of the hung processor.

    Arg4: 0000000000000002, 0.

    Debugging Details:

    ------------------

    BUGCHECK_STR:  CLOCK_WATCHDOG_TIMEOUT_10_PROC

    DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

    PROCESS_NAME:  System

    CURRENT_IRQL:  d

    STACK_COMMAND:  kb

    SYMBOL_NAME:  ANALYSIS_INCONCLUSIVE

    FOLLOWUP_NAME:  MachineOwner

    MODULE_NAME: Unknown_Module

    IMAGE_NAME:  Unknown_Image

    DEBUG_FLR_IMAGE_TIMESTAMP:  0

    FAILURE_BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_10_PROC_ANALYSIS_INCONCLUSIVE

    BUCKET_ID:  X64_CLOCK_WATCHDOG_TIMEOUT_10_PROC_ANALYSIS_INCONCLUSIVE

  • correction, I meant to say I have gotten the same stop error 0x101 as listed in the kb article only 2 out of the last 3 blue screens. one of BSOD's generated the 0x19 I listed above.

  • Hi.

    I was testing the included Virtual PC in Windows 7 RTM. The PC is AMD Athlon 64x2 and also made a BSOD 0x101.

    Regards.

    Alex.

  • We have same problem. I hope it solves.

  • This didnt work for us.We get BSOD again in  4-5 days.

  • We hit this within 24 hours of our first build of Hyper-V Server 2008 R2 on an Intel SR1630HGP with Intel Xeon X3450 CPU.

    The hotfix went on after the blue screen which happened twice in short order.

    We shall now see if the server gets beyond the 24 hour mark without blue screening.

    http://blog.mpecsinc.ca/2009/12/hyper-v-clockwatchdogtimeout-error.html

    Philip

Page 1 of 2 (27 items) 12