Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

New MacBook kernel panics

Just wanted to add my own experience to the pile. My MBP 16" (5300M) has crashed (screen frozen, hard restart) when playing games (Shadow of the Tomb Raider & WoW Classic) dozens of times since I purchased it in December. SMC reset, RAM flash, and OS reinstall have not fixed the problem. Now, with 10.5.4, my computer is crashing after being put to sleep. I have reported the issue to Apple Support and intend to get my MBP replaced once Apple stores re-open.
 
  • Like
Reactions: Cosmo M3
The issue is documented and being tracked pretty well here:
mrmacintosh.com

10.15.5 & 10.15.4 = Wake from Sleep Kernel Panic on 16" MBPro (2019)

Does your 16" MacBook Pro 2019 Kernel Panic or Restart when you wake it from sleep after installing the Catalina 10.15.4/5 Update? Latest Info + Workarounds
mrmacintosh.com mrmacintosh.com

I've had this issue since I set up my new 16" MBP (migrating from a time machine backup of my 2016 15" MBP). Right now I'm using Amphetamine to keep macOS from going to sleep. Annoying, but it's the only thing I've found that works. I've tried resetting SMC/NVRAM multiple times, fiddling with various power management settings -- all results in a similar panic and crash message at some point.

Notable thing is that I have the MBP always connected to an LG display (which is also providing power via USB-C). I suspect that this plays a role in the crashes.
 
  • Like
Reactions: obargy and WiLLGT09
Mine has not crashed in about a week maybe 2 after turning off power nap in settings and I haven't had any hardware replaced like Cosmo so I think this is most likely just a software issue with power nap.
 
  • Like
Reactions: obargy
I have the exact same problem. My macbook pro is a retina from late 2015. It has crashed 8 times now. This never happened before upgrading to 10.15.4. I have no external hardware connected.
 
  • Wow
Reactions: obargy
Had the same problem. It's now solved.

Status here after 5 days with no problems.
My GPU Panic sleep problem is still solved. After the fix I also installed my video-rendering tools, my developer tools, all my other stuff.

My energy saving stuff is back to normal (standard settings), så is does the Power Nap as expected.

Having it gooing to sleep on power, on batteries, forced it to run out of batteries. Did intense GPU-use. Still no problems.

Running 10.15.4

Solution for me was
My brand new macbook pro 16 (Shipped 2. april 2020) also restarted (crashed) over nigth - actually it crashed (Kernel Panic GPU) everytime it went to sleep mode. I had nothing installed except default OSX with updates.

Solution details
  1. Reset: Pram & NVRAM (still crashed)
  2. Reset: SMC (still crashed)
  3. Internet Recovery Command+Option+R (when booting) (Crashed under installation, but continued install afterwards)
  4. Disabled "Prevent computer from sleeping automatically when the display is off." & "PowerNap.." in Energy Saver settings (Problems disappeared)
  5. Two days later I enabled "Prevent computer from sleeping...." and "Powernap..." again (Still no problems)
I don't know if step 1-3 is necessary, but I think so.

So a macbook pro 16 that I almost returned, is now working perfectly - and I'm very happy:)
 
  • Like
  • Wow
Reactions: obargy, Meuti and crouch
That is not a solution: "Prevent computer from sleeping automatically when the display is off".
You mean that your computer will always be turned on ???
That costs a lot of money and you cannot put the machine to sleep for travel.
 
mtmmtm said:
That is not a solution: "Prevent computer from sleeping automatically when the display is off".
You mean that your computer will always be turned on ???
That costs a lot of money and you cannot put the machine to sleep for travel.
Click to expand...

