When a Windows program crashes, Windows XP gives you the opportunity to send an error report to Microsoft. The process is called Online Crash Analysis. My advice: Do it. Here’s a perfect example of why it’s good for you and for your fellow PC users.
For years, I’ve encountered a sporadic problem with Word. The conditions that lead to the error are easy to identify, although I’ve never been able to reliably reproduce it. Basically, if I cut large blocks of text from a specific type of document (something I do fairly often when writing a book), I run a serious risk that Word will crash with an error message that points to “stamp 424d964d.” I’ve Googled the error and found that other people have it too. But I’ve never found an answer, and I’ve learned to be extra careful when doing mass cut-and-paste jobs. (The good news is that Word always recovers my documents perfectly, and I don’t lose any data – only some time as I reopen and repair each one.)
Today I encountered this error several times, and on the last time I decided to send in an error report. I’ve done this a hundred times or more before, but this time the response I got was different. After the error report finished sending, I was greeted with this Web page:

[Click image to see a larger view.]
Some engineer, using the great big bucket of error reports sent in from all sorts of people all over the world, found the problem, which turns out to be a bug in Word 2003. A fix is in the works. When the fix is ready, the Online Crash Analysis page will offer to install it for me when I bump into this error and send in a report. Imagine that!
Update: Turns out others have been talking about this lately as well. Read this, and this, and this, for instance (thanks, Nicholas). And this informative post from Chris Pratley (thanks, Zaine).