You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Macbook pro 16 2019 freezes randomly and restarts

I just bought a new macbook pro 16 inch 2019 that came with Catalina, I set it up as a new mac and installed some apps (Chrome) and started using it.

The problem is it always freezes at some points and I have to manually restart it by pressing the power button for a few seconds until it shuts down.


This might be just me, but I think this shouldn't happen on a laptop thats costs 2699€.

I updated it to the last version of Catalina and this didn't fix the problem.

I wanted to go back to Mojave, not an option I guess.


What is going on Apple?

MacBook

Posted on Dec 1, 2019 8:27 AM

Reply
Question marked as Top-ranking reply

Posted on Feb 29, 2020 12:21 PM

Darn it ... took too long to post: reposting.


Interestingly I too have a Space Grey MacBook Pro that was "custom".

My specs are: i9 2.3ghz, 32gb Ram, 1TB storage, AMD 5500m 4gb


It took 4 days to troubleshoot but I believe I have a reproducible way to test the Intel 630 UHD GPU issues people are having.


  1. Download Geekbench 5 (I used version 5.1.0)
  2. Select "Later" when the dialog pops up about paying for it. You'll be testing in "Tryout Mode"
  3. Look the the left of the program and you'll select the "Compute" Benchmark
  4. Select Compute API: METAL (OpenCL doesn't error out but Metal does.)
  5. Select Computer Device: Intel UHD 630 Graphics
  6. Open the Console Log app BEFORE YOU run the GEEKBENCH 5 test
  7. Select "Errors and Faults" from the Console log app. It should be at the top.
  8. Start the GeekBench test.
  9. Watch all the red dots proliferate the Console Log app. Most of them will be IntelAccel errors. Many times you will likely see the internal GPU restarting as evidenced by the attached screenshot. Look for signalHardwareError in your logs.

Here is my video of the whole thing. https://youtu.be/Rxh3wATgPOA


During my 7 minute video I try to select the "About the Mac" it takes almost 3 minutes for the window to render while the test is running. You can see in the Activity Monitor in the video it showing as unresponsive.


I truly hope this helps folks - and I wish you all luck. I love Apple and their products. This is obviously something they need to admit and get ahead of because this is turning into something that appears to be a real issue.


My laptop is currently at Apple repair awaiting a logicboard (MLB).


Edited because I hit post too quickly.

672 replies

Apr 24, 2020 12:50 PM in response to Viamusic

1 - Read the thread in its entirety


2 - Check your panic text


3 - Those who have had the aforementioned panic and a hardware repair may not get it fixed because they dont get updated manufactured LBs. They get old ones. <--- Read that... thats really really important.


4 - Go back to the simple formula. If its software, then we all will have the problem. If its hardware, then those with bad hardware have the problem. Think about that for a minute.


5 - We have yet to see > March LBs with the aforementioned GPU panics. Even if we did, its still a minority of users.


6 - People seem to be getting the panics here confused. The hardware panic text have been clearly stated in this thread as known hardware problems. All others are not known to be hardware or software for sure.


7 - I am now officially a broken record continuing to repeat myself over and over and over. This panic has been confirmed by Apple executive team who happen to be the bosses of support engineering.


I really wish people would read this thread entirely. All the data is here and at MacRumors for the problem, the cause, and the fix. Unfortunately the fix for that particular panic (Powerplay failed to xxxxxxxxx) is not software.



Apr 24, 2020 1:15 PM in response to fregsfdvbfeg

The most important thing is that Apple hears our combined voices as one BIG complaint that simply cannot be ignored. All of us have spent a lot of money on what we thought to be a state-of-the-art “best notebook computer Apple has ever made”. Well, this thread clearly says otherwise - not only in one way, but multiple. Bottom line is that we shouldn’t be having well intentioned folks arguing over how to fix our/their “panic” or other errors in the first place.


APPLE NEEDS TO READ THIS AND RESPECTFULLY ADDRESS THE FACT OUR 16” MacBook Pros CLEARLY HAVE ISSUES.


AT THIS TIME ESPECIALLY, WE DESERVE BETTER FOR WHAT WE HAVE PAID.


It is a stressful enough time for everyone already right now. THANKS TO EVERYONE for simply trying to help each other here.

Apr 24, 2020 2:03 PM in response to m0unt41nman

m0unt41nman wrote:

3 - Those who have had the aforementioned panic and a hardware repair may not get it fixed because they dont get updated manufactured LBs. They get old ones. <--- Read that... thats really really important.

5 - We have yet to see > March LBs with the aforementioned GPU panics. Even if we did, its still a minority of users.

6 - People seem to be getting the panics here confused. The hardware panic text have been clearly stated in this thread as known hardware problems. All others are not known to be hardware or software for sure.

I really wish people would read this thread entirely. All the data is here and at MacRumors for the problem, the cause, and the fix. Unfortunately the fix for that particular panic (Powerplay failed to xxxxxxxxx) is not software.

I think these are the main concerns I have about this whole thing.


#3 - How do I know I'm going to send my MacBook Pro in and get a LB that was manufactured in March or later?


#5 - The support person I talked to eluded to this happening and is the reason why mine isn't in a box heading for a service depot right now. But...I'm not 100% certain that the advisor I spoke with completely understood that the panic I was referring to was the "PowerPlay Failed Resume" panic. I mentioned this, but was it fully absorbed? I don't know.


#6 - This builds on my concern brought up in #5. There have been many panics that people are seeing, so how do I know this stayed straight between the advisor and senior advisor?


I have an open case with Apple. I'll update accordingly as to how things end up.

Apr 24, 2020 10:47 PM in response to ApaLagiMahu

It’s very frustrating. I feel I wasted my money on my setup (64GB 8TB, LG 27MD5KA monitor), to have a machine that I can’t leave alone to get a coffee because it panics and crashes, also my mouse lags because of some monitor resolution setting and finally the fan just fires up loudly almost for any simple graphics app I run. I feel I went backwards with my purchase. I can’t just return my laptop as I’m working on a project and don’t have the luxury to be without a mchine. I hope it’s a software issue just like the iPhones get upgrades that affect some people and not others thouythey all have the same software. —In the meantime I went ahead and disabled the "Prevent computer from sleeping automatically when the display is off" and have seen improvement though I still can’t trust it. I have seen both errors: with the panic gpu message and without. It’s not consistent.


Apr 26, 2020 10:49 AM in response to visualinventor

Late reply --


My week-old MBP16 has been having kernel panics whenever I wake it up in the morning. (no random freezes yet, knock on wood) I ran the same test and am getting this error instead of IntelAccel error that you mentioned:


void IOAccelFenceMachine::fence_timeout(IOTimerEventSource *): IntelAccelerator prodding blockFenceInterrupt


Any relation? Should I be prepping for a logic board replacement? (its Geekbench scores are still in the high 4000s, and it looks like it's passing its Sobel test)

Apr 26, 2020 10:59 AM in response to leland171

The panic messages that seem to be related to hardware issues have been discussed earlier in the thread, so I'd read back through to see exactly which ones.


I'm dealing with the "PowerPlay Failed Resume" panic at the moment. This particular panic, per Apple, could be hardware or software. They're just not sure, yet.


Others in the thread, though, have reported it is indeed hardware, and the only fix is to have the hardware replaced w/ a logic board and/or whole system that was manufactured in March of 2020, or later.


Do you know when your hardware was manufactured? (You can install "coconutBattery" for an easy way to find out...)

Apr 26, 2020 3:17 PM in response to Drakarced

I just wanted to post an update on my progress just in case anyone is wondering. I've responded to myself each time I posted so you can easily click back through my old posts by clicking the "in response to BretFromApple" at the top of my posts.


Apple sent me a brand new replacement and this resolved my issue. This was the only thing that could have resolved my issue. Some people report going through two or more replacements until finally getting one that works without issues. Don't spend your time trying to fix this issue yourself if you had the same issue as me. Please contact Apple and start the repair process to get closer to getting a replacement. The good part is that once you get a replacement, you get 14 days (in the US) to return the product. So you'll know within 14 days if your new MacBook is having the same issues and just get another replacement. You can keep doing this until you get one that works (if that's even needed). This is my first replacement and works great.


My prior MacBook would unexpectedly freeze for around 10 seconds, then the fans would spin at 100% for around 5 seconds, and the machine would then power off or restart. I would check the logs after this issue and get a "bad magic" kernel panic or some sort of other similar kernel panic.


I spent around two to three months working with Apple and I went through two repairs where the issue was not resolved and it kept shutting down or rebooting. During these repairs, they reinstalled MacOS, updated my T2 firmware, replaced my Touch ID Board, and replaced my Logic Board. This didn't resolve the issue.


My prior MacBook must have been a lemon because this brand new one has absolutely no issues at all. I've had it now for almost a month and have used it extensively for production. This new MacBook is how my first MacBook should have been but I somehow ended up with a lemon on my first purchase.


Anyways, I hope you all get this issue resolved like I did! This will be my last post on this forum unless I come across the same issue in the future with this new MacBook, which is very unlikely. Good luck all!

Apr 27, 2020 2:39 AM in response to Drakarced

Yep, repair/board replacement no good. Board replacements are coming from the older batches. My full macbook replacement fixed it with the March 2020 build date.


I think I found something though, on stackexchange forums. I'd made a note of it in one of my earlier comments without realising it was the cause of all this (maybe).


I always plug my charging cable & dongle in the left side, because I am right handed so don't want my mouse to bump in to the cable or dongle. I noticed on my original system and subsequent board replacements, the machine would get very hot when cable was plugged in on the left, as opposed to the right. Turns out the psu is on the right hand side. Plugging in to the left side on one of the faulty systems results in a kernel task being created to route power over to the right side of the board. For some reason on the faulty boards, the kernel task took 3-4 minutes to complete. This results in queueing kernel tasks, eventually your CPU is overcome with this endless kernel loop and panics the next time you give it a heavy task. Kernel tasks survive a reboot, which explains why once your macbook starts freezing a lot, the only way to stop that is to wipe it. On the faulty systems, plugging your charging cable in to the right side resulted in kernel tasks that only take up to 15 seconds so they complete before a queue is possible.


On my replacement system, the macbook doesn't get hotter if plugging in on the left side, and doesn't create kernel tasks that last 3-4 minutes. No idea why that is.


This could be why a lot haven't experienced the issue, some people like to plug things in on the right side and thus avoid the kernel task queue on a faulty system. Some people don't have a faulty system and the kernel task queue doesn't happen at all. It does mean there are users out there though with a faulty board who will eventually plug their charge cable on the left side and trigger the endless kernel task queue to route power, and be where a lot of people in this forum are at now.


Basically, if you do have a system that keeps restarting, completely wipe it, and only use the right hand side ports to charge. Of course this isn't a fix, but at least it'll make work on a machine built for work usable till you can get a replacement, and when it comes time to demo the fault to apple support, start charging with the left ports. 👍


Although the issue exists on other mac systems, it seems certain MBP 2019 16" units are affected by this severly, other batches not so much.


https://apple.stackexchange.com/questions/363337/how-to-find-cause-of-high-kernel-task-cpu-usage?answertab=active#tab-top

Apr 28, 2020 3:18 AM in response to fregsfdvbfeg

Hey guys,


I have exactly the same issue with my 16" MBP and have been putting off contacting Apple due to not have a machine for ages.


GOOD NEWS - I contacted Apple today expecting to send my machine in and they said I need to continue with the workarounds for now. I was like 'WHAT?, I want my machine fixed!" However, it seems this is a software issue and they have stopped setting up repairs because a fix is on the way. This is what she said:


Yes be on the look out for a new update. The engineers stated “Thanks to everyone who sent the data we have identified a fix for the next software update.”


Hopefully this fix is imminent and should relieve some of your worries about having to send in your machine for repair. Hope this helps 👍

Apr 30, 2020 1:26 PM in response to fregsfdvbfeg

My new 16" MacBook pro always crashed at night and tended to crash after sleep. I contacted Apple Support, they suggested that an update to the operating system should fix this, given that my logs had similar messages as those outlined in this thread (specific kernel panic messages). They indicated that, in the meantime, disabling power nap might work. It did. No crashes since turning off power nap in energy saver preference. Naturally, waiting for an update to fix this issue because power nap is a great feature of macs.


I had tried numerous fixes prior, utilities, reinstall system, etc... Turning off power nap was the only way to stop the crashes and odd behaviors.

May 3, 2020 8:09 PM in response to acuhealth

Same here - crashing on wake. Disabling power nap "solved it". I've been running it like this a few months now and get the occassional crash on wakeup, but it's maybe once or twice a week now instead of every time. No other problems. I can live with this I guess. I'll get extended care, and if it turns out to be hardware, they get to fix it. Hopefully if it's hardware, we'll see a recall at some point.


Probably my last Macbook. The quality isn't there anymore.

Macbook pro 16 2019 freezes randomly and restarts

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.