Mac Mini 2012 video blinking out

mfearby, I did exactly that, returned my 2012 and bought a 2011 2.5 with ATI 6630M (note it doesn't have the HD4000). It works no problem, and get this, the 2011/i5/2.5/dual-core/6630M has a better Cinebench CL score than the 2012/i7/2.6/quad-core with HD4000 had (23.75 to 23.25)! Your brother is actually doing you a favor!

I'm not too concerned about super graphics performance per se, but stable video output certainly is highly desirable :-) My brother is very keen on his multiple monitor setup, and wouldn't always be using his MBP away from his desk, so would I be doing him a favour by buying his Mac Mini? (don't worry, he knows all about this fiasco, so there's plenty of caveat emptor to be had).

His Mac Mini was purchased on 17/1/2012 so I could still transfer my AppleCare Protection Plan to his unit, but he has added an extra SSD and swapped the memory, so I'm not sure whether it'd be worthwhile. Apple might use that as reason to dishonour it anyway...

Yes, it's a possible scenario. But if Apple doesn't give me an acceptable solution, i will not buy Apple product. The difference between OSX and Windows is much less then few years ago.

I still trust Apple, perhaps undeservedly.

Watched your video - this is exactly what is happening to me, except on my Thunderbolt display. It also happens on any HDMI display I hook up as well - black screen for just a few seconds, then back to normal. It happens after wake as well, if I allow the Mac to go to sleep. On my other Mac Mini, before it was replaced by Apple, the screen would flicker and also "jump," as if it was interference or feedback.

Probably not the best idea, but I went into System Preferences --> Energy Saver and set "Computer sleep" to Never yesterday afternoon. Since then, I haven't had any issues so far with flicker on my Thunderbolt display, but we'll see how it goes today.

You just Simply set the Computer Sleep to Never not the Display Sleep, so your Display still goes to sleep but your Mac stays on ?

As I wrote earlier, I don't seem to have the problem. I keep my computer on 24/7 and let my display sleep after 15 minutes. The power usage is minimal and it lets me run BOINC software that helps with major scientific research projects. I have owned computers since the Radio Shack TRS-80 back in 1977 and I've kept them all on and I've never had a hardware failure (except for one hard drive back in the '80s) so it doesn't seem to shorten their lives. Power supply transients on power-up and power-down do as much damage to computers as the thermal stress of running them 24/7. You might try leaving yours own to see if it helps. YMMV.

This discussion has drifted off into wild speculation based on almost zero information. None of us knows how the Intel chip works. For instance, does it reduce the clock speed of the GPU when it is idling? If it uses a variable clock speed, it might glitch when the clock frequency changes. But this is just more speculation.

As a computer engineer (not at Apple or Intel) I am aware of how hard it is to track down this sort of intermittent problem. At this point Apple and Intel are well aware of the problem. More carping isn't going to help. The App Store will alert you when and if an update is available. In the meantime, I suggest patience if you can live with the problem. If you can't, return the mini to Apple for a refund. Either way, shouting louder isn't going to help either you or the Apple engineers.

As I also suggested earlier, I believe that different displays will have different levels of suseptability to any problem with the stability of the timing of video signals, so if you have severe problems, getting Apple to swap your mini while using the same display may not help.

One thing is a certainty. A specification definitely exists relative to video signal timing. It is possible that the mini meets the specification and that the problem lies with the monitors cheating the spec, perhaps even Apple's own monitors. As I said, everything at this point is pointless speculation. The two scenarios that I just presented are meant to show how pointless "end user" speculation is. It could be either of these two scenarios or one of a thousand others.

Yep, the display goes to sleep, but the computer never does. Still holding strong, no flicker on my Thunderbolt or HDMI-HDMI display.

Sounds good ➕, mine is also set up to never go to sleep and the only flicker that occured for me was when it was powercycled over the weekend with beeing turned of in the evening. I'll watch for further flickering,

Im a MM owner. I own other Apple computers as well. And I am appalled at what's happened here.

With nearly 50,000 views of THIS forum alone regarding this issue, I take exception to the "it may be a small segement of MM owers."

Many "late 2012" MM owners waited a substantial time for this upgrade - and Apple HAS HAD substantial time to make it. It was Apple's choice to use the HD4000 with this computer - they had time to test it and de-bug it - that shouldn't be my job as a consumer.

I've been a professional computer user since 1999 and I've reformatted/debugged/reinstalled/swapped out more hardware and software than I can remember - and I have no intention of taking a HUGE step back with this 2012 MM to get a consistent display.

