MBP Late 2016 - Audio stops working, requires reboot

Question

Level 1

13 points

MBP Late 2016 - Audio stops working, requires reboot

I'm really enjoying my new MacBook Pro (late 2016, 15"), but it's got a weird problem with sound.

After I've been using it for a while, the audio just stops working. It's often after it comes back from sleep.

It can also happen after I unplug some USB headphones. If I plug those same USB headphones back in, I can get audio through them again, but getting audio out of the internal speakers no longer works at all until I reboot.

Yes, "Internal Speakers" is selected as my sound output device. I've also tried selecting another audio device (the USB headphones, the DisplayPort-based monitor) and then switching back to "Internal Speakers", but it doesn't help. The only thing that fixes it is a reboot.

Any ideas?

Mac OS X (10.5.1)

Posted on Dec 3, 2016 1:39 PM

Reply

Answer 1

Top-ranking reply

Adam Darton

Level 1

9 points

Mar 22, 2017 6:32 AM in response to Mr. Grue

I have this problem too, about once a day my audio stops working. What you can try if you don't want to reboot which can be inconvenient is to force the audio daemon to restart. Works for me.

Open up the terminal and type:

sudo killall coreaudiod

Note: its going to ask for your password for permission

Reply

Answer 2

Dec 3, 2016 8:50 PM in response to Mr. Grue

There is another recent thread about this topic here:

https://discussions.apple.com/thread/7763090

No resolution yet as of this post. I'm not finding many other mentions of this issue besides these two threads, but I'm hoping that Apple acknowledges this issue soon.

Reply

Answer 3

Dec 9, 2016 7:15 AM in response to Mr. Grue

I am definitely have the same issue with my 15" 2016 MacBook Pro. I've tried to find a maneuver that will reactivate the headphone jack audio output (switching between the several outputs I have (all the others work), putting back to sleep and awakening, trying different audio sources). The only thing I've found that works is restarting the whole system. Unfortunately, I can't find a way to reproduce the problem consistently. It has happened to me 3 times since I got my system several weeks ago. Can't identify any pattern to this except that, for me, it seems to happen after awakening from sleep.

Sandy

Reply