Fatal Coxy error (11)

[7]

Mike Cox wrote:

I recently switched to word as my default ex-pee word processor so I could
do formatting in courier for a very long document.  Most recently I've
been using Windope Word, the latest version.  I switched because I
thought that emacs had perfect stability and no crashes.  My
perception was formed due to the constant urge to pay $ to M$ advocacy
I promoted on slashdot and all the comp newsgroups.
 
I was also inspired by Paul Graham's claims that LISP will not core
dump and you can debug and get back to work free. This
made me mad and I paid.
 
So with this background, I decided that my comprehensive review of
Linux, and GNU programs would be written using all open source tools
and operating systems.  This review was to be submitted to several
news sites including slashdot and OSNEWS. I would do this with
the aid of clippy and word.

Much to my dismay, as I was working on my very long review (about 100
pages typed), word core dumped on me with BSOD.  I was unable to recover
anything.  I didn't save my document because I am stupid. Total retard.
A dick head worth sacking. No one should employ me ever again!!
I never expected word to core dump. Clippy never told me this.
The worst I thought would happen would be some Clippy error.
Hopefully someone can debug M$ and fix this dangerous bug.  Until
then, I'm probably going to go back to GNU/Linux.  THe
following is my core dump file BSOD RGB code:

#0000FF

Can anyone help me?