Well I did exactly what I'd done 3 months ago and found a faulty RAM chip
this time
My guess is that back then the chip was still functioning some of the time,
and happened to be fine just when I was doing the tests.
This time I found it fairly easily with a systematic approach.
--
“Don't eat anything you've ever seen advertised on TV”
- Michael Pollan, author of "In Defense of Food"
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
Re: debugging RAM issues
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: CentOS mailing list <centos@xxxxxxxxxx>
- Subject: Re: debugging RAM issues
- From: Alan McKay <alan.mckay@xxxxxxxxx>
- Date: Wed, 14 Mar 2012 14:43:19 -0400
- Delivered-to: centos@xxxxxxxxxx
- In-reply-to: <CAH8ZPG=jujTnR3CJiwDcDW-Rc14XNEXPf=Lc25YCYUTow=rkaA@mail.gmail.com>
- Follow-Ups:
- Re: debugging RAM issues
- From: Les Mikesell
- Re: debugging RAM issues
- References:
- debugging RAM issues
- From: Alan McKay
- Re: debugging RAM issues
- From: Ross Walker
- Re: debugging RAM issues
- From: Scott Silva
- Re: debugging RAM issues
- From: Alan McKay
- debugging RAM issues
- Prev by Date: Re: mkswap, lvm and bootbits sectors
- Next by Date: Re: CentOS Server Backup Options: at runlevel 5?
- Previous by thread: Re: debugging RAM issues
- Next by thread: Re: debugging RAM issues
- Index(es):
 |