I did see this error a lot on my 750 running 4.2bsd and never did manage to a) fix it or b) isolate it..... but for what it is worth, it did disappear when I did bring up 4.3....sorry I can't help more.. -ed