MBP Boots Forever/Crashes on First (but not Second) Boot

Question

Level 1

82 points

MBP Boots Forever/Crashes on First (but not Second) Boot

Hi,

I am experiencing a somewhat odd phenomenon with my MBP:

If I close the lid without sleeping the MBP, the battery might keep on draining and when I open the MBP again later, all battery charge is gone.

If I now reconnect (power) and boot up the MBP, the MBP will not go past the stage where there is a grey background and the "beachball"... I had it in this stage for up to 2 hours, it is just not booting any further. If I do a hard reset (holding power button for 8 sec), the MBP boots normally... So, the MBP crahes on the first boot, but boots (always) successfully on the second boot.

The problem with the current state of things is, that I am regularily loosing work, as the latest files that were open are gone if not saved (which I tend to forget, as closing the lid does not always, and should never, lead to a system crash). I have Word set to auto-save every two minutes, but that does not always work and some other tools do not have that option.

My questions are:

1.) How can I make sure that closing the lid actually sleeps the MBP? (I was researching the problem and found that some people claim that this might be a problem of the Mac not being able to quickly enough dump my 8GB of RAM, and that disabling "safe sleep" via Terminal might solve the problem... it did not help).

2.) How can I prevent the make from freezing on the first boot? (I have also research that, but could not really find somehting specific. I have tried checking disk with disk utility (all OK) and reparing permissions to no avail).

I also had the MBP checked for hardware issues in the Store, and had Mavericks clean installed not long ago (had the same problem with Snow Leopard)...

Could it be my 4GB RAM extension? Or some specific app causing the problem? Any standard procedures to follow to narrow the issue down?

Cheers for any solution or workaround ideas!

Posted on Jan 9, 2014 5:14 PM

Reply

Answer 1

Melophage

Level 5

7,213 points

Jan 9, 2014 7:55 PM in response to _daniel_

_daniel_,

from your description, my suspicion would be that your currently installed RAM is faulty. If you still have your original 4 GB of RAM, try reïnstalling that, and see if these problems continue when you have 4 GB of RAM installed rather than your current 8 GB of RAM. If these problems stop, then you need to determine whether one or both of the newer memory modules have a fault.

Reply

Answer 2

_daniel_ Author

Level 1

82 points

Feb 7, 2014 12:43 AM in response to Melophage

Hi Melophage,

The MBP came with 8GB installed by an Apple resellers, so I am probably out of luck getting the original 4GB... but it also makes it less then likely that it is the RAM. But, if this is the solution, I will sent them my MBP.

Is there anything that I could try locally before doing so? Not so great to not have your MBP for some days...

Thank you!

Reply

Answer 3

Melophage

Level 5

7,213 points

Feb 8, 2014 11:46 AM in response to _daniel_

_daniel_,

to see how your MacBook Pro currently reacts to sleeping, try giving the following commands in Terminal:

pmset -g

pmset -g assertions

What output do these commands produce?

Regarding your second question, the range of possible options to perform locally depends upon which model MacBook Pro you have, and which version of OS X is installed on it. You could try resetting your System Management Controller, if you haven’t done do already.

Reply

Answer 4

_daniel_ Author

Level 1

82 points

Feb 9, 2014 12:55 AM in response to Melophage

Hi,

Thank you for helping me.

pmset -g

Active Profiles:

Battery Power -1

AC Power -1*

Currently in use:

standbydelay 4200

standby 0

womp 1

halfdim 1

hibernatefile /var/vm/sleepimage

sms 1

networkoversleep 0

disksleep 10

sleep 0 (sleep prevented by InternetSharing, coreaudiod, coreaudiod)

autopoweroffdelay 14400

hibernatemode 1

autopoweroff 1

ttyskeepawake 1

displaysleep 60

acwake 0

lidwake 1

pmset -g assertions

Assertion status system-wide:

BackgroundTask 0

PreventDiskIdle 0

ApplePushServiceTask 0

