HDD errors after cpu overclock

[Jerizo]

I overclocked my i7-860 to 3.6ghz a while back and just now to 4ghz with new SSD HDD and memory. I used to not get past 3.6ghz by increasing VCORE but increasing VTT helped me get to 4ghz.

When adjusting these settings in bios and booting back up to stress test I noticed that I sometimes have to run a hard drive consistency test. That didn't seem to be a problem until now with my new hardware.

When going for 4ghz i was prompted to do the consistency check but I skipped because I figured it was gonna pop up again after playing some more with the settings and I didn't want to do it multiple times.

After booting up I noticed that my new hdd was no longer accessible, it said bitlocker encrypted so I restarted to do the consistency check. It took more than 10 hours, it used to take 20-30 mins on my old HDD. The final few lines in the consistency check screen said that 7mb were bad sectors but the rest seemed ok.

I booted back up but my HDD was still not accessible. I tried formatting through Windows Disk Management but that gave me an error so I tried EaseUs Partition Master but that gave me an error as well: "There are some error occurred while writing partition chains on disk".

It now is showing up as Not Initialized in windows Disk Management and it gives me this error when I try to initialize but following the instructions didn't help: "The operation failed to complete because the disk management console view is not up to date. refresh the view by using the refresh task. If the problem persists close the disk management console, then restart disk management or restart the computer"


I don't care about loosing data on the HDD because there barely is anything on it since i just got it, I just want to be able to use it normally.

I need some help with this how should I proceed?


My System:

Gigabyte p55-ud3
i7-860
Sandisk Extreme II (on Sata II port)
Western Digital Velociraptor 1tb (on Sata II port)
4x4GB Mushkin 1600mhz 7-9-8-24 (2 of them are rated at 7-8-7-24 but running all at 7-9-8-24)
Ati Radion HD5870

 

[Dr-Kiev]

Best choice is RMA

 

[BrightCandle]

Go back to stock clocks and test it again. Don't ever try and debug a potential hardware problem with an overclock applies, stable or not.

 

[Jerizo]

I don't think I can RMA this. I bought the HDD off ebay. It was new without packaging but still sealed in the Western Digital anti static bag.

I am back on stock clocks but I can't format or partition it.

I'm not sure if this happened because it touched the VTT or the fact that that allowed for higher BCLK. Do you know the logical explanation for hdd corruption when ocing? Like does the BCLK affect the sata controller or something or did it make my memory unstable and cause corruption that way...

 

[BonzaiDuck]

I don't think I can RMA this. I bought the HDD off ebay. It was new without packaging but still sealed in the Western Digital anti static bag.

I am back on stock clocks but I can't format or partition it.

I'm not sure if this happened because it touched the VTT or the fact that that allowed for higher BCLK. Do you know the logical explanation for hdd corruption when ocing? Like does the BCLK affect the sata controller or something or did it make my memory unstable and cause corruption that way...

Depending on some hardware architecture, it is possible to increase the PCI-E bus speed inadvertently by overclocking. This was always evident before socket-1366: One would OC the processor by goosing the front-side bus speed -- as opposed to the core multiplier. Socket 1366 allows you to overclock the QPI as well as the CPU multiplier (I think, and see below.) Socket 1155 doesn't need this, the boards don't make it prone to inadvertent change.

I skipped socket 1366, so I don't know the particulars of your BIOS, and fact is -- I only scanned through some forum posts and OC'ing guides for that generation -- hoping to get a jump on better understanding socket 1155.

HOW . . . . E-VER . . . . .

If my explanation seems like it might apply to either your over-clocking strategy or hazards in your BIOS design/organization that could lead to putting too much stress on the PCI-E bus and the drives, you might investigate that angle further.

At least HDDs are cheap. Even so, I might also worry about your SSD, but it may pose a different -- even lesser risk -- I couldn't say for sure. But there could be other worries: Your storage controller may be going south -- maybe for the same reason. When you buy a replacement drive or go through RMA, test it on the same port that failed the first one. You'll know for sure by then, I'd think . . . .

 

[Jerizo]

Thanks for providing some insight on how this all works.

So are you saying that the only way I can fix this is to RMA it? Are there no Software Tools that could help initialize the drive perhaps?

I also noticed that windows is detecting 16GB Ram installed but only makes 7.99GB usable, not sure if this is related.

My SSD doesn't seem to have any problems, neither does my other hdd only this one got issues.

 

[Elixer]

If it don't work now, and it doesn't work on another machine, then RMA is only option.

 

[Bubbleawsome]

I assume you are running 1156, not 1366, and I will say that I've seen funky thins happen while overclocking the FSB, but nothing like that. It sounds like a software issue or a virus. But now that it is done a RMA might be the only choice.

 

[BonzaiDuck]

I assume you are running 1156, not 1366, and I will say that I've seen funky thins happen while overclocking the FSB, but nothing like that. It sounds like a software issue or a virus. But now that it is done a RMA might be the only choice.

Ah! Had to respond. I thought his processor was the 1366 socket. Must've got it wrong. . .

 

[Jerizo]

right I'm running 1156.

I'm not sure if I can RMA this, specially cuz I just found out that the HDD apparently came from the Asia-Pacific region and shows up as out-of-region when I check the serial number with the RMA s/n lookup tool on WD website.

Now I read on some forum that WD allows one out-of-region RMA per customer per year but I don't know if that is true and I wasn't able to find that information on the WD site either. I'll contact their support shortly.

Do you know how they handle these situations?

I don't think it was a virus issue because I had just installed a new ssd and this hdd and basically had a completely clean system except if my other hdd that was also enable could have migrated a virus.

I'm actually not so sure anymore that my Overclock caused this. I mean I wasn't going for a crazy OC or nothing. My BCLK was 190, Vcore ~1.28 VTT ~1.27. This is a pretty average OC on this chipset to my understanding. 180-200 BCLK appears to be the range for the average good OC.

Could this haven been caused by shipping perhaps?

Is it possible for hdds to be predestined to fail after brief usage?
It was running for four couple hours, might have even been the next day that I was prompted to check consistency after rebooting couple times which happened to be during adjusting my OC. So maybe that was only coincidence?