public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Overclocking CPU causes segmentation fault
Date: Wed, 23 Jan 2013 16:22:03 +0200	[thread overview]
Message-ID: <kdormv$4bk$1@ger.gmane.org> (raw)
In-Reply-To: <50FFD2EB.9030402@gmail.com>

On 23/01/13 14:09, Dale wrote:
> Nikos Chantziaras wrote:
>> On 23/01/13 03:55, Dale wrote:
>>> [...]
>>> I tired overclocking once a good while back.  It just wasn't worth it.
>>
>> I've been running a Core 2 Duo from 2.4Ghz to 3.4Ghz for over three
>> years.  Instead of a new CPU, I only bought a €30 cooler.
>>
>> Oh, it *was* totally worth it.  Mainly for games, where the
>> performance difference was really dramatic.
>>
>
> I doubt most get that lucky tho.  After all, overclocking is mostly
> luck.  Some CPU's won't overclock that much long term because of either
> the CPU itself or some other component that can't handle the increase.
> When you overclock, you are searching for that weak link.  Most of the
> time, you find that weak link.

In my experience, most of the time you can overclock.  The issue is with 
the user not knowing exactly how to do it.  You need to understand a few 
things and how they affect each other.  It's not just a knob you can turn.



  reply	other threads:[~2013-01-23 14:23 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 [this message]
2013-01-23 15:09             ` Nilesh Govindrajan
2013-01-23 15:35               ` Nikos Chantziaras
2013-01-23 16:22                 ` Bruce Hill
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='kdormv$4bk$1@ger.gmane.org' \
    --to=realnc@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