FIX: An application that is based on the .NET Framework 2.0 stops responding on a computer that has more than 32 processors, and the .NET Framework 2.0 Service Pack 2 or the .NET Framework 3.5 Service Pack 1 is installed
You have the Microsoft .NET Framework 2.0 Service Pack 2 (SP2) or the Microsoft .NET Framework 3.5 Service Pack 1 (SP1) installed on a computer that has more than 32 processors.
You run an application that is based on the .NET Framework 2.0.
The application calls the ThreadPool class.
The application also calls the NtGetCurrentProcessorNumber function to obtain the actual number of processors in the computer.
In this scenario, the application stops responding. If you debug the problem, you notice that a thread is waiting for a flag in the mscorwks!ThreadpoolMgr::RecycleMemory method.
This problem occurs because the maximum number of processors that the common language runtime (CLR) 2.0 can report is 32. However, when the NtGetCurrentProcessorNumber function obtains the actual number of processors in the computer, and this number is greater than 32 processors, the ThreadpoolMgr::RecycleMemory method enters an infinite loop.
To resolve this problem, apply this hotfix to the computer on which you have the .NET Framework 2.0 SP2 or the .NET Framework 3.5 SP1 installed. To work around this problem, see the "Workaround" section.
More information about this hotfix
Hotfix information
A supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Prerequisites
You must have one of the following installed to apply this hotfix:
Microsoft .NET Framework 2.0 Service Pack 2 (SP2)
Microsoft .NET Framework 3.5 Service Pack 1 (SP1)
Restart information
You may have to restart the computer after you apply this 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.
Note For additional file information, see the "More Information" section.
Windows Vista and Windows Server 2008 file information
For all supported x86-based versions of Windows Vista SP2 and Windows Server 2008 SP2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Mscorlib.dll
2.0.50727.4474
4,550,656
23-Aug- 2010
10:57
x86
Mscordacwks.dll
2.0.50727.4474
989,016
23-Aug- 2010
10:56
x86
Mscorwks.dll
2.0.50727.4474
5,819,728
23-Aug- 2010
10:57
x86
Sos.dll
2.0.50727.4474
388,936
23-Aug- 2010
10:57
x86
For all supported x64-based versions of Windows Vista SP2 and Windows Server 2008 SP2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Mscorlib.dll
2.0.50727.4474
4,567,040
23-Aug- 2010
10:56
x64
Mscordacwks.dll
2.0.50727.4474
1,758,552
23-Aug- 2010
10:56
x64
Mscorwks.dll
2.0.50727.4474
10,053,456
23-Aug- 2010
10:56
x64
Sos.dll
2.0.50727.4474
485,192
23-Aug- 2010
10:56
x64
For all supported IA-64-based versions of Windows Server 2008 SP2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Mscorlib.dll
2.0.50727.4474
4,009,984
23-Aug-2010
10:57
IA-64
Mscordacwks.dll
2.0.50727.4474
3,085,144
23-Aug-2010
10:57
IA-64
Mscorwks.dll
2.0.50727.4474
20,176,720
23-Aug-2010
10:57
IA-64
Sos.dll
2.0.50727.4474
872,776
23-Aug-2010
10:57
IA-64
Windows 7 and Windows Server 2008 R2 file information
For all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Mscorlib.dll
2.0.50727.5024
4,550,656
21-Aug-2010
00:57
x86
Mscordacwks.dll
2.0.50727.5024
995,672
21-Aug-2010
00:57
x86
Mscorwks.dll
2.0.50727.5024
5,822,800
21-Aug-2010
00:57
x86
Sos.dll
2.0.50727.5024
388,936
21-Aug-2010
00:58
x86
For all supported x64-based versions of Windows 7 and Windows Server 2008 R2
Collapse this tableExpand this table
File name
File version
File size
Date
Time
Platform
Mscorlib.dll
2.0.50727.5024
4,567,040
21-Aug-2010
00:59
x64
Mscordacwks.dll
2.0.50727.5024
1,755,480
21-Aug-2010
00:59
x64
Mscorwks.dll
2.0.50727.5024
10,042,704
21-Aug-2010
00:59
x64
Sos.dll
2.0.50727.5024
485,192
21-Aug-2010
00:59
x64
For all supported IA-64-based versions of Windows Server 2008 R2
To work around this problem, use one of the following methods.
Method 1
Upgrade the .NET Framework to Microsoft .NET Framework 4.0.
Method 2
Set the processor affinity mask to the first 32 processors by using the SetProcessAffinityMask function. For more information about the SetProcessAffinityMask function, visit the following Microsoft Developer Network (MSDN) website:
Back to the top
