Force Series 2.0 After the Update

[mikek70]

The 2.0 firmware update did not resolve my BSODs waking up from S3. The PC will show the login screen and even allow me to log in if I am fast enough, but after a few seconds, the BSOD occurs. Corsair F120 was shipped with firmware version 1.1, update to 2.0 went smoothly, but did not resolve the problem.

 

Motherboard Gigabyte GA-EX58-UD5 BIOS Version F13j

Processor Intel i7-920

Memory Corsair TR3X6G1600C8, 3x2GB, DDR3-1600, CL8@1.65V

Video Card Sapphire HD 4870 1GB Vapor-X, PCI-E 2.0 x16

Hard Drive # 1 Corsair Force F120 SSD (Firmware Version 2.0)

Hard Drive # 2 2 x ******** Caviar Black, 7200rpm, 1TB, RAID 1

Operating System Windows 7 Ultimate 64bit

 

Running Intel RST 9.6 drivers.

 

Update: Installed Intel RST 10.1.0.1008 yesterday and haven't had a BSOD since then...

[Rofor]

Hi,

 

BSOD after cold boot while the spinning Windows logo appears - have to wait appr. 30 sec after turning on the netbook, then it will boot. No problems after that with rebooting the netbook.

Had to delete the second (third, if you count the 100Mb windows partition) partition to update to firmware 2.0

Until now no problems after standby or hibernation

 

Asus EeePC 1215N Netbook Link to Website

Bios 0503 (Latest)

AHCI Enabled

AHCI Enhanced Mode (tried 'Compatibility Mode' also)

 

Corsair F120 (Firmware 1.1, 2.0)

 

Windows 7 Home Premium 32bit, all updates until 12/2010

Latest Intel RapidStore-Driver Intel RST 10.1.0.1008

 

Fresh install on Corsair F120, two partitions (C:/D:)

 

Hope, that there will be a solution for the 'cold boot' problem, as it's really annoying...

 

Greetings from Vienna,

Ciao, Robert :)

 

