Random Black Screen input - only for those with problem! - Page 2

Aerdna · Nov 16, 2012, 12:25 PM

Looks like I'm the first one to report this problem with a Thunderbolt display. That surprises me, considering that there are numerous hits for "thunderbolt display flicker" all over the Internet, many of them dating back to 2011. Since both my Mini and my Thunderbolt display are brand new, I don't even know which one is to blame.

rolsskk · Nov 16, 2012, 11:07 PM

Quote:

Originally Posted by xyion1

the washed out whites as noted in other threads, as well as the black screen and snow (which isn't necessarily related to color)

Mine has all of those problems.

ctone · Nov 17, 2012, 04:20 PM

Quote:

Originally Posted by Aerdna

Looks like I'm the first one to report this problem with a Thunderbolt display. That surprises me, considering that there are numerous hits for "thunderbolt display flicker" all over the Internet, many of them dating back to 2011. Since both my Mini and my Thunderbolt display are brand new, I don't even know which one is to blame.

I am using the TB port to DVI using an adaptor and have had a few dropouts, so it probably is the Mini to blame.

johnnybluejeans · Nov 20, 2012, 05:13 PM

Hi all, I debated just adding a comment to the other threads -- but I thought most people might never see it.

Anyway, I keep reading about people waiting 5-40 mins for their screen to go back to normal, or hard rebooting their minis. However on my 2012 i7 all I need to do is cycle the power on my monitor to get the picture back. It has worked every time when I have had a black or snowed out screen.

Still annoying and I hope this is fixable with an update -- but at least you shouldn't have to be hard rebooting.

Aerdna · Nov 21, 2012, 07:06 AM

Quote:

Originally Posted by ctone

I am using the TB port to DVI using an adaptor and have had a few dropouts, so it probably is the Mini to blame.

In my case I'm not so sure about that. We connected my husband's 2011 Mini to the Thunderbolt display and the screen also went black.

Westyfield2 · Nov 21, 2012, 07:27 AM

at koyeung's problems with the MDP to HDMI adapter...

View Poll Results: ONLY PEOPLE WITH THE ISSUE: Which setup are you using?
HDMI -> PC Display HDMI	23	43.40%
HDMI -> PC Display DVI using adaptor	24	45.28%
TB -> PC Display HDMI using adaptor	0	0%
TB -> PC Display DVI using adaptor	3	5.66%
TB -> PC Display DP	0	0%
TB -> Mac Display TB	1	1.89%
Other	2	3.77%
Voters: 53. You may not vote on this poll

Nov 20, 2012, 05:13 PM	#29
johnnybluejeans macrumors 6502 Join Date: Jan 2006 Location: New York, NY	2012 Mac mini blackout issue -- temporary relief Hi all, I debated just adding a comment to the other threads -- but I thought most people might never see it. Anyway, I keep reading about people waiting 5-40 mins for their screen to go back to normal, or hard rebooting their minis. However on my 2012 i7 all I need to do is cycle the power on my monitor to get the picture back. It has worked every time when I have had a black or snowed out screen. Still annoying and I hope this is fixable with an update -- but at least you shouldn't have to be hard rebooting. __________________ Apple Everything
	0

Nov 21, 2012, 07:27 AM	#31
Westyfield2 macrumors 6502a Join Date: Jun 2009 Location: Bath, UK.	at koyeung's problems with the MDP to HDMI adapter... __________________ iPhone 5 64GB on 4GEE iPad 3G+WiFi 64GB 13" MacBook Air (2.13GHz, 4GB, 256GB) - 15" MacBook Pro (2.4GHz, 4GB) Mac Mini (2.6GHz quad i7, 16GB, 256GB SSD)
	0

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

Nov 16, 2012, 12:25 PM	#26
Aerdna macrumors newbie Join Date: Nov 2012 Location: Germany	Looks like I'm the first one to report this problem with a Thunderbolt display. That surprises me, considering that there are numerous hits for "thunderbolt display flicker" all over the Internet, many of them dating back to 2011. Since both my Mini and my Thunderbolt display are brand new, I don't even know which one is to blame.
	0