The ASP.NET worker process stops responding because of a corrupted overlapped structure

Retired KB Content Disclaimer

View products that this article applies to.

Expand all | Collapse all

SYMPTOMS

The Microsoft ASP.NET worker process stops responding, or "hangs," and when you use a debugger such as the Windbg debugger to examine a user dump that was taken at the moment that the process stopped responding, many of the threads appear to be waiting on a critical section as shown in the following stack:

ChildEBP RetAddr  Args to Child              
1f01fd8c 77f85c55 00001230 00000000 00000000 ntdll!NtWaitForSingleObject+0xb
1f01fe00 77f85bd1 00141200 791b1844 00141288 ntdll!RtlpWaitForCriticalSection+0x9e
1f01fe08 791b1844 00141288 1f01fe2c 791c526e ntdll!RtlEnterCriticalSection+0x46
1f01fe14 791c526e 00141288 00000001 16c40848 mscorsvr!EE_EnterCriticalSection+0xc
1f01fe2c 791d8243 77e885e0 16c40848 77e876a1 mscorsvr!BaseCrst::Enter+0x98
1f01fe44 792077f5 00000000 00000001 16c40848 mscorsvr!ThreadStore::LockThreadStore+0xaa
1f01fe58 791c5c8e 16c40848 00000000 00000000 mscorsvr!ThreadStore::AddThread+0xd
1f01fe80 791cfb76 169f9db0 1f01ff40 791cfc92 mscorsvr!SetupThread+0x103
1f01fe8c 791cfc92 00000000 169f9db0 169f9db0 mscorsvr!SetupThreadPoolThread+0x15
1f01ff40 791cfc78 1476e808 00000001 00000001 mscorsvr!AddTimerCallbackEx+0x16
1f01ff54 791cfc4f 1476e808 00000001 791cfc40 mscorsvr!AddTimerCallback+0x10
1f01ff68 791c8712 169f9db0 14798ef8 793ac240 mscorsvr!ThreadpoolMgr::AsyncTimerCallbackCompletion+0xf
1f01ff98 79208ef6 14798ef8 0005ab25 1395dcff mscorsvr!ThreadpoolMgr::ExecuteWorkRequest+0x42
1f01ffb4 77e887dd 00000000 0005ab25 1395dcff mscorsvr!ThreadpoolMgr::WorkerThreadStart+0xc6
1f01ffec 00000000 79208e96 00000000 00000000 kernel32!BaseThreadStart+0x52

The thread that owns the critical section has the following stack:

ChildEBP RetAddr  Args to Child              
1a6ce64c 77e87ab7 00000001 1a6ce674 00000001 ntdll!NtWaitForMultipleObjects+0xb
1a6ce69c 77e8a31d 1a6ce674 00000001 00000000 kernel32!WaitForMultipleObjectsEx+0xea
1a6ce6b4 7922c01b 00000001 1a6ce7d8 00000000 kernel32!WaitForMultipleObjects+0x17
1a6ce8ec 7922bf00 00000001 160efe18 00000014 mscorsvr!Thread::SysSuspendForGC+0x189
1a6ce904 7922f72a 00000001 160efe18 00000014 mscorsvr!GCHeap::SuspendEE+0xd5
1a6ce918 791b3cd6 00000000 00000000 160efe18 mscorsvr!GCHeap::GarbageCollectGeneration+0xc
1a6ce940 791bae02 160efe18 00000014 79b50e24 mscorsvr!gc_heap::allocate_more_space+0x132
1a6ce964 791bad6f 160efe18 00000014 00000002 mscorsvr!GCHeap::Alloc+0x69
1a6ce978 791d0746 00000014 00000000 00040000 mscorsvr!Alloc+0x3a
1a6ce998 791d0797 79b50e24 1a6ceab8 09441894 mscorsvr!FastAllocateObject+0x25

This thread is waiting for all the threads to suspend work to start the GC but it hangs there forever (until the process recycles)

A thread exists that has not enabled garbage collection and it has the following stack:

ChildEBP RetAddr  Args to Child              
165bf7ac 77ebb04d d0000144 00000004 00000000 ntdll!ZwRaiseHardError+0xb
165bfac8 77ea8e90 165bfaf0 77ea18a5 165bfaf8 kernel32!UnhandledExceptionFilter+0x1d6
165bffec 00000000 79200971 00000000 00000000 kernel32!BaseThreadStart+0x65

The exception stack trace looks like the following:

ChildEBP RetAddr  Args to Child              
165bfea4 791c333a ffffffff 165bff6c 792f395b mscorsvr!ArrayList::GetPtr+0xf
165bfeb0 792f395b 00000000 77e873b2 793ac43c mscorsvr!SystemDomain::GetAppDomainAtId+0x12 
165bff6c 792f3caf 00000000 00000000 16ba3fa0 mscorsvr!BindIoCompletionCallbackStubEx+0x47 
165bff84 792009dd 00000000 00000000 16ba3fa0 mscorsvr!BindIoCompletionCallbackStub+0x13 
165bffb4 77e887dd 00000000 00000003 00000000 mscorsvr!ThreadpoolMgr::CompletionPortThreadStart+0x93 
165bffec 00000000 79200971 00000000 00000000 kernel32!BaseThreadStart+0x52

The ASP.NET worker process stops responding because the completion port receives a corrupted overlapped structure.

Back to the top

RESOLUTION

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it 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 Microsoft .NET Framework service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)

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.

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 tool in Control Panel.

   Date         Time   Version       Size       File name          Platform
   ------------------------------------------------------------------------
   12-Aug-2003  16:17  1.0.3705.449    200,704  Aspnet_isapi.dll   x86
   12-Aug-2003  16:11                    4,169  Aspnet_perf.h
   12-Aug-2003  16:18                  513,302  Aspnet_perf.ini
   12-Aug-2003  16:18                  510,714  Aspnet_perf2.ini
   12-Aug-2003  16:18  1.0.3705.449     24,576  Aspnet_regiis.exe  x86
   12-Aug-2003  16:18  1.0.3705.449     28,672  Aspnet_wp.exe      x86
   12-Aug-2003  15:40  1.0.3705.449     69,632  Corperfmonext.dll  x86
   12-Aug-2003  15:38  1.0.3705.449    303,104  Mscorjit.dll       x86
   13-Aug-2003  00:09  1.0.3705.449  1,953,792  Mscorlib.dll       x86
   12-Aug-2003  15:31                   10,284  Mscorlib.ldo
   12-Aug-2003  15:39  1.0.3705.449  2,269,184  Mscorsvr.dll       x86
   12-Aug-2003  15:39  1.0.3705.449  2,269,184  Mscorwks.dll       x86
   01-Aug-2002  21:38                       15  Smartnav.htm
   29-Jul-2003  20:30                    8,728  Smartnav.js
   13-Aug-2003  00:07  1.0.3705.449  1,196,032  System.web.dll     x86
   13-Aug-2003  00:07  1.0.3705.449     32,768  Tlbimp.exe         x86

Back to the top

STATUS

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

Back to the top

APPLIES TO

Microsoft .NET Framework 1.0 Service Pack 2

Back to the top

kbhotfixserver kbqfe kbhotfixserver kbqfe kbnetframe100presp3fix kbfix kbbug KB825076

Back to the top

Retired KB Content Disclaimer

This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.

Back to the top