tomfrenock
Level 1 (10 points)

Q: Crash on waking

I have a new mid-2012 MBP 13 - 2.9GHz/8GB with a 256GB SSD, running OS 10.7.4. When I started off with the supplied version of the OS (10.7.2 or 3?), I could close the cover on the computer to sleep -- or use any other method -- and the computer would wake as expected. Then I updated the software, which rolled me to OS 10.7.4 plus a variety of other updates. Now,  I my MBP 13 cannot sleep and wake without crashing. My screen freezes with a spinning pinwheel. My mouse can move that pinwheel, but all other inputs are not recognized. I searched the support discussions, but found no solutions that work for me. The most promising solution was to do a clean reload of the OS with a Time Machine backup. This is how I know that this behavior is related to the updated software. Any ideas?

MacBook Pro (13-inch, Mid 2012), Mac OS X (10.7.4)

Posted on Jul 11, 2012 11:44 AM

by tomfrenock,Solvedanswer
tomfrenock tomfrenock
Level 1 (10 points)
A:

Success!!!!! I cloned and installed the OWC Mercury Extreme 240 GB, and everything works as it should. I was able to format the disk and install a recovery partition, too. The OCZ V4 would not permit it. I am sorry that I was seduced by the printed tech specs for that OCZ. This OWC disk is plenty fast. Boot time is consistently 9 sec from button push (before optical drive sound) to login screen. I think that the problem is solved. I will stick with OWC in the future. They understand Macintosh.

Posted on Jul 19, 2012 8:34 PM

Close
tomfrenock

Q: Crash on waking

  • All replies
  • Helpful answers