That is not what I’m talking about. It’s the speciel “power nap” feature I refer to (last option in the power settings screen. When disabled your Mac will even sleep more than before because it will not check e-mails etc. When sleeping. Other people has reported the same observation and solution.
 
I have disabled power-nap for many years. Are you a mac-developer ? I thing this discussion is fundamentally wrong. Any user should be able to enter any input to any form. It should not be possible to crash my macbook whatsoever.
 
I'm experiencing this issue too now -- Less-than-a-month-old 2019 16" MacBook Pro (i7/32GB RAM/5300M) running 10.15.4 Supplemental Update (19E287).

Received Mac right around 10.15.4 OS update time. Updated macOS almost immediately. Initially, I experienced issues with the Mac rebooting on its own after waking the Mac from sleep while attached to my external display. Panic messages referred to: " userspace watchdog timeout: no successful checkins from com.apple.WindowServer"

Code: 
panic(cpu 6 caller 0xffffff7f8f1a0ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds

...etc etc ... (see here: https://forums.macrumors.com/thread...er.2222878/page-5?post=28331148#post-28331148)

Then, the 10.15.4 Supplemental Update came out, and perhaps that fixed this issue, or maybe it was due to me changing some of the Energy Saver settings (adjusting time-to-sleep and disabling Power Nap). Needless to say, I haven't had this exact issue now for a week or so, even with using mac attached to an external display. (And using mac by itself, raising lid to wake worked perfectly).

HOWEVER, now I'm seeing this other odd rebooting issue. Over the weekend, I had been using my MacBook Pro by itself, disconnected from my external LG UltraFine 4K monitor. This morning, I brought my Mac back to my desk, connected the monitor and attempted to wake the system with mouse/keyboard. Note that I had not waken the mac earlier today while away from my desk. I simiply unplugged mac from power cable, brought it over to the desk, connected the Thunderbolt cable for the external display/power, and woke the mac with external mouse and keyboard.

Initially, it worked, and I entered my password and saw the desktop. However almost immediately, the system was basically frozen. Mouse & keyboard were unresponsive. Then the screen goes black. Reboot. And I see this error message:

"panic(cpu 1 caller 0xfffffff01e2cb7b4): x86 CPU CATERR detected"

Panic message:

Code: 
panic(cpu 1 caller 0xfffffff01e2cb7b4): x86 CPU CATERR detected
Debugger message: panic
Memory ID: 0x6
OS version: 17P4281
macOS version: 19E287
Kernel version: Darwin Kernel Version 19.4.0: Mon Mar  2 20:38:56 PST 2020; root:xnu-6153.101.6~2/RELEASE_ARM64_T8010
Kernel UUID: 3695E9D9-323E-350E-9A6E-65819BE397D7
iBoot version: iBoot-5540.105.2
secure boot?: YES
x86 EFI Boot State: 0xd
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0x5
x86 Previous Power Transitions: 0x10001000100
PCIeUp link state: 0x89473614
Paniclog version: 13
Kernel slide:     0x0000000016294000
Kernel text base: 0xfffffff01d298000
mach_absolute_time: 0x1e03492014e
Epoch Time:        sec       usec
  Boot    : 0x5e99c322 0x0000ff4f
  Sleep   : 0x5e9d969e 0x000dc0e6
  Wake    : 0x5e9d96cc 0x00056e35
  Calendar: 0x5e9d96f7 0x00018901

Panicked task 0xffffffe000893c00: 3270 pages, 220 threads: pid 0: kernel_task
Panicked thread: 0xffffffe000c65520, backtrace: 0xffffffe01755b4b0, tid: 336
          lr: 0xfffffff01db5c764  fp: 0xffffffe01755b4f0
          lr: 0xfffffff01db5c5c0  fp: 0xffffffe01755b560
          lr: 0xfffffff01dc76e7c  fp: 0xffffffe01755b610
          lr: 0xfffffff01e12562c  fp: 0xffffffe01755b620
          lr: 0xfffffff01db5bf28  fp: 0xffffffe01755b990
          lr: 0xfffffff01db5c280  fp: 0xffffffe01755b9e0
          lr: 0xfffffff01e992934  fp: 0xffffffe01755ba00
          lr: 0xfffffff01e2cb7b4  fp: 0xffffffe01755ba30
          lr: 0xfffffff01e2bcbe4  fp: 0xffffffe01755baa0
          lr: 0xfffffff01e2beb0c  fp: 0xffffffe01755bb50
          lr: 0xfffffff01e2bc31c  fp: 0xffffffe01755bbe0
          lr: 0xfffffff01e283780  fp: 0xffffffe01755bc10
          lr: 0xfffffff01e092abc  fp: 0xffffffe01755bc50
          lr: 0xfffffff01e092340  fp: 0xffffffe01755bc90
          lr: 0xfffffff01e130514  fp: 0x0000000000000000


UGH. And this is the second time this has happened; after reconnecting Mac to external display while it's asleep and trying to wake the machine. Never had this issue with my previous Apple MacBooks.

(And I've tried resetting NVRAM, SMC, disk permissions for the earlier issues, but they seemed to have no real effect on the matter.)

Curious about testing 10.15.5 betas...
 
  • Wow
Reactions: obargy
I hit both the issues yesterday.

Had to chat with an Apple service rep and we did the following:
1. Reset SMC
2. Disable power nap (both battery and power adapter)
3. Disable sleeping when display turns off (First option under the power adapter)

I was consistently hitting the issue before doing these steps.

I have not seen it since then.

I will see how it goes!

Hope they fix it in the next software patch
 
Yeah, that seems to solve my initial panic issue related to "watchdog timeout: no checkins from watchdogd..." but there seems to be more than one issue with 10.15.4 (https://mrmacintosh.com/10-15-4-update-wake-from-sleep-kernel-panic-in-16-mbpro-2019/).

As I mentioned in my earlier post, I had experienced an unexpected reboot after reconnecting my still-sleeping MacBook Pro to my external monitor and then trying to wake it...

Interestingly, today I tried a different order of operations, starting with mac asleep & disconnected from the display once more: first opening the lid and waking the mac up (login via touch id), then shutting the lid and quickly connecting the mac to my external monitor and re-waking it with the mouse and keyboard. I managed to do it quickly enough that the system didn't sleep (didn't have to re-enter user password with keyboard), and I didn't experience any freeze or panic/reboot like I did the other day. Hmm..

^ EDIT: Something just occurred to me... I should add that my current privacy & security settings are set so that my system requires my password for 5 seconds after sleep or screen saver starts. I'm guessing that if I increase this time limit, I wouldn't need to "rush" plugging my Mac back into the displays after shutting the lid.
 
Last edited:
Just had this happen today. Piece of **** update, I've had this computer since December without any serious issues (besides the unfixable audio popping which doesn't bother me in my use case). Finally now having non bad magic kernel panics. Does anyone know if rolling back to 10.15.3 fixed it?
 
Viamusic10000 said:
Just had this happen today. Piece of **** update, I've had this computer since December without any serious issues (besides the unfixable audio popping which doesn't bother me in my use case). Finally now having non bad magic kernel panics. Does anyone know if rolling back to 10.15.3 fixed it?
Click to expand...

I doubt if rolling back to 10.15.3 would fix this issue. It’s been happening with my MBP16 for the last few weeks using 10.15.3.
 
interbear said:
I doubt if rolling back to 10.15.3 would fix this issue. It’s been happening with my MBP16 for the last few weeks using 10.15.3.
Click to expand...
It just happened to me and I never got it before, strange. Are you sure it’s the same error log? I have a friend who’s getting this error on the pre t2 13 in so it must be software
 
This helped me after my macbook couldn’t complete booting for 2 hours due to kernel panics:
1. Booting in save mode
2. System Preferences / Energy Saver / Power Adapter -> Disabling: “Prevent computer from sleeping…” & “Enable Power Nap while…”
3. open terminal -> sudo pmset -a standby 0
 
I have tried the Terminal PMset workaround and turning off the relevant power settings. And yet, last night, I got another one. Woke up to a shutdown MacBook and new instantly that it had KP'd overnight.

"macOSPanicFlags" : "0x4",
"macOSPanicString" : "panic(cpu 0 caller 0xffffff801b016487): \"AppleIntelFramebuffer::setPowerState(0xffffff836321d000 : 0xffffff7f9e5a6d88, 2 -> 1) timed out after 45439 ms\"@\/AppleInternal\/BuildRoot\/Library\/Caches\/com.apple.xbs\/Sources\/xnu\/xnu-6153.101.6\/iokit\/Kernel\/IOServicePM.cpp:5296\nBacktrace (CPU 0), Frame : Return Address\n0xffffff83c5703b40 : 0xffffff801a9215cd \n0xffffff83c5703b90 : 0xffffff801aa5a3c5 \n0xffffff83c5703bd0 : 0xffffff801aa4bf7e \n0xffffff83c5703c20 : 0xffffff801a8c7a40 \n0xffffff83c5703c40 : 0xffffff801a920c97 \n0xffffff83c5703d40 : 0xffffff801a921087 \n0xffffff83c5703d90 : 0xffffff801b0c2c7c \n0xffffff83c5703e00 : 0xffffff801b016487 \n0xffffff83c5703e50 : 0xffffff801b015d69 \n0xffffff83c5703e60 : 0xffffff801b02d2fe \n0xffffff83c5703ea0 : 0xffffff801b014b18 \n0xffffff83c5703ec0 : 0xffffff801a963545 \n0xffffff83c5703f40 : 0xffffff801a963071 \n0xffffff83c5703fa0 : 0xffffff801a8c713e \n\nBSD process name corresponding to current thread: kernel_task\nBoot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev\n\nMac OS version:\n19E287\n\nKernel version:\nDarwin Kernel Version 19.4.0: Wed Mar 4 22:28:40 PST 2020
 
So I disabled PowerNap and Automatic Graphic Switching in the Energy Saver settings. 3 days later and my MBP16 has slept overnight with zero crashes / restarts and I’ve not had the strange graphics issue that was randomly occurring on certain apps (pixelated screen). Everything seems to be working just fine. Hopefully it continues like this.
 
I talked to engineering about this. They are apparently aware of this and working on it. I can also confirm that turning off power nap fixed any sleep/wake issues I was having.
 
  • Like
Reactions: WiLLGT09
Ross Pomeroy said:
Just wanted to add my own experience to the pile. My MBP 16" (5300M) has crashed (screen frozen, hard restart) when playing games (Shadow of the Tomb Raider & WoW Classic) dozens of times since I purchased it in December. SMC reset, RAM flash, and OS reinstall have not fixed the problem. Now, with 10.5.4, my computer is crashing after being put to sleep. I have reported the issue to Apple Support and intend to get my MBP replaced once Apple stores re-open.
Click to expand...
That probably has more to do with the games than your computer. The crash during sleep is a software issue that is happening on older computers as well and won’t be fixed by replacing your computer. Have you tried gaming in bootcamp? Usually if a game hard locks it’s a driver issue or you’re running out of vram
 
I've experienced this one "panic(cpu 0 caller 0xffffff8011291b2c): Sleep transition timed out after 180 seconds while notifying clients about upcoming system capability changes. Suspected bundle: com.apple.iokit.IOGraphicsFamily. Thread 0x74."
I disabled power nap at all and Prevent computer from sleeping automatically when the display is off.
I will check tomorrow if it works or not. Anyway I am still thinking about "sudo pmset -a standby 0". Sorry for this simple question but what does this command mean?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back