Jump to content
Corsair Community

F120 SSD Random Kernel-Power 41 BSOD; Not Detected on Boot


Recommended Posts

  • Replies 623
  • Created
  • Last Reply

Hey Guys

 

I have an AMD System and if Trim is enabled the system reboots in idle....

Then it hangs and the Controller didn´t find the Corsair SSD...........

I turn off the Computer and on again then works fine.

 

I tried the Gigabyte AHCI Sata Driver, then it works without reboots and without trim too :(

now i am using the msahci driver and without Trim it works fine.

 

Sorry for my english, i hope you guys find a way too fix that Problem quickly..

 

How long did the Corsair Force Series Work nice without trim ??

Link to comment
Share on other sites

i'm not waiting anymore, i'll take my loss and trash the drive.

this takes too long and corsair has no longer my money on new products.

 

i'm out, trash my account please

also i'll be sending back my drive to you with a notice to get my money back from you.

Link to comment
Share on other sites

Xenn0x come on man... Why not send Corsair your drive or at the very least RMA it? Don't give up, I'm sure there will be an update for us soon.

 

I've had zero issues since I turned Trim off and it has been 2 weeks now. All I need is a firmware upgrade so I can go ahead and turn it back on.

Link to comment
Share on other sites

so... Has corsair been able to reproduce the issue?
Weekend = no response until Monday.

 

 

i'm not waiting anymore, i'll take my loss and trash the drive.

this takes too long and corsair has no longer my money on new products.

 

i'm out, trash my account please

also i'll be sending back my drive to you with a notice to get my money back from you.

Account locked per request. IIRC only the store can refund you as that's where you bought it from. Corsair can only RMA it, but I'm not sure if you've tried that route yet.
Link to comment
Share on other sites

Great. After just over 2 weeks of working great I came home to find a nice big 0x0000007A blue screen of death and NTFS.SYS as the culprit. So just like Xenn0x and with Trim disabled the drive still messed up. Just rebooting didn't help, the Corsair F120 is totally missing from the list.

 

A full power off and power on put the Corsair back in the BIOS HDD list.

 

So what I did is set my integrated SATA2 JMicron controllers to AHCI only instead of AHCI + IDE. Hopefully that will help. I'll report back here when and if something happens again.

 

Trim is still disabled.

Link to comment
Share on other sites

azraelsk: trace your package, have they received it?

 

I don't know, i sent the package last tuesday (10th of August) to Corsair in Netherlands, from there it should be sent to USA Office for RamGuy. It was delivered 22 hours later to Corsair Netherlands (got delivery report from the german postal service). I don't know how long it takes to send the package from Netherlands to U.S. West Coast (Fremont, CA), but i think it should be there now.

 

I wonder why they are so quiet about it. Maybe they are aware of the problem and mass recall would be a massive loss?

 

I think, they don't know what is the error's cause exactly yet. We can speculate about this cause, but Corsair can't do this: A "Hey guys, the SSDs are currently unreliable and we don't know why" would be more reputation loss than giving a error description with patch. A mass recall is unlikely, because the error is unpleasant, but not critical. The BSOD occurs afaik only in idle mode, when the SSD is inactive - the probability of file system damage und data loss is in my opinion very small. I had a dozen of BSODs, the SSD is the system drive... file system is okay and fully operational. I cloned it to HDD before i sent the SSD to corsair, no issues and BSODs.

Link to comment
Share on other sites

Well, I've loaded Win 7 - 32-bit on a Gigabyte EP45-UD3P test system. With a fresh load of windows and the ForceTrim program, I cannot re-create your error. No other drivers / programs loaded. Just load Win 7 and test.

 

Mind you, I've had my own issues with this drive: http://forum.corsair.com/v3/showthread.php?t=88741

 

I've let it idle for 12 hours and no crash....I'll test Win 7 x64 and see if this is a key element to the problem......

 

Based on my experience, these drives appear to get in a "bad" state and cause problems...such as my experience cloning the drive and yours with the TRIM command crashing the system. One thing seems consistent, the drive disappears and does not respond to commands under certain conditions with ICH10R. That is a common issue between both of our problems. However, my issue would not clear with any power down / reboot. I had to physically reformat, delete partitions through a USB->SATA adapter to get things recognized back on ICH10R.

 

Anybody having the TRIM command issue and not using an Intel ICH10R south bridge?

 

Chris V.

Link to comment
Share on other sites

  • Corsair Employees

We understand that people are getting impatient on this issue, and I’m sorry we have not been able to provide a solution yet. Let me give you a summary of what we currently know.

 

First of all, we have received enough drives back to perform some meaningful analysis, and we have, in fact, been able to re-create this failure mode. However, drives that fail on a problem system work fine on other systems. It appears to be some sort of compatibility issue that only appears on a very rare combination of hardware and software.

 

We have been spending lots of time in the lab trying to find out what causes the failure mode – I/O driver, motherboard manufacturer, CPU, PSU, OS version and settings, SSD firmware, etc. There are lots of variables, and we have not been able to determine yet what causes (or, what fixes) this issue.

 

We have been in close contact with Sandforce, and they are working on this issue as well. We have sent entire platforms to motherboard vendors to get their assistance on the problem. This is a compatibility problem and appears to affect a very small percentage of systems; the scarcity of the problem makes it very elusive and time consuming to resolve.

 

If we had a firmware version that appeared to solve the problem, we would certainly offer it here. But we do not want to do so until we can confirm that it improves things (and, in fact, does not make them worse).

 

We understand that it is extremely frustrating to experience problems like this on performance hardware. And, we understand that lack of information is equally frustrating. So, we will start posting a regular status update here on what progress we are making.

 

We certainly appreciate your patience, and are working hard to resolve this issue!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • Create New...