Not sure if this is the right fix? We've added this issue to our memory dump diagnostic which can confirm.
Symptoms
On a computer that is running Windows Server 2008 Service Pack 2 (SP2) or Windows Server 2008 R2 together with the Hyper-V role installed, you receive an error message that resembles the following:
STOP: 0x0000001a ( Parameter , Parameter , Parameter , Parameter ) MEMORY_MANAGEMENT
On Windows Server 2008, error messages resembling the following may also occur:
STOP: 0x00020001 (0x00000011, 0x00000000, 0x00001007, Parameter )
Cause
This problem occurs because Intel Westmere processors have a new Virtual Machine Control Structure(VMCS) caching feature. This feature is added to provide a virtualization assistance to increase the hypervisor performance. Because this feature was introduced after both Windows 2008 SP2 and Windows 2008 R2 were released, the hypervisor does not handle the VMCS caching correctly. Therefore, the system memory may be corrupted. This behavior can cause the 0x0000001a stop error.
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. The Hotfix Request form may be misleading because this fix only applies to Windows Server 2008 and Windows Server 2008 R2. For Windows Server 2008, select Windows Vista and for Windows Server 2008 R2, select Windows 7/Windows Server 2008 R2.
Prerequisites
To apply this hotfix, you must be running Windows Server 2008 SP2 or Windows Server 2008 R2 on the computer. Additionally, you must have the Hyper-V role installed on the computer. If you are experiencing this problem on Windows Server 2008 RTM, you must first upgrade to SP2, and then apply the hotfix.
Restart requirement
You must 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 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
SR_Level
Service branch
6.0.600
2. 18xxxWindows Server 2008
SP2
GDR
6.0.600
2. 22xxxWindows Server 2008
SP2
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" section. MUM files 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
File name |
File version |
File size |
Date |
Time |
Platform |
---|---|---|---|---|---|
Hvax64.exe |
6.0.6002.18242 |
651,264 |
14-Apr-2010 |
16:33 |
x64 |
Hvboot.sys |
6.0.6002.18005 |
110,056 |
11-Apr-2009 |
07:15 |
x64 |
Hvix64.exe |
6.0.6002.18242 |
672,256 |
14-Apr-2010 |
16:33 |
x64 |
Virtualization.events.xml |
Not applicable |
1,384 |
18-Feb-2009 |
18:42 |
Not applicable |
Hvax64.exe |
6.0.6002.22382 |
651,264 |
14-Apr-2010 |
16:34 |
x64 |
Hvboot.sys |
6.0.6002.22382 |
108,424 |
14-Apr-2010 |
20:14 |
x64 |
Hvix64.exe |
6.0.6002.22382 |
672,256 |
14-Apr-2010 |
16:34 |
x64 |
Virtualization.events.xml |
Not applicable |
1,384 |
03-Apr-2009 |
20:56 |
Not applicable |
Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
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.16xxxWindows Server 2008 R2
RTM
GDR
6.1.760
0.20xxxWindows 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.16573 |
643,584 |
14-Apr-2010 |
03:45 |
x64 |
Hvix64.exe |
6.1.7600.16573 |
707,072 |
14-Apr-2010 |
03:45 |
x64 |
Hvax64.exe |
6.1.7600.20691 |
643,584 |
14-Apr-2010 |
03:51 |
x64 |
Hvix64.exe |
6.1.7600.20691 |
707,072 |
14-Apr-2010 |
03:51 |
x64 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
More Information
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. Intel Westmere processor models that are affected by this issue include the Xeon Processor 5600 series. For complete details about this issue, visit the following Intel website:
Intel Xeon Processor 5000The 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
Additional files for all supported x64-based versions of Windows Server 2008 and for Windows Server 2008 R2
File name |
Amd64_0a24dc1a26b77c60407659f627d59558_31bf3856ad364e35_6.0.6002.18242_none_87fbba471cbbf825.manifest |
File version |
Not applicable |
File size |
699 |
Date (UTC) |
15-Apr-2010 |
Time (UTC) |
04:58 |
Platform |
Not applicable |
File name |
Amd64_d3eaac5b4b6d00a8d3f8a47b0e206eb6_31bf3856ad364e35_6.0.6002.22382_none_63c7551c98c30254.manifest |
File version |
Not applicable |
File size |
699 |
Date (UTC) |
15-Apr-2010 |
Time (UTC) |
04:58 |
Platform |
Not applicable |
File name |
Amd64_microsoft-hyper-v-drivers_31bf3856ad364e35_6.0.6002.18242_none_c70d9193ad18e96c.manifest |
File version |
Not applicable |
File size |
9,808 |
Date (UTC) |
15-Apr-2010 |
Time (UTC) |
04:58 |
Platform |
Not applicable |
File name |
Amd64_microsoft-hyper-v-drivers_31bf3856ad364e35_6.0.6002.22382_none_c76beeaec656f8fa.manifest |
File version |
Not applicable |
File size |
9,216 |
Date (UTC) |
14-Apr-2010 |
Time (UTC) |
21:18 |
Platform |
Not applicable |
File name |
Package_1_for_kb981791_bf~31bf3856ad364e35~amd64~~6.0.1.0.mum |
File version |
Not applicable |
File size |
2,165 |
Date (UTC) |
15-Apr-2010 |
Time (UTC) |
04:58 |
Platform |
Not applicable |
File name |
Update.mum |
File version |
Not applicable |
File size |
2,136 |
Date (UTC) |
15-Apr-2010 |
Time (UTC) |
04:58 |
Platform |
Not applicable |
Additional files for all supported x64-based versions of Windows Server 2008 R2
File name |
Amd64_3bc26dc6d3c11a97fad44b0085c1a82f_31bf3856ad364e35_6.1.7600.16573_none_651a849445808d38.manifest |
File version |
Not applicable |
File size |
710 |
Date (UTC) |
14-Apr-2010 |
Time (UTC) |
23:57 |
Platform |
Not applicable |
File name |
Amd64_b91e1af16ed3bb4a1a35404959229a50_31bf3856ad364e35_6.1.7600.20691_none_9f981d0c4f7bffc4.manifest |
File version |
Not applicable |
File size |
710 |
Date (UTC) |
14-Apr-2010 |
Time (UTC) |
23:57 |
Platform |
Not applicable |
File name |
Amd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7600.16573_none_8c4f182c7f2ffa0d.manifest |
File version |
Not applicable |
File size |
3,985 |
Date (UTC) |
14-Apr-2010 |
Time (UTC) |
23:57 |
Platform |
Not applicable |
File name |
Amd64_microsoft-hyper-v-drivers-hypervisor_31bf3856ad364e35_6.1.7600.20691_none_8cc1148b985f9f0b.manifest |
File version |
Not applicable |
File size |
3,985 |
Date (UTC) |
14-Apr-2010 |
Time (UTC) |
23:57 |
Platform |
Not applicable |
File name |
Update.mum |
File version |
Not applicable |
File size |
1,456 |
Date (UTC) |
14-Apr-2010 |
Time (UTC) |
23:57 |
Platform |
Not applicable |