The Corsair User Forums  

Go Back   The Corsair User Forums > Corsair Product Discussion > Solid State Drives (SSD) > SSD Firmware Update

Notices

Closed Thread
 
Thread Tools Search this Thread Rate Thread Display Modes
  #1  
Old 09-30-2011, 05:04 PM
Yellowbeard's Avatar
Yellowbeard Yellowbeard is offline
Corsair Tech Mktg
 
Join Date: Oct 2002
Location: Atlanta,GA, USA.
Posts: 11,208
POST ID # = 531319
Yellowbeard Reputation: 45
Send a message via AIM to Yellowbeard
Default Force Series 3 and Force GT Firmware Update Ver 1.3.2

Corsair Force Series 3 / Force GT Firmware Update Instructions

Here is the Force Series 3 and Force GT 1.3.2 firmware update. Please carefully and completely read the following before you attempt to update your firmware.

IMPORTANT NOTES BEFORE BEGINNING YOUR UPDATE


If you are stable and do not have issues, we suggest that you do not flash your firmware.

This update is intended to not be destructive. However, we strongly urge that you back up any important data before beginning this procedure.

This update has been validated for use with Windows 7. It has not been validated with Windows Vista and Windows XP however it may work with these OS's. Users are encouraged to update the drives with Windows 7 when possible.

This update tool is intended to be run with the drive controller in AHCI mode. If your drive controller is not AHCI enabled and your update fails, you will need to change it to AHCI mode and also enable AHCI in your OS registry. Here is page with a guide for ENABLING AHCI.

AMD USERS TAKE NOTE: If you have issues updating using the Microsoft AHCI driver, you may need to update using the latest driver from your drive controller manufacturer. The opposite may also apply on some boards. If you fail to update using the driver from the drive controller manufacturer, you may need to update using the MS-AHCI driver.

Our latest testing shows that this update will not work using a Marvell controller. Some users have reported that they cannot update with other controllers. Our internal validation has been done only with the AMD and Intel controllers. Operation on other controllers cannot be guaranteed.

If your update fails using the Marvell controller, you will need to update using the chipset based drive controller on your motherboard. This applies to SATA2 and SATA3 controllers.

DO NOT at any time power off your system during this procedure.
This may “brick” your drive. After your update if you still have issues, we strongly recommend the following steps:


1. Complete clearing of the BIOS. This is a good idea after any firmware flash of any device.

2. Secure erase the SSD. For some users, cloning of the drive works, for others it does not. This may be dependent upon the cloning tool used.

3. A clean installation of the OS if you experience instability after a BIOS clearing and secure erase.

UPDATE YOUR BIOS. As always for users with issues, we recommend that you update your motherboard/notebook to the most recent BIOS before attempting to flash your firmware. This may or may not resolve your issue but it is an excellent first step. Quite a few boards/notebooks have been given SSD specific updates over the past few months.

We have seen no issues updating directly from 1.2 to 1.3.2.

Ignore any terms in the firmware file name relating to Micron, Intel, etc. This has no bearing on the upgrade. You need only match the SIGNATURE as noted in the .PDF file.

Be sure to download the correct version for your drive. We have had people complaining that our files are wrong only to find that they downloaded the wrong file.

__________________
Follow me on Twitter: XMSYELLOWBEARD

Make friends on Facebook: XMSYELLOWBEARD

Last edited by Yellowbeard; 10-06-2011 at 04:21 PM.


Did you find this post helpful? Yes | No
  #2  
Old 09-30-2011, 05:29 PM
Yellowbeard's Avatar
Yellowbeard Yellowbeard is offline
Corsair Tech Mktg
 
Join Date: Oct 2002
Location: Atlanta,GA, USA.
Posts: 11,208
POST ID # = 531325
Yellowbeard Reputation: 45
Send a message via AIM to Yellowbeard
Default

Please note that Corsair is closed on weekends. We'll be back Monday.

Due to NDA there is only 1 change log item available.

1. “Fix an issue where SMART attribute 194 erroneously reported 128C instead of 30C when no temperature sensor was present”.
__________________
Follow me on Twitter: XMSYELLOWBEARD

Make friends on Facebook: XMSYELLOWBEARD

Last edited by Yellowbeard; 09-30-2011 at 05:47 PM.


Did you find this post helpful? Yes | No
Closed Thread

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -5. The time now is 10:51 AM.


Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.