New Retina Macbook pro 13 Haswell system hang/unresponsive

Just happened to me for like the fourth time, but this time I just shut the lid and opened it about two minutes later and it worked fine. As for some of the correlations that some people have been looking for:

- Has happened to me both on battery power and when plugged in

- Someone suggested multitasking was a factor, however it happened to me with only Safari open

- The apps being used don't seem to matter, has happened to me with Chrome, Safari, Word, etc.

- Someone mentioned that it may be a bluetooth issue, but I've had bluetooth turned off the entire time I've had the Macbook.

Hopefully that helpful to some extent.

almostinverted wrote:

at least I know I'm not alone!

You deffinitely are not!

Us and at least 156 other users are facing this issue.

Do not worry, Apple will have this fixed very soon!

Kyawlin, yes, That is correct. I have posted that much earlier in the day 🙂

Also, this has been featured on:

CNET, MacRumors, GTB, Product-Reviews, Trusted-Reviews, AppleInsider,ModernReaders, TechRadar, The Inquirer, and so on....

Oh, any my survey is on there too! (MacRumors link)

According to users in a support thread spanning over 14 pages, the trackpad and the keyboard on the 13-inch Retina MacBook Pro are reportedly locking up at random during use, with a hard reset through the machine's power button appearing to be the only present solution to the problem. Users are also reporting that a reset of the MacBook's System Management Controller (SMC) appears to be ineffective, and a small survey (MINE MINE MINE!)of users within the thread show that the problem is affecting all three configurations of the 13-inch model. Currently, it is unknown as to whether the freezes are a hardware or software problem, as Apple has not officially commented on the errors.

Muahaha, Kyawlin and I are the most popular people here 🙂

Have the same problem with random hang. Hard power reset to get out. Talked with Mike in TS. Reloaded OS and still hung.

First time ever buying a Mac. Hummm.

Same problem here in Italy. Mbp late 2013 2.4/256/8gb/13"/retina.

I'm planning to ask the refund if the problem will not be fixed before the 14 days will be ended.

Bye

Hey guys. I just spent some time with a tier 2 tech and they are aware of the problem but need people to call in. From there side,they are adamant IT IS NOT a Mavericks problem. It is Mavericks that has uncovered a hardware problem etc. For those having problems after upgrading older computers, Mavericks is uncovering a separate issue.

This is interesting. So every single freeze has been on Mac OSX? This is good news isn't it? Since if it also happened on Windows it could point to a hardware/firmware issues, but if it is just Mac OSX it is probably just some easily fixed software bug.

Ugh...within an hour of turning it on I experienced the same issue. Putting it to sleep as someone suggested (close the lid for a few minutes) got the keyboard and trackpad working again. Pretty annoying though. Hopefully this doesn't happen often.

So this means that they never tested Mavericks together w the new hardware? This doesn't even make sense to me :(

Plus if it's true and it's a hardware issue that surfaced through Mavericks, then I think we can begin returning our beloved laptops sooner or later. That's just sad :(

thanks, your solution (just plugging in an iPhone) worked for me just now. no restart needed.

in other news, people Please stop panicking about your hardware. i get it that you're freaked about the expensive piece of hardware you just bought. but that ain't it.

as has been reported by me and others on this thread, the problem affects MBP's of both 13" and 15" from 2007, 2009, 2012, and iMacs -- AT LEAST.

so it's not specific to 13", nor retina, nor Haswell, nor even laptops.

gotta be a s/w issue. not that unlike some other .0 releases (anyone remember the erasing entire disks cutie?).

it will be fixed, likely within a week or so.

anthock wrote:

Hey guys. I just spent some time with a tier 2 tech and they are aware of the problem but need people to call in. From there side,they are adamant IT IS NOT a Mavericks problem. It is Mavericks that has uncovered a hardware problem etc. For those having problems after upgrading older computers, Mavericks is uncovering a separate issue.

We are all relieved to say that that they are aware of the issue - that's fantastic news!
If they say that the issue is not a OSX Mavericks issue, then it either means that a) it's a bad firmware, or b) it's bad hardware.

All fingers seem to point to Mavericks however, the only reason being is that - under Windows, there is no such problem.

Another reason I seem to think that, is because the error in question (in kernel log) seems to point to a power management issue (which falls under a driver-related problem). I have seem similar issues on Hackintoshes and FreeBSD.

In any case, I HIGHLY doubt that this is a hardware fault, as this was a MAJOR slip of Quality Control, and I don't think Apple would allow this.

To wrap things up, Apple should have this fixed soon, and we are glad that they are aware of the matter. It would be nice, however, that a statement be issued saying that - "Yes, Apple is aware of the matter"

Hopefully, this is done sooner then later, as this is a product-breaking bug that I would rate very high up on the scale - and I assume everyone is with me on this.

And remember...

View results of issue specs:

https://docs.google.com/forms/d/1QBSLV-bEuxyBUNtFmzDbTWl2Tu3EFU4IPNNvobhKdPA/vie wanalytics

Submit your issue to the comminity here:

https://docs.google.com/forms/d/1QBSLV-bEuxyBUNtFmzDbTWl2Tu3EFU4IPNNvobhKdPA/vie wform

And don't forget!

Report your issue to Apple directly!

https://www.apple.com/feedback/macbookpro.html

Remember, the more active this thread is, the better chance we have to get noticed!

A BIG Thanks to everyone who is contributing here!

wigglybridge wrote:

thanks, your solution (just plugging in an iPhone) worked for me just now. no restart needed.

in other news, people Please stop panicking about your hardware. i get it that you're freaked about the expensive piece of hardware you just bought. but that ain't it.

as has been reported by me and others on this thread, the problem affects MBP's of both 13" and 15" from 2007, 2009, 2012, and iMacs -- AT LEAST.

so it's not specific to 13", nor retina, nor Haswell, nor even laptops.

gotta be a s/w issue. not that unlike some other .0 releases (anyone remember the erasing entire disks cutie?).

it will be fixed, likely within a week or so.

Quick update,

You are completely correct! I talked to some people and they said that they have had the same lockup when using Macbook Air Haswell and MacBook Pro Early 2013 (Previous) 13" and 15".

The issue here is, I think it's much more frequent under OSX (Mavericks) than Other previous OSX and Windows.