FIX: SQL Server process that uses the.NET Framework 2.0 does not make any progress during a garbage collection while CPU usage is high


Consider the following scenario:
  • A SQL Server process that uses the Microsoft .NET Framework 2.0 runs on a multiprocessor computer.
  • The garbage collection is triggered in the SQL Server process.
In this scenario, the CPU usage may increase to a high value for tens of seconds. However, the SQL Server process does not make any progress.


This issue occurs because the waiting mechanism for garbage collection does not correctly handle a scenario where the garbage collection thread and a lower priority SQL thread run on the same CPU.


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 software update 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.


To apply this hotfix, you must have the .NET Framework 3.5 Service Pack 1 (SP1) installed on a computer that is running Windows 7 or Windows Server 2008 R2. 

Note The .NET Framework 3.5 Service Pack 1 (SP1) contains the .NET Framework 2.0 Service Pack 2 (SP2).

Restart requirement

You do not have to restart the computer after you apply this hotfix if the affected files are not being used.

Hotfix replacement information

This hotfix does not replace a previously released 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.

For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2 
File nameFile versionFile sizeDateTimePlatform
Mscorlib.dll2.0.50727.56564,567,04001-Mar- 201100:45x64
Mscorwks.dll2.0.50727.56569,992,52801- Mar-201100:45x64
For all supported IA-64-based versions of Windows Server 2008 R2 
File nameFile versionFile sizeDateTimePlatform
Mscorlib.dll2.0.50727.56564,009,98401-Mar-201100:40IA- 64
Mscorwks.dll2.0.50727.565620,342,09601-Mar- 201100:40IA-64

Additional file information

Additional file information for x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_mscorlib_b77a5c561934e089_6.1.7600.20912_none_3dbc37d282d8be93.manifest
File versionNot Applicable
File size368,857
Date (UTC)01-Mar-2011
Time (UTC) 09:41
File nameAmd64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.20912_none_a12729a6c8612eeb.manifest
File versionNot Applicable
File size2,738
Date (UTC)01-Mar- 2011
Time (UTC)09:36
File nameAmd64_netfx- mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.20912_none_a86306bff0602318.manifest
File versionNot Applicable
File size6,927
Date (UTC)01-Mar-2011
Time (UTC)09:40
File nameAmd64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.20912_none_89f57167bc560b00.manifest
File versionNot Applicable
File size2,010
Date (UTC)01-Mar-2011
Time (UTC) 09:35
Additional file information for  IA-64-based versions of Windows Server 2008 R2
File nameIa64_mscorlib_b77a5c561934e089_6.1.7600.20912_none_85694c6b97551f7d.manifest
File versionNot Applicable
File size368,856
Date (UTC)01-Mar-2011
Time (UTC) 09:38
File nameIa64_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7600.20912_none_e8d43e3fdcdd8fd5.manifest
File versionNot Applicable
File size2,737
Date (UTC)01-Mar- 2011
Time (UTC)09:33
File nameIa64_netfx- mscorwks_dll_b03f5f7f11d50a3a_6.1.7600.20912_none_f0101b5904dc8402.manifest
File versionNot Applicable
File size6,926
Date (UTC)01-Mar-2011
Time (UTC)09:36
File nameIa64_netfx-sos_dll_b03f5f7f11d50a3a_6.1.7600.20912_none_d1a28600d0d26bea.manifest
File versionNot Applicable
File size2,009
Date (UTC)01-Mar-2011
Time (UTC) 09:32


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.