Ok, this is the funniest error message I ever saw. I have VS 2010 up and debugging an application. I also had a .NET 2.0 site running that I shut down. There were two worker processes running on my machine. I killed various apps such as IE but they all still showed up in the task bar.

So I thought, the darn worker process must be freezing up my machine. I killed it and got the strange Zombie Message below.

I had a user control embedded in an ASPX (parent) page as a hidden layer. The control was placed inside of a panel control that was hidden. The parent page would load an show the user control

Once the user completed the work they clicked "Close Window" that would raise an event on the parent page, and  the parent page would hide the hidden layer.

1. User Control (ASCX): Add the following delegates and events

// Delegate declaration  
public delegate void OnButtonClick(string strValue);          
// Event declaration  
public event OnButtonClick btnHandlerEditAccount;

2. User Control (ASCX): Button close event will raise btnHandlerEditAccount causing the parent page to hide the panel with the user control.  

protected void BtnCloseWindow_Click(object sender, EventArgs e)
{
   //Make the parent close the window
   if (btnHandlerEditAccount != null) btnHandlerEditAccount(string.Empty);
            
}

3. Parent Page: Handles btnHandlerEditAccount from the user control.

//Event Handlers to close windows from user controls (place in Page_Load)
UCEditAccountInfo.btnHandlerEditAccount += new EditAccountInfo.OnButtonClick(UCEditAccount_btnHandler);

//Syntax of item above: UserControlName dropped on the page += new Class.NameOfActualUserControl.OnButtonClick(handler created in step 1)

/// 

/// Handle the Window Close on the Edit Account User Control
/// 
protected void UCEditAccount_btnHandler(string strValue)
{
     PnlGrid.Enabled = true;
     PnlAccountEdit.Visible = false;
     ReloadGrid(false);
}

If you ever hit the error below the first thing to check is a endless loop or a recurring call between methods. This happen in a site I was running in localhost when an exception was raise, and email was sent, that email failed raise the exception handler and attempted to email it, then on an on...

A process serving application pool suffered a fatal communication error with the Windows Process Activation Service. The process id was 5388. The data field contains the error number. A process serving application pool suffered a fatal communication error with the Windows Process Activation Service. The process id was 4228. The data field contains the error number.