Charlie
Wed Oct 17 21:56:31 PDT 2007
Thanks for the support, but let's keep it professional. ;)
He's entitled to his opinion, though when he starts by saying I don't know
what I'm talking about, he's probably not going to find a whole lot of
support here.
I have overclocked. Not on any system where I actually cared about what I'm
doing with it, but a gaming box? Sure, why not? but then, I know so little
about what I'm doing that I actually think a parity bit is a good idea, and
that ECC RAM is even a better idea. One worth paying for.
--
Charlie.
http://msmvps.com/xperts64
http://mvp.support.microsoft.com/profile/charlie.russel
"Frank" <fb@osspan.clm> wrote in message
news:eIKt$%23TEIHA.4308@TK2MSFTNGP06.phx.gbl...
> Adam Albright wrote:
>
>> On Wed, 17 Oct 2007 18:30:55 -0700, "Charlie Russel - MVP"
>> <charlie@mvKILLALLSPAMMERSps.org> wrote:
>>
>>
>>>Windows doesn't care. Right up to the point where your overclocked system
>>>does something that it isn't supposed to do, because it failed. Either
>>>because of overheating or because an overclocked component produced the
>>>wrong output. Keep in mind that a single-bit error introduced by the CPU
>>>or the memory could result in a BSOD (best case) or subtle data
>>>corruption that goes unrecognized until it's too late (worst case).
>>>
>>>You can probably tell what I think of overclocking. ;)
>>
>>
>> Yep, ignorance is bliss or so they tell me. ;-)
>>
>>>You want to overclock? go for it. But _expect_ problems. And please don't
>>>report errors here that happen when the system is overclocked.
>>
>>
>> What I can tell is you don't really understand the topic. I've
>> overclocked all kinds of systems. Problems? Zero. Lets backup.
>> Introducing the CPU cycle.
>>
>> Over simplified, one key element is the fetch-decode-execute
>> instruction cycle or the time period during which one instruction is
>> retrieved from memory, by the CPU and it's supporting circuits,
>> decoded then executed. View it as similar to some real word clock. The
>> faster the clock runs, the faster time would appear to pass or in the
>> case of a CPU the faster the clock runs the quicker the CPU can
>> process instructions and obviously the faster your computer will do
>> what you ask of it. The clock frequency or how fast it oscillates
>> between two possible
>> states keeping things in sync. Depending on the instruction the CPU is
>> processing it can take multiple cycles to complete the instruction.
>> The CPU is internally aware of this. So if it has two instructions to
>> be executed and it knows that the first will delay five clock cycles
>> to be executed, it will automatically start the execution of the next
>> instruction on the 6th clock tick. Newer CPU designs allow several
>> execution units to work in parallel. So in effect modern CPU's can
>> process multiple instructions at once.
>>
>> Why overclock? Over clocking pushes the CPU to run faster because of
>> a higher clock rate that is driving it so the time it takes between
>> each cycle is shorter, thus resulting in better performance. The CPU uses
>> both and internal and external clocks. Instructions
>> internally passing through registers in the CPU itself are running at
>> a very high clock rate (internal clock) BUT data transferring to and
>> from the memory on their journey to and from the CPU is controlled by
>> the much slower North Bridge, a separate chip. This communication
>> happens over the FSB (front side bus) By bumping up how fast this bus
>> runs, data pulled from memory can flow faster. That is a nutshell (lots
>> of technical gibberish left out on purpose)
>> is basically what overclocking is all about. It is easy, safe and
>> supported by all major mother board manufactures on many of their MB
>> models and is easily altered form BIOS. If or not it is depends on
>> what you buy. Some box makers may not implement overclocking but to
>> suggest overclocking is dangerous, caused CPU's to overheat or Windows
>> or any OS to start making mistakes or corrupt data is simply
>> unfounded. Overclocking is self limited in you know you've pushed
>> things too far if the system won't boot or hangs trying. Then like I
>> said in my original post you simply back off a bit.
>
> Hey dumb-ass...Charlie is 100% correct in what he said and you're just a
> big mouth fukkin idiot. Overclocking is not for newbies and can corrupt
> your OS and installed data especially on Win OS's before Vista, like (98,
> 2K & XP). We've been oc'ing since the early '90's and are fully aware of
> the benefits and the inherent problems associated with doing it. We've
> just about done it all; dual processors, hand lapped cpu's, modified
> mobo's, cases cut to near ribbons...huge fans, wc and anything and
> everything else associated with oc'ing.
> You can easily spend more on cooling than if you simply bought a higher
> clocked cpu.
> So my advice is if you haven't ever oc'ed then don't even bother. If
> you're a veteran oc'er, then you know all too well what to expect.
> Frank