🚀 go-pugleaf

On Tue, 16 Nov 1999 at 23:26:07, Anahata <anahata@freereed.demon.co.uk>
wrote in demon.tech.pc:
(Reference: <f6ps08.c43.ln@stravinsky>)

>On Tue, 16 Nov 1999 10:24:32 GMT, Michael Bungey <spam@fuelwise.clara.co.uk>
>wrote:
>
>>>
>>The problem is adequate cooling I should think... that's the only reason
>>it'd crash overclocked but not normally clocked =>  Buy a better
>>heatsink/fan =)
>
>Overheating is a separate problem.  It can be a consequence of overclocking,
>and overheating can cause errors, but that's not the only reason why an
>overclocked device goes wrong. If the logic can't respond fast enough to
>have the right data at the output when the next clock pulse arrives, there
>will be errors, simply because the internal logic can't move fast enough (at
>any temperature).
>
Well said. I was wondering when someone would try and make this point.
Overclocking might work with some components, possibly even the majority
of components. You are only guaranteed that the component you have
bought will work at the speed it is claimed to.

If you overclock, How do you know that everything will work all the
time, in all circumstances, and what certainty do you have that there
will be an error reported if anything fails to work.

Personally, although mine is a personal home system, for which I pay, I
place more reliance on my data and the results of its processing to rely
on luck in that manner. That is not, of course, a criticism of any who
do overclock, just a cautionary note to them if things go wrong - my
sympathy will not be that obvious.

-- 
John Underwood