MacBook Pro 2016 GPU failure

Here is a compilation of problems already encountered by users of the new MacBooks Pro [atualizado]

Much has been said about the new MacBooks Pro, whether approving or disapproving aspects of new Apple computers. Despite this, something that goes beyond opinions are real problems reported by users; these cannot be ignored.

There is a graphical flaw appearing in the new MBPs, with reports in the Apple support forum [1, 2] and also in the MacRumors, where there is even a publication by user Jan Becker accompanied by a video to demonstrate exactly what is happening:

I put my new MBP to work and went to edit a project in Premiere Pro. When I used Adobe Media Encoder, the graphics card went crazy and the computer crashed. I went to an Apple Store and they said it was probably a hardware problem. So, I ordered a new one. I kept using MPB that I have now because when I put Final Cut Pro X on, everything seems to be working fine. But the technician said I shouldn’t trust this after I showed him the video of him going crazy. I have Radeon Pro 460 with 4GB of memory.

One of the editors of the 9to5Mac, Jordan Kahn, noticed that several application windows appeared “torn” and it was possible to see the background of the Table (Desktop). Others also reported red and black bands and other distortions.

MacBook Pro 2016 GPU failure

Although they appear to be different GPU-related problems (most cases in the 15-inch MBP), many are seeing flaws when running Premiere Pro and, more especially, Adobe Media Encoder.

· · ·

And, if you think that the complaints stop there, you are wrong.

Another problem that also appeared both in the Apple community and in the MacRumors [1, 2, 3, 4] it was a flaw in the trackpad of the new MBPs, in both the 13 and 15 inch models. Users complained that the three-finger drag gesture on trackpads (used to move a window) is either interpreted as another gesture or simply does not recognize any movement.

I have the new 15-inch MacBook Pro with Touch Bar and it looks like there is a problem with the trackpad. Although enabled, the three-finger drag feature does not work on the upper left side of the trackpad. It’s very bizarre.

Luke, forum user MacRumors.

Try to activate the three-finger drag gesture and make the gesture at the bottom left of the trackpad: there is a 40% chance that it will interpret as a secondary click. Sometimes it was not possible to detect the gesture or the middle of the trackpad.

Darren, user of the Apple support community

One of the users recalled that this problem may have to do with the palm rejection feature (palm rejection); since the trackpad is a lot bigger in the new models, it might actually make sense, even if the ideal was that it didn’t happen.

It is not yet known whether the above problems are actually hardware or if the failures are software – which would be infinitely easier to fix, just by releasing an update (s). However, one last reported problem suggests a specific flaw in a Windows audio driver when users use macOS Boot Camp on new MBPs.

What happens is that users hear loud “pops” when they are running Windows on their machines and some even said that this would be causing physical problems to the speakers. Users stated that the problem ceases as soon as they connect any headphones or speakers to MPB (both 13 ″ and 15 ″); others said they solved the problem by installing Realtek HD Audio Driver version 6.0.1.7989 (released 11/15). However, Apple’s official recommendation is that, as soon as the user witnesses the problems, he calls AppleCare.

With this large number of problems being reported, we need to use Breno Masi’s phrase and say that the new MacBook Pro “is not a bit bizarre, it is bizarre and a half” (listeners of the MacMagazine On Air # 206 will understand ?).

[via 9to5Mac, MacRumors, AppleInsider]

Update, for Rafael Fischmann · Nov 30, 2016 at 21:57

At least one of these problems, that of the Boot Camp, has already been corrected by Apple. His Windows drivers were updated a few days ago silently, but obviously the speakers that were damaged by the bug need to be physically replaced.

[via AppleInsider]