title: Fastest way to break in WinDbg for specific exception? .net 4.0 app
body: <p>Folks,</p>
  
  <p>Debugging a .net 4.0 app using WinDbg (I'm a beginner to WinDbg).  I'm trying to break when I hit a stack overflow:
  (NTSTATUS) 0xc00000fd – A new guard page for the stack cannot be created</p>
  
  <p>Unfortunately, this overflow happens about 2-hours into a long-running process and logs tells me that it doesn't always happen at the same time/place.  If I attach to the process in the debugger, the program runs terribly slow...it might take a few days to hit the bug!  Is there a way to speed up the app/WinDbg by telling WinDbg to ONLY break for this particular error?</p>