• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.
  • The forums have been upgraded with support for dark mode. By default it will follow the setting on your system/browser. You may override it by scrolling to the end of the page and clicking the gears icon.

Problem with SSD

Joined
Dec 30, 2010
Messages
1,221 (0.23/day)
Location
Canada
System Name Brutus
Processor i5 4690k @4.7Ghz (Watercooled)
Motherboard z97 MSI Gaming 5
Cooling NZXT Kraken x61 AIO watercooler
Memory Gskill Ripjaws 8gb (2x4gb) 1600mhz 7-8-7-24
Video Card(s) MSI Gaming GTX 980ti x2 (sli)
Storage 1 SSD 64GB (OS) + 2x500GB WesternDigital RAID 0
Display(s) YAMAKASI Catleap q270 SE 27inch Glossy 2560x1440
Case NZXT Phantom
Audio Device(s) ASUS Xonar DX
Power Supply Antec TPQ 1200w
Software Windows 7 (64 bit)
I have a 64gb Kingston ssd and I'd say about 6 months ago it started having a little problem.

Sometimes at boot, it does not get detected... So I have to reboot and often times on the second reboot it gets detected and loads windows fine (windows is installed on it)...

It started going this on my previous mobo, and on this new one it has the same problem too.

Could it be the ssd is somehow "dying"?
How long are ssds supposed to last anyhow?

Could it be something else?
I checked my wired and all seems fine
 
I was thinking it's probably the ssd going bad because I never updated my old mobo bios... And yet the ssd ran for 5 years no problems until 6 months ago...

Same problem in is new mobo. Thanks for the link. I'll run the tests
 
Its the controller kingston uses
 
