A computer that is running an x64-based version of Windows Server 2008 R2 and has more than 128 processors crashes at the startup stage

Applies to: Windows Server 2008 R2 EnterpriseWindows Server 2008 R2 DatacenterWindows Server 2008 R2 Standard

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:
  • You have a computer that is running an x64-based version of Windows Server 2008 R2.
  • The computer has more than 128 processors.
  • The x2APIC mode is enabled in BIOS.
  • You try to start the computer.
In this scenario, the system crashes at the startup stage.

For example, you have a computer that has an Intel 8 socket Westmere-EX processor and can support up to 160 logical processors. After you install an x64-based version of Windows Server 2008 R2 on the computer and then try to start the computer, the startup process stops responding.

Cause


The issue occurs because Windows Server 2008 R2 uses an incorrect method to read APIC ID.

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

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2.

Registry information

To use the hotfix, you do not have to change the registry.

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 global 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
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 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 very important 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.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Ntoskrnl.exe6.1.7600.166725,507,96809-Sep-201005:45x64
Ntoskrnl.exe6.1.7600.207965,474,68809-Sep-201005:38x64
Ntkrnlpa.exe6.1.7600.166723,955,58409-Sep-201004:44Not applicable
Ntoskrnl.exe6.1.7600.166723,899,77609-Sep-201004:44Not applicable
Ntkrnlpa.exe6.1.7600.207963,964,80009-Sep-201004:33Not applicable
Ntoskrnl.exe6.1.7600.207963,909,50409-Sep-201004:33Not applicable

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 the x2APIC mode, click the following article number to view the article in the Microsoft Knowledge Base:
2303458 The "x2APIC" mode is not supported in x64-based version of Windows Server 2008 R2 systems
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 nameAmd64_081aac387ff608a023ce22ee310b6742_31bf3856ad364e35_6.1.7600.16672_none_2ef4a50cd4909ac4.manifest
File versionNot applicable
File size699
Date (UTC)09-Sep-2010
Time (UTC)08:01
PlatformNot applicable
File nameAmd64_08f8f04b2424b4dc486001d971c861e4_31bf3856ad364e35_6.1.7600.20796_none_a2932cf3d247fb9f.manifest
File versionNot applicable
File size699
Date (UTC)09-Sep-2010
Time (UTC)08:01
PlatformNot applicable
File nameAmd64_2ce4a45edade3ec809b10dd6422d5048_31bf3856ad364e35_6.1.7600.16672_none_dbb5327496fb15aa.manifest
File versionNot applicable
File size1,042
Date (UTC)09-Sep-2010
Time (UTC)08:01
PlatformNot applicable
File nameAmd64_5c68fc8e18f7bf5a774c15651c0a422e_31bf3856ad364e35_6.1.7600.16672_none_36b1063c580edbf5.manifest
File versionNot applicable
File size701
Date (UTC)09-Sep-2010
Time (UTC)08:01
PlatformNot applicable
File nameAmd64_c4e3edb86aec2b32db42118a09f0fb14_31bf3856ad364e35_6.1.7600.20796_none_d7896a6935ee6886.manifest
File versionNot applicable
File size1,042
Date (UTC)09-Sep-2010
Time (UTC)08:01
PlatformNot applicable
File nameAmd64_fa7ed43cedc97be6cfb5d70f33271140_31bf3856ad364e35_6.1.7600.20796_none_039f56f8f6f9b3b9.manifest
File versionNot applicable
File size701
Date (UTC)09-Sep-2010
Time (UTC)08:01
PlatformNot applicable
File nameAmd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.16672_none_c82d2807cdcea88e.manifest
File versionNot applicable
File size15,291
Date (UTC)09-Sep-2010
Time (UTC)06:23
PlatformNot applicable
File nameAmd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20796_none_c8a52622e6f8e596.manifest
File versionNot applicable
File size15,291
Date (UTC)09-Sep-2010
Time (UTC)06:15
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,115
Date (UTC)09-Sep-2010
Time (UTC)08:01
PlatformNot applicable
File nameX86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.16672_none_6c0e8c8415713758.manifest
File versionNot applicable
File size16,151
Date (UTC)09-Sep-2010
Time (UTC)05:13
PlatformNot applicable
File nameX86_microsoft-windows-os-kernel_31bf3856ad364e35_6.1.7600.20796_none_6c868a9f2e9b7460.manifest
File versionNot applicable
File size16,151
Date (UTC)09-Sep-2010
Time (UTC)05:02
PlatformNot applicable