This event might occur when you use the Response.BinaryWrite method to download files that are 400 MB or larger from an ASP.NET page. See ME821387
to find out the cause of this problem and for a hotfix applicable to Microsoft Visual Studio .NET (2002) and ME823409
for a hotfix applicable to Microsoft Visual Studio .NET 2003.
This error occurs if the .NET runtime cannot dispose of all of the threads when the runtime tries to unload the application. See ME321564
for a hotfix applicable to Microsoft ASP.NET.
for a hotfix applicable to Microsoft Content Management Server 2002.
for a hotfix applicable to Microsoft .NET Framework 2.0.
for a hotfix applicable to Microsoft .NET Framework 1.1.
for additional information about this event.
A page I found suggested changing the responseDeadlockInterval attribute in the machine.config file from responseDeadlockInterval="00:03:00" to responseDeadlockInterval="00:10:00" which seemed to do the trick. Make sure you restart IIS after making this change.
This event also occurs if you have written an application that runs in an infinite loop. When you kill the application, you will receive this event.
Change the application setting for the website, which you will find under IIS Console. There is a button Configuration. There you will find a checkbox "Cache ISAPI Application". For asp.net this option must be enabled, otherwise you get this error.
From a newsgroup post: "My problem was an oledb driver for Sybase 7. In my case the only driver I could get to work with .Net was 18.104.22.168 patch".