I noticed I have a thing called "intel raid controller" (a driver) that is included in the MOBO drivers (on the mobo's CD). Should I install this?
My 2x HDD in RAID 0 work fine already without that driver installed (with only the mobo set to raid 0)...

don't know if it would help the mobo detect the "non raid drive" ssd...
if happens like 1/2 the time...

every 1/2 times the SSD is not detected until I reboot and then it does get detected
 
I was thinking it's probably the ssd going bad because I never updated my old mobo bios... And yet the ssd ran for 5 years no problems until 6 months ago...

Same problem in is new mobo. Thanks for the link. I'll run the tests
The mobo bios and SSD firmware or the drive croaking should not have a thing to do with each other.

Intel raid drive won't help a single SSD. Apples and baseballs.
 
Same thing happened to me but over the course of 2 days then it was kaput!! Luckily, it was still under warranty. It lasted 1 year after that then it was done.
 
sounds like a typical sandforce controler on its way out
backup your data and replace the drive ASAP
 
if its sandforce I have probs with it since z87. but just booting with bsod-reboot and all is ok for hours.
boots and runs well on x79
be it corsair or ocz or other is no diff.
 
Don't use HDTune with SSDs

Use Crystal Disk
 
Yeah I'm just waiting to be done with my GPU OC and monitor OC to make a image backup of Windows so I'm able to restore it later.
 
If the ssd is about to die, can it be the cause of some of the BOSDs I've been having?

(my windows install is on that ssd)
 
Certainly. What are the bsod codes? Look em up and see what it relates to.
 
Yeah I'm just waiting to be done with my GPU OC and monitor OC to make a image backup of Windows so I'm able to restore it later.
I wouldn't wait I would do it RIGHT NOW because the next boot may be the last time that drive will be accessible
 
get a new drive fast!
 
The BOSDs I was getting are the code 124. But km fairly certain it's just my overclock. Seemed stable but apparently needed a bit more voltage ok the vcore

As for the ssd, it's been doing what it's doing for like the past 8 months...

Also when I was using it on my Asus mobo, I was using an ide superspeed mode for my raid 0 drives... So the Kingston was controlled by a ide controller. This time on this msi mobo, there is no ide super speed. There is just simple ide, raid 0 and acpi or something like that...

Which I think might be the reason behind my problems. I have a feeling my 5 year old Kingston ssd might just not be compatible with this controller setting I'm using...

I'll try swapping my sata cable with my disc drive sata cable to see if the cables to blame
 
Your drive sounds as if it is dying as has been said multiple times. Back your stuff up now. You have been warned of impending drive failure. When it dies and you didn't back up well can't blame anyone but yourself. I hope for your sake a cable is all thats wrong. If not please do as been said.
 
I've done the backup, we're good. I'm gonna test the cable in a min. Meanwhile, I just got a BSOD with the following title: BAD POOL CALLER
started with a code like this: 0x000000c2 ... something like that...

is that a specific type of BSOD code?
 
so here we are, months later. still the same issue but the ssd still works.
It takes a few reboots now to detect it but then everything runs fine. I backed up everything.

My question: What kind of lifespan does a SSD drive have?
And what kind of warranties usually come with them? how many years ?
 
says here, 3 year on your drive
 
Ok guys I got some news that might help us unveil the source of the problem:

My SSD doesn't always get detected during bios boot. Sometimes I need to press the "reset" button on the PC case in order to reboot until eventually (usually now between 2 to 10 reboots) the SSD gets detected correctly and windows boots, from there (once in windows) I have no issues at all... no BSOD no disk errors... nothing

Sometimes (akward) the Kingston SSD gets detected but I still get the same bios error message (I think the message has a bunch of zeros then some text that says: boot partition missing or "couldn't find boot partition" or drive missing... can't remember exactly, I'll post back with the exact error message I get)

And after a few reboots eventually I boot into windows fine (7 64bit)

The part I understand is WHAT is causing this problem. I do not believe my SSD is going out (it's not that old and it's not been used for documents and games only windows 7 install is on it)

I did a lot of google research and found some similar cases where there are mentions of sandforce controllers being incompatible with z87-97 (but i had the same problem on my old mobo which was LGA 1156 so ...) There were also some mentions of older SSDs from 2010 and before being incompatible with new bios versions.

I suspect the firmware/controller from my SSD (V100 series from kingston) is probably incompatible with some of the newer bios versions. Which would explain why my old mobo didn't have the problem at first and I remember I started having the issue a little bit after upgrading my bios firmware on it.

Conclusion: I'm at a loss for a solution, of course I could go out and buy a new SSD and hope for the best (that the problem is only caused by the SSD and not something else) OR... and I Hate the idea of doing this: Never turning off my PC in the future until I buy a 1tb SSD (when the prices finally become more affordable).

Because as long as I don't HAVE to reboot my PC I never have to deal with all that b***s***
 
Ok guys I got some news that might help us unveil the source of the problem:

My SSD doesn't always get detected during bios boot. Sometimes I need to press the "reset" button on the PC case in order to reboot until eventually (usually now between 2 to 10 reboots) the SSD gets detected correctly and windows boots, from there (once in windows) I have no issues at all... no BSOD no disk errors... nothing

Sometimes (akward) the Kingston SSD gets detected but I still get the same bios error message (I think the message has a bunch of zeros then some text that says: boot partition missing or "couldn't find boot partition" or drive missing... can't remember exactly, I'll post back with the exact error message I get)

And after a few reboots eventually I boot into windows fine (7 64bit)

The part I understand is WHAT is causing this problem. I do not believe my SSD is going out (it's not that old and it's not been used for documents and games only windows 7 install is on it)

I did a lot of google research and found some similar cases where there are mentions of sandforce controllers being incompatible with z87-97 (but i had the same problem on my old mobo which was LGA 1156 so ...) There were also some mentions of older SSDs from 2010 and before being incompatible with new bios versions.

I suspect the firmware/controller from my SSD (V100 series from kingston) is probably incompatible with some of the newer bios versions. Which would explain why my old mobo didn't have the problem at first and I remember I started having the issue a little bit after upgrading my bios firmware on it.

Conclusion: I'm at a loss for a solution, of course I could go out and buy a new SSD and hope for the best (that the problem is only caused by the SSD and not something else) OR... and I Hate the idea of doing this: Never turning off my PC in the future until I buy a 1tb SSD (when the prices finally become more affordable).

Because as long as I don't HAVE to reboot my PC I never have to deal with all that b***s***
buy a better SSD preferably something not sandfarce based
the problem is indeed the drive or rather kingstons choice of controler
 
Back
Top