AppleACPIPlatformPower Kernel Panic Fix on Wake

Kernel panic on wake from sleep pointing at AppleACPIPlatformPower? It's almost always a third-party kext or bad sleep state S3/S4 handling. Here's the real fix.

Quick answer: Boot in Safe Mode, pull any third-party kexts (especially USB, audio, and network drivers), check /Library/Logs/DiagnosticReports for the panic stack, and if the panic persists, reset NVRAM and force hibernatemode 0 or 3 depending on the Mac.

AppleACPIPlatformPower is the ACPI power management driver that handles sleep states S3 (suspend to RAM) and S4 (hibernate to disk). When macOS wakes, this driver has to reinitialize the PCIe bus, USB controllers, and GPU in the right order. If a third-party kext is mid-transaction when the power state flips, or if the firmware hands back bad ACPI tables, the kernel panics and dumps the stack right at AppleACPIPlatformPower. I've seen this most on 2013–2015 MacBook Pros and 2017+ iMacs running Monterey through Sonoma, usually right after the user installed a USB audio interface driver or a VPN client with a network filter.

Step 1: Confirm the panic is real, not a wake-loop

Open Terminal and pull the last few panic reports:

ls -lt /Library/Logs/DiagnosticReports | head -20
cat /Library/Logs/DiagnosticReports/Kernel*.panic | tail -60

Look for the panicString line. If it says panic(cpu X caller 0x...): "AppleACPIPlatformPower" followed by a backtrace that includes a third-party kext name, you've got your answer. If the backtrace is pure Apple kexts, skip to Step 4.

Step 2: Boot Safe Mode and disable third-party kexts

Intel Macs: power off, hold Shift at boot. Apple Silicon: power off, hold the power button until "Loading startup options" appears, then hold Shift while clicking your disk. Safe Mode disables third-party kexts and clears the kext cache.

Once you're in, list what's loaded:

kmutil showloaded --collection auxiliary
ls /Library/Extensions

Anything in /Library/Extensions that isn't Apple-signed is a suspect. Common offenders: Blackmagic Desktop Video, Focusrite Saffire, Rogue Amoeba Loopback, Little Snitch's network extension, and various Thunderbolt dock drivers.

Step 3: Sleep, wake, and watch

While still in Safe Mode, put the Mac to sleep and wake it. If it wakes clean, you've confirmed a third-party kext. Reboot normally and remove kexts one at a time. Don't try to be clever and remove them all at once — you'll never know which one caused it.

To remove a kext properly:

sudo kextunload /Library/Extensions/OffendingKext.kext
sudo rm -rf /Library/Extensions/OffendingKext.kext
sudo kmutil clear-staging
sudo reboot

Step 4: If it's still panicking on stock kexts

Then it's ACPI or firmware. Reset the NVRAM first — it's free and fixes about 20% of these:

sudo nvram -c
sudo reboot

On Intel, hold Cmd+Opt+P+R at boot for two chimes. On Apple Silicon, NVRAM is handled automatically; skip this step.

Next, check your hibernatemode. On desktops (iMac, Mac mini, Mac Pro), it should be 0. On portables with an SSD, 3 is fine. A mismatched hibernatemode after a disk upgrade or OS migration is a classic trigger:

pmset -g | grep hibernatemode
sudo pmset -a hibernatemode 0

Also disable Power Nap. It runs background tasks during sleep and I've seen it wake the ACPI driver into a bad state on 2014-era Macs:

sudo pmset -a powernap 0

Step 5: SMC reset (Intel only)

If nothing else works, it's an SMC issue. On a MacBook with a non-removable battery: shut down, plug in the charger, hold Shift+Control+Option+Power for 10 seconds, release all at once, then boot. On a Mac mini or iMac: unplug for 15 seconds, plug back in, wait 5 seconds, boot.

Alternative fixes if all that fails

Disable sleep entirely as a stopgap: sudo pmset -a sleep 0 disksleep 0. Not a fix, but it keeps you working.
Boot from an external drive with a clean macOS install. If it sleeps fine there, your internal install has corrupted kernel caches. Reinstall macOS over the top — your data stays.
Check for a firmware update. Apple quietly ships ACPI fixes in EFI updates. On Intel Macs, run Software Update and check for a firmware item, not just a macOS update.
Apple Silicon users: you can't really fix this at the user level. If it panics on wake with stock kexts, it's a hardware or firmware bug. Take it to Apple. I've seen two M1 MacBook Airs with bad RAM that presented exactly this way.

Prevention

Before you install any USB audio interface, Thunderbolt dock, or VPN with a network filter, check the vendor's site for a macOS-version-specific driver. The panic almost always shows up after a macOS point update breaks kext compatibility — Ventura 13.4 and Sonoma 14.2 both broke a handful of audio drivers on wake. If you're running a critical machine, hold off on point updates until the vendor confirms support. And keep a bootable clone; it's the fastest way to prove whether a panic is software or hardware.

One more thing: don't trust third-party "cleaner" apps that claim to fix kernel panics. They don't. They just clear caches you can clear yourself with sudo kmutil clear-staging.