Macbook Pro 13" keeps frying my SSD's

[Andersbruhn]

I have a Macbook Pro 13" mid 2012 that I've upgraded with 16 gb ram and an SSD (kept the 500gb hdd instead of the disc drive). First I tried with a Corsair SSD Force Series GS 128GB, but after some time it stopped working - as in it's 100% dead. Doesn't work in other devices either. Then I bought a WD Blue 3D NAND SSD, but the same thing happened. Both drives are now dead.

At first I thought I could be the HDD cable, since it's a known issue with this model - but as far I can see, the SSD should still work in other devices when the HDD cable fails in the Macbook Pro. So I haven't changed it.

Anyone have an idea of what could be wrong or where I might look for an solution?

 

[chrfr]

I have a Macbook Pro 13" mid 2012 that I've upgraded with 16 gb ram and an SSD (kept the 500gb hdd instead of the disc drive). First I tried with a Corsair SSD Force Series GS 128GB, but after some time it stopped working - as in it's 100% dead. Doesn't work in other devices either. Then I bought a WD Blue 3D NAND SSD, but the same thing happened. Both drives are now dead.

At first I thought I could be the HDD cable, since it's a known issue with this model - but as far I can see, the SSD should still work in other devices when the HDD cable fails in the Macbook Pro. So I haven't changed it.

Anyone have an idea of what could be wrong or where I might look for an solution?

I'd definitely stop putting more drives into that computer until you replace the cable. The cable can short out against the metal housing as the insulation wears so it wouldn't surprise me that disks could be damaged from this.

 

[Fishrrman]

"At first I thought I could be the HDD cable, since it's a known issue with this model - but as far I can see, the SSD should still work in other devices when the HDD cable fails in the Macbook Pro. So I haven't changed it."

Change the cable anyway.
Could a defective cable have done something to "short out" the SSD's controller boards?

If that doesn't work, at "10 years old", perhaps it's time to start shopping for a replacement...

 

[avz]

Wow. This is just made me concerned about my own MacBook Pro 13" Mid 2012. No issues at the moment but I will definitely keep this in mind.

 

[Cide]

That really sucks. Did you ever find a solution by chance? Or was it just coincidental failures?