From: Bruce Hill <daddy@happypenguincomputers.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Overclocking CPU causes segmentation fault
Date: Wed, 23 Jan 2013 10:22:08 -0600 [thread overview]
Message-ID: <20130123162208.GL30998@server> (raw)
In-Reply-To: <kdp002$h6d$1@ger.gmane.org>
On Wed, Jan 23, 2013 at 05:35:09PM +0200, Nikos Chantziaras wrote:
>
> The part that's really important is the mainboard. RAM doesn't matter.
>
> As I said above, the mainboard is really the only important factor.
Though I've not overclocked in better than a decade, I disagree with your
statement that RAM doesn't matter. Especially now, since there is a plethora
of junk RAM on the market.
Just my 2 cents.
--
Happy Penguin Computers >')
126 Fenco Drive ( \
Tupelo, MS 38801 ^^
support@happypenguincomputers.com
662-269-2706 662-205-6424
http://happypenguincomputers.com/
Don't top-post: http://en.wikipedia.org/wiki/Top_post#Top-posting
next prev parent reply other threads:[~2013-01-23 16:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 7:41 [gentoo-user] Overclocking CPU causes segmentation fault Nilesh Govindrajan
2013-01-22 9:16 ` Helmut Jarausch
2013-01-22 9:43 ` [gentoo-user] " Nikos Chantziaras
2013-01-22 11:14 ` Nilesh Govindrajan
2013-01-22 11:43 ` Nikos Chantziaras
2013-01-22 11:46 ` Nilesh Govindrajan
2013-01-22 13:49 ` Nilesh Govindrajan
2013-01-22 18:35 ` [gentoo-user] " Volker Armin Hemmann
2013-01-22 18:45 ` Nilesh Govindrajan
2013-01-23 1:55 ` Dale
2013-01-23 8:21 ` [gentoo-user] " Nikos Chantziaras
2013-01-23 12:09 ` Dale
2013-01-23 14:22 ` Nikos Chantziaras
2013-01-23 15:09 ` Nilesh Govindrajan
2013-01-23 15:35 ` Nikos Chantziaras
2013-01-23 16:22 ` Bruce Hill [this message]
2013-01-23 16:32 ` Nikos Chantziaras
2013-01-23 17:16 ` Volker Armin Hemmann
2013-01-23 17:21 ` Michael Mol
2013-01-23 18:46 ` Nikos Chantziaras
2013-01-23 17:13 ` Volker Armin Hemmann
2013-01-23 18:52 ` Nikos Chantziaras
2013-01-24 2:23 ` [gentoo-user] " Peter Humphrey
2013-01-24 4:08 ` Dale
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=20130123162208.GL30998@server \
--to=daddy@happypenguincomputers.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