>This sounds suspiciously like a problem related to an ill-behaved printer driver; there's been an ongoing problem with drivers from certain manufacturers, notably HP, which do not handle the floating point/MMX registers of the CPU in a consistent and predictable fashion. The symptoms are a wide range of errors immediately following actions that invoke the printer driver, in many cases at the start of a subsequent call.

I have a hp 4000tn, found all my problems went away when I switched to the postscript driver that came with it.