M1 Mac Mini - Pixel issue on Apple Thunderbolt Display 27"

[gbobcat]

Seeing very similar behavior to what others are seeing with flickering, color-shifting pixels located toward the upper right. I have a 2021 14" MBP M1Max and a 27" Thunderbolt Display. It's not quite as large an area as some of the earlier examples, but still quite distracting!

The pixels are very active and flickery when the background is one of stock patterns or pictures. The situation is less noticeable with solid backgrounds, but still present. "Space Gray Pro" and darker causes there to be a few flickering whitish pixels. "Space Gray" and lighter causes there to be a few flickering blackish pixels.

 

[flightmansam]

Can confirm issue is still present with Macbook Pro 16" M1Pro 10c16g 16GB ram with a Comsol MDp to USB-C adaptor on macOS 12.0.1. I am using the LED Cinema Display 27". I have about 5-7 white pixels flickering in the menu-bar. Haven't tried other adapters yet. Considering upgrading the panel with some DIY to one of the LG 5K panels and using a 3rd party panel driver.

The pixel bug doesn't occur with a screen recording so we can be much more sure that it's a driver issue.

Interestingly, previous versions of macOS had no trouble controlling the brightness with inbuilt brightness controls, however I have had to control brightness using MonitorControl, maybe a missing kext? idc.

 

[SmileyDude]

I can confirm it happens with the M1 Max as well (tested on both a 32GB 16" and 64GB 14" running macOS 12.1 beta 3). I have yet to see it on any of the other displays that I use with these machines.

As far as the issue that flightmansam reported, I have no issues with using the brightness controls on my external keyboard to control the TB display brightness. The built in keyboard always adjusts the brightness on the built in display, as expected.

 

[raphaelz]

Hi everyone.
I have the same issue here with my 2020 MacBook Pro M1 and a Thunderbolt Display using the original usb-c to thunderbolt adapter.
Hope to find a fix for that.

 

[Segev]

I have the exact same issue with a 14" M1 pro connected to two Thunderbolt displays using a daisy chain. The pixels are in the exact same place as the pictures above.

Did any one got a response from apple about this?

 

[tabormeister]

Same issue, 27" Thunderbolt Display and 2021 14" MacBook Pro M1 Pro - calling and yelling at Apple today. Is there a MacOS bug specific reporting line?

 

[tabormeister]

Update: Case# 101581542849 escalated to Apple engineering.

 

[Segev]

Thanks @tabormeister. Please let us know if you get any updates regarding this.
This is very distracting to work with.

 

[tommiy]

I have a M1 Max and a thunderbolt2 27inch monitor and have the same issue. It is connected via an Apple thunderbolt2 to 3 adapter. I've tried 3 adapters and none make any difference. I have a 2017 4 port MBP and this corruption does not exist with it. I have tried a 2020 M1 on the same connection and it is corrupted as well. How do I log a issue with Apple? If I go through the support pages the only option I get is for a voice call. Is that it? I have to go down this path? I'd rather just log the problem because its obvious that its a M1 issue. The 2020 M1 is on BigSur and the M1 Max is on 12.01. They both react the same. the 2017 MBP is on Bigsur as well. So I think its pretty clear that reinstalling the OS will produce nothing new.

 

[tabormeister]

I've already reinstalled macos on the 2021 14" and created a new user acct per apple, no difference. It doesn't do it when in recovery mode so I'm pretty sure it's a kext that's only loaded when fully booted - thunderbolt or display kext. Yes calling is only way to log issue, reference my case#!

 

[tommiy]

I thought I must have blocked something to see the only available option to log an issue is via voice. Seems back in the 1990s. I'll find the time to try and spend with Apple today.

 

[tmi0815]

The Apple M1 x Architecture apparently, have a big Problem with a flacking Pixels on external Thunderbolt (27er Apple) Displays.

The pixels correlate with other pixels at the bottom of the desktop and change colors.
The Defective Pixels are located in the right side in the first line above the desktop menu bar.

The problem is also present in the rebuild console, due to the correlation of the pixels it just can't be seen because the colors on the desktop prevent it here.

Apple clearly advertises multi-screen operation with its new MacBooks, so such errors should not occur.
The problem appears even before the start of the operating system, e.g. input mask password (FileFault).

Follow Links describe the Problem.

https://www.apfeltalk.de/community/...thunderbolt-bildschirmen.565324/#post-5672935

https://communities.apple.com/de/thread/252547141

https://www.mactechnews.de/forum/di...play-am-Mac-mini-M1-angeschlossen-343079.html

This Problem was Testing (Clean Installs) in follow OSX (M1) Versions:
Monterey 12.0.1
Monterey 12.1
Monterey 12.2 (B1)

Case Numbers :
101581542849 (already known / see first infos in this thread).
101598018776 (new).

Is an exchange possible ?
Is Apple working on a solution to the problem?

You can use the Feedback Product Apple Home Page for a report.

Product Feedback

We would love to hear your comments about any of our hardware and software products. Send us your thoughts.

www.apple.com

I really hope it's not a problem in the hardware.
Apple also doesn't seem to use Intel chips for Thunderbolt technology, does anyone here know more ?

