0
kicks
On Diagnosing Infinite Loops with WinDBG
Imagine this scenario: With not much traffic hitting your site, the entire server has ground to a halt and the CPU is pegging at 100%. No requests are being serviced, despite IIS taking all available CPU time. What's going on? One potential issue is that you have a poorly written page or method with an infinite loop.