MacBook Pro 16 2019 10.15.4 Kernel Panic / Reboot When Plugged In -- Help!

I have same problem, on my MBP 16 core i9

This issue a hardware or software?,

every time after asleep is kernel panic. Reinstall system doesn’t help.

I am very worried, I just bought and have issues :(

I'm also having the same issue. Ordered a refurbished 16" direct from Apple - came installed with 15.3 and I haven't upgraded to 15.4 yet since the error seems to continue. It's the 2.4GHz i9 processor with 32GB RAM and the 630 graphics. I've been keeping a daily log of the crash reports, most typically it's a "GPU panic" error but for two days I also received "hibernate restore error" instead.

The conditions are identical - closing the lid on the computer for more than an hour, coming back and it doesn't awake from sleep. I need to hold down the power to start up from the black and white logo, then get a crash log on the desktop after signing in with password. Really frustrating for a brand-new, professional grade laptop. I bought to replace a 2011 13" MBP that also just developed kernel panics, which was more acceptable in a 9-year old machine.

Also adding that I called help once already to start a file, told support that I'm seeing records of this relating to a logic board issue, and they dismissed me after an NVRAM and PRAM reset which did nothing.

can you tell me something about my report? I will try clean system tonight. Anyway with my backup every morning problem occurs. Disable power nap works. Then I tried to work with Parallels (still version 14 maybe that’s problem) settings and yesterday I turned back on power nap and at the morning it was fine. I can still return my mbp (till Friday) that’s why I ask. I don’t know what to do. If it is soft I can live with it

have the same exact issue with my MacBook 15 from 2017, apple replace it for a new 16 inch. Same issue ....

I hope that if it is a software issue the solve it quickly if not I am going to ask to have my money back .

I am posting here so I can see if an answer gets posted. This has been a frustrating problem for me as well.

MacBook Pro (16-inch, 2019)

2.6 GHz 6-Core Intel Core i7

16 GB 2667 MHz DDR4

Intel UHD Graphics 630 1536 MB

Running 10.15.4

Thanks, I brought this 16 inch macbook pro and I had it for less than a week and I am seeing this problem. I cant believe these idiots do not think it is worthy of their time to address your concerns. You have spent so much time in trying to trouble shoot this. If this problem occurs for me again, I am sending this back to apple. They can have their macbook, I know I wont make a dent, but at this rate I dont think they will benefit either.

This attitude is visible even when we go to a apple store, apple should know that no matter how good their products are, without customers they are worthless.

I have had the same problem. I posted a blog post about it here. I used a workaround to see if there is no reboots or kernel panics with watchdog or windowserver odd super high cpu. There are a number of posts around about this rebooting issues. I have a brand new MacBook Pro. If this article helps you, awesome.

Appreciate all you have done to try and get to the bottom of this. I am not particularly technical - especially from a hardware POV - so when I got my new Mac (having spent a small fortune in uncertain times) you can imagine how alarming it was seeing a brand new machine repeatedly crash. I agree that it seems the perception and lived experience of Apple customers has become more like it was for many of us in the bad old MS windows PC days years ago when you more or less expected your machine to randomly fall over and struggled to make it work with peripherals. Certainly it means jumping out of the Apple ecosystem becomes less unthinkable when Apple's reputation for leading in high quality usable products and reliability is tarnished by fumbles like this.

Spoke to a friend last night. He has a standard config 2.3 MBP without any KP issues. As I have a customized one I was wondering that might be of influence. Anywone with KP issues here have a standard config?

Thanks and yes it is indeed so dismaying. I do believe Apple has lost its way in many respects. I still prefer MacOS and iOS to any alternatives and this continue to make them my primary computing platforms. Though the past two years I’ve been put in an awkward position more than once to seriously consider a jump back to (blasphemy) Windows.

I believe the most frustrating aspect of what is happening is that so much good can be riddled with just enough bad that it ruins the experience entirely.

A beautiful and powerful laptop that crashes when it goes to sleep??? I haven’t had to contend with such issues since dealing with managed corporate Windows Laptops in the early 2ks. And Macs has no such issues.

The tables have sadly turned. But hopefully this is just a speed bump along the road of progress. Honestly, the best we can do is to be vocal. Send feedback. Be loud about what we want and ultimately vote with our wallets by withholding on upgrades if absolutely necessary.

As an example I refused to upgrade to a new MacBook Pro from my last late 2014 fully maxed/custom Pro until they offered at least 32GB of ram. I needed that and held out as long as I could. Thankfully it paid off and now I have machines with 64GB. Haha. Granted they just need to ensure they don’t crash and I’ll be quite pleased.

Me too! I got a maxed out spec machine and did the upgrade and have the KP issue when nap enabled. I too also get the sharp shift in screen colour every now and again. Agree to have these niggles having paid so much is super annoying.

I have the same issue with 2014 MacBook Air 11 since upgrading to 10.15.4. I thought something got messed up during the upgrade so I did a fresh install of the OS. No dice. Same issue. My laptop is usually plugged in and lid closed connected to an Apple Thunderbolt Display. PowerNap is off.

I have this happening to me, too. The beginning part of the message looks like this:

panic(cpu 0 caller 0xffffff800be16487): 
"AppleIntelFramebuffer::setPowerState(0xffffff81bb0e1000 : 0xffffff7f8f3a8d88, 1 -> 0) 
timed out after 45917 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/
xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296

I walk away with computer totally fine, but come back to a computer that's turned off. Pressing a key restarts the computer, then it shows this message "Your computer was restarted because of a problem."

Every. Single. Time.

Has anyone found a solution to this other than keeping the monitor turned on at all time? My MBP also has the fan on really strong whenever I start Premier or After Effect. Just starting. Not even doing anything in the app, and my MBP starts running the fans in full speed.

Here is my MBP hardware: MBP 16-inch, 2019. 2.3 GHz 8-Core i9. 16GB 2667 MHz DDR4. AMD Radeon Pro 5500M 4GB. Intel UHD Graphics 630 1536 MB. Boot ROM Version: 1037.100.362.0.0 (iBridge: 17.16.14281.0.0,0)

Catalina 10.15.4

Thanks!

I ask myself why they do never mention this problem officially and why Apple does not care about customers having this very serious problem? I experience kernel crashes on a regular basis with a new MBP 16'.

I am so disappointed about the software quality of Apple since I never had such a serious issue with a Windows 10-based device. Considering the premium prices that customer do pay for Apple Notebooks I really expected much much more than being left alone with an unusable device.