Greetings from Germany
Tomas

 

[tmi0815]

I've already reinstalled macos on the 2021 14" and created a new user acct per apple, no difference. It doesn't do it when in recovery mode so I'm pretty sure it's a kext that's only loaded when fully booted - thunderbolt or display kext. Yes calling is only way to log issue, reference my case#!

the error also exists in the recovery mode, the pixels are correlate with other pixels on your desktop. if the colors here are identical or compatible, you just don't see it.

 

[Segev]

the error also exists in the recovery mode, the pixels are correlate with other pixels on your desktop. if the colors here are identical or compatible, you just don't see it.

I can confirm that..

To be honest I'm not really sure how this passed QA.
It's not like it's a SAMSUNG screen from 2015. It's a Thunderbolt display.
No one at apple checked the M1s with their own displays?

 

[tmi0815]

I can confirm that..

To be honest I'm not really sure how this passed QA.
It's not like it's a SAMSUNG screen from 2015. It's a Thunderbolt display.
No one at apple checked the M1s with their own displays?

The Apple M1 x Architecture apparently, have a big Problem with a flacking Pixels on external Thunderbolt (27er Apple) Displays. (Maybe others too).

It can also be that it does not appear with one external screen, but with two external screens it appears 100%.

The pixels correlate with other pixels at the bottom of the desktop and change colors.
The Defective Pixels are located in the right side in the first line above the desktop menu bar.

The problem is also present in the rebuild console, due to the correlation of the pixels it just can't be seen because the colors on the desktop prevent it here.

Apple clearly advertises multi-screen operation with its new MacBooks, so such errors should not occur.
The problem appears even before the start of the operating system, e.g. input mask password (FileFault).

This Problem was Testing (Clean Installs) in follow OSX (M1) Versions:
Monterey 12.0.1
Monterey 12.1
Monterey 12.2 (B1)

Case Numbers :
101581542849 (already known / see first infos in this thread).
101598018776 (new).

it's really totally stupid bug.

 

[tabormeister]

I can confirm that..

To be honest I'm not really sure how this passed QA.
It's not like it's a SAMSUNG screen from 2015. It's a Thunderbolt display.
No one at apple checked the M1s with their own displays?

Truly unbelievable. Does it do it on a thunderbolt dock?

 

[Segev]

According to users on here, apple forums and reddit, I couldn't find a single scenario where it doesn't happen when you mix a thunderbolt display and m1.

 

[tabormeister]

According to users on here, apple forums and reddit, I couldn't find a single scenario where it doesn't happen when you mix a thunderbolt display and m1.

Right, I mean a non-apple display but over a thunderbolt dock

 

[tmi0815]

The first Thread i will find on this BUG was in:

Apple Thunderbolt Display - einige Pixel … - Apple Community

communities.apple.com

on: 11.03.2021

Apple not interested this ?

 

[Segev]

Right, I mean a non-apple display but over a thunderbolt dock

oh no idea. It would be interesting to test.

The first Thread i will find on this BUG was in:

Apple Thunderbolt Display - einige Pixel … - Apple Community

communities.apple.com

on: 11.03.2021

Apple not interested this ?

The strange part is that apple still hasn't acknowledged that. If you'll call support, they will still run you trough a series on unnecessary tests.

 

[tmi0815]

oh no idea. It would be interesting to test.



The strange part is that apple still hasn't acknowledged that. If you'll call support, they will still run you trough a series on unnecessary tests.

It would be interesting if you could connect both screens separately with one adapter each.

Does anyone have 2 adapters (usb-c Thunderbolt2) ?

Can someone test this?

 

[tabormeister]

I bet it doesn't do it on the pro display xdr

 

[tmi0815]

Yes, there is once no adapter in between (maybe the whole thing will react differently.) The XDR screen interpolate such errors probably by itself , this function is called magic mouse aeh no, sorry … magic screen. ? ....

I have somehow no desire to spend >10.000,00 euros for two functioning screens that I actually do not need.

Is certainly a scam from Apple ...

I would be interested to know if this flickering of the individual pixels could damage the screen in the long run.
Then Apple will surely donate XDR screens to us.

Maybe I should also buy an one Apple stock and submit this question at the next meeting. That's sure to go down well.

However, Apple should slowly know about this error and then not treat the customers in the hotline, like shamed users.

I would almost laugh if it wasn't so sad.

 

[tommiy]

Spent 90 min going through the Apple chat session and was escalated twice. According to the end person that I got this issue should be resolved in 12.1. Unfortunately I'm still running 12.0 because i need outlook search to work. Assuming the beta that Microsoft has is released soon I'll upgrade and see what happens. Is anyone else here running 12.1 already and can say this is still occurring?

 

[305raj]

Spent 90 min going through the Apple chat session and was escalated twice. According to the end person that I got this issue should be resolved in 12.1. Unfortunately I'm still running 12.0 because i need outlook search to work. Assuming the beta that Microsoft has is released soon I'll upgrade and see what happens. Is anyone else here running 12.1 already and can say this is still occurring?

They told me to upgrade to 12.1 last week on a call. It did not fix the issue.