Jump to content
Corsair Community

Performance 3 series P3-128 - Freezing up


timpayne

Recommended Posts

Hi,

 

Now I set up this computer last February and it worked great for 6 months. My computer started to freeze when doing normal operations. The computer would be frozen and the HDD light would be a solid light. This freeze would sometimes recover after 10-15mins but most of the time the freeze was indefinite. I tried many things that I found from google including re-installing windows, this had no effect and within 30 mins of the computer being up after the windows re-install the SSD would freeze again.

 

I RMA'd the SSD back to the supplier (http://www.scan.co.uk) and they sent me my replacement drive, they also reported that the drive i sent back failed the generic SSD test so there was a fault with it. I reinstalled everything on the drive and it seemed to work great again..... for 4 days! On the 5th day the freezing started again! So I thought it must be the same problem (faulty drive) I returned the drive to scan once again but this time it passed the SSD tests!

 

I am scratching my head, why did this work for 6 months but now it just keeps freezing? I didnt update any firmware or anything to kick off this issue.

 

Can anyone suggest ways in which to get this drive to work? Is this a common problem on these drives?

 

I have also looked for a firmware upgrade for the drive but it seems there are none available.

 

I want this nightmare to be over! I have been without a computer for a month now!

Link to comment
Share on other sites

Since your replacement started acting up there might be a problem with the drives interaction with your system ( no idea about the reason ). You can try a number of steps:

- update the BIOS for your motherboard ( http://www.gigabyte.com/products/product-page.aspx?pid=3762#bios )

- install a newer IRST ( if you are using it - http://www.gigabyte.com/products/product-page.aspx?pid=3762#driver - Intel Rapid Storage Technology )

- apply the LPM fix ( http://forum.corsair.com/v3/showthread.php?t=96663 - AFAIK this has effect only if you are using IRST )

- uninstall IRST and let Windows use its default MsAHCI driver

- change SATA cable

- change power cable

Link to comment
Share on other sites

Ok I have done those steps, system "seems" a lot more stable. Will see how it goes over the next few hours.

 

Just wondering though, as I haven't change any of these settings since Feb, why have they suddenly stopped working?

 

Thanks

 

Is your SSD full? Maybe you should erase some data from the disk

Link to comment
Share on other sites

Ok very strange, I disconnected the power and attempted to start it up again, I noticed it said "SMART Command Failed" on the SSD on start up and then failed to find the boot drive.

 

I went into the BIOS and disabled SMART HDD. It now boots fine.

 

WTF is going on?

Link to comment
Share on other sites

Final update from todays findings is that the SSD is now not showing up on boot! it doesnt appear on the list.....

 

I would like some answers from a Corsair rep please as this is driving me insane.

 

Enabled TRIM?

Updated BIOS?

Have you tried to opened from an earlier setpoint?

I`ve no other options to give you. Hope you sort it out. GL

Link to comment
Share on other sites

http://forum.corsair.com/v3/showthread.php?t=86403

 

U maybe need to this from SAFE MODE if windows doesn`t start.

 

 

Ok thanks, I am off to buy a new HDD just so that I can install windows to it and then do a full format of my SSD drive.

 

Once all that is done I will enable Trim and see how I get on.

 

Thanks for your help, I am praying this is going to work!

Link to comment
Share on other sites

Ok thanks, I am off to buy a new HDD just so that I can install windows to it and then do a full format of my SSD drive.

 

Once all that is done I will enable Trim and see how I get on.

 

Thanks for your help, I am praying this is going to work!

 

Do perform a clean windows install when using a ssd. the P3 do NOT have any FW update and therefor is easy to handle. Enable TRIM and Bios settings in AHCI mode. Good luck.

Link to comment
Share on other sites

Do perform a clean windows install when using a ssd. the P3 do NOT have any FW update and therefor is easy to handle. Enable TRIM and Bios settings in AHCI mode. Good luck.

 

Did all of the required and then came to tun on TRIM, by default it seems to be on, so I am worried this install is just going to die soon.

Link to comment
Share on other sites

Ok, so I did everything I should do....

 

* Secure erase the SSD

* Installed the latest IRST drivers

* Re-installed windows

* Ran the LPM reg fix

* Enabled TRIM

* Updated windows to the max

 

It was fine for 24 hours although it did BSOD during one of the windows updates, the computer restarted and came back normally. I then left the computer on over night downloading. When i came to sit at the computer this morning I moved the mouse to reactivate the display and saw the screen come up for about 10 seconds, my IRC app had been running all night and then suddenly I get a BSOD. The computer then restarted and couldn't detect the drive. I unplugged the computer for 5mins and then started it back up again, I now see the SSD on start up but get BOOT DISK FAILURE again.

 

I seem to be getting all the issues that the Force drives seem to get but there is no FW update for my drive!

 

I am going to install windows to the HDD and run my computer on that for the time being as I cant afford to not have a working computer any longer.

 

Does anyone from Corsair care to comment? I haven't had a single reply from any of the reps. Do I now wait untill corsair get this fixed? Any ideas how long this will take? Or do I just get a refund and buy a different SSD?

Link to comment
Share on other sites

Hi,

I have excatly the same problem. My Performance 3 128 just freeze after every reboot. The disk works fine for 6 months but today I can't work with it anymore. I also attached the SSD to another PC but chkdsk freezes there too. :(

 

This is the output of smartmontools:

 

smartctl 5.41 2011-06-09 r3365 [i686-linux-3.0.0-pmagic] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF INFORMATION SECTION ===
Device Model:     Corsair Performance3 SSD
Serial Number:    REMOVED
LU WWN Device Id: 5 000000 000000000
Firmware Version: 1.0
User Capacity:    128,035,676,160 bytes [128 GB]
Sector Size:      512 bytes logical/physical
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   7
ATA Standard is:  ATA/ATAPI-7 T13 1532D revision 4a
Local Time is:    Sun Sep 25 12:30:15 2011 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status:  (0x00)	Offline data collection activity
				was never started.
				Auto Offline Data Collection: Disabled.
Self-test execution status:      (   0)	The previous self-test routine completed
				without error or no self-test has ever 
				been run.
Total time to complete Offline 
data collection: 		(   10) seconds.
Offline data collection
capabilities: 			 (0x15) SMART execute Offline immediate.
				No Auto Offline data collection support.
				Abort Offline collection upon new
				command.
				No Offline surface scan supported.
				Self-test supported.
				No Conveyance Self-test supported.
				No Selective Self-test supported.
SMART capabilities:            (0x0002)	Does not save SMART data before
				entering power-saving mode.
				Supports SMART auto save timer.
Error logging capability:        (0x00)	Error logging supported.
				General Purpose Logging supported.
Short self-test routine 
recommended polling time: 	 (   2) minutes.
Extended self-test routine
recommended polling time: 	 ( 100) minutes.
SCT capabilities: 	       (0x003d)	SCT Status supported.
				SCT Error Recovery Control supported.
				SCT Feature Control supported.
				SCT Data Table supported.

SMART Attributes Data Structure revision number: 1
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
 1 Raw_Read_Error_Rate     0x0003   100   100   044    Pre-fail  Always       -       0
 3 Spin_Up_Time            0x0003   100   100   000    Pre-fail  Always       -       0
 4 Start_Stop_Count        0x0002   100   100   020    Old_age   Always       -       0
 5 Reallocated_Sector_Ct   0x0003   100   100   036    Pre-fail  Always       -       0
 9 Power_On_Hours          0x0002   100   100   000    Old_age   Always       -       378
10 Spin_Retry_Count        0x0003   100   100   097    Pre-fail  Always       -       0
12 Power_Cycle_Count       0x0002   100   100   020    Old_age   Always       -       866
178 Used_Rsvd_Blk_Cnt_Chip  0x0003   100   100   010    Pre-fail  Always       -       1
187 Reported_Uncorrect      0x0002   100   100   000    Old_age   Always       -       1
190 Airflow_Temperature_Cel 0x0002   100   100   045    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0002   100   100   000    Old_age   Always       -       0
193 Load_Cycle_Count        0x0002   100   100   000    Old_age   Always       -       0
194 Temperature_Celsius     0x0002   100   100   000    Old_age   Always       -       0
195 Hardware_ECC_Recovered  0x0002   100   100   000    Old_age   Always       -       0
197 Current_Pending_Sector  0x0002   100   100   000    Old_age   Always       -       0
198 Offline_Uncorrectable   0x0000   100   100   000    Old_age   Offline      -       0
199 UDMA_CRC_Error_Count    0x0002   100   100   000    Old_age   Always       -       0

SMART Error Log Version: 1
Warning: ATA error count 0 inconsistent with error log pointer 4

ATA Error Count: 0
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.

Error 0 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
 When the command that caused the error occurred, the device was in an unknown state.

 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 04 00 40 60 6b b2 00  

 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
 -- -- -- -- -- -- -- --  ----------------  --------------------
 00 47 40 60 d6 9a 00 7c  39d+05:32:16.256  NOP [Reserved subcommand]
 00 04 40 60 ca 9a 00 44  25d+00:45:18.720  NOP [Reserved subcommand]
 00 04 40 60 35 83 00 43  39d+05:40:54.400  NOP [Reserved subcommand]
 00 86 40 60 29 83 00 ab  47d+04:19:15.584  NOP [Reserved subcommand]
 00 00 00 03 00 00 00 00   9d+21:58:22.976  NOP [Abort queued commands]

Error -1 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
 When the command that caused the error occurred, the device was in an unknown state.

 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 60 00 88 6b 00 00 00   at LBA = 0x0000006b = 107

 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
 -- -- -- -- -- -- -- --  ----------------  --------------------
 40 61 e5 53 00 00 00 40      19:52:41.952  READ VERIFY SECTOR(S)
 08 61 44 3c 00 00 00 40      15:14:03.432  DEVICE RESET
 00 60 af 24 00 00 00 40  46d+12:01:24.488  NOP [Reserved subcommand]
 08 60 a3 24 00 00 00 40  17d+17:41:31.976  DEVICE RESET
 08 03 00 00 00 00 00 00  19d+16:00:37.952  DEVICE RESET

Error -2 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
 When the command that caused the error occurred, the device was in an unknown state.

 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 0d 4f 00 00 00 00 00

 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
 -- -- -- -- -- -- -- --  ----------------  --------------------
 58 06 02 00 00 40 c0 55  18d+16:33:50.662  [RESERVED]
 b0 ee 01 00 00 08 08 b4  18d+16:33:31.994  [Vendor specific SMART command]
 b0 d7 01 00 00 08 08 13  18d+16:33:31.994  SMART WRITE ATTRIBUTE THRESHOLDS [NS, OBS-4]
 b0 bf 01 00 00 08 28 70  18d+16:33:31.994  [Reserved SMART command]
 b0 00 00 00 00 08 20 00  18d+16:33:31.994  [Reserved SMART command]

Error -3 occurred at disk power-on lifetime: 768 hours (32 days + 0 hours)
 When the command that caused the error occurred, the device was in an unknown state.

 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 00 00 00 00 00 00 00

 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
 -- -- -- -- -- -- -- --  ----------------  --------------------
 13 00 00 80 08 98 5a 01  32d+14:03:05.664  RECALIBRATE [RET-4]
 13 00 00 80 08 98 5a 01  28d+00:05:48.224  RECALIBRATE [RET-4]
 13 00 00 80 08 98 5a 01  23d+09:47:45.600  RECALIBRATE [RET-4]
 13 00 00 80 08 98 5a 01  18d+19:40:38.336  RECALIBRATE [RET-4]
 13 00 00 80 08 98 5a 00  14d+05:31:20.000  RECALIBRATE [RET-4]

Error -4 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
 When the command that caused the error occurred, the device was in an unknown state.

 After command completion occurred, registers were:
 ER ST SC SN CL CH DH
 -- -- -- -- -- -- --
 98 31 5a 13 40 60 a7

 Commands leading to the command that caused the error were:
 CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
 -- -- -- -- -- -- -- --  ----------------  --------------------
 1a 98 5a 13 40 60 06 08  24d+20:31:23.649  RECALIBRATE [RET-4]
 f9 1e 65 05 40 60 51 08  24d+20:31:23.648  [Reserved SET MAX command]
 e1 1e 65 05 40 60 af f8   5d+01:10:07.616  IDLE IMMEDIATE
 ca d8 44 03 40 61 0d f0   5d+01:10:07.616  WRITE DMA
 00 00 00 00 00 03 00 00   1d+13:16:57.728  NOP [Abort queued commands]

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Short offline       Completed without error       150%         0         -
# 2  Short offline       Completed without error       150%         0         -
# 3  Short offline       Completed without error       150%         0         -
# 4  Short offline       Completed without error       150%         0         -
# 5  Short offline       Completed without error       150%         0         -
# 6  Short offline       Completed without error       150%         0         -
# 7  Short offline       Completed without error       150%         0         -
# 8  Short offline       Completed without error       150%         0         -
# 9  Short offline       Completed without error       150%         0         -
#10  Short offline       Completed without error       150%         0         -
#11  Short offline       Completed without error       150%         0         -
#12  Short offline       Completed without error       150%         0         -

Device does not support Selective Self Tests/Logging

 

Any suggestions?

Link to comment
Share on other sites

Hi,

I have excatly the same problem. My Performance 3 128 just freeze after every reboot. The disk works fine for 6 months but today I can't work with it anymore. I also attached the SSD to another PC but chkdsk freezes there too. :(

 

 

Any suggestions?

 

I have PMd yellowbeard to bring his attention to this thread. See what he comes up with.

 

Thanks

Link to comment
Share on other sites

I also have freeze problems with my p3-128 from time to time...I bought it 5 months ago and since then i had to format the ssd (parted magic) 3 times already - it is the only way to "kill-delay" the freeze's for one month or so. I did everything the most of you did -

* Secure erase the SSD

* Installed the latest IRST drivers

* Re-installed windows

* Ran the LPM reg fix

* Enabled TRIM

* Updated windows to the max

and nothing helped.....

Hope someone from the forum knows what to do...

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...