CoreAudiod 90% cpu and hightemps

Perfekt solution, safes my life.

Thanks a lot

Al

Thank you, sasansamit. That's the answer.

Hello,

I'm new to macs and have this as my first big issue. I found this post and it sounds like what I need. MBP barely a month old and have no idea how to "update the config" as sasansamit suggested. Could anyone offer guidance on how to do this? For me the issue started when playing a flash video in Safari.

Any help is appreciated! Thanks!

Samit, thank you!

Yes, that directory was missing just as you said, after restoring an image with DeployStudio, and coreaudiod over 100% and making the mini warm. So I packaged up those plists and installed them, and after a reboot coreaudiod seems back to normal. 🙂

Thanks mondomori for your clues. Like I said, I don't know what I am doing so I used these clues to find out how to restore the audio preferences. I must have nuked the preferences file trying to fix something else (my mistake). I used this trick and recreated the single missing Audio preferences folder with permissions. Once I did that, a plist file was immediately created by the coreaudio process. After restarting to clear the PRAM and NVRAM, another plist file appeared in the folder and now my audio seems to work fine!

Thanks for all your help!!

I was having the same problem and finally fixed it after 4 hours and a good 30 different attempts at fixes from around the web.

I grabbed the Library/Preferences/Audio folder from another Mac I own, dropboxed it to myself, and dropped it into my the Preferences folder of the affected Mac after I noticed that folder was missing.

Reboot and boom, solved my problem.

Killing the process didn't help me, nor did PRAM, etc.

I found that the following (from another post) fixed the issue of the overheating CPU for me. Hopefully this will help others.

Deleted the Audio folder located at [OSX HDD Name]/Library/Preferences/ and create a new one as root in the terminal:
"sudo mkdir /Library/Preferences/Audio"

then set permissions:
"sudo chown -R _coreaudiod:admin /Library/Preferences/Audio"

Where does Coreaudiod come from? Is it an Apple function? Has anybody noticed this happening after using Amazon's Cloud to play music? I had not seen Coreaudiod in my system until after playing Amazon Cloud music yesterday.

Re: "coreaudiod" issues in Mountain Lion 10.8.2. I'm not sure exactly which post to reply too, but I'm having a similar problem "without the heat issue." My problem is my sound icon just grayed out half way though loading at start-up. Obviously, I had "no sound" after same. I'm been working on this off and on for a couple of months. The problem seems to be "bad drivers or at least incompatiable drivers" with the Upgrade to Mountian Lion.

The only fix I have found so far, as Tech Support seemed as though they had never heard of this problem ....Huuummmm (after reading this and other post), was to open Activity Monitor and "Quit" the very first "coreauditd" driver listed. It seems like there are many on my machine, because when I "quit one" another one pops up in it's place. Different size, etc. Thus, the 2nd driver always works. Hence, my strong suspicion that "some" of my sound drivers are either corrupted or incompatible. Hope this helps someone, as I was ready to throw my new machine in the Ocean. I have spent countless hours on this .... NOT HAPPY !! I have reinstalled Mountain Lion at least 4 times, and reset everything I could reset many, many times. One would think Apple would bring their Techs up to speed on this issue, as "what good is Tech Support ... when the Techs giving the support .. are clueless on the issue"??

Contining ... on the "MBP coreaudiod sound issue." The reason I said "upgrade to Mountain Lion" was because this new machine 15" (which came with ML) was a replacement for a 17" MBP that was only a year or two old, but it had a Bad Video Card, and I got the Black Screen of Death all the time. Thus, I have gone from "one problem machine to another" ... Again, NOT HAPPY !!

I think the bad/corrupt or incompatible drivers were introduced to the New machine when Tech Support in the Store cloned over my hard drive so I wouldn't lose all my data, at my request. I had no idea that I was setting myself up for a "bad drivers/incompatible" driver issue. Sooo again, I just hope this helps someone. Now I need to figure out how to get rid of bad/corrupted or incompatible drivers, and the world should "in theory" ... be a better place.

I had the same problem with coreaudiod running at 100 -140% for no reason from start up and after a short while the MBP froze.

I loaded iTunes and the problem is gone. Machine still running a bit slow but running iTunes has sorted it.

Hope this helps someone.

Well, for myself ... I haven't had "the heat issue's," but trying to figure out why I had "no sound" 8 out of 10 times when I booted up my computer was nothing short of "maddening." I asked multiple people/techs etc... and no one could resolve the issue. So again, I have a "band-aid resolution" ... for now .. and that is to simply start "Activity Monitor" and then "quit" the 1st "coreaudiod" file that loads. When the 2nd one automatically loads ... I then have sound. I wish I knew how to " permantently delete" the first bad driver, as that should resolve my problem permanately. I had spent more time trying to resolve the problem and/or find a solution, than the computer is even worth .. if one calulates my wages, against the time I had to spend. Again, NOT HAPPY !!

I had the same coreaudiod problem on Mountain Lion 10.8.3, sasansamit's solution worked in seconds!

In simpler terms:

1. go to /Library/Preferences (make sure it is not /Users/yourname/Library/Preferences, it must be the root directory).

2. Then create a new folder in the Preferences folder and name it Audio.

3. If you have Time Machine setup, simply enter Time Machine while still in that directory, go back a few weeks and there should be 4 files in the Audio folder.

4. Select all of them and press restore. Within seconds everything will be fine

If you don't have Time Machine copy the Audio folder in /Library/Preferences from another Mac to yours.

How to solve the coreaudiod eating up CPU and slowing down your Mac problem.

I wrestled with this for a few hours and wanted to post what I think is the problem and the solution - a few of the replies previously have been 'try this and try that and hope something works'.

After watching my coreaudiod eat up over 100% of CPU for a few hours I tried killing it. That didnt work - it just sprung back. I tried zapping the PRAM and restarting. Coreaudiod would kick in and grind the machine to a halt.

If you are experiencing this, here is what to do:

1. Unload coreaudiod to get your machine back to speed

Enter the following into terminal:

sudo launchctl unload /system/library/launchdaemons/com.apple.audio.coreaudiod.plist

This should free up some CPU for you to complete the fix.

2. Navigate to HD/Library/Preferences and delete the folder named Audio. If you don't have one skip to #3

This is the cause of the issue. This folder contains the preferences for coreaudiod and when the folders permissions go wonky it doesnt know what to do so keeps trying to write prefs to the folder over and over and over and over..

3. Create a new Audio folder in /Library/Preferences

Enter the folliwing into terminal:

sudo mkdir /Library/Preferences/Audio

(or alternately just create a folder in the preferences directory using the finder)

You are making a new blank folder that you are going to set permissions on. Then coreaudiod can record its own prefs and stop freaking out.

4. Set permissions for read/write for admin for this folder

Enter the folliwing into terminal:

sudo chown -R _coreaudiod:admin /Library/Preferences/Audio

(or alternately get info in finder on your new Audio folder, unlock it using the little lock icon, and set permissions to read/write for admin)

5. reload coreaudiod

Enter the folliwing into terminal:

sudo launchctl load /system/library/launchdaemons/com.apple.audio.coreaudiod.plist

That should solve your problems.

Thanks to https://discussions.apple.com/thread/4160772?start=0&tstart=0 for the pieces that finally worked for me.

Awesome answer *thumbs up*