> ## Documentation Index
> Fetch the complete documentation index at: https://docs.macstadium.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Why are coreaudiod and launchd using a high amount of resources?

> A customer-confirmed fix for coreaudiod and launchd consuming high CPU on macOS, caused by a crashed Bluetooth daemon (com.apple.blued).

We've heard about this from a couple of customers. Here's a fix one customer confirmed resolved `coreaudiod` and `launchd` consuming a high amount of CPU.

<Note>
  We're an infrastructure provider first, and can only offer limited help with software issues like this one. We can't guarantee this fix works for every case, contact Apple for further support on the underlying software. We can also provide a list of vendors we work with if you need dedicated software support.
</Note>

From a customer:

> I figured out what the problem was, in case anyone else runs into this. The Bluetooth daemon had crashed. I'm not sure why that made `coreaudiod` and `launchd` go crazy, but the fix is this:
>
> ```shell theme={null}
> sudo launchctl unload -w /System/Library/LaunchDaemons/com.apple.blued.plist
> ```
>
> If the daemon has crashed, you may see a message like this:
>
> ```
> /System/Library/LaunchDaemons/com.apple.blued.plist: Could not find specified service
> ```
>
> Next, run this:
>
> ```shell theme={null}
> sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.blued.plist
> ```
>
> Once `blued` is running properly again, `coreaudiod` and `launchd` both settle down.


## Related topics

- [Resiliency, High Availability, and Disaster Recovery](/orka/orka-resources/resiliency-high-availability-and-disaster-recovery.md)
- [Private Cloud x86 VMs](/iaas/x86-vms-private-cloud-vms/private-cloud-x86-vms.md)
- [Working with Orka VM metadata and custom tags](/orka/orka-resources/working-with-vm-metadata.md)
- [MacStadium VDI troubleshooting quick reference](/remote-desktop-vdi/reference/troubleshooting-quick-reference.md)
- [Advanced configuration](/remote-desktop-vdi/configuration/advanced-configuration.md)