You are currently offline, waiting for your internet to reconnect

FIX: After an AppDomain Unload, the ASP.NET Worker Process Uses 100 Percent of the CPU

This article has been archived. It is offered "as is" and will no longer be updated.
Under moderate to heavy load, if an AppDomain unload occurs, the ASP.NET Worker Process (Aspnet_wp.exe) may use 100 percent of the CPU on a single-processor computer. When this problem occurs on a multiprocessor computer, the Aspnet_wp.exe process uses 100 percent of one of the processors.
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The P1 version of this fix has the file attributes (or later) 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 tool in Control Panel.
   Date         Time   Version       Size       File name   --------------------------------------------------------------   23-Jan-2003  17:41  1.0.3705.398    196,608  Aspnet_isapi.dll   23-Jan-2003  17:35                    4,169  Aspnet_perf.h   23-Jan-2003  17:35                   20,468  Aspnet_perf.ini   23-Jan-2003  17:35                   20,342  Aspnet_perf2.ini   23-Jan-2003  17:41  1.0.3705.398     24,576  Aspnet_regiis.exe   23-Jan-2003  17:41  1.0.3705.398     28,672  Aspnet_wp.exe   23-Jan-2003  17:03  1.0.3705.398     69,632  Corperfmonext.dll   23-Jan-2003  17:01  1.0.3705.398    303,104  Mscorjit.dll   24-Jan-2003  04:40  1.0.3705.398  1,953,792  Mscorlib.dll   21-Jan-2003  14:55                   10,284  Mscorlib.ldo   23-Jan-2003  17:02  1.0.3705.398  2,269,184  Mscorsvr.dll   23-Jan-2003  17:01  1.0.3705.398  2,269,184  Mscorwks.dll   01-Aug-2002  14:38                       15  Smartnav.htm   17-Oct-2002  10:55                    8,728  Smartnav.js   24-Jan-2003  04:42  1.0.3705.398  1,191,936  System.web.dll

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 810280 - Last Review: 02/27/2014 18:42:56 - Revision: 1.6

Microsoft .NET Framework 1.0, Microsoft ASP.NET 1.0

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbhttpruntime kbnetframe100presp3fix kbfix kbbug KB810280