On behalf of those of us without a computer science background, appreciation for your analysis! If the issue is indeed related to the display driver, why it would be affecting some machines and not others? I ask this from a place of ignorance. Several members here have been unable to get their machines to crash despite valiant attempts.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
M1 Pro and M1 Max MacBook Pro Owners Complain of Crashes Playing HDR YouTube Videos
- Thread starter MacRumors
- Start date
- Sort by reaction score
10NOV2021: Thoughtful comments and appreciated. I went back and looked at my last crash report, and it is very similar to the snapshot you posted:
panic(cpu 2 caller 0xfffffe00208d7d68): DCP PANIC - IOMFB int_handler_gated: failure: axi_rd_err [0x40300034]
- iomfb_driver(8)
IOMFB int_handler_gated: failure: axi_rd_err [0x40300034]
RTKit: RTKit-1826.40.9.debug - Client: local-t600xdcp.release !UUID: 63c86ca9-4c8f-33e2-9b03-9b1e9da40cfa
Time: 0x00000000e703fd93
In my case, a different core and other minor, probably related, differences. I've held onto my machine for several days hoping Apple would "come up with something" but now I've finally decided to return it to Apple whilst its within the 14day window. I know if there is a HW issue Apple will cover it under warranty for a year, however my rationale is - this is a problem impacting only a few machines; this is an unresolved issue; I don't know if it's HW, FW or SW; I believe that the vast majority of machine do NOT have this problem; given the choice, I prefer to be in the vast majority and own a machine that does not start on Day 1 with a problem..... so ... sadly, I'm taking it back to Apple today and will wait another couple of months for replacement.
To everyone that has tried troubleshooting this behavior, thank you for the work and suggestions and I hope (as suggested above) it is not a HW issue and Apple issue a FW/SW fix soon - actually... it would be encouraging if Apple actually communicated something about this issue - my case file is still open and not updated by Apple.
I don't know the answer to your question and I doubt anybody other than Apple would be able to give you a firm answer. Obviously the conditions leading to the crash are quite specific and we can't be certain that different people are testing in the same way.
Personally, I've had my MBP since release day and had a crash on day one, but not since. Maybe the crash is dependent on the size of the particular frame or frames in the buffer, or it could be related a specific timer in software or hardware. Too many variables to make a really educated guess.
I would say that I expect that ALL new MacBooks are affected even if their respective owners are unable to actually trigger the bug.
Returning a piece of equipment which doesn't perform as intended is absolutely your right, regardless of whether the issue is software or hardware, and I can absolutely understand why you'd want to do that.
If you do get a replacement on which you can't trigger the bug it would be interesting to know. I'm working on the basis that all machines are affected.
I do believe it's a driver issue and we know that drivers on all of the new MBPs are identical. In theory, you will see the same behaviour on a replacement. I know others say they aren't having the issue but as I said in the post above, there are just too many variables to know for sure whether the bug doesn't exist on their machines or whether they're just unable to trigger it, which are two very distinct things.
So on 12.0 my MBP didn't crash. Now just updated to 12.0.1 and the first HDR video I watch on Youtube crashed it..
Nope! I am convinced this is software, since it didn't happen prior to the upgrade. And the only reason I am watching HDR Youtube videos on it, is because of this thread
I didn’t even try it on 12.0 - as soon as I opened my laptop I updated to 12.0.1 - I wonder how long until we get a fix.
Me too - I have been able to at least stop it by switching to compact tabs - have you tride that? I really enjoy this computer a lot and I wish apple would let us know if a fix is coming or if we need to exhange.Nope! I am convinced this is software, since it didn't happen prior to the upgrade. And the only reason I am watching HDR Youtube videos on it, is because of this thread
have you been skipping over every post that says that it's not happening for them?
10NOV2021: RETURN for refund to my APPLE CARD.... it was a custom config and not possible to exchange, and now I have to go back onto Apple webstore and create a new order and join the queue all over again.... however, perhaps by the time they build the machine this issue will be sorted???
However people are saying they’ve been able to replicate or display models at the store.
10NOV2021: Yep - after a full DFU Restore and the crash continues, I am just not positive on the HW/FW/SW answer, so I took the machine back to Apple and returned it for credit on my Apple Card. Now I will create a new order on Apple's webstore and waiting until year end for the next machine..... I truly don't know what to expect from the next version, but it will be interesting. At the very least, by the end of 2021 more should be known and understood and maybe even the root cause resolved - I hope! My wait begins again. ...
Since you don’t have a base model I guess I understand returning more so.10NOV2021: Yep - after a full DFU Restore and the crash continues, I am just not positive on the HW/FW/SW answer, so I took the machine back to Apple and returned it for credit on my Apple Card. Now I will create a new order on Apple's webstore and waiting until year end for the next machine..... I truly don't know what to expect from the next version, but it will be interesting. At the very least, by the end of 2021 more should be known and understood and maybe even the root cause resolved - I hope! My wait begins again. ...
I’d call this something of a coincidence. Mine definitely crashed on 12.0 but I haven’t come across an HDR video since upgrading.
Well hopefully you shouldn’t have to wait too long. As bugs go, this one is pretty serious and affecting enough users (even if it’s only a small percentage) that Apple will, from the automatic crash reports alone, almost certainly know about it.10NOV2021: Yep - after a full DFU Restore and the crash continues, I am just not positive on the HW/FW/SW answer, so I took the machine back to Apple and returned it for credit on my Apple Card. Now I will create a new order on Apple's webstore and waiting until year end for the next machine..... I truly don't know what to expect from the next version, but it will be interesting. At the very least, by the end of 2021 more should be known and understood and maybe even the root cause resolved - I hope! My wait begins again. ...
I managed to crash mine within an hour of receiving it. Second HDR video I watched, while “testing” the screen.
I’ll be shocked if the next release of macOS, once generally released, doesn’t include a fix.
Not able to repro the crash so far on 12.1b2 (21C5031d) on my 16 Max. Using this video in Safari and Chrome:
Read my previous post which is an analysis of the crash and you’ll understand why I believe it isn’t a hardware issue.
Furthermore, even if it is a hardware issue, it doesn’t mean that a software fix can’t detect and work around hardware errors. That’s not even uncommon.
I wasn't able to replicate the error on the display model at Best Buy. Apple should put a statement out - so those of us that are impacted can know what we should do in the mean time.
In addition the the tab mode, you might try using YouTube in dark mode - not the iOS setting, just the dark mode setting on YouTube's website. Someone else suggested this and I've been unable to produce a crash (so far) using this mode.
Like x86 architectural bugs that exist for more than 20 years, and that were "fixed" by OSes. I don't even think they call it a fix anymore, it's a x86 OS "feature" required to make your software on that platform.
And more recently the Meltdown/Spectre exploits. Which maybe weren't a bug in the CPU per-se, more like an exploitation of a hardware operation that was designed to speed things up. Those were big, serious and dangerous and they were fixed by software as well.
If this is by all means a bug in Apple's CPU architecture, then I don't think returning/exchanging your laptop for another M1 would solve it. Apple will probably fix this on M2 and issue a software workaround like Saturnine described. (And like we've been dealing with in x86 for years).
As I suggested to another member, there is no rush to return/exchange if you receive(d) the laptop on or after Nov. 1st because of the extended holiday return policy through Jan. 8th. Best to wait a couple of months and see if Apple produces a software fix.