2019 16-inch MacBook Pro crashes

[scottish]

To update on my situation - MacBook hasn’t crashed since I had the logic board replaced so that’s good. The Touch Bar sometimes works and sometimes doesn’t. There doesn’t seem to be any pattern to it. Sleeping/waking brings it to life sometimes and other times doesn’t. Anyone know if this more likely to be software or hardware related?

 

[graysonanthony]

I have started having this issue. I recently purchased a 2019 MacBook Pro 16" from Apple and within the first few days it started having the Kernel Panics within the first 2 days. They are still having me do different things but it's happening. What should I do?

 

[astrorider]

Just happened again now. (watching MKBHD full-screen.)

It is a full, legitimate freeze - keyboard presses like ESC don't do anything in the OS. But trackpad and keyboard does respond with force touch and backlights responding, so maybe not a T2 issue thank God.

A graphics issue? Or indeed, a Catalina bug.

Still annoying, but minor compared to what we've gone through with the T2 and butterfly issues. (etc.)

I agree, Catalina is buggy as hell...

Sorry if I'm misunderstanding, but does force quitting the app work? If a fullscreen app freezes just pressing ESC alone may not work, but you may still be able to bring up the force quit screen and quit the app. https://support.apple.com/en-us/HT201276

 

[markedlymac]

Just had a lovely vintage style T2 crash right now on my 16-inch.

(Using all official apple products and cables), I had my iPhone plugged in to the MacBook with headphones also plugged in while listening to some audio on the iPhone, then I plugged in the Mac's power cable. BOOM. Extremely sudden fan blowout and this time went all the way to the black apple logo boot screen.

It even gave me a crash log this time. Gee, what year is this, 2017??

Much shorter log compared to what they used to be:

panic(cpu 1 caller 0xfffffff01748f7b4): x86 CPU CATERR detected
Debugger message: panic
Memory ID: 0x6
OS version: 17P4263
macOS version: 19E266
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: REMOVED-COS-ITS-UNNN-ECESSARY
iBoot version: iBoot-5540.105.2
secure boot?: YES
x86 EFI Boot State: 0x16
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:     0x000000000f458000
Kernel text base: 0xfffffff01645c000
mach_absolute_time: 0xc8e8d330114
Epoch Time:        sec       usec
  Boot    : 0x5e7a8567 0x000d4985
  Sleep   : 0x5e8afe37 0x000168a6
  Wake    : 0x5e8b00ed 0x00094f1a
  Calendar: 0x5e8b0118 0x000b666a

Panicked task 0xffffffe0001faa00: 3506 pages, 222 threads: pid 0: kernel_task
Panicked thread: 0xffffffe00040af88, backtrace: 0xffffffe0109134b0, tid: 386
          lr: 0xfffffff016d20764  fp: 0xffffffe0109134f0
          lr: 0xfffffff016d205c0  fp: 0xffffffe010913560
          lr: 0xfffffff016e3ae7c  fp: 0xffffffe010913610
          lr: 0xfffffff0172e962c  fp: 0xffffffe010913620
          lr: 0xfffffff016d1ff28  fp: 0xffffffe010913990
          lr: 0xfffffff016d20280  fp: 0xffffffe0109139e0
          lr: 0xfffffff017b56934  fp: 0xffffffe010913a00
          lr: 0xfffffff01748f7b4  fp: 0xffffffe010913a30
          lr: 0xfffffff017480be4  fp: 0xffffffe010913aa0
          lr: 0xfffffff017482b0c  fp: 0xffffffe010913b50
          lr: 0xfffffff01748031c  fp: 0xffffffe010913be0
          lr: 0xfffffff017447780  fp: 0xffffffe010913c10
          lr: 0xfffffff017256abc  fp: 0xffffffe010913c50
          lr: 0xfffffff017256340  fp: 0xffffffe010913c90
          lr: 0xfffffff0172f4514  fp: 0x0000000000000000

Um. Thanks?

 

[LGrillo]

Hi there. I've had my new 16" MacBook Pro for a couple of weeks and it crashes every day with a kernel panic any time it's been sleeping for more than a few hours. I'm going to set up a tech support session with Apple and hopefully they can diagnose it. Brand new computer shouldn't behave so badly.

 

[D_Apple]

Similar conditions and result as the OP, mine just crashed and it’s been out the wrapper less than 6 hours.

 

[meirithekid]