Had to correct me - also BSOD after Standby! :(

After standby the login-screen appears and immediately after logon the netbook resets and for the next two times windows hangs on the spinning logo like i described above! Should have staid with the P-series, which works without a glitch on my desktop pc... :(

 

-- Edited on 12-30-2010 --

 

Exchanged the F120 with the P128 from my desktop - now all works as it should, P128 with no glitches in my Asus EeePC 1215n and the F120 in my old desktop pc (Abit IP35 Pro with p35 chipset)! Only one little problem - F120 hangs with the new Intel RST 10.1.0.1008 on booting windows shortly after the spinning win7-logo disappears. With normal win7 drivers there is no problem and it works perfectly!

[quozl]

Since the 2.0 firmware upgrade I get a Blue Screen on Cold Boot if the PC has been completely powered down.

 

You can download the Blue Screen Viewer Dump files HERE other than that the system is completely stable.

 

When it blue screens from cold boot if I just reboot by pressing the reset button the machine then boots perfectly and will continue to warm and cold boot perfectly unless I let it power down completely by letting all residual current expire. If I do that then I will get the cold boot blue screen again at windows log on screen or just after entering windows.

 

Edit: Of note is that I was getting the exact same issue, though more severe when using a Asus P6X58D-E motherboard and we changed it to the Gigabyte hoping to solve the issue to no avail. We have also tried different ram both Corsair and O C Z, different video card, both ASUS GTX 480 and the current EVGA GTX 480 but the issue still persists.

 

System specs are as follow

 

Motherboard: Gigabyte X58A-UD3R Ver2.0 - Bios Fe1

 

Processor: Intel i7 950 @3200 MHz

 

Memory: 6GB of Corsair CMP6GX3M3A1600C7

 

Video Card: EVGA Nvidia GTX 480

 

Hard Drive: Corsair CSSD-F120GB2 Firmware 2.0

Hard Drive: ******** Caviar Black WD2001FASS-00W2B0 2TB

Hard Drive: WD Velociraptor WD6000HLHX-01JJPV0 600GB

Hard Drive: 1.5 TB Seagate External USB drive

 

Optical Drive: LG 22x DVD

 

Case: Fractal Design

 

Power Supply: Corsair AX 850 ATX

 

Sound Card: Realtek HD Audio on board sound

 

Monitor: Dell U2711

 

Operating System: Windows 7 64 Professional

 

USB Flash Drive: Transcend 4GB

[jlinton]

Originally my F120 had 1.0 (? or so the flash utility said).

 

That version worked fine, if slowly, for a few months but the machine its in isn't my primary. It sort of sits in standby 99.9% of the time.

 

So recently, I was using the machine for some testing and I reinstalled a couple of time, and booted a couple Linux versions, took it apart a few times, etc. During this time, something changed and the BIOS could no longer detect the drive if the controller was set to AHCI mode. It worked as IDE though.

 

So, I decided to secure erase it, and attempt to get AHCI back at the same time. The secure erase worked, but the BIOS still wouldn't find it in AHCI mode. I changed delay times, reset the CMOS, the list goes on. In desperation, I decided to flash the 2.0 firmware. What a PITA that was. Lets say, that might be the most unimpressive flash utility I've every used (or for that matter written). I could list a half dozen easy improvements.

 

Sort version, after a few flash failures (hung>30 mins/power cycle, because nothing else worked, drive couldn't be detected after just a reset), something mysteriously changed and the BIOS started seeing it as a AHCI drive again. At that point I flashed it again, and the flash utility counted to 827(or was it 829?) hung for 30 seconds, the machine appeared to reset (no bluescreen/crash dump/etc). And now the flash utility says I have 2.0.

 

So, the performance is pretty respectable now.

 

The only problem is that >50% of the time, resuming from S3 standby bluescreens with a STOP 0xF4 (CRITICAL_OBJECT_TERMINATION), after a short period of time. Often, I can even log back in before it happens.

 

As I'm not getting a crashdump, thats a pretty strong indication that the drive isn't accessible.

 

Only diffrence between this totally clean install and the last one, other than the firmware diffrences on the drive itself is the fact that this copy was installed in IDE mode and then changed to AHCI, vs the old one which was installed directly in AHCI mode. There is also another 8G of RAM now (12 total, previously only 4G). Other than a 10.12 Catalyst driver, this machine has a copy of windows installed from a retail CD, and the lastest MS updates.

 

I can probably arrange to get a windbg connection via RS232 to another machine if someone wants more information on the crash. Its fairly reproducable. I'm pretty shocked that this problem still exists, as this was one of the first problems with this drive I heard about 6 months ago.

[Case]

My new laptop crashes every time I resume it from sleep. HD status light shows no disk activity and after a few seconds the system crashes with BSOD. Stop code is 0x0000007A and it can't write memory dump.

 

System configuration:

HP ProBook 5320m

Intel Core i5 450M

Intel HD Graphics

1 x 4GB PC3-10700 (Micron Technology)

Corsair Force F90 (firmware v2.0)

AHCI mode with Microsoft driver

Windows 7 Professional x64

 

BIOS and firmware were latest by default, Windows fresh install and fully updated.

[article22]

Issue when resuming from sleep. BSOD STOP F4 pretty much every time.

 

Tried :

 

1. Old image with a working Windows 7 x64 image

2. Full OS install W7 x64

 

Both had all the latest Intel drivers on them.

 

Configuration : HP Envy 15 laptop

HDD: Corsair F120 SSD (fw:2.0)

Processor Intel Core i7-820qm

Motherboard bios : Latest F.2B (also tried F.2A)

Memory : 2x4096 Crucial DDR3 memory (tested with MemTest)

Graphics : Ati Mobility Radeon 5830

Bios Mode: AHCI

Windows checked: AHCI mode

OS : Windows 7 Home Premium x64

[falc0n]

As far as I see - I can only confirm the most common problem - BSOD when resuming from sleep.

My config:

 

Newest BIOS(rev A27), AHCI mode set

 

Laptop Dell Latitude e6400

Processor Intel Mobile Core 2 Duo T9400

GPU: Nvidia Quadro NVS 160M 256MBytes

Motherboard: DELL 0RX495, chipset Intel PM45 (Cantiga-PM) + ICH9M (Enh)

 

 

OS: Windows 7 Ultimate N x64, build 7600; 3 reinstalling tries.

Tried Drivers: Intel Rapid 9.​6.​0.​1014, currently on the newest 10.1.0.1008

 

Is it possible to get the approximate date of the fix to the issue?

 

UPDATE: forgot about disk model:

Corsair F120

[nej_simon]

I just created a new thread about my problem but obviously I should've replied here instead. Anyway, I also get bluescreens when resuiming from sleep.

 

Model: Samsung NF310 laptop

HDD: Corsair F120 SSD (2.0 firmware)

CPU: Atom N550

Chipset : Intel Atom Host Bridge rev. 02

Southbridge: Intel NM10

BIOS : 02MY (latest)

Memory : 1x1GB DDR3

SATA Mode : AHCI

SATA Controller: Intel ICH7R/DH

SATA Version : 2.0 (SATA 300)

OS : Windows 7 Ultimate 32 (same thing with 64 bit)

Driver: Intel RST 10.1.0.1008 (same thing with Microsoft's driver)

 

The bluescreen I get say KERNEL_DATA_INPAGE_ERROR.

 

I had to use the alternative 2.0 upgrade and I got a bluescreen afterwards, if that matters.

Crash.zip

[rogerdk]

Problem when resuming from sleep (suspend to RAM).

In Windows the system just reboots after resuming.

In Linux the system wake up but the disk (/dev/sda) disappears, so nothing can be done. A hard reboot is required.

 

System specifications:

Asus PC eee 1005PE (Intel Atom N450 @1.66, 2 cores)

1GB DDR2

SSD-F60GB2 (FW tested: 1.1a and 2.0)

Bios: rev 1202 (latest)

OS: Windows 7 Professional 32 bits & ArchLinux 32 bits

[aggelos]

System specifications

Asus m2v-mx SE motherboard

VIA VT8237S Southbridge

AMD semprom LE-1100 @ 1,9 Ghz

2X1GB DDR2 667Mhz Memory Kingstom

Nvidia 9600MGT - 1Gb RAM DD3 PCIe x16

******** 500GB X 1 HDD

DVD burner IDE

Corsair F60 SSD (FW 2.0)

lattest Bios compatible (0601) with the motherboard

 

Problem(s):

When i connect only the SSD corsair F60 is not detected (in sata slot 1 or sata slot 2). But if i connect HDD 500Gb in sata slot 1 and SSD F60 in sata slot 2 , it's recognized.

All this in IDE mode SATA.

In RAID mode SATA, i can connect (and recognized) F60 in sata slot 1 and HDD 500Gb in sata slot 2.

I cannot use in RAID mode SATA two Hard Drive(SSD and HDD) separated, can i?

the issue is: i cannot install the OS and i cannot use as principal drive the F60 as IDE mode SATA.

 

Thanks for all.

[Wehwehchen]

Specs:

 

Dell Vostro V130 Notebook

BIOS Version A04 (this is the latest one)

Core i5 470UM, Intel HM57 Express Chipset, 2 GB DDR3-800

Onboard Intel GMA HD

1x SATA-II, set to AHCI in BIOS

No Optical Drive

Corsair F60 SSD, came with FW 2.0

Ubuntu 10.10 amd64 (OS not relevant though, the problem appears before booting starts)

 

The Vostro came with a 500 GB HDD which I immediately replaced with the F60.

 

Problem:

 

Every time I turn the power on, the system goes through POST, fails to detect the SSD and stops, telling me to "reboot and select proper boot device". I can then press Ctrl-Alt-Del, the SSD is detected and the OS boots normally.

 

This happens every single time when powering on, no exceptions so far. It appears that the F60 is taking too long to respond upon power-up. The Vostro's POST is pretty quick - I guess it takes just about 5 seconds from pressing the power button until the boot error appears. However, this works flawlessly with the original HDD.

 

It's baffling to see a solid state drive failing to initialize in time for POST, while a regular hard drive can manage to do this easily. Please advise on whether this problem will be addressed with updated firmware in the near future.

 

No other problems so far, S3 sleep works for me. But I think it's safe to assume that all those S3 problems and all the cold boot problems reported here are directly related to the drive's failure to respond in time. Note to all Windows 7 users suffering BSODs when resuming from sleep: Microsoft has a fixed version of the msahci.sys driver which might help you (see KB977178).

[nej_simon]

I just created a new thread about my problem but obviously I should've replied here instead. Anyway, I also get bluescreens when resuiming from sleep.

 

Model: Samsung NF310 laptop

HDD: Corsair F120 SSD (2.0 firmware)

CPU: Atom N550

Chipset : Intel Atom Host Bridge rev. 02

Southbridge: Intel NM10

BIOS : 02MY (latest)

Memory : 1x1GB DDR3

SATA Mode : AHCI

SATA Controller: Intel ICH7R/DH

SATA Version : 2.0 (SATA 300)

OS : Windows 7 Ultimate 32 (same thing with 64 bit)

Driver: Intel RST 10.1.0.1008 (same thing with Microsoft's driver)

 

The bluescreen I get say KERNEL_DATA_INPAGE_ERROR.

 

I had to use the alternative 2.0 upgrade and I got a bluescreen afterwards, if that matters.

 

This is what I've tried so far:

 

• Updating the drive to 2.0.
  
• Doing a clean reinstall of windows.
  
• Using Windows 7 32bit instead of 64.
  
• Trying with Microsoft's driver instead of Intel RST.
  
• Moving the drive to another computer to run the firmware update again (at least that computer didn't bluescreen at the end).
  
• Doing a secure erase of the drive (this improved the benchmark scores a lot btw, despite the fact that it's only a few weeks old).
  
• Doing another clean reinstall of windows.
  
• Updating the system BIOS (a new version was released yesterday).
  

 

But the bluescreens on resume keeps coming back. I've spent so many hours on this drive, why wont the damn thing work? :mad:

[Giant]

Specs:

 

Lenovo T400 laptop

Intel Core 2 Duo T9600 2.80GHz

8GB PC3-10600 DDR3 SDRAM 1333MHz SODIMM Memory (2 DIMM)

ATI Mobility Radeon HD 3400 w/ 256MB dedicated

Corsair F120 SSD w/ FW 2.0

Intel ICH9M-E/M AHCI Controller w/ 10.1.0.1008 Intel RST drivers

Windows 7 Ultimate x64

 

 

After updating to FW 2.0 I started getting a blue screen every time I power back on the PC after shutting it down completely. The error message is STOP: 0x00000007B (0xF78A2528, 0xc00000034, 0x00000000, 0x00000000) INACCESSIBLE_BOOT_DEVICE. After the blue screen, Windows launches the startup repair on the next boot attempt. If I go back to a previous restore point, windows will boot until I shut it down again. The problem always resumes after a complete shutdown and restart.

 

I have tried reinstalling Windows several times, as well as doing a secure wipe and installing Windows, but I still get the same blue screen after the first time I shut it down. It doesnt seem to matter which version of the storage controller drivers I use. I have tried the latest from Intel, as well as version 9 and the default Microsoft drivers.

[pitrix]

Specs

Notebook: HP 8510w

Processor: Intel Core 2 Duo T7500

Memory: 4GB ********

Chipset: Mobile Intel PM965 (with ICH8 controller)

OS: Windows 7 64bit (with TRIM enabled)

 

If AHCI is enabled in BIOS (in HP BIOS it's called "SATA native mode"):

- with Intel AHCI 9.6.0.1014/10.0.0.1046 I got BSOD when resuming from sleep and on cold start

- with MS AHCI 1.0 standard driver (6.1.7600.16385) I got BSOD only when resuming from sleep

 

If AHCI is disabled in BIOS:

- everything works fine (no BSOD ever)

 

!!! EDIT:

Just several hours ago I tried to wake my notebook from sleep (I was running with AHCI disabled) but Windows froze. I turned my notebook off and on, but now BIOS is unable to detect the SSD drive. It was my primary boot drive. What a lovely user experience with this Corsair SSD drive :( I'm returning it to reseller.

[av8er]

I also have problems after resume from S3 sleep. similar symptoms as others, usually makes it to the login screen but BSOD's within 30 sec. No problems with Normal HDD's

 

F120 drive w/ 2.0 firmware

Gigabyte GA-P35-DQ6, F9 Bios

Intel E8600 Stock speed

4 gb ******** Memory at 1066

Clean install Win7 Pro, x64

intel ICH9R, AHCI Mode

10.1.0.1008 Intel AHCI drivers

 

Rick

[Henrik]

Hi

 

Hdd not allways detected in coldboot, Ctrl + Alt + Delete solves it.

 

Bsod issue when resuming from suspend. There are no problems with hibernate.

 

OS-version: 6.1.7600.2.0.0.256.48

 

BCCode: f4

BCP1: 0000000000000003

BCP2: FFFFFA8007A795B0

BCP3: FFFFFA8007A79890

BCP4: FFFFF8000358C2D0

OS Version: 6_1_7600

Service Pack: 0_0

Product: 256_1

 

 

Bsod comes when:

 

Getting ready to login after suspend or after login has been entered

 

Some times it happens when the lid of the notebook is closed

 

AHCI Drivers tried:

Intel SATA AHCI Controller Version: 9.5.6.1001

Intel SATA AHCI Controller Version: 10.1.0.1008

Standard AHCI1.0 Serial ATA Controller

 

Notebook : Lenovo T410

HDD: Corsair F120 SSD tried fw: 1.1a and 2.0

Processor Intel i5-560m

Bios : 1.34 (latest)

Memory : 2x2048MB, DDR3

Graphics : Intel HD Graphics Card

Bios Mode: AHCI

Windows checked: AHCI mode

OS : Windows 7 pro 64 bit

 

 

Kind regards

 

Henrik Høy

[SSDer]

Symptoms:

-Freezes when wake up from sleep - it freezes about 15 secs from waking up and I have to remove battery to recover

-does not always detect drive from cold boot - warm boot is ok

-System can hibernate without issue.

 

AHCI Drivers tried:

 

- Intel SATA AHCI Controller Version: 9.6.0.1014

- Intel SATA AHCI Controller Version: 10.1.0.1008

- Standard MS AHCI Serial ATA Controller

 

Configuration : Laptop Acer 1830T

HDD: Corsair F120 SSD (fw:1.1 and 2.0)

Processor Intel Core i5 430UM

Motherboard bios : rev 1.2 (latest)

Memory : 8GB (2x4GB)

Graphics : Intel onboard graphics

Windows checked: AHCI mode

OS : Windows 7 Home Prem x64

[TrackSmart]

I should have heeded the warnings of others not to buy this drive for any laptop, but I checked online and found that people were successfully using this same SSD in the same model of laptop, so I took the plunge. Bad move, I guess.

 

Storage: Corsair Force F60 (CSSD60-F60BB2)

 

Problem: Blue Screen after returning from Sleep (intermittent frequency)

- Problem happened with original firmware (unknown version)

- Problem continued (more often?) with firmware 2.0

 

Next, I updated laptop BIOS from v1.80 to the latest, v1.90, dated March 2, 2011). Same problems. All other system drivers updated to the latest.

AHCI is enabled. No other performance issues with the drive (WEI storage score of 7.5 - 7.6 each time)

I turned off power saving features for the hard drive in windows (i.e. the drive will never "sleep"). Didn't help.

 

 

Laptop Manufacturer: TOSHIBA

Model: PORTEGE R705-P35

Processor: Intel Core i3-370m (2.4 GHz)

Graphics: Intel HD graphics (integrated)

4.00 GB RAM

Windows 7 Home Premium 64-bit

BIOS v1.90 (latest, dated March 2, 2011)

 

 

Network

------------------

Network Adapter Intel® 82577LC Gigabit Network Connection

Network Adapter Intel® Centrino® WiMAX 6250

Network Adapter Intel® Centrino® Advanced-N 6250 AGN

 

Optical Drive: Matsh.ita DVD-RAM UJ892ES

[dean1962]

Specs

 

Gigabyte G41MT-S2P - Latest Firmware F1 (Non AHCI)

http://www.gigabyte.com/products/product-page.aspx?pid=3743#ov

Corsair SSD F60 Latest Firmware Ver 2.0 (Came with this version)

WD2500

Corsair Ram - New DDR3 - CM3X2G1333C9 4GIG

Intel SATA Controller ICH7/R - 82801GB

Win 7 - 64 bit Pro - New Install

Nvidia GT 220

 

In the Bios of this board there is no facility for AHCI. So running in IDE mode. System is stable and Atto reports quite good transfer rate.

 

When the system is put in Sleep it fails to wake up correctly, it will normally hang on either the main screen at boot (No password on bootup) or when you go to open a program it will just sit there and not do anything so a reboot is normally required.

 

I have tried both S1 and S3 and have managed to start normally on a very rare occasion but normally the longer you leave it the issue will come back again.

 

Have tried various forms of power profiles, hibenate is off .... nothing works with any changes I make here.

 

Have disabled sleeping and now have to rely on turning system off. Anyway hopefully the issue can be resolved in future updates. My first Corsair SSD:(:

[velocity7]

Model: ASUS F8Sn

CPU: Intel Core 2 Duo T5450

RAM: 3GB

GPU: nVidia GeForce 9500M GS 512 MB

HDD: Corsair CSD-F120GB2 SSD (FW 2.0, came installed), OS installed on SSD

DVD: HL-DT-ST DVDRAM GSA-T40N

OS: Windows 7 Ultimate x64

Extra: No overclocking, no memory timing changes. Everything is at stock.

 

Problem: Randomly there is a BSOD when immediately coming out of sleep (standby) mode. Error in minidump files all say KERNEL_DATA_INPAGE_ERROR, caused by either ntoskrnl.exe or ntkrnlmp.exe. Subsequent reboots do not produce any further BSODs and the HDD is detected at all times, but going into standby and resuming may result in another BSOD again.

Minidump.zip

[RAM GUY]

Let's get it replaced, please use the On Line RMA Request Form and we will be happy to replace it. Be sure to check the box that says “I've already spoken to Technical Support and/or RAM Guy.”

[bbogey]

Problem description:

MacBook Pro 13" early 2011, with Corsair F120, firmware version 2.0, Mac OS X does not resume from hibernation.

 

By default OS X on laptop hibernates (goes to safe sleep) when battery is almost empty.

 

Resuming process starts fine, but freezes in second/third step in process bar and OS X requests to press power button for a while to restart.

 

System Diagnostics Report for the crash attached.

 

How to reproduce:

 

Unplug the power adapter, wait until battery runs out and laptop hibernates. Plug the power adapter back, power on laptop. Hibernation resume fails.

 

Or if you don't want to wait the battery discharges:

 

"sudo pmset -a hibernatemode 1"

Put laptop to sleep: Click on Apple icon -> Sleep. Wait that laptop hibernates (power led shuts off). Power on laptop.

Resume fails.

 

Workaround:

Disable hibernate by “sudo pmset -a hibernatemode 0″ = suspend to RAM only (default on desktops)

 

Other settings are:

“sudo pmset -a hibernatemode 1″ = suspend to disk only (hibernate / safe sleep)

“sudo pmset -a hibernatemode 3″ = suspend to disk + RAM (default on laptops)

 

To see your current hibernatemode: “pmset -g | grep hibernatemode”.

 

Hardware Overview:

 

Model Name: MacBook Pro

Model Identifier: MacBookPro8,1

Processor Name: Intel Core i5

Processor Speed: 2,3 GHz

Number of Processors: 1

Total Number of Cores: 2

L2 Cache (per Core): 256 KB

L3 Cache: 3 MB

Memory: 4 GB

Boot ROM Version: MBP81.0047.B04

SMC Version (system): 1.68f96

Sudden Motion Sensor:

State: Disabled

 

Intel 6 Series Chipset:

 

Vendor: Intel

Product: 6 Series Chipset

Link Speed: 6 Gigabit

Negotiated Link Speed: 3 Gigabit

Description: AHCI Version 1.30 Supported

 

Corsair CSSD-F120GB2:

 

Capacity: 120,03 GB (120*034*123*776 bytes)

Model: Corsair CSSD-F120GB2

Revision: 2.0

Serial Number: 1106650035000998009F

Native Command Queuing: Yes

Queue Depth: 32

Removable Media: No

Detachable Drive: No

BSD Name: disk0

Medium Type: Solid State

TRIM Support: No

Partition Map Type: GPT (GUID Partition Table)

S.M.A.R.T. status: Verified

Volumes:

Capacity: 209,7 MB (209*715*200 bytes)

Writable: Yes

BSD Name: disk0s1

Mac OS X:

Capacity: 119,69 GB (119*690*149*888 bytes)

Available: 72,94 GB (72*936*632*320 bytes)

Writable: Yes

File System: Journaled HFS+

BSD Name: disk0s2

Mount Point: /

 

System Software Overview:

 

System Version: Mac OS X 10.6.7 (10J3250)

Kernel Version: Darwin 10.7.3

Boot Volume: Mac OS X

Boot Mode: Normal

Secure Virtual Memory: Enabled

64-bit Kernel and Extensions: Yes

hibernate_crash_macbook.txt

[Synbios]

Problem description:

MacBook Pro 13" early 2011, with Corsair F120, firmware version 2.0, Mac OS X does not resume from hibernation.

 

By default OS X on laptop hibernates (goes to safe sleep) when battery is almost empty.

 

Resuming process starts fine, but freezes in second step in process bar and OS X requests to press power button for 10 seconds to restart.

 

Workaround:

Disable hibernate by “sudo pmset -a hibernatemode 0″ = suspend to RAM only (default on desktops)

 

Other settings are:

“sudo pmset -a hibernatemode 1″ = suspend to disk only (hibernate / safe sleep)

“sudo pmset -a hibernatemode 3″ = suspend to disk + RAM (default on laptops)

 

So for you, suspend to RAM (sleep) works better than suspend to disk (hibernate)?

 

Strange....

 

(sorry about the location of this post, a mod can move it if needed)

[bbogey]

So for you, suspend to RAM (sleep) works better than suspend to disk (hibernate)?

 

Strange....

 

(sorry about the location of this post, a mod can move it if needed)

 

Yes if you google "macbook hibernate sandforce" you see it's a common problem with sandforce and macbook pro.

 

Everything else including suspend to RAM (normal sleep) works fine.

[guitrein]

Problem description:

MacBook Pro 13" early 2011, with Corsair F120, firmware version 2.0, Mac OS X does not resume from hibernation.

 

By default OS X on laptop hibernates (goes to safe sleep) when battery is almost empty.

 

Resuming process starts fine, but freezes in second step in process bar and OS X requests to press power button for 10 seconds to restart.

 

I have the exactly issue with my early 2011 MacBook Pro 13" i7.

Here is my spec:

 

Hardware Overview:

Model Name: MacBook Pro

Model Identifier: MacBookPro8,1

Processor Name: Intel Core i7

Processor Speed: 2.7 GHz

Number of Processors: 1

Total Number of Cores: 2

L2 Cache (per Core): 256 KB

L3 Cache: 4 MB

Memory: 8 GB

Boot ROM Version: MBP81.0047.B04

SMC Version (system): 1.68f96

Sudden Motion Sensor:

State: Disabled

 

Intel 6 Series Chipset:

Vendor: Intel

Product: 6 Series Chipset

Link Speed: 6 Gigabit

Negotiated Link Speed: 3 Gigabit

Description: AHCI Version 1.30 Supported

 

Corsair CSSD-F240GB2:

Capacity: 240.06 GB (240057409536 bytes)

Model: Corsair CSSD-F240GB2

Revision: 2.0

Native Command Queuing: Yes

Queue Depth: 32

Removable Media: No

Detachable Drive: No

BSD Name: disk0

Medium Type: Solid State

TRIM Support: No

Partition Map Type: GPT (GUID Partition Table)

S.M.A.R.T. status: Verified

 

System Software Overview:

System Version: Mac OS X 10.6.7 (10J3250)

Kernel Version: Darwin 10.7.3

Boot Volume: Mac OS X

Boot Mode: Normal

Secure Virtual Memory: Enabled

64-bit Kernel and Extensions: Yes