• Welcome to Overclockers Forums! Join us to reply in threads, receive reduced ads, and to customize your site experience!

(Resolved) Uh Oh, First SSD Dead Experience.....I think.

Overclockers is supported by our readers. When you click a link to make a purchase, we may earn a commission. Learn More.

RollingThunder

Destroyer of Trolls & Spammers
Joined
Jan 7, 2005
New build and first SSD experience:

Loading has been a little sluggish lately and a W10 update looks like it killed it on an update reboot:

"Disk Read Error, press CTL-ALT-Del to reboot."

Disk would boot after several retries and go into "Prep Auto Repair" and "Diagnose PC" which I
wasn't aware was there, and finally just the error C-A-D. "Restarting" would go into an endless loop too.

I have read that there is no warning to a dead or near dead SSD and it looks like I have witnessed it. Am I correct
or is there something else to check?

I'll check the cables to be sure. How is Samsung's RMA? :)
 

Silver_Pharaoh

Likes the big ones n00b Member
Joined
Sep 7, 2013
New build and first SSD experience:

Loading has been a little sluggish lately and a W10 update looks like it killed it on an update reboot:

"Disk Read Error, press CTL-ALT-Del to reboot."

Disk would boot after several retries and go into "Prep Auto Repair" and "Diagnose PC" which I
wasn't aware was there, and finally just the error C-A-D. "Restarting" would go into an endless loop too.

I have read that there is no warning to a dead or near dead SSD and it looks like I have witnessed it. Am I correct
or is there something else to check?

I'll check the cables to be sure. How is Samsung's RMA? :)

That's what I read. No warning signs.... SMART however does provide enough warning in advance it seems.
Wonder if you're able to pull the SMART data?

I also hear Samsung has good CS so I don't think an RMA will be painful.
 
OP
RollingThunder

RollingThunder

Destroyer of Trolls & Spammers
Joined
Jan 7, 2005
Is it seen in the BIOS?

Yes, it's there. I checked that when it was slow booting / error booting.

I had run the SMART info a few weeks ago and it was fine and ran the
Magician Performance test when it was slow booting yesterday and the data
transfers were way down from the original tests of ~6900 range to the
400 range. So there WAS some clue something was not right.

I'm not too concerned, it happens and I was still "playing" with clocks, tests
and diag software only. Ddn't even install my MS 2013 Office yet.
 

ATMINSIDE

Sim Racing Aficionado Co-Owner
Joined
Jun 28, 2012
~6900 means RAPID mode was enabled. ~400 means it wasn't. Not an indication of a failing drive.
If it's seen in the BIOS the drive is most likely fine.

Try booting to the Win10 install media and running repair from there.
 
OP
RollingThunder

RollingThunder

Destroyer of Trolls & Spammers
Joined
Jan 7, 2005
~6900 means RAPID mode was enabled. ~400 means it wasn't. Not an indication of a failing drive.
If it's seen in the BIOS the drive is most likely fine.

Try booting to the Win10 install media and running repair from there.

Will do. I actually installed W8.1 and took the free upgrade to W10. Make any difference?
There are many "Firsts" here of me on this learning curve!
 

wingman99

Member
Joined
Dec 10, 2003
Will do. I actually installed W8.1 and took the free upgrade to W10. Make any difference?
There are many "Firsts" here of me on this learning curve!

You can go directly to windows 10 now even if your going to do a full install, MS keeps your Activation on that hardware.
 

Robert17

Premium Member
Joined
Feb 1, 2011
Location
Republic of Texas
Don't know your config but if you can install the drive as a secondary in another PC and format it from there you may determine if it's got a firmware issue vs. a NAND issue. It's already sounding like firmware from your description.
 
OP
RollingThunder

RollingThunder

Destroyer of Trolls & Spammers
Joined
Jan 7, 2005
I removed the back side panel to check connections, they seemed OK but
rechecked them anyhow. Problem was resolved and it's been fine since. :)

I really don't know what the solution was but a Windows update reboot
stalled in an endless loop and I'm sure that didn't help either.