VFD002 Diagnostic Error - macOS won't boot with hardware acceleration

Mac

I put my MacBook Pro 13" Late 2013 on the charger last night, opened it up this morning, it worked for a few minutes, then everything froze. The clock stopped counting the seconds, trackpad wouldn't move mouse, keyboard input didn't work, shutting the lid didn't turn off the display. I held down the power button and tried to reboot, but the same thing would happen either at the login screen or while showing the apple logo with progress bar. I reset SMC and NVRAM, no dice. I ran diagnostics and got a VFD002 error. The laptop runs just fine in safe mode without hardware acceleration except everything moves at a snail's pace when working with ANY graphics, the CPU also runs very hot. I'm not using an external display, it looks just fine in Diagnostics, Safe Mode, and Recovery Mode. I've read online that I may want to just get a new internal display, which I'd be willing to pay for. However if the logic board / shitty Haswell processor is broken, I'll just go out and get a new laptop. Do you think it could be a display issue or a logic board/CPU issue? If I haven't provided enough information, please tell me how I could provide more.

From System Report: Model Name: MacBook Pro Model Identifier: MacBookPro11,1 Processor Name: Intel Core i5 Processor Speed: 2.4 GHz Number of Processors: 1 Total Number of Cores: 2 L2 Cache (per Core): 256 KB L3 Cache: 3 MB Memory: 8 GB Boot ROM Version: MBP111.0138.B25 SMC Version (system): 2.16f68 Intel Iris:

Chipset Model: Intel Iris Type: GPU Bus: Built-In VRAM (Dynamic, Max): 1536 MB Vendor: Intel (0x8086) Device ID: 0x0a2e Revision ID: 0x0009 Displays: Color LCD: Display Type: spdisplays_built-in_retinaLCD Resolution: 2560 x 1600 Retina Pixel Depth: 32-Bit Color (ARGB8888) Main Display: Yes Mirror: Off Online: Yes Rotation: Supported Automatically Adjust Brightness: Yes Connection Type: DisplayPort

note, the information from system report is while macOS was booted into "safe mode" (or whatever Apple calls it). I've checked, none of the Intel HD drivers are loaded, I'm just guessing it's using a default, non-HA driver?

EDIT: Everything works fine as long as the internal display is disabled and an external one is attached. An HP w19 1440x900 if that matters. Could the problem just be a broken display cable? Again, it looks just fine without the graphics drivers enabled, so could a semi-important pin be damaged on the connector or cable? If so, is there any way to fix it myself?

Posted Jun 3, 2017, 5:12 PM UTC · edited

24
Loading comments…