No one likes to see them. They normally happen at the most incandescently infuriating time and indeed Software vendors don't like to admit that software can sometimes be...slightly less than perfect. Crashes are a fact of life and the reality is that no software is ever perfect. When you experience a crash you are normally, ungracefully dumped back to the desktop, resulting in one of these....
DONT FORGET TO ENTER YOUR EMAIL ADDRESS
All Autodesk software users acknowledge that software is not perfect by accepting the End User License Agreeement (I know you probably never read it :-) ).
However, Error Reports are a fundamental basic tool to allow all software developers to improve the quality of their products. Not only do they provide precise information as to what commands were executed and failed immediately prior to the crash, but they provide invaluable statistical information to development so they know what issues to fix first based on the numbers submitted. If they get 500 reports from one issue, they will fix that, before addressing the issue reported only 10 times. Simple.
There is a tendency to think that if you send the Error Report, it will disappear into a black hole and the issue will never get fixed. My personal experience is the complete opposite. This is true both of Autodesk products and other vendors like Microsoft. Indeed I have used an erroneous email from home (no way for anyone to tell my name or who I work for) to send an Error Report to Autodesk only to be contacted days afterwards by a QA engineer asking for more information on how to reproduce it. Other times, I have received an email back saying that the issue is fixed in a public hotfix or service pack.
So, if you experience one of the above error reports, and it occurs regularly, it really is in everyones best interests to click "Send Report" every single time.
You can view all the best and worst practice blog posts by selecting the "Best Practices" or "Worst Practices" category in the right hand column of this site.