From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Random reboots. Where to start?
Date: Mon, 28 Feb 2011 01:03:26 -0600 [thread overview]
Message-ID: <4D6B48BE.7000007@gmail.com> (raw)
In-Reply-To: <AANLkTimOTDh+F8KRmdw8KOt9u1ENWHoRiUAVKo41KZWm@mail.gmail.com>
Jason Weisberger wrote:
>
> I actually have 4 gigs of gskill DDR 3 1600 and from experience I can
> tell you that the stock voltage on those chips is set too low. The
> company actually recommends that you use 1.9 volts while most
> motherboards will default to 1.5 or 1.6. Double check this however,
> because I know they were working on some JEDEC compliant DDR 3
> (standard voltage of 1.5) a while back but I'm not certain if they
> just decided to throw in the towel on that effort. My system would
> crash using 1.5 but wouldn't produce any errors on memtest86+. This
> all just sounds too familiar.
>
>
I updated my kernel so I had to reboot. I checked the voltages and it
appears to be set to 1.5. It was set to auto, when I selected manual,
it said 1.5v. I don't know for sure that is what it is when it is
running tho. That could just be where it starts when in manual mode.
Since it is working now, I set it back to auto. Don't want there to be
anything, so I ain't going to start anything either. ;-) According to
gkrellm, Vcore1 is 1.39. Vcore2 is 1.52. I assume that is Vcore2.
I just bought my memory sticks in the past month or so for the last
three. The first stick I got was about 2 months ago. Maybe the new
ones are "improved" or something? How long you had yours?
Is there some way to check on BIOS settings while booted into Linux?
I'm talking about things like timings and such. I have gkrellm set up
for some stuff. Just don't see timings and such in there. Just curious
tho.
Dale
:-) :-)
next prev parent reply other threads:[~2011-02-28 7:05 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 [this message]
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
[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=4D6B48BE.7000007@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