This is what happens from time to time when I open the lid to wake it from sleep (15 second video):
It's the base non touch bar 13" model.
It's the base non touch bar 13" model.
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.
Graphics Defect in my all new 13" base model Macbook Pro
- Thread starter kathyricks
- Start date
- Sort by reaction score
Not sure it's a software/driver issue. That kind of graphical corruption could also be caused by hardware issues.
There have been a lot of graphics issues with the new macs these days. If you're in your return period take it back, otherwise call AppleCare, and get a warranty replacement. Better to be safe than to be stuck with a possibly defective unit.
There have been a lot of graphics issues with the new macs these days. If you're in your return period take it back, otherwise call AppleCare, and get a warranty replacement. Better to be safe than to be stuck with a possibly defective unit.
RELAX!
This is macOS Sierra issue. I have Early 2015 MacBook Pro 13 and have the same. On El Capitan is working fine.
Already talked to AppleCare. They pretend to have never heard of the issue and asked me naive, canned questions like "What OS are you using? Let's check your Safari settings." So I told them I would return the unit to Best Buy for a refund since I bought it only 1 week ago. I like these new MacBook Pro's but they're not yet ready for prime time - maybe early next Spring the bugs will have been worked out of them.
[doublepost=1481055976][/doublepost]
Good to know, but why aren't AppleCare reps being trained to publicly acknowledge there's a serious macOS Sierra issue that will be will soon be fixed with an update?
It's not happening on my MBP 13 with touch bar at all. Hasn't done it a single time.
At this point, since it involves 2016 non-touchbar 13" machines, touch bar 13" machines and 15" machines, it's got to be a software issue - all these machines use different processors and iGPUs or dGPUs. So either every single Skylake processor coming out of Intel has this issue or it's an OS driver bug.
While not completely ruling out hardware, I think it's almost certainly going to turn out to be a software issue.
While not completely ruling out hardware, I think it's almost certainly going to turn out to be a software issue.