crwdns2933423:0crwdne2933423:0

The March 2015 update of Apple's 13" MacBook Pro Retina Display, model A1502, features fifth-generation Intel Core i5 and i7 processors and introduces the Force Touch trackpad.

crwdns2934591:01185crwdne2934591:0 crwdns2934593:0crwdne2934593:0

Why does my MacBook spazz out, but not when connected to external Dis?

Hello everyone,

I have a 2015 MacBook Pro Retina that I purchased new from Apple. It has been taken great care of through its life and kept in a protective case when it’s not in use. I replaced the battery a few months ago due to minor swelling of the original battery and the laptop has worked fine ever since. One morning I opened the laptop to be surprised with a display that was spazzing out with colors everywhere. I connected the computer to an external display to check to see if the GPU was fried, and to my surprise, the display quit spazzing out and worked completely normal. When I unplugged the external display, it went back to spazzing out.

I erased the SSD and reinstalled macOS thinking that would solve the problem. Nope

I reset the SMC and the NVRAM. Nothing.

This confirmed three things:

  1. The OS is not the issue
  2. The built-in display works fine when connected to an external display.
  3. The GPU is operational.

Does anyone know why my MacBook is having these issues?

Please watch the included video of the laptop connected to the external display.

Thanks!

J

crwdns2934081:0crwdne2934081:0 crwdns2934083:0crwdne2934083:0 crwdns2934093:0crwdne2934093:0

crwdns2934109:0crwdne2934109:0

crwdns2889612:0crwdne2889612:0 0
crwdns2934285:0crwdne2934285:0

crwdns2933313:01crwdne2933313:0

crwdns2934051:0crwdne2934051:0

Someone posted a very similar question a while back. They decided to replace the display assembly and this fixed the issue. Here’s the other internal display only works when an external display is connected.

crwdns2934105:0crwdne2934105:0

crwdns2889612:0crwdne2889612:0 2

crwdns2942205:01crwdne2942205:0:

@zpl This is a weird one for sure!

I've never was able to nail it down. I found plugging in a HDMI cable without the display also works. This appears to be a loading issue within the MUX logic.

crwdns2934271:0crwdnd2934271:0crwdne2934271:0

crwdns2934285:0crwdne2934285:0

crwdns2934229:0crwdne2934229:0

J Jones crwdns2934231:0crwdne2934231:0
crwdns2936625:0crwdne2936625:0:

crwdns2936751:024crwdne2936751:0 0

crwdns2936753:07crwdne2936753:0 0

crwdns2936753:030crwdne2936753:0 0

crwdns2942667:0crwdne2942667:0 45