can o/c mess your hard drive up?

[Badbry]

and make the bios not recognize it anymore?and upon boot-up give messages like "boot disk failure"?


Bryan

 

[Badbry]

BUMP

 

[yiwonder]

Are you using the KT7A?

 

[Badbry]

MSI K7T Pro2-A

 

[yiwonder]

Oh, I know of a few that have had the same problems on the KT7A and all they had to do was to reset the CMOS. This will mess up all of your BIOS settings, but might be worth a try. Upping the FSB shouldn't hurt your hard drives.

 

[HamHam]

heheh I did the same thing on mine MSI K7T Pro2-A, i just restarded the computer and it booted fine but the mobo was not stable with the uped fsb so i am running @ 100 .

 

[Badbry]

i think it's dead.....i tried clearing the cmos,but the same thing.... boot disk failure.......and it's only 3 months old...

 

[ST4RCUTTER]

Did you boot with a boot disk? If so, can you see the C: drive? It may just be that your boot partition go hosed and the data is still there.

 

[RSI]

Upping the FSB shouldn't hurt your hard drives.

It can, and it happens. Your hard drive runs on the PCI bus. Unless technology has changed a lot and I'm really behind times, upping your whole FSB is effectively overclocking all your PCI peripherals as well, INCLUDING your hard drive. I have messed up a Seagate hard drive doing this. It still works, but it's very flukey.

So, if you want to overclock more safely, use the multiplier if possible. If not, well, I guess you have to take the risk.

 

[RSI]

Actually I just thought bout something .. on these new mobos, are you able to change FSB in the BIOS? If so, does this change for the CPU only somehow? I think I've heard of this somewhere, I'm really vague on this though, so don't count on me.

 

[Badbry]

i just tried to boot to a disk,and when it got to the A:\ prompt,i typed fdisk,it said no drive installed or something like that.... when i typed c:\,it listed some files.....but wouldn't let me format...

 

[Badbry]

Please help!!!! i need a working puter...i am at stock speed right now 1300mhz.i don't have the money to buy another hdd right now...

 

[SuperSix]

<< Upping the FSB shouldn't hurt your hard drives.

It can, and it happens. Your hard drive runs on the PCI bus. Unless technology has changed a lot and I'm really behind times, upping your whole FSB is effectively overclocking all your PCI peripherals as well, INCLUDING your hard drive. I have messed up a Seagate hard drive doing this. It still works, but it's very flukey.

So, if you want to overclock more safely, use the multiplier if possible. If not, well, I guess you have to take the risk. >>



Correct. I know Maxtor made some drives that were very sensitive to FSB, in the late Socket7 heyday.

 

[Badbry]

it is my samsung 40 gig drive(3 months old) that it not working properly.....i am on someone elses computer. i used to have a maxtor....

 

[Badbry]

i'm gonna see if he will let me buy his 40 gig maxtor...

 

[obenton]

Get the Samsung hard drive utility at http://www.samsungelectronics.com/hdd/support/faqs/faq_1311.html and test the drive.

 

[yiwonder]

Earlier I said that &quot;Upping the FSB shouldn't hurt your hard drives.&quot;. I meant responsibly upping the FSB slowly. I don't know, but it does make sense that if you change the FSB by a lot, you might be able to damage the drive. I know that some can run fairly high FSBs and still not have any problems with their hard drive. I still don't think you killed your hard drive by o/c.

 

[Jiggz]

Reset the BIOS to it's optimal or defaul setting. Set the CPU to its stock speed. Boot from a boot disk. On the A:\ Prompt type:

Fdisk /mbr [Enter]
Sys C: [Enter]

This should fix your problem. As for the original question, YES, higher FSB can mess up your HDD.

 

[TunaBoo]

<< Actually I just thought bout something .. on these new mobos, are you able to change FSB in the BIOS? If so, does this change for the CPU only somehow? I think I've heard of this somewhere, I'm really vague on this though, so don't count on me. >>



No it all goes faster no matter where u change the FSB.

However, on some chipsets you can run the RAM at PCI + Host MHZ (so if CPU is 100 RAM is at 133). However if you OC, all your parts still get OCed.

 

[SerraYX]

Run the utility, get an RMA.

BTW, Maxtor drives are picky as hell with FSB speed. I can't go over 133 (KT133A) without the hard drive not booting Windows properly. Sucks too, with Corsair pc133 CAS-2 RAM.

 

[Badbry]

i tried all those,even the samsung setup disk that came with it,says there is no hard disk installed.....and when i try to fdisk,it says there is no fixed disks installed....i'm calling them tomorrow.i wonder if they work the same way as maxtor,they will send you another drive,and you send them the defective one back in the same box?and can they tell if i had it o/c?

thanks,
Bryan

 

[SuperSix]

<< i tried all those,even the samsung setup disk that came with it,says there is no hard disk installed.....and when i try to fdisk,it says there is no fixed disks installed....i'm calling them tomorrow.i wonder if they work the same way as maxtor,they will send you another drive,and you send them the defective one back in the same box?and can they tell if i had it o/c?

thanks,
Bryan >>




Samsung does not do advance RMA replacement, just call them or get an RMA HERE.

More info HERE.

 

[cruelpsycho]

Does your samsung spin up? mine would spin up then stop and no hard drive detected and that was on a system that was never oc'ed i RMA'ed the drive it was bad.

 

[novice]

I had a Quantum Fireball get corrupted data after mild (75 MHz fsb) overclocking on a Soyo SY7I-WM/L motherboard. I was finally able to reformat and reinstall windows and it is currently working fine for my father, but I believe that even that mild overclocking of the PCI bus caused its' problems. Especially since it has been fine since running at the standard 66 Mhz fsb for the Celeron 366 processor.
Chuck

 

[StarRover]

I killed a Maxtor drive by overclocking it before they made mobo's that have the 1/4 divider for the 133FSB,When you go over the 133FSB your PCI bus starts to get overclocked again.