Ongoing issues with my SSD (Samsung 470)

[mclaren777]

Everything was working fine until today. My computer had been sitting idle for 30 minutes while I was watching TV. I glanced up to see the final seconds of a BSOD and it restarted on its own. All drives still show up in the BIOS.

I swapped the primary boot drive to a SATA 2.0 port and it still gave me the "Disk Read Error" message, but when I swapped back to the original SATA 3.0 port I was greeted with this message...

I inserted the Windows DVD and tried to repair but I couldn't select Windows 7 from the OS list. Furthermore, my SSD isn't showing any data (Disk C).

I then tried some Command Prompt utilities but they didn't have good news for me.

This is really disappointing because I just bought the drive about six weeks ago.

I will be contacting Samsung in the morning to discuss my options.

 

[razel]

When you did diskpart and listed the volumes, I think I see the partitions. Could you try again, but this time do list partition. I'm assuming the Samsung is a 64GB, because I see the default 100MB Win7 utilities partition and then a 59GB. If that is all correct, then you can breathe a bit.

I would do a SMART test 1st to see if the drive is fine. After that then I'd run any of the free partition managers such as EASEUS, which come with free partition recovery. It's best to take the drive out and plug it into another computer preferrably direct via SATA. Have fun.

 

[jmet]

Any update on this?

 

[mclaren777]

Nothing I tried ever worked so I contacted Samsung and they're sending me a replacement.

Now I just need to do some research to see if SSDs can be imaged/cloned.

 

[flamenko]

Your ssd is not dead. It says that your Boot Manager is missing and this is something you might want to google. Your answer is there as your boot record has become corrupted and can be fixed with a little reading.

BCDEdit works although a repair of the disk through Windows recovery may also work.

Of course ssds can be imaged and cloned and, in fact, if you use that disk as a secondary you will be able to access the drive.

 

[GundamF91]

Yeah, it sounds like Bootmgr that's having corruption, which could happen to HDD as well. It's more likely of a problem within Windows OS. But this would make me feel iffy about using this particular SSD.

 

[flamenko]

Yeah, it sounds like Bootmgr that's having corruption, which could happen to HDD as well. It's more likely of a problem within Windows OS. But this would make me feel iffy about using this particular SSD.

It has nothing to do with the SSD whatsoever and this occurs, most often, when one is using a multiple OS system or has drives connected to the desktop where, more than one has an OS hooked up.

The most important thing here is that the data is not lost and that drive can be fixed as it is simply a corrupted data file that tells your system to boot from that drive. The easiest fix it Windows Repair.

 

[mclaren777]

I wish I would have known this before sending it back but I couldn't get anything to access the drive (as seen in the photos) so I'm not sure there was anything I could have done.

 

[Starcrossed11]

I had a very similar thing happen to my SSD. I ended up using the Repair Computer option off of my Win7 DVD. Basically, Bootrec.exe /Fixboot solved the problem.

Instructions:

http://support.microsoft.com/kb/927392

 

[mclaren777]

I tried that, Starcrossed. You can see the outcome in the final picture. None of the Bootrec options worked.

 

[mclaren777]

My replacement drive just died the same way as before but I was able to see the BSOD message as it went down.

Kernel_Data_Inpage_Error

I'm starting to wonder if these reliability issues are caused by my first-gen P67 motherboard. My SSD is connected to a SATA 3.0 port (which shouldn't be affected by the recall issue) but it seems really odd that I'd have two disc rear errors in just two months.

Thoughts?

 

[mclaren777]

When you did diskpart and listed the volumes, I think I see the partitions. Could you try again, but this time do list partition. I'm assuming the Samsung is a 64GB, because I see the default 100MB Win7 utilities partition and then a 59GB. If that is all correct, then you can breathe a bit.

I know this probably has nothing to do with my problem, but whenever I get this computer up and running again, I'm going to leave the paging file on the SSD just for peace of mind.

 

[mclaren777]

Hmm. The three internal drives aren't showing any free space. Does that seem strange to anyone else?

 

[DominionSeraph]

check your RAM. You're not showing all of the right symptoms, but I've had bad RAM kill a windows install and it's an easy check.

 

[mclaren777]

The RAM seems to be fine. And according to Microsoft Answers this could be an issue with the paging file, which I moved off of the SSD and onto the HDD like many people seem to do.

The error code KERNEL_DATA_INPAGE_ERROR STOP: 0x0000007A states that the requested page of kernel data from the paging file could not be read into memory. It appears that there are some issues with the hard disk.

 

[mclaren777]

Here's a crazy plan: what if I just install W7 again over the top of W7 using the upgrade option?

Would that allow me to keep all of my previously installed programs?