kyawlin

Q: New Retina Macbook pro 13 Haswell system hang/unresponsive

Hello Everyone.

 

I have just got my new macbook pro retina 13 Haswell (October Model). This is my second day of usage and i have encountered sudden system freeze for 2 times already. The keyboard and the trackpad stops working including brigtness keys and volume control keys. i have use apple hardware test but no problem are found.

 

 

Could anyone tell  me what is going on or having the same issue?

MacBook Pro with Retina display, OS X Mavericks (10.9)

Posted on Oct 25, 2013 5:56 AM

Close

Q: New Retina Macbook pro 13 Haswell system hang/unresponsive

  • All replies
  • Helpful answers

first Previous Page 63 of 199 last Next
  • by Lizzy85,

    Lizzy85 Lizzy85 Oct 30, 2013 12:36 PM in response to Oli.S72
    Level 1 (0 points)
    Oct 30, 2013 12:36 PM in response to Oli.S72

    Thanks for the info. 62 pages is a lot to read ;-)

  • by c0rney,

    c0rney c0rney Oct 30, 2013 12:41 PM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 12:41 PM in response to kyawlin

    Same issue here.

     

    I've exchanged my late 2013 13" MBP once already. Just got the new one set up and I'm experiencing the same issues. The only thing that seams to work for me is restarting or closing the lid for a while.

     

    This is obviously a serious issue and Apple needs to address it ASAP.

     

    macbook pro retina 13 Haswell: 13"/2.4/8GB/256GB.

  • by DSL_Steve,

    DSL_Steve Oct 30, 2013 12:44 PM in response to Pudge52
    Level 1 (45 points)
    Oct 30, 2013 12:44 PM in response to Pudge52

    Pudge52 wrote:

     

    I'm starting to fear hardware problem with the 13MBP. It doesn't seem to be affecting the 15 MBP as much or we aren't hearing from them.

     

    Read this thread. Most of the data here points to a software (Mavericks) problem.

  • by rellik12,

    rellik12 rellik12 Oct 30, 2013 12:44 PM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 12:44 PM in response to kyawlin

    I've just organised a return. Problems happen but I can't get over the fact that this has been going on over a week with no feedback from Apple. Terrible customer service.

  • by azbe,

    azbe azbe Oct 30, 2013 12:45 PM in response to iDevelope
    Level 1 (0 points)
    Oct 30, 2013 12:45 PM in response to iDevelope

    iDevelope wrote:

     

    I have MBP 15" late 2008 with the same problen. Now I cannot even login, It freezes at the login panel.

    That's quite a relief (sorry:), because it's almost sure that it's a software issue.

  • by kitteth,

    kitteth kitteth Oct 30, 2013 12:48 PM in response to Pudge52
    Level 1 (10 points)
    Oct 30, 2013 12:48 PM in response to Pudge52

    My friend just got a new 15" rMBP today, and he doesn't have the warning messages in the console.

     

    I'm starting to wonder if this really is a software thing. The 13" and 15" presumably have the same software shipped, but it seems that this is only an issue for 13" rMBP. Wouldn't that point to a hardware issue?

  • by ArgyrisFromUK,

    ArgyrisFromUK ArgyrisFromUK Oct 30, 2013 12:50 PM in response to kitteth
    Level 1 (0 points)
    Oct 30, 2013 12:50 PM in response to kitteth

    Not really...

     

    I had pre-installed the 13A2093 build and a friend of mine who got the same exactly setup

    13'' 2.4 8gb 256 has the 13A603. Now why the same laptop come with different build....it's a miracle!

  • by Oli.S72,

    Oli.S72 Oli.S72 Oct 30, 2013 12:56 PM in response to ArgyrisFromUK
    Level 1 (0 points)
    Oct 30, 2013 12:56 PM in response to ArgyrisFromUK

    ArgyrisFromUK wrote:

     

    Not really...

     

    I had pre-installed the 13A2093 build and a friend of mine who got the same exactly setup

    13'' 2.4 8gb 256 has the 13A603. Now why the same laptop come with different build....it's a miracle!

    And your friend does have the freez issue as well? Because from what is known so far, the 13A603 should be bug-free

  • by xuhaotian,

    xuhaotian xuhaotian Oct 30, 2013 1:04 PM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 1:04 PM in response to kyawlin

    I understand that it may take a while to release a fix to us, but why Apple doesnt step out and say we are going to fix this? so sad

  • by noeltz,

    noeltz noeltz Oct 30, 2013 1:04 PM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 1:04 PM in response to kyawlin

    I'm running an old MacBook Pro mid 2009 (no problems with mavericks) and I'm considering buying the new rMBP.

     

    Did anyone try to downgrade to an older version of osx on his/her new haswell macbook?

     

    Might help to figure out whether the bug is a hardware or software issue.

  • by blackfishes,

    blackfishes blackfishes Oct 30, 2013 1:04 PM in response to ArgyrisFromUK
    Level 1 (0 points)
    Oct 30, 2013 1:04 PM in response to ArgyrisFromUK

    very interesting! first time i heard of it coming with 13A603 on the new 13", any screenshots? i might try to install 603 if i know it can work.

  • by Olly76,

    Olly76 Olly76 Oct 30, 2013 1:08 PM in response to kitteth
    Level 1 (0 points)
    Oct 30, 2013 1:08 PM in response to kitteth

    If it was a hardware issue it would occur in a Boot Camp environment running Windows as well - but nobody here has reported that to happen. I have tried this out myself and didn't experience any freeze or strange Event Log entries within Windows.

  • by abrahamzon1,

    abrahamzon1 abrahamzon1 Oct 30, 2013 1:10 PM in response to kyawlin
    Level 1 (0 points)
    Oct 30, 2013 1:10 PM in response to kyawlin

    Seems like you can close the lid for 30sek - 1 min or so, then mine works again!

  • by JordanCat,

    JordanCat JordanCat Oct 30, 2013 1:11 PM in response to Pudge52
    Level 1 (10 points)
    Oct 30, 2013 1:11 PM in response to Pudge52

    @Pudge52 , ramito1 and everyone else too: As a new MacBook Pro Retina (15") owner I've been following this thread with interest for days- particularly when 15" MacBooks and iMacs are mentioned.  Occasional questions about the specs of systems which are NOT experiencing these problems are what prompts me to post here today. 

     

    Neither of my computers- a one-week old MacBook with OS as shipped, and my iMac which I upgraded to Mavericks from Mountain Lion, have experienced any of these (possibly Mavericks-related?) keyboard/mouse freezes, and neither computer shows a single one of the oft-quoted error messages from the console.

     

    MacBook Pro Retina Late 2013: 15", 2.3 GHz i7, 16 GB RAM, Mavericks build 13A3017

     

    iMac 21.5" Late 2012: 2.9 GHz i5, 16 GB RAM, Mavericks build 13A603

     

    On the 15" MacBook I almost immediately installed iWork and updated the iLife apps, then installed Sophos AV, Flash and Firefox.  After five days of light but frequent use, this laptop shows no keyboard/trackpad error messages and has worked flawlessly.  (So far?)

     

    After an easy upgrade to Mavericks a few days ago, the iMac continues humming along without a glitch also.  (I actually felt compelled to go into "About This Mac" to verify that I'd actually upgraded successfully.)

     

    I'll continue following this thread with great interest, as it will be an indication to me of just how well Apple takes care of its customers.

  • by blackfishes,

    blackfishes blackfishes Oct 30, 2013 1:12 PM in response to idark77
    Level 1 (0 points)
    Oct 30, 2013 1:12 PM in response to idark77

    idark77 wrote:

     

    I made it and other people have the same issue but didn't know this thread...

    I called Apple store, where i bought my Macbook late 2013 6 days ago,  and i asked if they know this issue, the guy said no problem with new MBP Retina and they are not aware of it ( Incredible ). I said to look at internet and on Apple Communities Support because we have problems with this new MBP. Just i cannot beleve it .... 

     

    exactly! i spoke to a few different apple support folks over the phone and pointed them to this thread and they told me the same thing "this is the first time i heard about it".

     

    so if you have not done so, call them and log a case with them- so that they can track internally. (eg: xxx number of cases on the same issue)

first Previous Page 63 of 199 last Next