I blame XAML, and I'm justified. Some of my teammates here have changed Visual Studio to open XAML files with the XML editor, which means * Visual Studio no longer crashes all the time, and * they lose all XAML intellisense.

I choose to keep the XAML editor for its usefulness, but I run Task Manager (well, Process Explorer) open in the tray at all times to monitor my CPU. If your CPU spikes while you're doing nothing, it's a good sign that Visual Studio may crash.

And as everyone else says, it's rock-solid while doing web development or anything not involving XAML.