The problem isn't that ASP.NET is out of memory all the time on Win6... just enough to really piss you off :evil: . .NET garbage collection takes care of things so that the error will disappear, but it keeps popping up. (I could be mistaken about this, but I've seen enough of those errors that I've just given up looking into the exact error.) Pointing out the error is useless because by the time somebody gets around to checking, garbage collection will have taken care of it.
I recently got mail from Google taking my ad campains offline because the server was on error. The nature of the error is irrelevant because not working is not working.
I'm guessing that someone on Win6 is running some application that really sucks up memory really bad, and kills the rest of us. X(