Hey guys,

 

recently my brother purchased a very nice new computer, with a gigabyte Sniper G1 mobo and kingston SSD hyperx 120gb. So he recieved it the other day, installed a HDD from his old computer (not the old computers boot drive, an extra one) and was booting fine, then today it BSOD'ed and won't start up, constantly giving the "a disk read error occurred" error. He has removed the SSD and put it back in, still problem

 

specs:

 

intel i7 980

gigabyte sniper G1 mobo

12gb corsair DDR3 ram

2 x nvidia 580

1200w PSU (corsair)

1x Kingston 120gb hyperx SSD (boot drive)

win 7 64bit

DVD optical drive

 

did I forget anything??

 

Tried booting off recovery CD, was taking too long so will try again later.

 

plan on following these instructions

 

Because this error is not usually associated with data loss, DO NOT RE-PARTITION THE DRIVE. Your data is likely safe and sound.

 

Here's how we'll recover your data. Try each step below, in order, and see if your drive becomes accessible after each step. In my experience, you won't start seeing results until step 5 or so.

 

1. Run CHKDSK /R /P from the recovery console (it will typically find no error)

2. run FIXBOOT from recovery console (typically has no result)

3. run FIXMBR from recovery console (typically has no result)

4. Run the manufacturer's diagnostic utility, downloaded from their website (it will typically find no error)

5. Changing the drives from cable select to Master/Slave may fix it.

6. Replacing the data cable may fix it, but usually not.

7. Setting the BIOS to use defaults may fix it, but usually not.

8. Changing the BIOS drive settings from auto to user-specified, ensuring that LBA is selected may fix it.

9. Pulling the CMOS battery to let the BIOS lose it settings may work.

 

At this point, you may be feeling some frustration. :-)

 

If you guys have any experience in this area, or have any ideas, they would be much appreciated!!

 

Thanks

I had a Kingston 120GB HyperX SSD and the exact same thing happened to me earlier this year. Considering the price, I wasn't exactly happy and had to go back to Umart for them to send it back to be repaired.

 

The problem is (from what I was reading earlier this year) is that a Windows Update completely screws with the SSD and it simply will not be recognized by the operating system without a complete firmware reset and I wasn't sure how to do that.

 

In my case, there was absolutely no trace of the hard-drive anywhere in the BIOS so there was nothing I could do - I tried it with about seven different SATA cables, every single port in the motherboard but still nothing. It essentially stopped being recognized as a piece of hardware in my case, not sure if you have the same problem. I just took it back and waited a couple weeks for it to come back. Do you still have the warranty on the drive? Those things (SSD's) don't come cheap unfortunately.

I had a Kingston 120GB HyperX SSD and the exact same thing happened to me earlier this year. Considering the price, I wasn't exactly happy and had to go back to Umart for them to send it back to be repaired.

 

The problem is (from what I was reading earlier this year) is that a Windows Update completely screws with the SSD and it simply will not be recognized by the operating system without a complete firmware reset and I wasn't sure how to do that.

 

Do you still have the warranty on the drive? Those things don't come cheap unfortunately.

 

Because the computer was built by umart, I'm sure it's under warranty seeing as it is only a day old! Anyway, you said windows update screws with it, I asked my brother and he is pretty sure he hasn't loaded any windows updates for the machine yet.

 

anyway, thanks for your help! if we don't fix it tonight, then It'll probably go back to umart. Cheers

Windows update was the most likely culprit for me but I think it was to do with the firmware, so if you have no luck fixing it don't hesitate to demand Umart send it back for you lol, they are obviously still stocking that same SSD that screwed up on me earlier this year.

Unplug the SSD from the PC , power and sata.

Start PC with the other drive still plugged in and check in BIOS you can see everything apart from the disconnected SSD.

Leave the SSD unplugged for a time , overnight if you have time or 6 hours if you dont.

Try plugging it in again . Make sure its in sata o or sata 1 port on the mainboard.

Should detect and boot now.

Another method that may work and be quicker is disconnect just the sata cable from the SSD and turn the power point for the PC plugged in but off.

Press and hold the power button on PC for several sec several times.Any led on mainboard should now not be lit.

What both these methods are trying to do is discharge any capacitors in the SSD that power temp cmos memory. The SSD doesnt do a full initialization unless its been powered down for a while, or a factory reset ,or firmware update is done.

The last two options are closed as the drives OS (the drive itself is a small computer) is corrupted and isnt presenting itself to the rest of the computer on boot. Thus why you cant see it in BIOS and why it wont boot from.

When it does fully initialize after a reset or full power down that corruption should be overwritten and the drive present to the PC.

 

Make sense ?

 

Try it as it cant break anything and doesnt cost.

 

Now when you realize I was right dont forget to inflate my ego with praise !

 

:hi:

Hey Fallen, THANKS!!!

 

I haven't tried it yet as he isn't home, but its first on the list. Will make sure you know how appreciated I am If it works

 

Cheers anyways

Alright as of now, he plugged it into another HD bay, and works! BUT- he finds it to be halting every 10seconds or something, so it might just be faulty?