Help me!! OCing killled my new HDD!

Q

questioner

n00b
Joined
Dec 21, 2005
Messages
4
Hey there i need help urgently! I just got my new pc recently and i have attempted to OC my pc to 4400 X2 level (from 3800X2). I have recently been attempting to do this with a program called easytune5 however my computer has been crashing after each attempt. To try and make it work i decided i would go into the bios and see if that would make it work. When i got there i coed the cpu to 4400 level and rebooted the pc. On reboot i found that the computer was continually crashing so i went bacxk into the bios and loaded the default optimal settings. After this however my computer has failed to detect my HDD and continues to do so despite my reconnecting the cables and atempting to force a detection in the BIOS. Can someone please please please help me! i am seriously freaking out! This is a brand new computer and if my mum and dad find out i have already screwed it before i have even had it for a week they will KILL ME! We are under a bit of financial pressure at the moment and my dad is under heaps of stress from his job and this is extra stress they do not need.
SOMEONE PLEASE HELP ME!!!
 
people on other forumns have suggsted that i may have burnt out my sata/raid controller on my mobo in which case id have to get a new one? Is that possible?
 
1) What are your specs? What motherboard?
2) Take those harddrives and try them in a different computer and make sure they work all right. Then (assuming they are fine) attach them again to your PC and you can try using IDE 2 instead of 1 or vice versa. Or are they SATA?
3) Did you increase the voltage or something when OCing?
And if it is a DFI Ultra-D, make sure you select AUTO detect
 
{NcsO}ReichstaG said:
1) What are your specs? What motherboard?
2) Take those harddrives and try them in a different computer and make sure they work all right. Then (assuming they are fine) attach them again to your PC and you can try using IDE 2 instead of 1 or vice versa. Or are they SATA?
3) Did you increase the voltage or something when OCing?
And if it is a DFI Ultra-D, make sure you select AUTO detect
Click to expand...

hey its a Gigabyte GA-K8N-SLI mobo. I have a eVGA 7800GT CO, 1GB pc3200 ram, 200GB Sata II HDD, 3800 X2 CPU

Yeh i increased the voltage by 0.5.

I dont have any other computers in the house to try them in (only laptops)

I have been talking to some of my frends who are computer experts (one has a degree in computer stuff) and they both think that i coudlnt have damagd anything by ocing as i only increased the FSB by 200MHz and the voltage by 0.5. The computer degree guy thinks i may have corruupted the HDD when the PC was crashing, and that reformatting it might fix it. However i cant even detect it to reformat it :(
 
Is the motherboard posting? Meaning is it booting up the bios loader?
Is it beeping at you? If so, count the number of beeps and refer to the manual to check the error code. I've never heard of an overclock attempt frying a HDD.

More than likely you just corrupted the OS. You should be able to boot from the OS CD and run a repair on the OS loaded on the HDD from the setup. If not then if you have a second system with sata, then put the HDD in there boot up the working systems and run a check disk or scan disk on the bad drive.
 
you should make sure sata is enabled on your board. you may have it plugged in to a sata channel that is off. (most newer boards use the nvidia one and have an extra one added on)
 
Maybe try to clear the CMOS? I think this iffy HDD is something most of us could fix if it was right beside us hands on, I too have never heard anything about killing a HDD. Too many attempts to OC @ too high of FSB with windows have loading etc. will get you a corrupted os for sure. I would try to reload windows.

Gigabyte Help

I would look around there, you may have tweaked something wrong in the bios. I am showing that board has 8 Sata Connectors

Also make sure RAID is disabled. Let us know.
 
1st) u bought a junkabyte
2nd) don't worry, yet, it could just be something small. Test to see if the drive work well on another computer
3rd) a simple windows repair might do the trick... for OCin read eclipse guide in memory.
4th) if its new you should still have some kind of warranty
 
coolkishan said:
Did you lock pci/sata frequencys before ocing?
Click to expand...

