Consider the following scenario:
-
You install some Intel Westmere processors on a computer that is running Windows Server 2008.
-
The computer has more than 64 processors. For example, the computer has 8 10-core Intel Westmere processors.
-
You try to shut down the computer.
In this scenario, you receive an error message that resembles the following during the shutdown process:
STOP: 0x0000000A (parameter1, parameter2, parameter3, parameter4)
IRQL_NOT_LESS_OR_EQUAL
Notes
-
The parameters in this Stop error message vary, depending on the configuration of the computer.
-
Not all "0x0000000A" Stop errors are caused by this problem.
現象
This issue occurs because of a calculation error in the processor selection function. This causes Windows to schedule a thread on a processor that does not exist. Therefore, you receive this Stop error message that described in the "Symptoms" section.
原因
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.
Prerequisites
To apply this hotfix, you must be running Windows Server 2008 Service Pack 2 (SP2) on the computer.For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
968849 How to obtain the latest service pack for Windows Server 2008
Registry information
To use the hotfix in this package, you do not have to make any changes to 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 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.
22xxxWindows Server 2008
SP2
LDR
-
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 |
|---|---|---|---|---|---|
|
Ntoskrnl.exe |
6.0.6002.22600 |
4,690,304 |
02-Mar-2011 |
16:32 |
x64 |
解決方法
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
状況
For more information about performance issues that occur when more than 64 logical processors are installed in Windows Server 2008 R2 or in Windows 7, click the following article number to view the article in the Microsoft Knowledge Base:
2510206 Performance issues when more than 64 logical processors are used in Windows Server 2008 R2 or in Windows 7For more information about the DNS Server service issues that occurs when more than 64 cores are used in Windows Server 2008 or in Windows Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2506969 The DNS Server service fails to start or fails to install on W2K8 or W2K8 R2 computers with 64 coresFor 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
Additional files for all supported x64-based versions of Windows Server 2008
|
File name |
Amd64_15490fe178c0e119ce0f43883c4f5e6c_31bf3856ad364e35_6.0.6002.22600_none_d0749cf59ee37310.manifest |
|
File version |
Not applicable |
|
File size |
721 |
|
Date (UTC) |
02-Mar-2011 |
|
Time (UTC) |
21:09 |
|
Platform |
Not applicable |
|
File name |
Amd64_aa7cd4cc61cde3586a1a394378e1679e_31bf3856ad364e35_6.0.6002.22600_none_93b93d63de3d2b42.manifest |
|
File version |
Not applicable |
|
File size |
701 |
|
Date (UTC) |
02-Mar-2011 |
|
Time (UTC) |
21:09 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-os-kernel_31bf3856ad364e35_6.0.6002.22600_none_cabf1b0782c461c4.manifest |
|
File version |
Not applicable |
|
File size |
16,512 |
|
Date (UTC) |
02-Mar-2011 |
|
Time (UTC) |
16:52 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-r..gistry-trustedtypes_31bf3856ad364e35_6.0.6002.22600_none_e28cb2f9fd096c5e.manifest |
|
File version |
Not applicable |
|
File size |
7,656 |
|
Date (UTC) |
02-Mar-2011 |
|
Time (UTC) |
16:47 |
|
Platform |
Not applicable |
|
File name |
Update.mum |
|
File version |
Not applicable |
|
File size |
3,305 |
|
Date (UTC) |
02-Mar-2011 |
|
Time (UTC) |
21:09 |
|
Platform |
Not applicable |