Previous Page 2 of 3 last Next

  • by Linc Davis,

    Linc Davis Linc Davis Jul 12, 2012 1:15 PM in response to tomfrenock
    Level 10 (208,044 points)
    Applications
    Jul 12, 2012 1:15 PM in response to tomfrenock

    You want to test with a completely clean system. If it doesn't work in that configuration, you have a warranty issue.

  • by tomfrenock,

    tomfrenock tomfrenock Jul 12, 2012 1:32 PM in response to Linc Davis
    Level 1 (10 points)
    Jul 12, 2012 1:32 PM in response to Linc Davis

    Agree. Thanks.

  • by tomfrenock,

    tomfrenock tomfrenock Jul 17, 2012 12:50 PM in response to Linc Davis
    Level 1 (10 points)
    Jul 17, 2012 12:50 PM in response to Linc Davis

    Linc - I spent a lot of the weekend cloning disks and doing Time Machine startups. I determined that the problem is with the OCZ Vertex 4 SSD. Perhaps there is something about its architecture that is not compatible with my Mac. I had trouble formatting it, also, but it would load

     

    I got a return authorization from Amazon and have it en route at this time. I ordered a new OWC Mercury Extreme to replace it, so I will see how that goes. Currently, I am running on a mechanical HDD, and everything works great, except for that intermittant keyboard lighting thing. Did you run across that one yet?

  • by Linc Davis,

    Linc Davis Linc Davis Jul 17, 2012 1:07 PM in response to tomfrenock
    Level 10 (208,044 points)
    Applications
    Jul 17, 2012 1:07 PM in response to tomfrenock

    That might be fixed by an SMC reset.

  • by tomfrenock,

    tomfrenock tomfrenock Jul 17, 2012 1:17 PM in response to Linc Davis
    Level 1 (10 points)
    Jul 17, 2012 1:17 PM in response to Linc Davis

    It wasn't I did multiple SMC and PRAM resets in the process. The only fix was removing the OCZ hardware. Since writing my reply above, I noted that there are a lot of others having similar or same issues with that SSD. Hopefully, the OWC hardware will work flawlessly. I deserve it.

  • by Halfmoonh4,

    Halfmoonh4 Halfmoonh4 Jul 17, 2012 7:22 PM in response to tomfrenock
    Level 1 (0 points)
    Jul 17, 2012 7:22 PM in response to tomfrenock

    I had the same issue, 10.7.4 causes "many" SSDs to be ejected after sleep....  here's my story on another thread

     

    https://discussions.apple.com/message/18924099#18924099

     

     

    I went thru 3 SSD before I found one that would work (Samsung > OCZ > Crucial).   It took the Apple Store Geniuses 4 hours to help me figure all this out (I have to thank them for their patience... because 10.7.4 is so new, they hadn't seen the problem before either.

     

     

    As I'm typing this, the Crucial SSD is hanging in there, but my Momentus XT 750 just got booted (ejected) off the Optical bay, for the umteenth time!   The Optical bay port has even worse issues.

     

    This same set up worked great on my 2009 MBP.  Why did my "upgrade" turn into a "downgrade" ????

     

    You can only hope someone at Apple is re-writing firmware to fix this major flaw as we speak.

  • by tomfrenock,

    tomfrenock tomfrenock Jul 18, 2012 7:18 AM in response to Linc Davis
    Level 1 (10 points)
    Jul 18, 2012 7:18 AM in response to Linc Davis

    Linc -

     

    I think that I figured out the keyboard lighting thing. I am using my 2012 machine in the same office work environment as my 2009. The new MBP seems to be intermittant, working sometimes for no apparant reason. The 2009 model would always be dark (operating in adequate lighting) then light up when the sensor gets shaded. The 2012 basically operates lit up at almost all times.

     

    To troubleshoot, I shined a light into the sensor, and sure enough it dimmed to proper daytime operation. I will now assume that the photocell sensor is different from that in my 2009 model, and the thresholds are different. My work environment must have lighting that is just on that threshold level. I can point my screen a little to the left or up, and the keyboard lighting will extinguish.

     

    I will assume that this is not a hardware or software issue. It is just a coincidence of the office lighting level and the variation between the photocells. Thought you would like to know about this finding.

  • by tomfrenock,

    tomfrenock tomfrenock Jul 18, 2012 7:27 AM in response to Halfmoonh4
    Level 1 (10 points)
    Jul 18, 2012 7:27 AM in response to Halfmoonh4

    Thanks, Halfmoon. From reading your other posting, I assume that you are having this issue in the optical bay. Mine is in the normal HD bay. Funny thing is that I could not "see" the OCZ V4 when connecting to my 2012 with 10.7 or my 2009 with 10.6 to do the formatting before cloning. I kept getting  error messages when I attempted a verification and repair. Took it to the Mac retailer, and they could connect and format. Spooky.

     

    Question for you ... did you find a mechanical drive that works in your optical bay? I am thinking of doing that configuration for Time Machine. A SATA II would be fine for that application, if SATA III does not work. What about your 2009 MBP? I also have one that I might configure the same. Will SATA II work in that optical bay?

  • by Halfmoonh4,

    Halfmoonh4 Halfmoonh4 Jul 18, 2012 11:21 AM in response to tomfrenock
    Level 1 (0 points)
    Jul 18, 2012 11:21 AM in response to tomfrenock

    eXactly My plan... Waiting for a WD Scorpio Black SATA II to be delivered, will let you know.   We can only hope 10.8 or 10.8.1 will fix this.   I read one post that thought it was 10.7.4 specifically that introduced all theses problems, dunno.  At least my 2009 never crashed.   I miss it already

  • by tomfrenock,Solvedanswer

    tomfrenock tomfrenock Jul 19, 2012 8:34 PM in response to Linc Davis
    Level 1 (10 points)
    Jul 19, 2012 8:34 PM in response to Linc Davis

    Success!!!!! I cloned and installed the OWC Mercury Extreme 240 GB, and everything works as it should. I was able to format the disk and install a recovery partition, too. The OCZ V4 would not permit it. I am sorry that I was seduced by the printed tech specs for that OCZ. This OWC disk is plenty fast. Boot time is consistently 9 sec from button push (before optical drive sound) to login screen. I think that the problem is solved. I will stick with OWC in the future. They understand Macintosh.

  • by tomfrenock,

    tomfrenock tomfrenock Jul 19, 2012 8:35 PM in response to Halfmoonh4
    Level 1 (10 points)
    Jul 19, 2012 8:35 PM in response to Halfmoonh4

    Halfmoon -  Success. Read my entry.

  • by Halfmoonh4,

    Halfmoonh4 Halfmoonh4 Jul 20, 2012 5:57 AM in response to tomfrenock
    Level 1 (0 points)
    Jul 20, 2012 5:57 AM in response to tomfrenock

    Did you put the OWC SSD in the optical bay?  If so, that means its very finicky because it ejects my mechanical HD, Momentus XT Hybrid.   What kind of read write speeds?  The Crucial M4 gets 500 MB/s read, but in the main bay.

  • by tomfrenock,

    tomfrenock tomfrenock Jul 27, 2012 6:45 AM in response to Halfmoonh4
    Level 1 (10 points)
    Jul 27, 2012 6:45 AM in response to Halfmoonh4

    No, the SSD went into the normal drive bay. I have a data double being shipped to put a HDD into the optical bay. Plan to use my SATA III in my mid-2009 MBP 13 and purchase a new SATA II for the mid-2012 model. Data speed on these extra drives is not important for me. It will be considerably faster than using an external. I'll let you know how the HDD installation works out.

  • by Halfmoonh4,

    Halfmoonh4 Halfmoonh4 Jul 27, 2012 8:47 AM in response to tomfrenock
    Level 1 (0 points)
    Jul 27, 2012 8:47 AM in response to tomfrenock

    I had a SATA III Seagate Momentus XT 750 that kept gettting kicked off (ejected) of the Optical Bay.   I haven't tried the SATA II WD drive.   But, I did get a 2nd SATA III Crucial to work.  See below.    I think both the ports are just plain finicky (i.e. they have buggy firmware).

     

    https://discussions.apple.com/message/18980874#18980874

  • by slackerbot,

    slackerbot slackerbot Jul 30, 2012 4:22 PM in response to Halfmoonh4
    Level 1 (5 points)
    Jul 30, 2012 4:22 PM in response to Halfmoonh4

    Thanks for this. I too have had the same issues (crash from sleep) with OCZ Vertex 4 mounted in the main bay, running OS 10.8 on a mid-2012 MBP.

     

    I was going to put another SSD in the optical bay but good to know this is finicky too.

     

    I'm going to flash the firmware first on the Vertex4 before playing roulette with more SSD drives. It seems really hit or miss. This should obviously be addressed with an Apple firmware update.

Previous Page 2 of 3 last Next