Apple refused to give a refund, as it is 'within warranty repair conditions' or something like that.
Sent it back to be repaired for the 3rd time, this time they said they replaced the screen 🤷‍♂
In total this far it's been in repair about 2 months out of the 3 since it was purchased, and got every single component in the computer replaced - let's see if third time's the charm.. I'll keep updating

 

[meirithekid]

So, I got the MBP16 back 3 days ago, with a completely drained battery and they forgot to send charger along with it.. so it's been sitting with a dead battery for 3 days until I just received the charger. Once charged, the computer won't boot into the OS... spent over and hour on the phone with Apple support trying to reinstall catalina but no success, seems like another hardware issue.
I really don't know what to think anymore, what the hell ??

 

[marzfreerider]

So, I got the MBP16 back 3 days ago, with a completely drained battery and they forgot to send charger along with it.. so it's been sitting with a dead battery for 3 days until I just received the charger. Once charged, the computer won't boot into the OS... spent over and hour on the phone with Apple support trying to reinstall catalina but no success, seems like another hardware issue.
I really don't know what to think anymore, what the hell ??

I had that issue once when I had my logic board/ssd replaced. Turned out the place that did the repair forgot to assign the serial number to it. Had to take back, they hooked it up did something to assign it and then it went as it should. Not sure if it's the same issue but possible. For that many issues I would be escalating that further for a replacement, unacceptable to have to go through that much. Good luck.

 

[gnocchi]

I can confirm the latest 10.15.4 update does NOT fix the problem. Installed it last night and had a freeze about 5 minutes ago. Seems to be related to thermals, which is bad news. It really looks like Apple has no clue how to fix this. They need to come clean and start replacing machines if necessary. The silence on this borders on consumer fraud.

 

[cpnotebook80]

I received mine Earlier in the week but before sending it back for refund and before I had the few issues mentioned here creep up, I checked the manufacturer date and it said nov 2019. I read someone that newer models Manufacturerd in March 2020 seem fine with some users on here. Maybe hardware related? I still have my 2013 late mbp13 which I am using.

Me thinks maybe spec bump to this mbp16 when the 14” comes out on the Apple website and new hardware silently updated. Who knows. They did do it with gpu additions to iMac Pro. I do agree that spending that amount money on a product to give issues right off the bat is bad, and it was a Debby downer for sure after my excitement opening it and trying it out.

but crossing fingers it’s easy fix and software mostly fix and if not Apple comes through and helps with replacements or something.

 

[jw77777]

Not to add fuel to the fire, but I bought a MacBook Pro 16" in Mid March, and ever since then, it would shutdown or restart after waking from a long period of sleep. I would get the error message once I see the desktop. I was on the phone with Apple Support yesterday, and they had me do a reinstall of the whole system, wiping out my entire HD and files. (thanks for back up). But still, the problem is still there. The tech's explanation of what went wrong was that there could have been buggy code in the system OS that came loaded with the MacBook Pro, and it didn't get overwritten when updated. I'll give Apple Support a call today to find out more. But I'm really trying to avoid sending this laptop in, as I use this for work, and since everything is pretty much shut down in the DC area, this will be a pain.

Thanks for all your posts. It's relieving to know that this is not an isolated issue.

 

[kit l]

I have had my 16"MBP for about five months. I live in the country, so (especially in the COVID-19 era) not possible to take the machine into an Apple store.

My MBP freezes at least once a day these days, and the freezes take various forms. The most common is that the screen, keyboard, and touchpad are 100% unresponsive, and Force Quit can't be accessed. So, reboot via power button being held down is only option. Another variety is that the machine restarts itself, if left for a while, so password utility has to have its password re-entered, all windows reloaded, and all the things one needs to do after a restart. Reporting here in case anyone comes up with a way of overcoming this: I have two other Macs running the same programs here, and I may have to go back to a 2013 rMBP that has never crashed (but it runs High Sierra, as does the 5K iMac).

It's becoming closer to a deal-breaker for me, every day.

 

[no girls]

Hi there. I've had my new 16" MacBook Pro for a couple of weeks and it crashes every day with a kernel panic any time it's been sleeping for more than a few hours. I'm going to set up a tech support session with Apple and hopefully they can diagnose it. Brand new computer shouldn't behave so badly.

i have this issue too. did you receive any more info/help from apple support regarding this issue?

 

[scottish]

To update on my situation - MacBook hasn’t crashed since I had the logic board replaced so that’s good. The Touch Bar sometimes works and sometimes doesn’t. There doesn’t seem to be any pattern to it. Sleeping/waking brings it to life sometimes and other times doesn’t. Anyone know if this more likely to be software or hardware related?

I had to restart last night after installing some new software and setting some things up I hadn't got round to. Uptime was 49 days. macOS 10.15.4 was installed when I restarted.

I have just opened the lid to find that it's crashed again!

""AppleIntelFramebuffer::setPowerState(0xffffff81b9e65000 : 0xffffff7f8e3a8d88, 1 -> 0) timed out after 45991 ms"@/AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-6153.101.6/iokit/Kernel/IOServicePM.cpp:5296"

The fact I've had no issues up to now hopefully points to a software issue this time.

On another note my Touch Bar isn't being unresponsive as often.

 

[amine250]

Hi, I just created an account to report this too.
Exactly as described by some people, the mouse/trackpad freezes for like 20 seconds, then the fans blow out and the laptop restarts...

It's maybe worth to mention that I own in since November and never faced this issue, until after the 10.15.4 update. Since then, I face this 2 times a day.

 

[markedlymac]

I've just had a repeat of the crash I had on 14th April.

panic(cpu 1 caller 0xfffffff0240bd3dc): x86 CPU CATERR detected
Debugger message: panic
Memory ID: 0x6
OS version: 17P5300
macOS version: 19F101
Kernel version: Darwin Kernel Version 19.5.0: Tue May 26 20:16:42 PDT 2020; root:xnu-6153.121.2~1/RELEASE_ARM64_T8010
Kernel UUID: 123C59BB-125A-31AF-A916-AAF729BE6BE8
iBoot version: iBoot-5540.125.4
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:     0x000000001c084000
Kernel text base: 0xfffffff023088000
mach_absolute_time: 0x9124cdf8b89
Epoch Time:        sec       usec
  Boot    : 0x5ed88e1a 0x00011986
  Sleep   : 0x5ee56a38 0x0000e17c
  Wake    : 0x5ee56d1d 0x000e0b0c
  Calendar: 0x5ee56d48 0x000a7b3c

Panicked task 0xffffffe00044c200: 3480 pages, 221 threads: pid 0: kernel_task
Panicked thread: 0xffffffe00076af88, backtrace: 0xffffffe0112a34b0, tid: 373
          lr: 0xfffffff02394c764  fp: 0xffffffe0112a34f0
          lr: 0xfffffff02394c5c0  fp: 0xffffffe0112a3560
          lr: 0xfffffff023a671e0  fp: 0xffffffe0112a3610
          lr: 0xfffffff023f1562c  fp: 0xffffffe0112a3620
          lr: 0xfffffff02394bf28  fp: 0xffffffe0112a3990
          lr: 0xfffffff02394c280  fp: 0xffffffe0112a39e0
          lr: 0xfffffff024782934  fp: 0xffffffe0112a3a00
          lr: 0xfffffff0240bd3dc  fp: 0xffffffe0112a3a30
          lr: 0xfffffff0240ae80c  fp: 0xffffffe0112a3aa0
          lr: 0xfffffff0240b0734  fp: 0xffffffe0112a3b50
          lr: 0xfffffff0240adf44  fp: 0xffffffe0112a3be0
          lr: 0xfffffff0240753a8  fp: 0xffffffe0112a3c10
          lr: 0xfffffff023e835d8  fp: 0xffffffe0112a3c50
          lr: 0xfffffff023e82e5c  fp: 0xffffffe0112a3c90
          lr: 0xfffffff023f20514  fp: 0x0000000000000000

All I did was plug in my official Apple iPhone charger and the power charger one shortly after the another. Far from resolved.

 

[LinkRS]

I've just had a repeat of the crash I had on 14th April.

panic(cpu 1 caller 0xfffffff0240bd3dc): x86 CPU CATERR detected
Debugger message: panic
Memory ID: 0x6
OS version: 17P5300
macOS version: 19F101
Kernel version: Darwin Kernel Version 19.5.0: Tue May 26 20:16:42 PDT 2020; root:xnu-6153.121.2~1/RELEASE_ARM64_T8010
Kernel UUID: 123C59BB-125A-31AF-A916-AAF729BE6BE8
iBoot version: iBoot-5540.125.4
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:     0x000000001c084000
Kernel text base: 0xfffffff023088000
mach_absolute_time: 0x9124cdf8b89
Epoch Time:        sec       usec
  Boot    : 0x5ed88e1a 0x00011986
  Sleep   : 0x5ee56a38 0x0000e17c
  Wake    : 0x5ee56d1d 0x000e0b0c
  Calendar: 0x5ee56d48 0x000a7b3c

Panicked task 0xffffffe00044c200: 3480 pages, 221 threads: pid 0: kernel_task
Panicked thread: 0xffffffe00076af88, backtrace: 0xffffffe0112a34b0, tid: 373
          lr: 0xfffffff02394c764  fp: 0xffffffe0112a34f0
          lr: 0xfffffff02394c5c0  fp: 0xffffffe0112a3560
          lr: 0xfffffff023a671e0  fp: 0xffffffe0112a3610
          lr: 0xfffffff023f1562c  fp: 0xffffffe0112a3620
          lr: 0xfffffff02394bf28  fp: 0xffffffe0112a3990
          lr: 0xfffffff02394c280  fp: 0xffffffe0112a39e0
          lr: 0xfffffff024782934  fp: 0xffffffe0112a3a00
          lr: 0xfffffff0240bd3dc  fp: 0xffffffe0112a3a30
          lr: 0xfffffff0240ae80c  fp: 0xffffffe0112a3aa0
          lr: 0xfffffff0240b0734  fp: 0xffffffe0112a3b50
          lr: 0xfffffff0240adf44  fp: 0xffffffe0112a3be0
          lr: 0xfffffff0240753a8  fp: 0xffffffe0112a3c10
          lr: 0xfffffff023e835d8  fp: 0xffffffe0112a3c50
          lr: 0xfffffff023e82e5c  fp: 0xffffffe0112a3c90
          lr: 0xfffffff023f20514  fp: 0x0000000000000000

All I did was plug in my official Apple iPhone charger and the power charger one shortly after the another. Far from resolved.

Howdy mindfulmac,

Just got finished reading this whole thread, yikes! I have a less than 2-week old CTO 2019 MacBook Pro 16", myself and this concerns me. I have not had any (quick knock on wood) full system crashes. I have had a few application crashes, but none have been with Apple programs, all third-party (Microsoft ha, ha) and Epic. My system has a build date of 25 May (the day after I ordered it), so is pretty new. I have a background in fixing/repairing computers (both Windows and older Macs), so am particularly interested interested in your crashes.

Can you cause your system to crash on-demand? Meaning can you take a series of steps and predictably cause a crash, or is it random? Are you using Safari, or a different web browser? Have you tried to use your system off of just the internal Wi-Fi vices your USB Ethernet cable? Have you tried using the TB 2 Ethernet adapter instead of USB?

FWIW, if the crashes are predictable, meaning that you can cause them by completing a series of steps (or conditions), this is usually indicative of a hardware problem. If the crashes are random, meaning that you can't predictably cause one (you don't know when it will happen), that is indicative of a software or driver issue.

Rich S.

 

[SantaCruzDad]

Howdy mindfulmac,

Just got finished reading this whole thread, yikes! I have a less than 2-week old CTO 2019 MacBook Pro 16", myself and this concerns me. I have not had any (quick knock on wood) full system crashes. I have had a few application crashes, but none have been with Apple programs, all third-party (Microsoft ha, ha) and Epic. My system has a build date of 25 May (the day after I ordered it), so is pretty new. I have a background in fixing/repairing computers (both Windows and older Macs), so am particularly interested interested in your crashes.

Can you cause your system to crash on-demand? Meaning can you take a series of steps and predictably cause a crash, or is it random? Are you using Safari, or a different web browser? Have you tried to use your system off of just the internal Wi-Fi vices your USB Ethernet cable? Have you tried using the TB 2 Ethernet adapter instead of USB?

FWIW, if the crashes are predictable, meaning that you can cause them by completing a series of steps (or conditions), this is usually indicative of a hardware problem. If the crashes are random, meaning that you can't predictably cause one (you don't know when it will happen), that is indicative of a software or driver issue.

Rich S.

According to this info from the Apple forums this should be a reliable way to reproduce the problem:

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.

 

[kaans]

Thanks for sharing the test @SantaCruzDad

I paid $2800 for my device, but even though I don't even have the issue, I'm writing $1400 off, I wasted exactly half my money with this purchase - like someone on the Apple Forums thread said very well: "Keeping my 2017 Macbook with a faulty keyboard might've been better"

I really hate living with paranoia of imminent hardware failures, if so many other devices have failed, it's just a matter of time ours will fail too (Dec 2019 here) - So I definitely feel the pain

One peculiar thing tho, which gives me hope, most issues seem to be software, I (hopefully) had 1 WindowServer software crash too, as I read, others have external peripherals connected that crashes systems on wake etc. - BUT - the hardware issues mentioned on the Apple thread, must be happening, let's say 10% of the time, which is a high assumption, because if it was 10%, it would definitely be extremely widespread and globally inflated already, but let's say 10% - now, some say they get 4 replacements and ALL have the same issues, if the chance is 10%, their unluckiness beats a 1/10000 odd - even if it was happening 80% of the time, those that received ~4 replacements should've got one good one

So I also hope/wonder that/if something is fishy - just to be able to avoid this issue

 

[jasoncarle]

I thought this problem went away after recent Catalina updates, but I was wrong.

I just had a full crash - a forced reboot - after the screen froze for a solid minute while watching a youtube video in full-screen. Audio continued on for a minute, touch bar etc. unresponsive, then suddenly an awful glitchy colours on the entire screen and then a forced log out of the user session. (Not as bad as the old full system reboot. Maybe they're trying to make it less bad?)

I keep getting regular full-screen video playback temporary freezes, as well. They're VERY frequent. Almost once a day.

I hate this.

Other than this though, the 16-inch MBP feels extremely solid. Really worth the $5000 price I paid for it. And in my case, this issue is not bad enough to bring it in to Apple like the butterfly keyboard or former T2 models crashes were.

It's also harder to prove this defect to Apple anyway, because as I observed some months ago, Apple is no longer showing ANY of these crash logs in Console.app even though the crashes are still happening, and that is absolutely reprehensible.

I'll bet that they are now 1. recording crash logs secretly in the system and 2. forcibly uploading them to Apple without our knowledge or consent, where who knows what other private data is being sent without our consent? It's obvious they can't be trusted, and that they don't give a **** about us or our privacy.

All this unconscionable behaviour is why I am trying to plan to move to Linux full-time. I love Apple hardware and software, and god damn I love that Apple trackpad, but more importantly my computer is a tool of democratic power and expression and autonomy, and with macOS, we don't truly have control over our own devices.

I'm going to go out on a limb here and say that until there is a solid fix, don't watch any full screen videos...

 

[kaans]

By the way, I just tested 5.1.0 explicitly http://cdn.geekbench.com/Geekbench-5.1.0-Mac.zip - Previously I didn't realise I was using 5.2.0 - In 5.1.0 the GPU crashes, I get 2000sth instead of 4000sth - However no "Powerplay" error in the console - Tested only once, probably going to not test again It's scary

 

[beefstew]

Just received a MacBook Pro 16-inch, 2019 with macOS 10.15.6 installed and have experienced multiple crashes and USB failure.

This weekend it was hard crashes (freeze, black screen, fan whoosh, restart) seemingly triggered by moving enough data through a USB 3.0 hub (Macally TRIHUB9) or connecting the hub. After hours of debugging, I performed a full reinstall and a fresh user account (no Migration Assistant). The new behavior I'm seeing is for external USB devices to sometimes go dead until a reboot. This seems to be triggered by moving enough data through the new Thunderbolt hub (Plugable TBT3-UDV) that I am using in place of the USB 3.0 hub.

I experimented with moving external backup drive (USB 3.0) to an Apple USB-C to USB-A adapter, but problem still exists. As of 2020-08-26 12:00, I'm now experimenting using only external mouse & keyboard through Apple adapter (no other USB devices plugged in).

Update 8/27: I have also been able to trigger a hard crash by plugging in the Thunderbolt hub after the machine has been running for a few hours with just the keyboard & mouse connected via Apple adapater.

Given Apple's apparently persistent inability to fix this problem, it seems like I'm going to have to give up on macOS and switch to Windows. I can't accept a work machine that requires rebooting a couple times a day.

What I can find in the Console around the time of the latest USB deaths suggests faulty drivers:

→ log show --predicate 'eventMessage contains "USB" and eventMessage contains "Exception"'
Filtering the log data using "composedMessage CONTAINS "USB" AND composedMessage CONTAINS "Exception""
Skipping info and debug messages, pass --info and/or --debug to include.
Timestamp Thread Type Activity PID TTL
2020-08-25 00:41 [not directly observed]
2020-08-25 00:41:45.529542-0400 0x2c9 Default 0x0 0 0 kernel: (IOUSBHostFamily) 042789.072153 AppleUSBXHCIFL1100@02000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000080
2020-08-25 00:41:45.539221-0400 0x2c9 Default 0x0 0 0 kernel: (IOUSBHostFamily) 042789.081840 AppleUSBXHCIFL1100@02000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000004
2020-08-25 00:42:15.561838-0400 0xce0 Default 0x0 0 0 kernel: (IOUSBHostFamily) 042819.104450 AppleASMedia1042USBXHCI@01000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000080
2020-08-25 00:42:15.570151-0400 0xce0 Default 0x0 0 0 kernel: (IOUSBHostFamily) 042819.112770 AppleASMedia1042USBXHCI@01000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000004
2020-08-25 14:00 [USB death; manually initiate restart; reboot]
2020-08-25 14:00:12.978855-0400 0xb6c Default 0x0 0 0 kernel: (IOUSBHostFamily) 007216.255063 AppleUSBXHCIFL1100@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000080
2020-08-25 14:00:12.987955-0400 0xb6c Default 0x0 0 0 kernel: (IOUSBHostFamily) 007216.264171 AppleUSBXHCIFL1100@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000004
2020-08-25 14:00:31.737345-0400 0x2e3 Default 0x0 0 0 kernel: (IOUSBHostFamily) 007235.013559 AppleASMedia1042USBXHCI@02000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000080
2020-08-25 14:00:31.747195-0400 0x2e3 Default 0x0 0 0 kernel: (IOUSBHostFamily) 007235.023411 AppleASMedia1042USBXHCI@02000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000004
2020-08-26 10:40 [USB death; manually initiate restart; kernel panic & fan whoosh; reboot]
2020-08-26 10:40:01.859447-0400 0x306 Default 0x0 0 0 kernel: (IOUSBHostFamily) 072932.698478 AppleUSBXHCIFL1100@02000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000080
2020-08-26 10:40:01.869925-0400 0x306 Default 0x0 0 0 kernel: (IOUSBHostFamily) 072932.708962 AppleUSBXHCIFL1100@02000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000004
2020-08-26 10:40:20.352347-0400 0xa8ca9 Default 0x0 0 0 kernel: (IOUSBHostFamily) 072951.191378 XHC3@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000080
2020-08-26 10:40:20.358416-0400 0xa8ca9 Default 0x0 0 0 kernel: (IOUSBHostFamily) 072951.197453 XHC3@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: attempting recovery
2020-08-26 10:40:20.358429-0400 0xa8ca9 Default 0x0 0 0 kernel: (IOUSBHostFamily) 072951.197470 XHC3@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000004
2020-08-26 10:40:20.358439-0400 0xa8ca9 Default 0x0 0 0 kernel: (IOUSBHostFamily) 072951.197480 XHC3@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: attempting recovery
2020-08-26 10:40:20.358540-0400 0xa8ca9 Default 0x0 0 0 kernel: (IOUSBHostFamily) 072951.197581 XHC3@03000000: AppleUSBHostController::hardwareExceptionThreadCallGated: 0x00000008
2020-08-26 11:50 [USB death; manually initiate restart; kernel panic & fan whoosh; reboot]

 

[appleuser181]

Just had my first ever T2 crash on the 16-inch MBP.

At least I think it's a 'T2 crash', because it's the exact same behaviour as on the 2018 MBP - macOS suddenly freezes, trackpad also non-responsive, then shuts off with a fan blow-out, and then reboots.

It happened IMMEDIATELY after plugging in an Ethernet-to-USB-C adapter - the adapter I've used since my 2017 MBP (which doesn't have the T2) and which since only my 2018 MBP have I had crashes with.

I caught it on camera.

And here's the crash log upon restart:
View attachment 891278
"BAD MAGIC! (flag set in iBoot panic header), no macOS panic log available"

That's definitely the T2 chip. Been getting these since July 2018 on my 2018 MBP 15". Ridiculous how Apple isn’t doing anything to fix this. I'm guessing it's a hardware issue with the T2...

 

[chshs11]

I had the same issue for a a couple months with my macbook 16 before finally deciding to take it to apple. The issue seems to be caused by the T2 chip/ overheating (Especially when using GPU intensive applications). Got the T2 chip replaced and started controlling/ boosting the fan speed to maximum and charging on the right side instead of left (there's an earlier thread regarding charging the mac on the left causing overheating).



Been running flawlessly for 2 weeks now, issues disappeared so far,

Initial issues includes

• unable to wake from sleep mode
• crashing while running/ waking up from sleep mode
• unable to boot up
• unable to switch graphics/ crash while trying to
• crashing when switching from power cord to battery
• crashing after prolonged use of graphics intensive apps

Hope this helps