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

caustica

macrumors newbie
Original poster
Apr 26, 2020
10
0
Have read a lot of threads on similar problems, but without avail, so wanted to ask if anyone had any suggestions, regarding:

Macbook Pro 2018 13" that is around a year old suddenly started repeatedly crashing and force restarting two days ago. By repeatedly I mean it force restarts, then within a ~5 minutes of booting up, regardless of whether I log in or not (I.e. stay on login screen), it will crash and force restart again, with BridgeOS error in the log.

Another problem, not sure if it's related, is that the touch bar display has stopped working -- it still responds to touch, but I can't see any of the virtual buttons. Have tried restarting via running various commands in the Terminal to kill the existing process to no avail.

What I've tried that has not worked:
- SMC reset
- NVRAM reset
- Safe boot
- (ETA) Ran Apple Diagnostics --> no issue
- All application & software upgrades (was Mojave, now running latest Catalina)
- Unplugged all external devices, power cable both plugged in & not plugged in
- Various sleep-related settings -- based on various threads I read, but my symptoms were slightly different (wasn't crashing just when sleeping, but when using it) so not surprised that this hasn't helped

I could not reinstall the OS via Recovery Mode as every time I tried, it would crash & force restart before completing.

Also tried to call Apple Support but they weren't able to offer anything useful.

Has anyone faced this before / have any ideas for what else I could try? The caveat being, of course, that whatever solution must be quick to implement, otherwise it will crash before it can be done. :(
 
Last edited:

chrfr

macrumors G5
Jul 11, 2009
13,716
7,290
Have read a lot of threads on similar problems, but without avail, so wanted to ask if anyone had any suggestions, regarding:

Macbook Pro 2018 13" that is around a year old suddenly started repeatedly crashing and force restarting two days ago. By repeatedly I mean it force restarts, then within a ~5 minutes of booting up, regardless of whether I log in or not (I.e. stay on login screen), it will crash and force restart again, with BridgeOS error in the log.

Another problem, not sure if it's related, is that the touch bar display has stopped working -- it still responds to touch, but I can't see any of the virtual buttons. Have tried restarting via running various commands in the Terminal to kill the existing process to no avail.

What I've tried that has not worked:
- SMC reset
- NVRAM reset
- Safe boot
- All application & software upgrades (was Mojave, now running latest Catalina)
- Unplugged all external devices, power cable both plugged in & not plugged in
- Various sleep-related settings -- based on various threads I read, but my symptoms were slightly different (wasn't crashing just when sleeping, but when using it) so not surprised that this hasn't helped

I could not reinstall the OS via Recovery Mode as every time I tried, it would crash & force restart before completing.

Also tried to call Apple Support but they weren't able to offer anything useful.

Has anyone faced this before / have any ideas for what else I could try? The caveat being, of course, that whatever solution must be quick to implement, otherwise it will crash before it can be done. :(
Try running diagnostics: https://support.apple.com/en-us/HT202731
Given that the computer fails to successfully install the operating system, chances are good there’s been a hardware failure. Has the computer ever suffered from a liquid spill, from being dropped, or from something else?
The fact that the Touch Bar doesn’t work makes it seem that a repair is likely necessary.
 

caustica

macrumors newbie
Original poster
Apr 26, 2020
10
0
Try running diagnostics: https://support.apple.com/en-us/HT202731
Given that the computer fails to successfully install the operating system, chances are good there’s been a hardware failure. Has the computer ever suffered from a liquid spill, from being dropped, or from something else?
The fact that the Touch Bar doesn’t work makes it seem that a repair is likely necessary.

Thanks for the suggestion. Actually, I had already tried this, but forgot to include it in the post (have edited it now). Apple Diagnostics unfortunately didn't identify any problem.

It seems to me that the computer fails to install the operating system because of the quick crashing issue (which happens regardless of what is running), rather than because of the actual action of installing the OS.

No liquid spill or drop. The only thing is that due to WFH, I've been using it intensely a lot more in recent weeks -- for the last few weeks it's been almost constantly plugged into a 34" monitor and rarely gone to sleep. So maybe this has worn the hardware down? -- But Apple Diagnostics couldn't find anything.

From what I've read online it seems like BridgeOS issues have been software-related... But in that case, I would expect other people to be facing the same issue too. :(
 

chrfr

macrumors G5
Jul 11, 2009
13,716
7,290
Thanks for the suggestion. Actually, I had already tried this, but forgot to include it in the post (have edited it now). Apple Diagnostics unfortunately didn't identify any problem.

It seems to me that the computer fails to install the operating system because of the quick crashing issue (which happens regardless of what is running), rather than because of the actual action of installing the OS.

No liquid spill or drop. The only thing is that due to WFH, I've been using it intensely a lot more in recent weeks -- for the last few weeks it's been almost constantly plugged into a 34" monitor and rarely gone to sleep. So maybe this has worn the hardware down? -- But Apple Diagnostics couldn't find anything.

From what I've read online it seems like BridgeOS issues have been software-related... But in that case, I would expect other people to be facing the same issue too. :(
A lot of what people are calling "BridgeOS" issues have differing causes. Using your computer for work is what these computers are designed to do- that has not caused your problem.
If you start up the computer from internet recovery and just let it sit for a bit, will it crash while it's just sitting there?
If not, have you reformatted the disk and then tried a reinstallation?
If you have access to another Mac, I would try this procedure: https://mrmacintosh.com/how-to-restore-bridgeos-on-a-t2-mac-how-to-put-a-mac-into-dfu-mode/
The above process might revive the Touch Bar and thus resolve the crashing.
 

caustica

macrumors newbie
Original poster
Apr 26, 2020
10
0
A lot of what people are calling "BridgeOS" issues have differing causes. Using your computer for work is what these computers are designed to do- that has not caused your problem.
If you start up the computer from internet recovery and just let it sit for a bit, will it crash while it's just sitting there?
If not, have you reformatted the disk and then tried a reinstallation?
If you have access to another Mac, I would try this procedure: https://mrmacintosh.com/how-to-restore-bridgeos-on-a-t2-mac-how-to-put-a-mac-into-dfu-mode/
The above process might revive the Touch Bar and thus resolve the crashing.

Thanks for those additional tips! I started the computer up from internet recovery -- it did not crash -- tried to reinstall OS -- crashed -- started again from internet recovery -- reformatted the disk -- reinstalled OS -- has so far been working for the last one hour without crashing. Hooray!

Sadly, the Touch Bar is not back (still not displaying anything but does register taps), and unfortunately I don't have access to another Mac in lockdown.
 

caustica

macrumors newbie
Original poster
Apr 26, 2020
10
0
Update: it just crashed again, even though I was able to use it for a couple of hours before it did that. And now it's back to crashing every few minutes. Sigh.

This is the error I get:
Code:
panic(cpu 0 caller 0xfffffff00fcde058): userspace watchdog timeout: no successful checkins from com.apple.dfrd in 180 seconds
service: com.apple.dfrd, total successful checkins since load (210 seconds ago): 3, last successful checkin: 180 seconds ago
service: com.apple.UserEventAgent-System, total successful checkins since load (210 seconds ago): 22, last successful checkin: 0 seconds ago
service: com.apple.bridgeaudiod, total successful checkins since load (210 seconds ago): 22, last successful checkin: 0 seconds ago
service: com.apple.logd, total successful checkins since load (210 seconds ago): 22, last successful checkin: 0 seconds ago

Debugger message: panic
Memory ID: 0xff
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: 0x16
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0xec
x86 Previous Power Transitions: 0x70707060400
PCIeUp link state: 0x1614
Paniclog version: 13
Kernel slide:     0x000000000786c000
Kernel text base: 0xfffffff00e870000
mach_absolute_time: 0x13795cefc
Epoch Time:        sec       usec
  Boot    : 0x5ea60aed 0x000dd0ac
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x5ea60bc3 0x000a9bd4

Total cpu_usage: 15377367
Thread task pri cpu_usage
0xffffffe0010674d0 watchdogd 97 0
0xffffffe000f6b4d0 bridgeaudiod 37 0
0xffffffe001448a90 watchdogd 31 0
0xffffffe0007b0548 kernel_task 0 5154010
0xffffffe0004bda68 kernel_task 0 6128065

Panicked task 0xffffffe0012a8e00: 226 pages, 3 threads: pid 33: watchdogd
Panicked thread: 0xffffffe0010674d0, backtrace: 0xffffffe015a0b000, tid: 815
          lr: 0xfffffff00f134764  fp: 0xffffffe015a0b040
          lr: 0xfffffff00f1345c0  fp: 0xffffffe015a0b0b0
          lr: 0xfffffff00f24ee7c  fp: 0xffffffe015a0b160
          lr: 0xfffffff00f6fd62c  fp: 0xffffffe015a0b170
          lr: 0xfffffff00f133f28  fp: 0xffffffe015a0b4e0
          lr: 0xfffffff00f134280  fp: 0xffffffe015a0b530
          lr: 0xfffffff00ff6a934  fp: 0xffffffe015a0b550
          lr: 0xfffffff00fcde058  fp: 0xffffffe015a0b570
          lr: 0xfffffff00fcddd94  fp: 0xffffffe015a0b590
          lr: 0xfffffff00f691fc0  fp: 0xffffffe015a0b5f0
          lr: 0xfffffff00fcdd2e8  fp: 0xffffffe015a0b6d0
          lr: 0xfffffff00f69b00c  fp: 0xffffffe015a0b860
          lr: 0xfffffff00f21e8d0  fp: 0xffffffe015a0b980
          lr: 0xfffffff00f139f24  fp: 0xffffffe015a0b9e0
          lr: 0xfffffff00f10fcf0  fp: 0xffffffe015a0ba60
          lr: 0xfffffff00f127c7c  fp: 0xffffffe015a0bb10
          lr: 0xfffffff00f245760  fp: 0xffffffe015a0bbd0
          lr: 0xfffffff00f24efd4  fp: 0xffffffe015a0bc80
          lr: 0xfffffff00f6fd62c  fp: 0xffffffe015a0bc90
          lr: 0x00000001d2847198  fp: 0x0000000000000000
 

chrfr

macrumors G5
Jul 11, 2009
13,716
7,290
Update: it just crashed again, even though I was able to use it for a couple of hours before it did that. And now it's back to crashing every few minutes. Sigh.

This is the error I get:
Code:
panic(cpu 0 caller 0xfffffff00fcde058): userspace watchdog timeout: no successful checkins from com.apple.dfrd in 180 seconds
service: com.apple.dfrd, total successful checkins since load (210 seconds ago): 3, last successful checkin: 180 seconds ago
service: com.apple.UserEventAgent-System, total successful checkins since load (210 seconds ago): 22, last successful checkin: 0 seconds ago
service: com.apple.bridgeaudiod, total successful checkins since load (210 seconds ago): 22, last successful checkin: 0 seconds ago
service: com.apple.logd, total successful checkins since load (210 seconds ago): 22, last successful checkin: 0 seconds ago

Debugger message: panic
Memory ID: 0xff
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: 0x16
x86 System State: 0x0
x86 Power State: 0x0
x86 Shutdown Cause: 0xec
x86 Previous Power Transitions: 0x70707060400
PCIeUp link state: 0x1614
Paniclog version: 13
Kernel slide:     0x000000000786c000
Kernel text base: 0xfffffff00e870000
mach_absolute_time: 0x13795cefc
Epoch Time:        sec       usec
  Boot    : 0x5ea60aed 0x000dd0ac
  Sleep   : 0x00000000 0x00000000
  Wake    : 0x00000000 0x00000000
  Calendar: 0x5ea60bc3 0x000a9bd4

Total cpu_usage: 15377367
Thread task pri cpu_usage
0xffffffe0010674d0 watchdogd 97 0
0xffffffe000f6b4d0 bridgeaudiod 37 0
0xffffffe001448a90 watchdogd 31 0
0xffffffe0007b0548 kernel_task 0 5154010
0xffffffe0004bda68 kernel_task 0 6128065

Panicked task 0xffffffe0012a8e00: 226 pages, 3 threads: pid 33: watchdogd
Panicked thread: 0xffffffe0010674d0, backtrace: 0xffffffe015a0b000, tid: 815
          lr: 0xfffffff00f134764  fp: 0xffffffe015a0b040
          lr: 0xfffffff00f1345c0  fp: 0xffffffe015a0b0b0
          lr: 0xfffffff00f24ee7c  fp: 0xffffffe015a0b160
          lr: 0xfffffff00f6fd62c  fp: 0xffffffe015a0b170
          lr: 0xfffffff00f133f28  fp: 0xffffffe015a0b4e0
          lr: 0xfffffff00f134280  fp: 0xffffffe015a0b530
          lr: 0xfffffff00ff6a934  fp: 0xffffffe015a0b550
          lr: 0xfffffff00fcde058  fp: 0xffffffe015a0b570
          lr: 0xfffffff00fcddd94  fp: 0xffffffe015a0b590
          lr: 0xfffffff00f691fc0  fp: 0xffffffe015a0b5f0
          lr: 0xfffffff00fcdd2e8  fp: 0xffffffe015a0b6d0
          lr: 0xfffffff00f69b00c  fp: 0xffffffe015a0b860
          lr: 0xfffffff00f21e8d0  fp: 0xffffffe015a0b980
          lr: 0xfffffff00f139f24  fp: 0xffffffe015a0b9e0
          lr: 0xfffffff00f10fcf0  fp: 0xffffffe015a0ba60
          lr: 0xfffffff00f127c7c  fp: 0xffffffe015a0bb10
          lr: 0xfffffff00f245760  fp: 0xffffffe015a0bbd0
          lr: 0xfffffff00f24efd4  fp: 0xffffffe015a0bc80
          lr: 0xfffffff00f6fd62c  fp: 0xffffffe015a0bc90
          lr: 0x00000001d2847198  fp: 0x0000000000000000
I don’t know if this is you, but here’s someone having the same panics and the same issues with the Touch Bar: https://discussions.apple.com/thread/251182823
I strongly believe you need to have the computer repaired.
 
  • Like
Reactions: Honza1

caustica

macrumors newbie
Original poster
Apr 26, 2020
10
0
I don’t know if this is you, but here’s someone having the same panics and the same issues with the Touch Bar: https://discussions.apple.com/thread/251182823
I strongly believe you need to have the computer repaired.

Thanks for that link! It does sound really similar indeed. Shame there was no conclusion.

Yeah, if this were normal times, I'd bring it into an Apple store to get someone to look at it and take it in for repair if necessary. Unfortunately that's just not straightforward right now, so want to be sure I've tried everything I can before resorting to that.

Separately from that, I actually found a couple of threads on the same error too -- seems to be affecting quite a few people ATM, although 1) I haven't seen the Touch Bar mentioned and 2) they seem to pinpoint Catalina as the issue, but the exact same thing happened to me with Mojave.


 

chrfr

macrumors G5
Jul 11, 2009
13,716
7,290
Thanks for that link! It does sound really similar indeed. Shame there was no conclusion.

Yeah, if this were normal times, I'd bring it into an Apple store to get someone to look at it and take it in for repair if necessary. Unfortunately that's just not straightforward right now, so want to be sure I've tried everything I can before resorting to that.

Separately from that, I actually found a couple of threads on the same error too -- seems to be affecting quite a few people ATM, although 1) I haven't seen the Touch Bar mentioned and 2) they seem to pinpoint Catalina as the issue, but the exact same thing happened to me with Mojave.


I’m familiar with those, and while yours sounds similar, I don’t think it’s the root cause here.
 

caustica

macrumors newbie
Original poster
Apr 26, 2020
10
0
I’m familiar with those, and while yours sounds similar, I don’t think it’s the root cause here.

Hm, why do you think that? Because of Touch Bar and the fact that I was experiencing this with Mojave as well? Or is there some other reason?
 

chrfr

macrumors G5
Jul 11, 2009
13,716
7,290
Hm, why do you think that? Because of Touch Bar and the fact that I was experiencing this with Mojave as well? Or is there some other reason?
Yeah, exactly. The Touch Bar not working definitely indicates you’ve got some hardware problem, and that you had these panics in Mojave means that these new panics that started happening with the 10.15.4 update aren’t really related to your computer problems.
 

Stan Lin

macrumors newbie
Apr 28, 2020
6
0
Exact issues and log here. Touch Bar works without backlights. And BridgeOS panics cause repeatedly reboot. Have you got it fixed somehow?
 

caustica

macrumors newbie
Original poster
Apr 26, 2020
10
0
Exact issues and log here. Touch Bar works without backlights. And BridgeOS panics cause repeatedly reboot. Have you got it fixed somehow?

Unfortunately no :( I'm out of ideas on what to try now that I've even reformatted my disk & done full OS reinstall.

The fact that you're experiencing the same thing gives me some hope that it _may_ be a software issue. Please do let me know if you come across any other cases/anything works for you!
 

Stan Lin

macrumors newbie
Apr 28, 2020
6
0
Unfortunately no :( I'm out of ideas on what to try now that I've even reformatted my disk & done full OS reinstall.

The fact that you're experiencing the same thing gives me some hope that it _may_ be a software issue. Please do let me know if you come across any other cases/anything works for you!
I'm planning to pay a visit to Genius Bar, because I think that this is still a Touch Bar issue. My 2018 MacBook Pro was suffering from so-called Touch Bar Flickering issue this week before this repeatedly reboot happens. Also, I found one tweet,
[automerge]1588153155[/automerge]
 

caustica

macrumors newbie
Original poster
Apr 26, 2020
10
0
I'm planning to pay a visit to Genius Bar, because I think that this is still a Touch Bar issue. My 2018 MacBook Pro was suffering from so-called Touch Bar Flickering issue this week before this repeatedly reboot happens. Also, I found one tweet,
[automerge]1588153155[/automerge]

That's interesting, thanks for sharing the tweet. I would ideally like to go visit the Genius Bar but all stores are closed in my area. In the few days prior to the repeated reboot issue I was primarily using an external keyboard & mouse, so I did not notice if there was a Touch Bar flickering issue, unfortunately.
 

Stan Lin

macrumors newbie
Apr 28, 2020
6
0
That's interesting, thanks for sharing the tweet. I would ideally like to go visit the Genius Bar but all stores are closed in my area. In the few days prior to the repeated reboot issue I was primarily using an external keyboard & mouse, so I did not notice if there was a Touch Bar flickering issue, unfortunately.
I live in China. Apple Stores have already reopened for a while. And after I had my MacBook shutdown, I could still spot Touch Bar was flickering occasionally!
 

chrfr

macrumors G5
Jul 11, 2009
13,716
7,290
I'm planning to pay a visit to Genius Bar, because I think that this is still a Touch Bar issue. My 2018 MacBook Pro was suffering from so-called Touch Bar Flickering issue this week before this repeatedly reboot happens. Also, I found one tweet,
[automerge]1588153155[/automerge]
That tweet isn't applicable to the 2018 model, which uses the T2 to run many more things than the T1 did in the older computers.
Nonetheless, taking the computer in for repair is likely the right approach. It may just need to have the T2 firmware reinstalled via Apple Configurator, but there may also be a hardware problem as well.
 

Stan Lin

macrumors newbie
Apr 28, 2020
6
0
That tweet isn't applicable to the 2018 model, which uses the T2 to run many more things than the T1 did in the older computers.
Nonetheless, taking the computer in for repair is likely the right approach. It may just need to have the T2 firmware reinstalled via Apple Configurator, but there may also be a hardware problem as well.
I post this tweet mainly because it says what kind of a device com.apple.dfrd may be, which is the cause of Bridge OS kernel panic I suppose. So I know it should be an hardware issue related to Touch Bar itself.

The reason I skipped the DFU restore for T2 chip is that this crash happens so quickly after I enter the password that I'm concerned if it crashes again while restore isn't finish.
[automerge]1588167200[/automerge]
That tweet isn't applicable to the 2018 model, which uses the T2 to run many more things than the T1 did in the older computers.
Nonetheless, taking the computer in for repair is likely the right approach. It may just need to have the T2 firmware reinstalled via Apple Configurator, but there may also be a hardware problem as well.
I post this tweet mainly because it says what kind of a device com.apple.dfrd may be, which is the cause of Bridge OS kernel panic I suppose. So I know it should be an hardware issue related to Touch Bar itself.

The reason I skipped the DFU restore for T2 chip is that this crash happens so quickly after I enter the password that I'm concerned if it crashes again while restore isn't finish.
Unfortunately no :( I'm out of ideas on what to try now that I've even reformatted my disk & done full OS reinstall.

The fact that you're experiencing the same thing gives me some hope that it _may_ be a software issue. Please do let me know if you come across any other cases/anything works for you!
Did you ever try DFU-restore the firmware of T2 chip via Apple Configurator 2?
 
Last edited:

chrfr

macrumors G5
Jul 11, 2009
13,716
7,290
The reason I skipped the DFU restore for T2 chip is that this crash happens so quickly after I enter the password that I'm concerned if it crashes again while restore isn't finish.
A panic in this case shouldn't happen because the operating system isn't running while the computer is in DFU mode, but it's certainly wise to be cautious when doing anything with firmware.
 

Stan Lin

macrumors newbie
Apr 28, 2020
6
0
A panic in this case shouldn't happen because the operating system isn't running while the computer is in DFU mode, but it's certainly wise to be cautious when doing anything with firmware.
I can still login to macOS within tight timeframe. If this firmware restore isn't going well, then.. things are gonna be considerably tricker. So I'm not gonna take the risk.
 

caustica

macrumors newbie
Original poster
Apr 26, 2020
10
0
I post this tweet mainly because it says what kind of a device com.apple.dfrd may be, which is the cause of Bridge OS kernel panic I suppose. So I know it should be an hardware issue related to Touch Bar itself.

The reason I skipped the DFU restore for T2 chip is that this crash happens so quickly after I enter the password that I'm concerned if it crashes again while restore isn't finish.
[automerge]1588167200[/automerge]

I post this tweet mainly because it says what kind of a device com.apple.dfrd may be, which is the cause of Bridge OS kernel panic I suppose. So I know it should be an hardware issue related to Touch Bar itself.

The reason I skipped the DFU restore for T2 chip is that this crash happens so quickly after I enter the password that I'm concerned if it crashes again while restore isn't finish.

Did you ever try DFU-restore the firmware of T2 chip via Apple Configurator 2?

No, I have not tried this, as I do not have a secondary Mac that I can use as a host Mac.
 

Stan Lin

macrumors newbie
Apr 28, 2020
6
0
After having my top case replaced at Apple Store, this issue seems has been resolved. It should be a longer period of time to tested with though.
 

caustica

macrumors newbie
Original poster
Apr 26, 2020
10
0
After having my top case replaced at Apple Store, this issue seems has been resolved. It should be a longer period of time to tested with though.

Awesome! Please do let me know if the issue reoccurs again -- otherwise I will aim to do this as well :)
 

Jojonut

macrumors newbie
Apr 15, 2022
5
0
Have you found a solution?

For background, I bought the chassis of a MacBook Pro 2019 13 inch which only had a tested screen, everything else was untested (including the touchbar). I then put in a functioning logic board and was able to get it to boot with the caveat of it shutting off every 180 seconds, or 3 minutes. During the time that it's on the touchbar doesn't function. There seems to be a dent near the touchbar and I suppose a drop in its past could have affected the functionality.

I thought it might be a software issue so I wiped the SSD only to realize that it cannot reinstall an OS due to it restarting every 3 minutes. This means I'm stuck without an OS until I can get this issue solved. Running diagnostics I get APD000 meaning no detected hardware issues so I'm at a lost. I took apart the MacBook as well, examining the different parts but I didn't notice any damages.

I hope you have an answer that doesn't involve sending it to apple as I doubt they'd repair my frankensteined macbook.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.