My 128GB Kingston V100 bit the dust

[Hulk]

I purchased the drive in 2011 for a HTPC. Last year I upgraded the motherboard and CPU of the system and reloaded windows. Over the last year I had a lot of double starts, then triple starts and just a few years ago like 10 tries to get into Windows. Normally these restarts indicate motherboard or power supply issues so I flashed the BIOS and swapped out the PS a few months ago and it seemed a little better.

Then once or twice a few days ago the drive was not recognized. I immediately pulled it from the system and cloned it to an Intel 320 I wasn't using. I got lucky and it worked. Now the drive isn't recognized. If I can get it recognized again I'll run Crystaldiscinfo and post results.

I have an Intel 320 from 2011 that still works perfectly and never gave me a bit of trouble. An Intel 330 from 2012 that also has been flawless. A Crucial BX100 that so far (about a month) has been great. I don't think I'll be buying another Kingston SSD. This drive was rarely used and only as a boot drive in a HTPC computer in a relatively cool basement.

 

[Cerb]

Wow. Took long enough! Those old JMicron controllers generally knew how to burn up some flash.

 

[coercitiv]

I bought my 128G Kingston V+ 180 in 2011 as well. It saw some heavy duty work for about 2 years (likely 20GB+ per day) and afterwards got relegated to HTPC duty.

Never had any problems with it. Then again, it's essentially manufactured by Toshiba (flash&controller).

Later edit: I also have a V300, I use it as a flash stick

 

[Hulk]

Wow. Took long enough! Those old JMicron controllers generally knew how to burn up some flash.

Not really. I doubt I got 5 drive writes out of this SSD.
Still think it "took long enough?"

 

[Puffnstuff]

It's a well known fact that if electronics are going to fail that they usually fail early on so be grateful that you got 4 years out of it. My Adata failed at 2 months, my OCZ agility 2 failed at 6 months and my Samsung 840 pro failed at the 2 year mark.

 

[Hulk]

Well now it's back. I booted up today and the drive was recognized. I formatted it and it seems to be fine. I don't trust it as a boot drive or for much else for that matter so I don't know what I'm going to do with it.

 

[Dujith]

This sounds alot like the same issue alot of people are having with a certain controller (in my case the Vertex2 that has issues with Ivy Bridge when starting up.
Sometimes it will fail to detect the drive.

There is no issue with the drive itself, just that the bios doesnt see the drive sometimes.
No fix. So either swap it out or learn to hit the reset button a few times when that happens