Force Series 3 Users Having Issues with a Replacement Drive READ HERE PLEASE

Yellowbeard · #1 06-28-2011, 09:25 PM

Please read this ENTIRE post carefully before you post a reply. If you have a Force Series 3 120 GB SSD beginning with a serial # of 1122 or earlier, you need to RMA your drive. This RMA notice does not apply to Force GT, Force Series 3 240 GB, or Force Series 3 60 GB.

This thread applies to:

1. Users with issues after receiving a replacement Force Series 3 120 GB SSD (serial # 1123 or later).

2. Any user having issues with a Force Series 3 120 GB SSD beginning with serial # 1123 or later. Note, this is the serial number from the label only, NOT the digital serial number. The digital serial number has no relation to the firmware or this issue.

3. Any user having issues with a Force Series 3 SSD.

We are currently working with SandForce and in our lab to isolate issues that some users are seeing with Force Series 3 120 GB SSDs beginning with serial # 1123 or later. Here is what we have found so far and what we can recommend at this point for those users having issues. Most users are not having issues at this time so, please read carefully.

1. Some users have reported that they initially had problems with their drive dropping out, blue screening or freezing. Replacing the SATA cable with a better quality cable has in some cases resolved this.

2. Some users have reported that they initially had problems with their drive dropping out, blue screening or freezing. Replacing the SATA cable with a shorter cable has in some cases resolved this.

3. Some users have increased their stability (on P67, H67, and Z68 chipsets) by increasing their PCH voltage from the stock setting up to 1.15v. We do not recommend going past this voltage and you should consult your motherboard manual before making any adjustments with which you are not familiar.

4. Some users having motherboards with multiple SATA controllers have been able to gain stability by switching from 1 SATA controller to the other. This may mean switching from a secondary controller to the chipset based controller. For example, an Intel X58 board with an ICH10-R controller may also have a Marvell SATA3 controller.

5. Some users with boards showing instability with the chipset SATA3 controller have found stability by switching to the chipset SATA2 controller or a secondary controller.

6. If you have had a failed OS installation, repeated BSODs or other failures, or if you have had severe instability, we strongly recommend a secure erase before reinstalling the OS. Parted Magic is good for this.

At this point, these are the recommendations we have for users having the issues described above. We are in close and constant contact with SandForce and we are attempting to resolve this. Again, keep in mind that in most of these cases, the Force Series 3 SSD is functional and will work in some capacity as the issue seems to be platform related. Therefore, an RMA will most likely not resolve this if you have an otherwise working drive.

Sector7g · #2 06-28-2011, 09:55 PM

I am having issues with my 1124 variant.

I have tried installing in ide/achi/raid (but not set up in the raid bios)

I have tried it as the only drive

I have tried x64 and x86

It will load files do the 1st reboot, but will not load any further due to files missing or corrupt.

I have been able to install win7 x86 and x64 using 500 gb seagate 7200.4

I am tring to install it in a MSI GT780R notebook

I will now try the wipe as suggested above, It will need to be place in a external enclosure 1st.

I will report back to see if it helps.

Using Acronis True Image Home

6 hours for a security wipe (ouch)

Not have my new laptop for 2+ days now (double ouch)

MrNobodyWTB · #3 06-28-2011, 11:09 PM

The first drive received was a 1121 variant. My RMAd drive is a 1124 variant and I am still having bsod issues. Albeit not as frequently, but I've still had 4 in the past 5 hours.

Does the Force GT really not have this issue? I do not mind at all returning the force 3 and getting a Force GT if it gets rid of the mystery bug (the claims are stating that the problem lies in in sandforce drivers, so how can the force gt be devoid of this problem if it uses the same sf2###?

Wardrop · #4 06-29-2011, 02:03 AM

I have a Corsair Force 3 120GB drive which starts with serial 1124 (on the box and printed on the device) and am having problems exactly as described for the 1122 drives. BSOD every hour or two due to the SSD dropping out. Must actually power off the computer in order for the drive to be detected on next boot.

The only suggestion in the original post that may be applicable is point #6, although this is a brand new drive as of today so I don't understand how a secure erase could help. The computer is a Dell Optiplex 960 so it's got an Intel motherboard.

NOTE: I also have doubts over the reliability of the sticker on the box and the drive. My digital serial number begins with 1122 and while you've explicitly mentioned to ignore this in your original post, it would be nice if their was a way to query the device to determine whether it's faulty or not. I've never seen a device that has a similar but slightly different serial number printed on the box/device than what's actually reported by the device digitally. The number are virtually identical, except one begins with 1124 and one with 1122. It's not very comforting when you're trying to determine whether you have a faulty device or not (it's clearly faulty, but you know what I mean).

robertomad · #5 06-29-2011, 03:45 AM

I think it has something to do with the firmware detecting the current on the ssd. And even the temp is showing the highest on the sensors. Today is the day of the RMA pickup but I'm still reluctant for this as I really like the SSD and I'm sure it's only a firmware issue.

Max_from_Italy · #6 06-29-2011, 10:24 AM

I have a ssd corsair force3 120 gb replaced with rma with serial number 1124 on the box.
I have assembled the pc with mobo asus p8h67 m age + cpu intel i5 2500k + 4 gb ram g.skill.
I have installed windows 7 ultimate 32 bit on hdd wd 1tb and update with sp1 and there are no problems.
I have installed windows 7 ultimate 32 bit on ssd corsair force 3 120 gb and update with sp1 and they occur problems of freezingion with any application.

Connecting ssd force3 to the controller sata II all works without problems.

To leave force 3 connected to the controller sata III i should plan the tension PCH from 1.05 to 1.15 V: is it sure or do they race him some risks for the components of the pc?

Will Corsair release an up-to-date firmware to resolve the problem?

longroadtrip · #7 06-29-2011, 11:33 AM

Replacement drive having all of the problems described. Tried everything but moving to SATA II. Guess that's the only option left.

In case it is not stable, since I RMA'd the drive through Corsair, I cannot return it to the retailer. Will Corsair be offering refunds? EDIT: Or even better yet, a discount and trade in for a 240 Gb or GT?

I know you guys are working hard to resolve the issue with SandForce, however, my work is now suffering as I am having to deal with this issue and can't code on an unstable system. This has cost me more than 20 hours in working on this system between replacing drives, re-installing OS and software, re-configuring, etc. In other words, my $220 drive has cost me close to a $1000 in time that could have been used working for clients.

Isto · #8 06-29-2011, 12:06 PM

I also have a new drive 1123xx that is having the same issues listed above now after working ok for the first 2-3 days. I have tried all the other SATA 6gb cables I have from the motherboard and other components as well as 3gb cables to no effect. The PCH voltage didn't work either as the drive just dropped out of BIOS again. I am now on an SATA II connection and will see if that lasts until an resolution is reached. I can't get a refund from the retailer and it would be be pretty lame if it has to be on sata2 to work. :(

Yellowbeard · #9 06-29-2011, 12:40 PM

Quote:

Originally Posted by Wardrop

NOTE: I also have doubts over the reliability of the sticker on the box and the drive. My digital serial number begins with 1122 and while you've explicitly mentioned to ignore this in your original post, it would be nice if their was a way to query the device to determine whether it's faulty or not. I've never seen a device that has a similar but slightly different serial number printed on the box/device than what's actually reported by the device digitally. The number are virtually identical, except one begins with 1124 and one with 1122. It's not very comforting when you're trying to determine whether you have a faulty device or not (it's clearly faulty, but you know what I mean).

It's been repeated multiple multiple times. The digital serial number has NOTHING to do with this issue and relates to an entirely different phase of the manufacturing process involved.

Yellowbeard · #10 06-29-2011, 12:44 PM

THIS THREAD may be useful to some.

Sector7g · #11 06-29-2011, 01:05 PM

Just to update on the security sweep

It did complete, (I noticed an error that it was unable to read a specific sector 2 thousand something)

I tried to reinstall windows, it did get a little further, started to install after the 1st rebot, but still failed to load beacuase system registry file is missing or corrupt.

Yellowbeard · #12 06-29-2011, 01:19 PM

If you have not done so, please try a secure erase.

Sector7g · #13 06-29-2011, 01:21 PM

security sweep = secure erase.

Yes I have done this

Yellowbeard · #14 06-29-2011, 01:29 PM

What utility did you use to perform the secure erase?

Ekens · #15 06-29-2011, 01:37 PM

Not sure if it's any help, but I can add some information aswell.

My system is working great except some partial freezing. These freezes last for 1min and approx 1-2 times a day. I call it partial freeze because the mouse pointer is still working but the computer is not responding. After 1 min the freeze resolve itself and all stuff I have been clicking on during the freeze opens/close.

Otherwise stable for 2-3weeks now.
#1124