I saw a very similar error with Word on a user's box at work not long ago. I assumed the problem there is a memory problem, but I've not had a chance to check yet. In his case, a reboot seemed to have "solved" the problem.