SSD or system problem??
 

here's my story:

I bought a Corsair Force GT solid state drive 120gb becuz i wanted a faster loading windows n programs. I installed windows 7 and all the programs and everything went smooth. the next morning when i turned on my comp i get a message saying "windows failed to start" with an error code "0xc000000f".

when i checked my bios it did not detect the ssd at all. I unplugged my ssd and plugged it on a different sata port. It worked again for awhile. then one day i turned on my PC and bam, it gave me the error again and BIOS couldnt detect the ssd. had to unplug and replug the ssd in order to work.

anyone have an idea why this is happening?

this is my PC build:

ASUS Maximus Gene III mobo
Intel core I5 960
8gb G skill ripjaw ram
ATI Radeon 6850 x2 crossfire
OCZ Vertex 2 ssd 60gb
WD 640gb black caviar Harddrive
Corsair Force GT ssd 12gb (this is the ssd with the problems)
Corsair 750w power supply

Could be a defective cable. I have seen that quite a bit, oddly

Also check for a firmware update

i dont think its a cable issue. i bought a patriot pyro ssd before my corsair and it did the same problem even with a new sata cable. i thought i just had a defective ssd but i dont think its an ssd problem at all.

its the SSD i have the exact same problem a week ago i have the vertex 1 60gb
sent it back to OCZ for a refurb one .. installed window on another HD and everything was fine

it died pretty fast... had it for less then a year .. another buddy of mine had his died a month before me

i guess there's some truth to the recent findings that Intel drives provides the greatest compatibility and stability?

or it could be your windows that is not genuine :D

i think it may be a power supply issue. It just happened again awhile ago and both my SSD were not read in BIOS. I currently have my system overclocked along with the voltage settings. Ive put it back to stock form. I will monitor it to see if it still does it or not.

blah okay so i reinstalled windows on the the new SSD OCZ sent me and the same problem occurred...

this is weird that on a normal HDD everything is fine but when I install the OS on the SSD it just stops working ..
i tried changing the sata cable and plugging it in diff ports on the MB and still no luck ..

what kind of error do you get? i get this error:

http://www.techyv.com/sites/default/...a%20D./IMG.JPG

Hm, northbridge/southbridge chipset issues?

My Intel 320 120GB SSD is rock-solid on my Z68-based board.

I bet you switched your HDD mode from AHCI to IDE or vice versa. Check

i did but isnt IDE the recommended setting for ssd drives?

I've used AHCI with no problems. Thought IDE prevented TRIM firmwares from working properly?

If you switch back and forth between AHCI and IDE without reinstalling you'll get that issue. Same goes for traditional drives. The two modes address differently so you'll have to use a tool for MBR repair to get windows to recognize that you've changed things. Otherwise it just assumes that the hardware has changed and has no clue where to boot from. If that's the case you could use a usb linux distro to take care of it such as PartitionMagic.

okay this is weird... i took out one stick of ram and now the bios detects the SSD everytime and boots in to it without crashing when theres heavy workload..

could it be a faulty ram stick so when i install the OS on to the SSD it crashes due to limited ram space and there isn't enough virtual memory on the SSD for the computer to work?

but this doesn't explain why the bios didn't detect the SSD in the first place

Upgrade your BIOS. Switch to AHCI mode at least. I run mine in RAID mode because I had a RAID0 before. Install latest chipset driver. Upgrade SSD firmware.

Also, from what I've read so far, there's some issues with Sandforce SSD controllers and ASUS motherboards.

IDE is absolutely the INCORRECT setting to use for SSD and any modern hard drive made in the last 5 years.

My Kingston 128 GB just died. off to RMA it goes. 6 months of use only and light use...sad.

AHCI mode gives the ability to use "Native Command Queuing", which is a HUGE benefit to SSD's.

But the TRIM command works just fine in IDE mode.

i tried unplugging some harddrives i have and my SSD was detected no problem..

i am starting to think its my PSU getting weaker or something

ive been having no problems with my SSD ever since i reverted back from overclocked setup to stock setup. i figured it was a PSU problem for me since i tweaked my voltage.

This thread reminds me of the SSD Hot/Crazy scale: Coding Horror: The Hot/Crazy Solid State Drive Scale

whats the watt on ur pSU? i have a 650w it should be more then enough for this rig ..

SSDs use like 2 watts.

okay so i'm really confused. ..

i unplug most of my harddrives and system still bluescreen and crashed and didn't detect the SSD after the reboot

i'm starting to think its the motherboard crapping out now

dude, just stick in a conventional HDD with a OS on it. if that works fine, then you know it's probably just the ssd. or stick the ssd into another computer and if it works fine, you know it's not the ssd.


sorry to jack the thread, but my seagate 7200.11 main O/S drive just completely crapped out yesterday (known firmware issue, RMA time), and now im probably gonna go get a SSD.

shit like this thread is scaring me. Im reading about so many damn failures.

I was looking up most reliable ssd's and came across INTEL and CRUCIAL. i'd take reliability over speed any day...

anyways.. is this shit really that common? my mobo bios isnt upgraded to the latest version (p6t deluxe stock from 2008), and if this ssd is gonna be more of a headache than anything else i might as well get a conventional hdd instead. what do you guys think? i was gonna get a 120-128gig ssd for my O/S.

i have no idea what AHCI and all that crap means either. if it isnt something i can just plug and play like a conventional hdd, it's probably gonna be a headache right?