Перейти к основному содержанию

Отремонтируйте ваше устройство

Обучение ремонту


A1708/EMC 3164 — Released June 2017, this entry-level MacBook Pro retains its traditional function keys (as opposed to the OLED Touch Bar).

375вопросов Показать все

MBP 2017, black bars across screen, display failure.


My 2017 MBP has been developing a display fault resulting in a large black bar across the screen. This device was purchased refurbished at the start of 2018, and thus the 1 yr ltd warrenty is no longer active, but my statutory rights still stand (EU). From some research here and elsewhere it seems to be common, but not common enough to warrant a recall program.

The device is currently with an AASP, and according to them the GPU or another display component has been fried due to inadequate cooling.

The question is, would you consider this an inherent fault with the device? and has anybody sucessfully had an issue like this rectified without paying for it?

Block Image



Отвечено! Посмотреть ответ У меня та же проблема

Это хороший вопрос?

Оценка 2
Добавить комментарий

2 Ответов

Выбранное решение

This issue was covered under a warranty exception after presenting Apple with a tech report / repair quote

Был ли этот ответ полезен?

Оценка 1
Добавить комментарий
Наиболее полезный ответ

You need to hook it up to an external monitor to confirm the diagnostic.

Был ли этот ответ полезен?

Оценка 2


AASP confirmed this using an external.


Fine, as long as you saw it and not just them.


More often the internal displays T-CON board has this issue which won't show up on an external monitor. I would double check is you have the grey bar on it.

If the external's image is clean then you'll need a new display assembly, as the T-CON is part of the display via a set of ribbon cables.

As far as fault. In my option this is a design failure as the T-CON board is placed near the heat sink cooling fins. The lack of cooling either because the fans failed or the vents where blocked so air was not able to flow across the fins would be the root cause.

I would press for a warranty exception! As Apple should take responsibility.


@danj Thanks for your advice, they did indeed take responsibility for this issue.


Добавить комментарий

Добавьте свой ответ

padrick будет вечно благодарен.
Просмотр статистики:

За последние 24часов: 0

За последние 7 дней: 0

За последние 30 дней: 5

За всё время: 271