Date: Sat, 11 Dec 2004 12:44:36 +0000 From: Elton Machado <elton.machado@norteglobal.com> To: freebsd-questions@freebsd.org Subject: Re: Is this a sign of memory going bad? Message-ID: <41BAEBB4.3000403@norteglobal.com> In-Reply-To: <20041126203138.GA21174@dogma.freebsd-uk.eu.org> References: <6FC9F9894A9F8C49A722CF9F2132FC220276581D@ms05.mailstreet2003.net> <20041125234948.R27818@april.chuckr.org> <001801c4d372$b66b3bf0$1200a8c0@gsicomp.on.ca> <20041126203138.GA21174@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
In this case I would check about the processor cooler. It could not be working fine and need some lubrification or a clean, or in worst case a new one. Regards, Elton Jonathon McKitrick wrote: >On Thu, Nov 25, 2004 at 11:45:06PM -0500, Matt Emmerton wrote: >: Given the cost of memory these days, swapping it out is generally cheaper >: than the cost of random downtime and recovering from crashes in a production >: environment. > >I am *really* not a hardware guy. I just had a box built and will deal with >hardware issues when I have to. But I did turn the box off overnight, and >the build crashes went away. > > >jm >-- >My other computer is your Windows box. >_______________________________________________ >freebsd-questions@freebsd.org mailing list >http://lists.freebsd.org/mailman/listinfo/freebsd-questions >To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41BAEBB4.3000403>