From: Paul Hartman <paul.hartman+gentoo@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Random reboots. Where to start?
Date: Fri, 25 Feb 2011 12:03:48 -0600 [thread overview]
Message-ID: <AANLkTin6nGWbaknd__=amjswZLapaU0+RVjBHf-0atVj@mail.gmail.com> (raw)
In-Reply-To: <4D67CBC0.4000604@gmail.com>
On Fri, Feb 25, 2011 at 9:33 AM, Dale <rdalek1967@gmail.com> wrote:
> Well, I think my machine is possessed or something. I'm getting random
> reboots here. When it does this, it is like hitting the reset button. It
> is sitting on the grub screen when it does this. I noticed the first time
> the other day and this was before adding the extra memory. I seemed to be
> stable at 4Gbs but I seem to be rebooting at random. I ran memtest
> yesterday, it checked fine. It didn't find a error but it looked like it
> was only testing part of it. Memtest recognizes all 16Gbs on the last run
> but it didn't seem to be testing it all. Is there a trick to getting it to
> test the whole thing?
When you say "memtest" what memtest are you using, exactly? The one
from the kernel?
I prefer memtest86+ as it is updated and has support for the latest
CPUs and memory configurations. You can install it from portage and
add an entry to your Grub menu and don't need to mess with bootable CD
or USB or anything like that.
You can test specific ranges, if you suspect the new RAM is causing
trouble. Full memory testing of all patterns with 16 gigs of RAM can
take forever, but in my experience tests 5 and 8 in memtest86+ are
typically the only tests that actually produce errors on modern
systems. If you're in a hurry you can just run test 5 and that'll give
you many more passes in a shorter time. I would at least want to run
this kind of test for 12 hours with no errors before trusting the
machine. 24 or 48 hours if you can afford the wait. :)
If it does not always recognize the full 16GB i would suspect you need
to increase the voltage to your RAM. You may also (or instead) need to
reduce the memory speed.
On my previous motherboard, an Abit, with Patriot DDR2 RAM, it could
handle 4GB of RAM (2x2GB) no problems, running at recommended voltage
and full speed. When I doubled that to 8GB (4x2GB) it crashed often,
but not constantly. It could not pass an overnight memory test. I
ultimately had to raise the voltage by 0.3 and reduce the speed from
800MHz to 667MHz. I ran memtest86+ for 3 days and it had no errors.
After that it worked like a champ for 2 years, no problems.
Also, if you're using DDR3 which contains XMP data (timing and voltage
presets, basically) beware that it can sometimes be wrong. I have used
2 different brands of RAM whose XMP data did not match the values
printed on the packaging. The manufacturers both times suggested I use
what's printed on the packaging and ignore what the chip itself tells
me.
And of course on my recent Core i7 920 build, I spent a month trying
to get OCZ Gold RAM to work properly with my Gigabyte motherboard.
After 2 DOA sticks exchanged and a month of trying everything I could
possibly think of it still failed memory tests (sometimes it would
only fail after 5 or 6 hours of testing) and I gave up and returned it
to the store for a refund. I ordered some Corsair XMS3 RAM online
instead, it worked right away with the recommended settings, no
messing around, and I've been running happily ever after. :)
next prev parent reply other threads:[~2011-02-25 18:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 15:33 [gentoo-user] Random reboots. Where to start? Dale
2011-02-25 16:56 ` Helmut Jarausch
2011-02-25 23:06 ` Dale
2011-02-26 15:33 ` Yohan Pereira
2011-02-26 15:46 ` Dale
2011-02-27 17:52 ` Jason Weisberger
2011-02-27 20:12 ` Dale
2011-02-27 23:32 ` Peter Humphrey
2011-02-28 1:38 ` Dale
2011-02-28 7:03 ` Dale
2011-03-01 23:25 ` Jason Weisberger
2011-03-02 0:53 ` Dale
2011-03-02 14:15 ` Paul Hartman
2011-02-25 17:08 ` [gentoo-user] " Grant Edwards
2011-02-25 23:10 ` Dale
2011-02-26 22:20 ` walt
2011-02-26 22:40 ` Mark Knecht
2011-02-26 22:52 ` Dale
2011-02-25 17:14 ` [gentoo-user] " Mark Knecht
2011-02-25 18:03 ` Paul Hartman [this message]
2011-02-26 0:18 ` Dale
[not found] ` <4d67fbde.83a0df0a.5870.3917@mx.google.com>
2011-02-26 0:24 ` Dale
2011-02-26 9:27 ` Mick
2011-02-26 14:28 ` Dale
2011-02-27 17:15 ` [gentoo-user] " Grant Edwards
2011-02-27 19:43 ` Mick
2011-02-27 20:23 ` Dale
2011-02-27 23:34 ` Peter Humphrey
2011-03-01 23:14 ` Mick
2011-03-01 23:51 ` Peter Humphrey
2011-03-02 15:51 ` Mick
2011-03-02 16:29 ` Neil Bothwick
2011-03-02 16:37 ` Mick
2011-03-02 16:51 ` Neil Bothwick
2011-03-02 16:52 ` Alex Schuster
2011-03-02 23:52 ` Peter Humphrey
2011-02-26 16:18 ` [gentoo-user] " Volker Armin Hemmann
2011-02-27 10:02 ` Volker Armin Hemmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTin6nGWbaknd__=amjswZLapaU0+RVjBHf-0atVj@mail.gmail.com' \
--to=paul.hartman+gentoo@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox