2018 MacBook Pros crashing with "Bridge OS" error

[dspdoc]

Boy, this humble thread I started exactly one month ago now has over 86,500 views and 47 pages of responses. I've also seen screenshots of this discussion on tech blogs and videos. We're famous! Although I'd rather be invisible, with a computer that doesn't crash...!

Very honorable response. I respect that and feel you. I wish none of this lately with Apple was even a “thing”. Cheers!

 

[ra004e]

So went back to Chrome and blam-o after a couple of hours. By the output shown below issue seems Intel graphics related.

{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-24 01:00:04.57 +0000","incident_id":"B32D6A96-01F6-4334-B2B7-0EC8E33822C3"}
{
"binaryImages" : [
[
"26cb7ffe-c7aa-68dd-8fce-c101101c7e4e",
18446743936270598144,
"U"
],
[
"00000000-0000-0000-0000-000000000000",
0,
"A"
],
[
"6c67aa31-2522-38c5-8373-088d4645ed4f",
6442450944,
"S"
]
],
"build" : "Bridge OS 2.4.1 (15P6703)",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-08-24 01:00:04.16 +0000",
"incident" : "B32D6A96-01F6-4334-B2B7-0EC8E33822C3",
"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",
"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 1006432 **\n",
"macOSPanicFlags" : "0x4",
"macOSPanicString" : "panic(cpu 4 caller 0xffffff800b699995): \"Graphics firmware encountered an exception: 0xd, from EIP = 0x10348\n\"@\/Library\/Caches\/com.apple.xbs\/Sources\/GPUDriversIntel\/GPUDriversIntel-10.36.19\/Common\/GLKernel\/Intel\/kbl\/sched3\/IGGuC.cpp:800\nBacktrace (CPU 4), Frame : Return Address\n0xffffff920bde3c20 : 0xffffff800b06c1c6 \n0xffffff920bde3c70 : 0xffffff800b195344 \n0xffffff920bde3cb0 : 0xffffff800b1875c4 \n0xffffff920bde3d20 : 0xffffff800b01e1e0 \n0xffffff920bde3d40 : 0xffffff800b06bc3c \n0xffffff920bde3e70 : 0xffffff800b06b9fc \n0xffffff920bde3ed0 : 0xffffff800b699995 \n0xffffff920bde3f30 : 0xffffff800b698102 \n0xffffff920bde3f70 : 0xffffff800b69772c \n0xffffff920bde3fa0 : 0xffffff800b01d557 \n\nBSD process name corresponding to current thread: kernel_task\n\nMac OS version:\n17G2208\n\nKernel version:\nDarwin Kernel Version 17.7.0: Fri Jul

 

[RumorConsumer]

Apple ordered me a replacement machine (sent to a local Apple store) and keeps calling to see when I will pick it up. I keep asking why would I even bother with an exchange when others have gotten multiple machines and kept having the same issue. The Apple rep keeps stressing that they want to "capture" my machine to test it. I'm not keen to go through the whole exchange, wipe, reinstall process just so they can do this though. If they are confident it's hardware, that's one thing, but there's no point exchanging for a software/firmware defect when the same thing will happen on the replacement. Furthermore, who knows if the replacement will have other issues that my current one doesn't have (crackling speakers, cosmetic damage, crashes while awake, etc.). No thanks.

Yes! That is the exact language we're wanting to hear. This is not your average exchange my friend. Capture means engineering has specifically requested units for inspection regarding an issue they are trying to get a handle on. So that, right there, is direct evidence that somebody who is capable of opening an engineering capture request (ie, not your average Apple Support person) is paying attention to this and is actively trying to analyze and solve it with the tools at their disposal. Full stop. You cannot ask for more.

 

[bigcat]

If this is so hard to reproduce for them, it must be a hardware issue with some chips. All I needed to crash mine was to open the lid after overnight sleep on battery, clean installation, no apps installed.

 

[dspdoc]

Yes! That is the exact language we're wanting to hear. This is not your average exchange my friend. Capture means engineering has specifically requested units for inspection regarding an issue they are trying to get a handle on. So that, right there, is direct evidence that somebody who is capable of opening an engineering capture request (ie, not your average Apple Support person) is paying attention to this and is actively trying to analyze and solve it with the tools at their disposal. Full stop. You cannot ask for more.

I agree, but unfortunately from the reports that continue to keep rolling in this seems like a very complicated and multifaceted issue. The post just above yours is a case in point. The hits just keep coming.

As scary as it might be, there indeed may be some hardware involvement here that cannot be updated with simple firmware and software updates after all. I’m of course speculating, but this is an ugly ordeal that continues to linger and spread.

 

[kryptticAZ]

If this is so hard to reproduce for them, it must be a hardware issue with some chips. All I needed to crash mine was to open the lid after overnight sleep on battery, clean installation, no apps installed.

Same here, but for some reason it doesn't happen every time. Sometimes I've gone 6 days without a crash.

 

[dspdoc]

If this is so hard to reproduce for them, it must be a hardware issue with some chips. All I needed to crash mine was to open the lid after overnight sleep on battery, clean installation, no apps installed.

Bingo!

 

[kryptticAZ]

So went back to Chrome and blam-o after a couple of hours. By the output shown below issue seems Intel graphics related.


All of my panic strings look like this:

"build" : "Bridge OS 2.4.1 (15P6703)",
"product" : "iBridge2,3",
"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",
"incident" : "DFC3CDAA-55ED-41C3-80EB-9A234DC14829",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-08-21 09:31:29.58 +0000",
"panicString" : "panic(cpu 1 caller 0xfffffff01b573984): x86 global reset detected\nDebugger message: panic\nMemory ID: 0x6\nOS version: 15P6703\nKernel version: Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010\nKernelCache UUID: 26CB7FFEC7AA68DD8FCEC101101C7E4E\niBoot version: iBoot-4076.75.2\nsecure boot?: YES\nx86 EFI Boot State: 0xe\nx86 System State: 0x0\nx86 Power State: 0x0\nPaniclog version: 9\nKernel slide: 0x0000000014e00000\nKernel text base: 0xfffffff01be04000\nEpoch Time: sec usec\n Boot : 0x5b786f7e 0x0008f96f\n Sleep : 0x5b7bdbe5 0x00024986\n Wake : 0x5b7bdbe5 0x000b966b\n Calendar: 0x5b7bdbe5 0x000cd747\n\nPanicked task 0xffffffe0003a9720: 3386 pages, 207 threads: pid 0: kernel_task\nPanicked thread: 0xffffffe00058c1d0, backtrace: 0xffffffe016f0b530, tid: 357\n\t\t lr: 0xfffffff01bff88f0 fp: 0xffffffe016f0b670\n\t\t lr: 0xfffffff01bee15f4 fp: 0xffffffe016f0b680\n\t\t lr: 0xfffffff01bf13a44 fp: 0xffffffe016f0b9f0\n\t\t lr: 0xfffffff01bf13dd4 fp: 0xffffffe016f0ba50\n\t\t lr: 0xfffffff01bf15914 fp: 0xffffffe016f0ba70\n\t\t lr: 0xfffffff01b573984 fp: 0xffffffe016f0bae0\n\t\t lr: 0xfffffff01b575bc8 fp: 0xffffffe016f0bb80\n\t\t lr: 0xfffffff01b57313c fp: 0xffffffe016f0bc00\n\t\t lr: 0xfffffff01b532aa4 fp: 0xffffffe016f0bc30\n\t\t lr: 0xfffffff01c370784 fp: 0xffffffe016f0bc60\n\t\t lr: 0xfffffff01c3700bc fp: 0xffffffe016f0bc90\n\t\t lr: 0xfffffff01beec500 fp: 0x0000000000000000\n\n",
"panicFlags" : "0x102",
"otherString" : "\n** Stackshot Succeeded ** Bytes Traced 95472 **\n",
"macOSPanicFlags" : "0x0",
"macOSPanicString" : "Global Reset\nGRC0 = 0x00010000\r\nGRC1 = 0x00000000\r\n",
"memoryStatus" : {"compressorSize":0,"compressions":0,"decompressions":0,"busyBufferCount":0,"pageSize":16384,"memoryPressure":false,"memoryPages":{"active":7937,"throttled":0,"fileBacked":9281,"wired":5236,"purgeable":10,"inactive":1590,"free":12466,"speculative":3103}},
"processByPid" : {

No mention of the Intel Graphics.

 

[SDColorado]

Apple ordered me a replacement machine (sent to a local Apple store) and keeps calling to see when I will pick it up. I keep asking why would I even bother with an exchange when others have gotten multiple machines and kept having the same issue. The Apple rep keeps stressing that they want to "capture" my machine to test it. I'm not keen to go through the whole exchange, wipe, reinstall process just so they can do this though. If they are confident it's hardware, that's one thing, but there's no point exchanging for a software/firmware defect when the same thing will happen on the replacement. Furthermore, who knows if the replacement will have other issues that my current one doesn't have (crackling speakers, cosmetic damage, crashes while awake, etc.). No thanks.

See, that’s what they said when they wanted me to send in my first one as well. At least it appears that maybe we are seeing some consistency? But it is also why I am not convinced it is software as others have suggested. They seem motivated to collect machines, which leads me to believe that either they suspect it is a hardware issue or else they are simply as uncertain as well.

 

[ra004e]

Yeah this looks like the majority of issues in this thread relating to the sleep issue. I was posting mine as something additional post adding to the issues we're all having. Always same error with Chrome and only Chrome no issues so far with Safari and have so far not seen sleep related crash others are reporting.

Should probably start my own thread ;-)

 

[SDColorado]

Boy, this humble thread I started exactly one month ago now has over 86,500 views and 47 pages of responses. I've also seen screenshots of this discussion on tech blogs and videos. We're famous! Although I'd rather be invisible, with a computer that doesn't crash...!
[doublepost=1535072267][/doublepost]

I saw StudioSanctums avatar scroll past on the ZoneofTech video posted earlier. Free publicity and any publicity is good publicity or something hahaha

 

[IG88]

If this is so hard to reproduce for them, it must be a hardware issue with some chips. All I needed to crash mine was to open the lid after overnight sleep on battery, clean installation, no apps installed.

My first KP came on day 5 during sleep, but it wasn't from opening the lid. It happened overnight.

 

[SDColorado]

Yeah this looks like the majority of issues in this thread relating to the sleep issue. I was posting mine as something additional post adding to the issues we're all having. Always same error with Chrome and only Chrome no issues so far with Safari and have so far not seen sleep related crash others are reporting.

Should probably start my own thread ;-)

Sounds like maybe it’s a different issue? Or are you getting a BridgeOS issue when it crashes?

I haven’t even tried Chrome yet. I have to say I am just not a big fan. I know it’s fast and very configurable. But it gobbles resources like Joey Chestnut at a hot dog eating contest

 

[patwithamac]

My money is on - it's a hardware issue.
They did a production run of a batch of system boards after someone loaded the wrong spec filter capacitors in a pick & place bot or something.

I'm going on week 4... and still no KP's (hope I didn't just jinx myself).

 

[ra004e]

Sounds like maybe it’s a different issue? Or are you getting a BridgeOS issue when it crashes?

I haven’t even tried Chrome yet. I have to say I am just not a big fan. I know it’s fast and very configurable. But it gobbles resources like Joey Chestnut at a hot dog eating contest

For sure a different issue than most here, but Bridge OS still reporting the error.

Funny you rag on Chrome as the machine seems like it's been much cooler using Safari vs Chrome.


{"caused_by":"macos","macos_system_state":"running","bug_type":"210","os_version":"Bridge OS 2.4.1 (15P6703)","timestamp":"2018-08-24 01:00:04.57 +0000","incident_id":"B32D6A96-01F6-4334-B2B7-0EC8E33822C3"}
{
"binaryImages" : [
[
"26cb7ffe-c7aa-68dd-8fce-c101101c7e4e",
18446743936270598144,
"U"
],
[
"00000000-0000-0000-0000-000000000000",
0,
"A"
],
[
"6c67aa31-2522-38c5-8373-088d4645ed4f",
6442450944,
"S"
]
],
"build" : "Bridge OS 2.4.1 (15P6703)",
"crashReporterKey" : "c0dec0dec0dec0dec0dec0dec0dec0dec0de0001",
"date" : "2018-08-24 01:00:04.16 +0000",
"incident" : "B32D6A96-01F6-4334-B2B7-0EC8E33822C3",
"kernel" : "Darwin Kernel Version 17.7.0: Fri Jul 6 19:25:51 PDT 2018; root:xnu-4570.71.3~1\/RELEASE_ARM64_T8010",
"macOSOtherString" : "\n** In Memory Panic Stackshot Succeeded ** Bytes Traced 1006432 **\n",
"macOSPanicFlags" : "0x4",
"macOSPanicString" : "panic(cpu 4 caller 0xffffff800b699995): \"Graphics firmware encountered an exception:

 

[RumorConsumer]

See, that’s what they said when they wanted me to send in my first one as well. At least it appears that maybe we are seeing some consistency? But it is also why I am not convinced it is software as others have suggested. They seem motivated to collect machines, which leads me to believe that either they suspect it is a hardware issue or else they are simply as uncertain as well.

Captures happen regardless of what they believe is the matter. What they are trying to do is catch a unit in a state of failure which means grabbing everything. Power adapter, all of it. They are for sure uncertain which is why they are wanting the full unit in question. You should not draw from this, however, that it is for sure "hardware" in the irremediable sense. As somebody who has worked with first responding to early failure analysis you would be surprised how many aspects of technology and engineering are totally hidden from the user, even those with the most technical understanding. For example, there are certain processes that may occur at different times on the same hardware which has it appear to be random but actually makes perfect sense to the logic thats been programmed. You really just never know. I can't tell you how many times Ive thought I nailed something and the engineer pushes his glasses up on the nose bridge and say "well how it actually works is...." and I say "ohhhh".

 

[SDColorado]

Captures happen regardless of what they believe is the matter. What they are trying to do is catch a unit in a state of failure which means grabbing everything. Power adapter, all of it. They are for sure uncertain which is why they are wanting the full unit in question. You should not draw from this, however, that it is for sure "hardware" in the irremediable sense. As somebody who has worked with first responding to early failure analysis you would be surprised how many aspects of technology and engineering are totally hidden from the user, even those with the most technical understanding. For example, there are certain processes that may occur at different times on the same hardware which has it appear to be random but actually makes perfect sense to the logic thats been programmed. You really just never know. I can't tell you how many times Ive thought I nailed something and the engineer pushes his glasses up on the nose bridge and say "well how it actually works is...." and I say "ohhhh".

I agree with you 100%. I am not convinced that it is definitely hardware, but some seem to be convinced that it definitely software and I am not ready to jump on that train either. I just don’t know and I am not sure they know for certain yet either.

Hopefully if it is hardware it is redeemable and won’t require a replacement. On a car or motorcycle they can replace the ECU since it isn’t soldered on, but if the chip is indeed faulty, maybe a fix isn’t so easy

 

[RumorConsumer]

I agree with you 100%. I am not convinced that it is definitely hardware, but some seem to be convinced that it definitely software and I am not ready to jump on that train either. I just don’t know and I am not sure they know for certain yet either.

Hopefully if it is hardware it is redeemable and won’t require a replacement. On a car or motorcycle they can replace the ECU since it isn’t soldered on, but if the chip is indeed faulty, maybe a fix isn’t so easy

Understood. I am personally rooting for Apple. That somebody got a "capture" is good enough for me. Don't stop believing. Hold on to that feeling!
[doublepost=1535079445][/doublepost]

Same here, but for some reason it doesn't happen every time. Sometimes I've gone 6 days without a crash.

Its not necessarily that its hard. Its that on these units its happening. So they acquire the ones with confirmed failures. Standard industry practice everywhere Ive worked.

 

[kryptticAZ]

My first KP came on day 5 during sleep, but it wasn't from opening the lid. It happened overnight.

Yes, all of mine are happening overnight during sleep too. I wake up and am greeted with the "Your Mac restarted due to an error" (and once with a black screen and need to force restart). Something is waking my machine after sleeping for a long time and causing it to panic. I've turned off everything I can think of that would wake it and unplugged everything during sleep too.

 

[bigcat]

My money is on - it's a hardware issue.
Someone loaded the wrong spec filter capacitors in a pic & place bot or something.

I'm going on week 4... and still no KP's (hope I didn't just jinx myself).

where did you order yours from?

 

[patwithamac]

where did you order yours from?

I ordered mine Jul 16th from apple.com
BTO - i9 2.9GHz, 32GB, 2TB
Had it shipped to my local Apple store, and picked it up on Jul 26th

 

[kryptticAZ]

My money is on - it's a hardware issue.
Someone loaded the wrong spec filter capacitors in a pic & place bot or something.

I'm going on week 4... and still no KP's (hope I didn't just jinx myself).

Do you ever let your computer sleep overnight for extended periods? If I chose to shutdown overnight instead of sleep, mine would (presumably) never KP either.

 

[patwithamac]

Do you ever let your computer sleep overnight for extended periods? If I chose to shutdown overnight instead of sleep, mine would (presumably) never KP either.

Yes, I've always put it to sleep by simply closing the lid.
Although, since I started following this thread, I've been digging a little deeper to see if/how my machine sleeps. Infact, I started a separate thread about it here -> https://forums.macrumors.com/threads/2018-mbp-doesnt-fully-sleep.2132515
Probably everyone has been too focused on this thread to notice the one I started.

My MBP is a personal-use machine. It really only gets used in the mornings and in the evenings.
My day job daily driver is a Lenovo P50 running Win 10 Ent.
So, my MBP is awakened in the morning for an hour or so, while I check mail, news, and this forum thread. Then it goes to sleep by closing the lid. It is awakened again when I return from work for a few hours while I check mail, news, and this forum thread again. Then, I put it to sleep by closing the lid before going to bed.

Lately, I've been experimenting with different permutations of sleep conditions (as you'll see that other thread).

I think I connected it to an external monitor once (via TB -to- HDMI dongle), right after I initially set it up, just to see if that would work. And I connected it to an external USB drive to do a Time Machine Backup once immediately after initial setup. Otherwise, it's never connected to anything except the AC adapter/charger.

 

[kryptticAZ]

Yes, I've always put it to sleep by simply closing the lid.
Although, since I started following this thread, I've noticed that my MPB doesn't sleep for more than a couple of hours at a time. Infact, I started a separate thread about it here -> https://forums.macrumors.com/threads/2018-mbp-doesnt-fully-sleep.2132515
Probably everyone has been too focused on this thread to notice the one I started.

My MBP is a personal-use machine. It really only gets used in the mornings and in the evenings.
My day job daily driver is a Lenovo P50 running Win 10 Ent.
So, my MBP is awakened in the morning for an hour or so, while I check mail, news, and this forum thread. Then it goes to sleep by closing the lid. It is awakened again when I return from work for a few hours while I check mail, news, and this forum thread again. Then, I put it to sleep by closing the lid before going to bed.

Lately, I've been experimenting with different permutations of sleep conditions (as you'll see that other thread).

I think I connected it to an external monitor once (via TB -to- HDMI dongle), right after I initially set it up, just to see if that would work. And I connected it to an external USB drive to do a Time Machine Backup once immediately after initial setup. Otherwise, it's never connected to anything except the AC adapter/charger.

Yeah, I've been watching that other thread too. I think my machine is waking up during sleep just like yours. The only difference is that mine kernel panics sometimes and you say yours hasn't yet. Not sure if it's relevant, but I always put it to sleep from the Apple menu with the lid open. Maybe I'll try closing the lid to see what happens.

 

[patwithamac]

... I always put it to sleep from the Apple menu with the lid open. Maybe I'll try closing the lid to see what happens.

I've tried various methods of putting it to sleep.
- Just closing the lid
- Apple menu -> Sleep
- Via the touch bar (I've added a sleep icon/option to my touch bar).

Doesn't seem to matter which option I use. Results are the same in my case.