From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Random reboots. Where to start?
Date: Fri, 25 Feb 2011 18:18:07 -0600 [thread overview]
Message-ID: <4D6846BF.3090802@gmail.com> (raw)
In-Reply-To: <AANLkTin6nGWbaknd__=amjswZLapaU0+RVjBHf-0atVj@mail.gmail.com>
Paul Hartman wrote:
> 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. :)
>
I figured out why it appeared not to be testing it all. I was just
checking it as I walked by and such and I guess it just happened to be
testing the first 2Gbs or so each time I walked by. I did another test
and just sat and watched a lot of it. It appears to be testing in 2Gb
chunks or something. It would test something to 2Gbs, then test 2Gbs to
4Gbs and so on. So, it was testing it all, I was just not there to see
it do it. The something in the first 2Gbs is what it needs to load the
test I guess. It was just a small amount tho.
Mine is G Skill ram. It calls for at least 1333 but I got 1600. I
usually get a little faster, in case I want to overclock a little but it
also allows for a ram that may not be quite up to speed. Plus, it was
on sale and was actually cheaper than 1333. lol That made the sale.
;-) It is DDR3 tho. It is also in ganged mode too. It is faster that
way.
I hope I don't have to swap my ram. I bought it at newegg and the
shipping would be fun I'm sure. At least I got plenty to run off of
while swapping tho.
Thanks.
Dale
:-) :-)
next prev parent reply other threads:[~2011-02-26 1:04 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
2011-02-26 0:18 ` Dale [this message]
[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=4D6846BF.3090802@gmail.com \
--to=rdalek1967@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