over overclocked

  • Thread starter Thread starter eng
  • Start date Start date
E

eng

i'm experimenting with simple overclocking by increasing FSB. what are the
problems assosiated with pushing FSB too far? excessive heat causing
un-commanded reboots, windows BSOD, what else? any chance of permanent
damage to the processor or RAM? TIA
 
i'm experimenting with simple overclocking by increasing FSB. what are the
problems assosiated with pushing FSB too far? excessive heat causing
un-commanded reboots, windows BSOD, what else? any chance of permanent
damage to the processor or RAM? TIA
Click to expand...
All the above.
 
I believe the worst and most likely problem is HD data corruption,
loss of important irreplaceable data. If you overclock in small
steps, you will find the point where stability is lost. The best
advice is perform testing with floppy boot disk programs to test out
basic system stability b4 booting windows or Linux and allowing the
CPU an opportunity to write to your hard disk during a faulty OC
operational state.

--
Best regards,
Kyle
| i'm experimenting with simple overclocking by increasing FSB. what
are the
| problems assosiated with pushing FSB too far? excessive heat causing
| un-commanded reboots, windows BSOD, what else? any chance of
permanent
| damage to the processor or RAM? TIA
|
|
 
If you use the machine mainly for playing games, I'd risk pushing it a bit.
If it is for office use, why risk having the aggravation? I'm in charge of
over 60 PCs where I work, mostly ASUS based systems (hmmm, who would have
influenced that???) We are an engineering firm and use AutoCAD with huge 3D
models (among other things). The software crashes enough on its own!
bg
 
i'm experimenting with simple overclocking by increasing FSB. what are the
problems assosiated with pushing FSB too far? excessive heat causing
un-commanded reboots, windows BSOD, what else? any chance of permanent
damage to the processor or RAM? TIA
Click to expand...

It depends on which motherboard it is. Many modern boards for both
Intel and AMD offers to lock pci and agp speed. Thereby is limited a
great deal of the problems.

Then overclocking the fsb involves just the cpu and ram. Ram will just
fail if it comes too high. No damage.

A hardware monitor program is suited for overviewing the cpu
temperature, and alarm adjustment. Normally also the motherboards bios
offers a shutdown temperature.

Actually ram mis-performance is the hardest to work with. So it could
be very wise to buy some very well-recommended and fast ram.

PSU is also critical. If it cannot deliver the needed power that will
give the same unpredictable kind of errors just like the ram.

But really then: no risk

(I have never blown a motherboard or a cpu because of OC, and I run
with a 50% overclocked amd 1700+ cpu)

best regards

John
 
I believe the worst and most likely problem is HD data corruption,
loss of important irreplaceable data. If you overclock in small
steps, you will find the point where stability is lost. The best
advice is perform testing with floppy boot disk programs to test out
basic system stability b4 booting windows or Linux and allowing the
CPU an opportunity to write to your hard disk during a faulty OC
operational state.
Click to expand...

No, data corruption isn't a big risk. The only data corruption problem
I've read about on overclockers.com is a result of bad implementation
of Raid on the early A7N8X DX bios. Modern motherboards allow you to
lock the PCI bus speed (and AGP) so the drives don't run over spec.

But insufficient cooling will fry your CPU. Again, current CPU/MB
combinations shut down or at least throttle back when heat gets to
dangerous levels so even that is less likely than before.

You can get data corruption if you get a BSOD while writing to a drive
of course. If stuff is irreplaceable (it should be backed up) then
don't push it. Reasonable OC is ok. Pushing it to get every last FPS
out of Unreal or something is an iffy proposition.
 
JK said:
It depends on which motherboard it is. Many modern boards for both
Intel and AMD offers to lock pci and agp speed. Thereby is limited a
great deal of the problems.

Then overclocking the fsb involves just the cpu and ram. Ram will just
fail if it comes too high. No damage.

A hardware monitor program is suited for overviewing the cpu
temperature, and alarm adjustment. Normally also the motherboards bios
offers a shutdown temperature.

Actually ram mis-performance is the hardest to work with. So it could
be very wise to buy some very well-recommended and fast ram.

PSU is also critical. If it cannot deliver the needed power that will
give the same unpredictable kind of errors just like the ram.

But really then: no risk

(I have never blown a motherboard or a cpu because of OC, and I run
with a 50% overclocked amd 1700+ cpu)

best regards

John
Click to expand...


"But really then: no risk"
John



Oh not true. When you overclock the CPU and MEM, errors in computation
occur even if no instability appears to exist. If the CPU happens to
write that data back to the HD, you could have serious problems. If
the NTLDR file is corrupt, or any other important sys file, you may
not be able to ever boot the OS again until a complete re-install. You
can also DEFINETlY fry the CPU or MEM by overvolting, but if you are
just oncreasing the FSB wothout overvolting, then you drastically
reduce the chance of disaster. Trust me, I've lost more than a couple
of installs in the fun of OC'ing;. These systems were not mission
critical and there was nothing on it I didn't mind losing, but DMAN I
hate having to reinstall the OS. Takes too long with the SP and the
updatees. UGH!!!
Just take it slow and don't push the voltage too much. if you do, go
slowly and only in .25 increments up to maybe a full 1.0 volt more
than your default. You should be safe, but I refuse to be held
responsible for any damage. Tkae it up with Bill G. Just kidding. But
do be careful.
 
Back
Top