UserIsActive 1

PreventUserIdleDisplaySleep 0

InteractivePushServiceTask 0

PreventSystemSleep 1

ExternalMedia 0

PreventUserIdleSystemSleep 1

NetworkClientActive 0

Listed by owning process:

pid 48(InternetSharing): [0x0000000800000172] 54:15:44 DenySystemSleep named: "com.apple.InternetSharing"

pid 176(coreaudiod): [0x0000000100002563] 00:13:32 NoIdleSleepAssertion named: "com.apple.audio.'AppleHDAEngineOutput:1B,0,1,1:0'.noidlesleep"

pid 176(coreaudiod): [0x00000001000010ee] 31:46:01 NoIdleSleepAssertion named: "com.apple.audio.'BoomEngine:0'.noidlesleep"

pid 50(hidd): [0x0000000a00002554] 00:16:54 UserIsActive named: "com.apple.iohideventsystem.queue.tickle"

Timeout will fire in 3595 secs Action=TimeoutActionRelease

No kernel assertions.

Can you tell anything from these responses?

I will also reset the SMC now (also I believe to have done that before)...

Kind regards

Reply

Answer 5

Melophage

Level 5

7,213 points

Feb 9, 2014 12:36 PM in response to _daniel_

_daniel_,

if you open the Sharing pane in System Preferences, is Internet Sharing currently checked? If so, then some other device using your MacBook Pro’s Internet Sharing could be preventing your MacBook Pro from sleeping. Try unchecking that check box, if you don’t need to provide Internet Sharing through your MacBook Pro.

It looks as though you have two audio devices that are also preventing your MacBook Pro from sleeping. I presume that the BoomEngine is found in a port of Doom? The AppleHDAEngineOutput would seem to be part of OS X, but I don’t know what controls it.

Reply

Answer 6

_daniel_ Author

Level 1

82 points

Feb 9, 2014 7:26 PM in response to Melophage

Hi,

I have disabled Internet Sharing and uninstalled Boom (an app to boost the volume of the Mac, sometimes I cannot understand my counterpart on Skype because the inbuilt speaker are so low)... However, I only enabled/installed those recently, the problem is older.

It might in fact be a problem in relation to the "AppleHDAEngineOutput" process... I googled it, and it was mentioned several times in relation to sleep issues.

If you or anyone knows how to fix that? Or could it still be something else?

Thank you,

Daniel

---

pmset -g

Active Profiles:

Battery Power -1

AC Power -1*

Currently in use:

standbydelay 4200

standby 0

womp 1

halfdim 1

hibernatefile /var/vm/sleepimage

sms 1

networkoversleep 0

disksleep 10

sleep 0

autopoweroffdelay 14400

hibernatemode 1

autopoweroff 1

ttyskeepawake 1

displaysleep 60

acwake 0

lidwake 1

MacBookPro-A820664C9D3B-3:~

pmset -g assertions

10/02/2014 2:25:32 pm AE

Assertion status system-wide:

BackgroundTask 0

PreventDiskIdle 0

ApplePushServiceTask 0

UserIsActive 1

PreventUserIdleDisplaySleep 0

InteractivePushServiceTask 0

PreventSystemSleep 0

ExternalMedia 0

PreventUserIdleSystemSleep 0

NetworkClientActive 0

Listed by owning process:

pid 50(hidd): [0x0000000a000009f8] 01:57:55 UserIsActive named: "com.apple.iohideventsystem.queue.tickle"

Timeout will fire in 3592 secs Action=TimeoutActionRelease

Kernel Assertions: 0x4=USB

id=503 level=255 0x4=USB mod=10/02/2014 1:48 pm description=EHC1 owner=AppleUSBEHCI

Reply

Answer 7

Melophage

Level 5

7,213 points

Feb 10, 2014 5:50 PM in response to _daniel_

_daniel_,

I don’t know what controls the AppleHDAEngineOutput, so I’m unable to make any recommendations regarding it.

Reply