Mike Tibor writes: > On Thu, 16 Jan 2003, Trevor Johnson wrote: > > > I just got a similar crash: > > > > unexpected machine check: > > > > mces = 0x1 > > vector = 0x670 > I believe a 670 machine check can also result from a read of a > non-existent I/O space. I'm not a programmer, but could that be the > problem here?
No, that's a 660. (system machine check). A 670 is much more likely to be bad ram, bad cache, bad CPU, etc. Its not always overheating. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message