That is the FIRST thing that came to mind, and that should be done on any mobo before OC'ing...not locking the PCI/SATA frequencies can seriously screw things up for ya...and yes, it could very well have led to what you're encountering now.

Until that is confirmed (one way or another) I wouldn't assume much else.

they both think that i coudlnt have damagd anything by ocing as i only increased the FSB by 200MHz
Click to expand...

Well, unless this is a typo (which I'm hoping to GOD it is) it's really easy to see why you'd be having issues. Setting your HTT to 400Mhz in the BIOS without locked PCI/SATA frequencies WOULD mess you up.

Sry, I know it was probly a typo...just couldn't resist commenting on it. :p
 
Clear the CMOS. Move SATA to 1st port, reboot. You could also try to hold Insert while booting. That puts sets Fail Safe Defaults and gets you into the BIOS (most of the time).
 
He said he reset bios and it still didnt work so even if the lock was or wasnt on doesn't make a difference now. It's something else.
 
Oh sorry, I didn't see that. Well I suggest going over all the plugs making sure they are in tight.
 
Hello? Why would you bother to OC when you can't afford to replace? Rule #1 for OCing, especially if you don't know what to do.

With that said, check your BIOS settings, and reset the CMOS by taking the battery out w/ the power supply not connected to the wall. Then load optimized defaults. Make sure everything is plugged in right. Make sure that SATA is enabled in your BIOS. Then, if no go, put in your XP disk like you are going to install windows, hit f6 at the beginning when prompted, and load your SATA drivers from the floppy disk you have(you made this, right?). Then, run the recovery console. Run fixMBR and hopefully it will fix your lost bootsector that was ruined when you OC'd and lost your SATA boot sectors.

Good luck

BTW--I think I have the same MOBO and its not junk, its great and works like a charm.
 
MC FLMJIG said:
He said he reset bios and it still didnt work so even if the lock was or wasnt on doesn't make a difference now. It's something else.
Click to expand...


Unfortunatley, not locking can permanently damage a HD.
 
questioner said:
hey its a Gigabyte GA-K8N-SLI mobo. I have a eVGA 7800GT CO, 1GB pc3200 ram, 200GB Sata II HDD, 3800 X2 CPU

Yeh i increased the voltage by 0.5.
Click to expand...
.5?! that is way to much isn't it? or do you mean .05? cause i remember reading that you shouldn't go beyond .2 or .3 at the max
 
That is way to much, I hope you didn't do that. lol..1.35V to 1.85V, big difference.
 
iSkylla said:
That is way to much, I hope you didn't do that. lol..1.35V to 1.85V, big difference.
Click to expand...

Haha, yeah...no kidding, I hope that's another typo. :p

Just wondering..does the DFI Ultra-D automatically lock the frequencies
Click to expand...

Yes, if you don't change any default BIOS settings they're locked out of the box.
 
I know you can damage if you don't don't lock it but it's not longer locked is what I meant.
Abit is usually already locked... ;) That is why I don't worry.
 
Wow, I'm amazed someone would just download a random program and attempt to overclock their computer BEFORE DOING PROPER HOMEWORK! That's why I spent a good week here on the [H]forums reading, learning, etc. before getting into overclocking.

Lessons learned my friend, I hope it all works out for you in the end! :p
 
First off, this post has gotten so much attention without an update from the OP, I don't know if it's for real. ~Especially with the crazy voltage adjustments.

Second, if you're for real, go through the whole process. Unplug PSU, leave CMOS jumper on the clear CMOS setting for at least a minute (I've owned rigs where this was truly necessary-Gigaboat motherboard for that matter). Then try to reboot at stock settings.

Third-try other SATA ports. If you blew up something it could be port specific. Not really that likely, but maybe.

Fourth-if you somehow recover for God's sake (and your own) do your homework next time. I'm not trying to be mean, but your story reads very much like "16 Year-Old Wraps Dad's 'Vette around Tree....25 Feet in the Air".
 
You must log in or register to reply here.
Back
Top