Forgot to mention the fact that I ran IISCrashHang debug tool for a while to see if I could isolate any templates that could be causing the issue. No luck. There was no pattern to the templates and files accessed by browsers. Which isn't nice. Taz