Unhandled exceptions are caught by the Visual Studio JIT debugger instead of Dr. Watson or a third-party debugger after you install certain versions of SQL Server 2005
This is how to correct it. :)
What it boils down to is disabling the debugger in Visual Studio, then re-enabling the normal windows one, Dr. Watson.
Of course, now you have to resolve the problem that caused the error in the first place, but at least you will get a regular error message and not the JIT debugger one.
