I noticed I hadn’t done a good job blogging about 2 patches that MS has released since the RTM of Windows Server 2008 R2 Hyper-V. Both are pretty important and I was peeved I couldn’t find them on my own blog (my virtual notebook). This blog post should rectify that.
KB974598 – You receive a "Stop 0x0000007E" error on the first restart after you enable Hyper-V on a Windows Server 2008 R2-based computer
Assume that you enable the Hyper-V role on a computer that is running Windows Server 2008 R2. You restart the computer after you enable the Hyper-V role. However, you receive the following Stop error message during the restart operation:
Stop 0x0000007E (ffffffffc0000096, parameter2, parameter3, parameter4) SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
This problem occurs because the system uses a C-state that is supported by the processor. However, the C-state is not supported by Hyper-V.
Fix: To resolve this problem, follow these steps:
- Disable Processor Virtualization in the BIOS.
- Start the computer normally.
- Apply this hotfix and then restart the computer.
My note: I suspect MS forgot to mention re-enabling Processor Virtualisation in the BIOS. Otherwise the Hyper-V role will fail to start during boot up.
Workaround: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base.
To work around this problem, follow these steps:
- Disable Processor Virtualization in the BIOS.
- Start the computer normally.
- Open an elevated command prompt, and then run the following command: reg add HKLMSystemCurrentControlSetControlProcessor /v Capabilities /t REG_DWORD /d 0x0007E06
- Restart the computer.
This workaround adds a registry entry that disables the C2 state and the C3 state.
KB975530 – 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"
Consider the following scenario:
A computer is running Windows Server 2008 R2 and has the Hyper-V role installed. This computer has one or more Intel Xeon processors (code-named Nehalem) of the 5500 series installed.
In this scenario, you receive the following Stop error message:
0x00000101 (parameter1, 0000000000000000, parameter3, 000000000000000c) CLOCK_WATCHDOG_TIMEOUT
This problem occurs because spurious interrupts are generated on the computer that uses Intel Xeon 5500 series processors. These interrupts are caused by a known erratum that is described in the Intel document number 321324. To view this Intel document, click the following link.
Microsoft 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.
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 Microsoft Web site.
Note: 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.
For more information about how to install the Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base.
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 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.
Windows Server 2008 R2 file information note
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately. 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 (attributes 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.20527 | 643,072 | 15-Sep-2009 | 02:29 | x64 |
| Hvboot.sys | 6.1.7600.16385 | 118,864 | 14-Jul-2009 | 01:48 | x64 |
| Hvix64.exe | 6.1.7600.20527 | 707,072 | 15-Sep-2009 | 02:29 | x64 |