This product should have come to me PERFECT. Right - perfect: plug it in, it works. That's why I pay the "Apple premium" for computers. If in 2012 I can't get that from Apple, then I feel like it's 2000 all over again with my Gateway/Dell/HP.

Apple needs to learn from Toyota and the other automakers with recalls/product flaws: Get the legitimate message out there ASAP. Frankly, I'm surprised and disappointed that the trade journals: Apple Insider/MacWorld/MacRumorsGizmodo/ARS Technica........CONSUMER REPORTS......aren't all over this as a consumer issue.

Finally this: The next time a "Genius" says to a 2012 MM owner words to the effect "I don't know anything about this as a problem" go to the nearest computer and show him this forum and tell him that 50,000 people DO know about this issue.............

Well said!

It is supposed to be a tool to let me do other things.

I'm not interested in relishing spending hours trying to get it to work!

Keep in mind, legitimate Mac users, that other companies pay employees to pose as Mac users on these forums spreading FUD (fear, uncertainty and doubt.) A lot of the "heat" in this discussion is probably coming from them, and, of course, none of the "light."

It's getting about time for Apple to lock down this topic, with a statement acknowledging that the problem is being investigated and a promise to post updates as actual information is gained.

Being new to Apple, I hadn't heard of that. Very underhand.😮

You are right, if Apple did that it would help a lot. It is their silence that is the root cause of the customer service issue.

Anyway, at least I have done my bit by talking direct to someone fairly senior in Apple.

I thought that switching from PCs to Apple would be great. I have an iPhone, Macbook Air and Mini all bought within a few days of each other. Their interpoperability is great, the people in Apple are lovely, I just can't understand why they can't bring themselves to apologise!

I thought that switching from PCs to Apple would be great. I have an iPhone, Macbook Air and Mini all bought within a few days of each other. Their interpoperability is great, the people in Apple are lovely, I just can't understand why they can't bring themselves to apologise!

Oops. Hit post before I added anything, so I'm editing my post. I'll repeat something I said earlier. A specification (probably a formal Standard) exists for computer - display interface signals. There are three possibilities.

1) The specification is faulty. That is, it may be possible to design two devices, both of which meet the specification, and have them not work together. If this is the case, it is not Apple's fault. In this case Apple is not responsible for making their computer work with your display. They are only responsible for meeting the specification.

2) Many displays may not meet the specification. Manufacturers of displays may be cheating the spec in a way that allows them to work with most, but not all, compliant computers. If this is the case it is not Apple's fault. As before, Apple would have no responsibility.

3) It may be that the Mac mini does not meet the specification. If so, this would be Apple's fault, and they should apologize and fix the problem. This is yet to be determined.

It is not reasonable to expect Apple to apologize before they know where the fault lies. Nor is it reasonable for them to release an under-tested update.

Message was edited by: dsmith35124

My replacement MacMini arrived yesterday, it replaced the one Apple 'captured' to use their phrase.

I suffered the snow and video blackout on the previous MM which I was running extended desktop. I only saw the problem on the HDMI connected screen, the TB/MDP screen remained fine throughout.

So yesterday I first installed my Crucial 16GB upgrade, then I set it up and migrated my stuff over to it. Having set it all up I used it for a while as I updated the software, reauthorized some Adobe applications and so on. This was all without any incident.

I have been using it today so far without incident also, first this morning without any problems and again this afternoon, it was swithched off in between. It has been allowed to go to sleep on a number of occasions and has been fine afterwards.

Now the only difference is I connected the screens the other way around.

My current setup:

Eizo ColorEdge CG223W connected by TB/MDP - DVI 1680x1050

Formac 1900 connected by HDMI - DVI - 1280x1024

Previously the Eizo was via HDMI and Formac by MDP?

Both screens are in use, I have the application on the Eizo/MDP screen and floating windows to do with the application on the other screen. Currently I have Safari on the MDP screen and Console and Activity monitor on the HDMI screen.

I was asked by Apple once I had received the new MM to inform them if it was working OK, I will wait till Friday at least to see if I remain snow and flicker free.

I used to train customer service for a top ten UK FTSE 100 company!

One of the points that was driven home to my delegates was that it is essential to immediately try to make the customer feel better by apologising that they are experiencing a problem.

That apology could then go on to say that whilst the cause of the problem is currently unknown the organisation is urgently investigating to find a solution. If no timescale is known then the company gives the customer a reasonable estimate of when there will be an update.

With the customer onboard the company investigates, identifies a solution and informs the customer how it will be delivered.

Once the customer has a working solution then a final apology is issued and the company considers any form of compensation (not punitive) and maybe offers an ex-gratia payment.

To good organisations it's not rocket science!