Buck wrote:
Yes, I described that very thing in my original note. I have
overclocked dozens of systems, some OEM, some custom built. As the OP
found out, in any OC machine, if there is any sort of unexplained error,
it's best to dial the frequency back to nominal as a diagnostic aid.
Forgive me if I misunderstood your earlier post. I thought you said the
system ran reliably until you used Firewire. That's why I responded
that Firewire is highly timing dependent and yes, overclocking can
affect it. Just as it can affect memory or graphics cards. But
typically it affects it right away, or at least reproducibly. This is
in contrast to, say, one day Word just crashes.
Are you saying the Firewire sometimes worked, sometimes didn't? Or did
it pretty consistently crash? I got the impression Firewire just plain
didn't work when you overclocked. Because I absolutely agree that you
need to make sure the rest of your hardware can handle the overclocking,
but I also have found that once you've successfully used your hardware,
the CPU doesn't usually act up later.
Anyway, if you don't want to overclock, then by all means don't. I've
got a 3GHz machine running 3GB of DDR2 at 900MHz with a 10K Raptor drive
that cost me $700 - a machine that would likely have cost closer to
$1200 on spec. It was worth the effort for me.
Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.