overclocking damage hard drive?

Recently got hold of a P4 1.8A as i knew it would be great for overclocking, can run at 2.4 and beyond. Overclocked the fsb gradually from 100 mhz to 133mhz (2.4ghz) without any problems, tested fine. Restarted after the successful test at 2.4 ghz only to find that somehow my hard drive had become corrupted and wouldn't boot, had to reformat. I havn't heard of overclocking damaging a hard drive, temps were fine, the board is capable of running at 533mhz (quad pumped), is this just a bizarre coincidence?

mobo: gigabyte GA-8SIML
cpu: P4 1.8A
hdd: 40gb ibm deskstar
memory: 512mb pc3200
os: windows 2000 pro
sound: creative 5.1 player
video: 5700 le

 

Overclocking can corrupt data, Push your system too far & you might have to reinstall the OS.


Seems as though you figured that out.

 

AT one point I ran the AGP at 70mhz and PCI at 37mhz, I don’t know if that done the damage or it was pushing the fsb too high. Anyway my sound card seems to have been damaged, lots of crackling, havn’t tested my graphics yet, bit scared too.

 

Best bet if your PC can still boot is enter Bios return all setting's to stock or Default.
If you can't boot, reset CMOS this will reset MOBO to Default settings.
Then you might be able to evaluate what's working or not??


AGP should never be set over 67mhz, 66mhz is the norm, Higher than 67 should cause dammage!
PCI 33mhz

You should Read this:
http://forums.majorgeeks.com/showthread.php?t=52812














Overclocking can get expensive, How much did it cost you?
For some is best to just to buy a faster PC !

 

My system is working fine after formatting and reinstalling apart from the occasional crackling from the sound card. Tested my graphics card which seems fine phew! I have heard of high AGP or PCI settings damaging a hard drive so maybe that’s whats done it.. Although at the final setting before it crashed AGP and PCI were running at normal speeds.

 

Its all about the PCI bus...... Iv seen data curruption as low as 35MHz and iv seen a system run fine up to a 42MHz PCI bus....but when it comes down to it thare is no way to test for data curruption ( that i know of ) for all you know at 34MHz PCI your hard drive could be slowly going currupt... overclocking the PCI bus on newer systems ( 1GHz or faster) just dosent pay.... try to find a PCI lock "DIMM/PCI lock" "AGP/PCI lock" normaly its AGP/PCI lock ..try enabling that ( it will force a 33MHZ PCI bus no matter what FSB speed )..........does the mobo officialy support 133MHz FSB ??

 

Officially this is 100mhz fsb board but in one review I read the guy had it running at 138 fsb. According to Sandra maximum fsb supported is 133mhz, upgradable to 3.07 ghz. This is what I don’t get, the crash happened at 133mhz fsb when the pci was running normally at 33mhz, why would that corrupt the hard drive? I had the pci running out of spec at 124mhz and maybe again at 127mhz, could the corruption have happened then and not actually have kicked in until later, doesn’t seem plausible.

 

Yes and thats prolly the case.....iv seen systems run fine for weeks befor thay start getting sighns of data curruption ....and iv seen systems run over a 36MHZ PCI bus just long enough to get into windows and reboot and then run stock 33PCI only to find that a fue days later it wont boot due to data curruption...data curruption caused by OCing the PCI bus is a realy random thing....

 

Okay, thanks. I really wasn't happy about running the pci at 37mhz, shoud've just bypassed 124 and 127mhz. I'll try running it again at 133mhz and see what happens. Wish me luck.

 

Data corruption can also be caused by overclocking the cpu and memory,nearly any compnent that is overclocked can cause it,regular programs wont detect it,thats why you must run a program like prime for hours to be sure your safe I recently entered an overclocking competition in which I pushed my comp to the limit,my board has a pci/sata/ide lock but I still managed to corrupt the HD,the comp would fail prime in 5 secs! but still managed to get through all of crystal marks tests for the competition,after 2 weeks of running my memory at 227mhz and cpu at 2.73 and continuously benching the comp finally failed to boot locking up about 3 secs into windows loading at stock speed,I knew it would,fresh install and everythings back to normal

 

I decided to o/c it again at 133mhz meaning that the pci bus would be running normally at 33mhz but again the hard drive became corrupted, didn’t even make windows this time. So everything you’ve said is spot on, just the simple fact of overclocking your cpu too far can cause corruption, something I never knew. Guess I’ll have to stick with a safe overclock at 112mhz, at least its past 2ghz. Really disappointing considering the potential of this cpu, every o/c review I’ve read the guy has managed to run it 133mhz at stock levels with no problems whatsoever.

 

try and find out whats stopping you,download clockgen

http://www.cpuid.com/clockgen.php

get the right one for your motherboard,set everything to stock in bios then slowly start upping your fsb using clockgen after each speed increase test how stable your comp is by running prime select just benchmarking,there are a couple of tests full system test,mostly cpu and blend,each test is pretty good for looking for errors in their various fields the best aspect is your comp wont lockup while running the test just report errors any error is bad,generally its only assumed a computer is 100% stable after prime has been running for 24 hours

Once you first start to see errors up the memory and cpu voltage in clockgen slightly until it becomes stable again,no stress will be put on the HD,clockgen will also show your pci bus bus speed so you will know definitively if you are overclocking your pci bus

http://files.extremeoverclocking.com/file.php?f=103