Black screen, computer still running, GPU Panic?

[Jezthomp]

My Mac is just turning off, well the screen mostly even connected to an external device sometimes restarts itself.
Fans have been going mental for months as well.

I've copied in the error report below along with its spec, is there anything i can do to fix this?

I can access the computer via share screen but nothing else.

Is it a genius bar and graphics replacement job and if so is it really worth it on a almost 6year old computer?


MacBook Pro "Core i7" 2.3 15" Retina 2012
Graphics Inter HD Graphics 4000

*** Panic Report ***

panic(cpu 2 caller 0xffffff7f854339e9): "GPU Panic: mux-regs 5 0 a0 d9 9 8 severity 3 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 9:f power-state 0 3D idle HDA busy : NVRM[0/1:0:0]: Read Error 0x0000e804: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xffffff9118fbb000 0x0e7150a2, D0, P1/4\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.16.21/src/AppleMuxControl/kext/GPUPanic.cpp:162

etc etc etc

 

[jerryk]

Take it in and see what they say. But, It is hard to justify spending a lot of money on the system.

 

[treekram]

It looks like a GPU issue but the "etc etc etc" could contain important information.

Your model had a "Repair Extension Program for Video Issues." The program has ended but you may want to contact Apple to see if they can run the diagnostic test mentioned in the below link on your MBP. If you can get them to run the program and it turns out that it's not the GPU, then the kernel panic report may have important information as I mentioned. You can try running the computer in safe mode as the computer will not load 3rd-party kernel extensions, etc. that are the cause of most non-hardware related kernel panics. If it works in safe mode when it didn't before, you have a software issue.

If it is the GPU then you should get quotes from Apple-authorized service providers as they would likely quote a lower price. But GPU repairs that Apple did for the 2011 model typically failed later - I don't know if the same is true of the 2012 GPU issues.

https://www.apple.com/support/macbookpro-videoissues/

https://support.apple.com/en-us/HT201262

 

[Jezthomp]

It looks like a GPU issue but the "etc etc etc" could contain important information.

Your model had a "Repair Extension Program for Video Issues." The program has ended but you may want to contact Apple to see if they can run the diagnostic test mentioned in the below link on your MBP. If you can get them to run the program and it turns out that it's not the GPU, then the kernel panic report may have important information as I mentioned. You can try running the computer in safe mode as the computer will not load 3rd-party kernel extensions, etc. that are the cause of most non-hardware related kernel panics. If it works in safe mode when it didn't before, you have a software issue.

If it is the GPU then you should get quotes from Apple-authorized service providers as they would likely quote a lower price. But GPU repairs that Apple did for the 2011 model typically failed later - I don't know if the same is true of the 2012 GPU issues.

https://www.apple.com/support/macbookpro-videoissues/

https://support.apple.com/en-us/HT201262

Sorry i just didn't want a big scroll, here is the rest...

*** Panic Report ***

panic(cpu 2 caller 0xffffff7f854339e9): "GPU Panic: mux-regs 5 0 a0 d9 9 8 severity 3 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 9:f power-state 0 3D idle HDA busy : NVRM[0/1:0:0]: Read Error 0x0000e804: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xffffff9118fbb000 0x0e7150a2, D0, P1/4\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.16.21/src/AppleMuxControl/kext/GPUPanic.cpp:162

Backtrace (CPU 2), Frame : Return Address

0xffffff913e542be0 : 0xffffff8003c4f606

0xffffff913e542c30 : 0xffffff8003d7c654

0xffffff913e542c70 : 0xffffff8003d6e149

0xffffff913e542cf0 : 0xffffff8003c01120

0xffffff913e542d10 : 0xffffff8003c4f03c

0xffffff913e542e40 : 0xffffff8003c4edbc

0xffffff913e542ea0 : 0xffffff7f854339e9

0xffffff913e542f00 : 0xffffff7f848e467e

0xffffff913e542fc0 : 0xffffff7f849b65be

0xffffff913e543020 : 0xffffff7f869b1fc9

0xffffff913e543070 : 0xffffff7f869b1564

0xffffff913e543120 : 0xffffff7f869b2355

0xffffff913e543180 : 0xffffff7f869bc607

0xffffff913e5431c0 : 0xffffff7f848fdf31

0xffffff913e5432e0 : 0xffffff7f869b845d

0xffffff913e543440 : 0xffffff7f869b8787

0xffffff913e5434e0 : 0xffffff7f848fe26c

0xffffff913e543510 : 0xffffff7f849f371d

0xffffff913e543590 : 0xffffff7f849f321b

0xffffff913e5435c0 : 0xffffff7f84a049df

0xffffff913e543690 : 0xffffff7f848bb20f

0xffffff913e5436f0 : 0xffffff7f848ba5df

0xffffff913e543710 : 0xffffff7f848ba1fe

0xffffff913e5437c0 : 0xffffff7f848b9fd9

0xffffff913e5437e0 : 0xffffff7f848a78ac

0xffffff913e543880 : 0xffffff7f848e9199

0xffffff913e543a80 : 0xffffff7f848e9e05

0xffffff913e543b70 : 0xffffff7f84ac8033

0xffffff913e543bc0 : 0xffffff7f84ac88d1

0xffffff913e543cc0 : 0xffffff7f848770d0

0xffffff913e543d50 : 0xffffff7f84859fff

0xffffff913e543dc0 : 0xffffff7f8485cff9

0xffffff913e543e00 : 0xffffff7f8480ec28

0xffffff913e543e50 : 0xffffff7f8480e7b6

0xffffff913e543e80 : 0xffffff7f84814feb

0xffffff913e543ed0 : 0xffffff8004290925

0xffffff913e543f30 : 0xffffff800428f132

0xffffff913e543f70 : 0xffffff800428e76c

0xffffff913e543fa0 : 0xffffff8003c004f7

Kernel Extensions in backtrace:

com.apple.iokit.IONDRVSupport(517.22)[5672A7EF-44E8-3897-90DE-DAF4C1488143]@0xffffff7f84858000->0xffffff7f84867fff

dependency: com.apple.iokit.IOGraphicsFamily(517.22)[2AEA02BF-2A38-3674-A187-E5F610FD65B7]@0xffffff7f84804000

dependency: com.apple.iokit.IOPCIFamily(2.9)[8E6C654E-4A8F-3C6B-BBFE-BA8A68C9C146]@0xffffff7f84494000

com.apple.driver.AppleMuxControl(3.16.21)[B4DB1D7A-D4DE-3965-94DC-05CE8B9F2802]@0xffffff7f85425000->0xffffff7f85437fff

dependency: com.apple.driver.AppleGraphicsControl(3.16.21)[2EB9A384-439B-3BDC-927C-34E390CB0E59]@0xffffff7f853ef000

dependency: com.apple.iokit.IOACPIFamily(1.4)[8794C760-FDD9-3664-ADED-4A9BBEC6E517]@0xffffff7f84f7f000

dependency: com.apple.iokit.IOPCIFamily(2.9)[8E6C654E-4A8F-3C6B-BBFE-BA8A68C9C146]@0xffffff7f84494000

dependency: com.apple.iokit.IOGraphicsFamily(517.22)[2AEA02BF-2A38-3674-A187-E5F610FD65B7]@0xffffff7f84804000

dependency: com.apple.AppleGraphicsDeviceControl(3.16.21)[F8503E88-24EF-3DBA-A4D6-FA1CE4C47427]@0xffffff7f84868000

com.apple.nvidia.driver.NVDAResman(10.2.8)[39AC3832-2295-3B7B-85F6-F69D66D46EC7]@0xffffff7f84875000->0xffffff7f84b5afff

dependency: com.apple.iokit.IOPCIFamily(2.9)[8E6C654E-4A8F-3C6B-BBFE-BA8A68C9C146]@0xffffff7f84494000

dependency: com.apple.iokit.IONDRVSupport(517.22)[5672A7EF-44E8-3897-90DE-DAF4C1488143]@0xffffff7f84858000

dependency: com.apple.iokit.IOGraphicsFamily(517.22)[2AEA02BF-2A38-3674-A187-E5F610FD65B7]@0xffffff7f84804000

dependency: com.apple.AppleGraphicsDeviceControl(3.16.21)[F8503E88-24EF-3DBA-A4D6-FA1CE4C47427]@0xffffff7f84868000

com.apple.nvidia.driver.NVDAGK100Hal(10.2.8)[7064CB37-CB6D-34F7-974D-DD12944BD354]@0xffffff7f86988000->0xffffff7f86b3afff

dependency: com.apple.nvidia.driver.NVDAResman(10.2.8)[39AC3832-2295-3B7B-85F6-F69D66D46EC7]@0xffffff7f84875000

dependency: com.apple.iokit.IOPCIFamily(2.9)[8E6C654E-4A8F-3C6B-BBFE-BA8A68C9C146]@0xffffff7f84494000



BSD process name corresponding to current thread: kernel_task



Mac OS version:

17D47



Kernel version:

Darwin Kernel Version 17.4.0: Sun Dec 17 09:19:54 PST 2017; root:xnu-4570.41.2~1/RELEASE_X86_64

Kernel UUID: 18D901F1-4A03-3FF1-AE34-C26B2732F13C

Kernel slide: 0x0000000003800000

Kernel text base: 0xffffff8003a00000

__HIB text base: 0xffffff8003900000

System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)



System uptime in nanoseconds: 8327363861513

last loaded kext at 7403831859834: com.apple.driver.AppleXsanScheme 3 (addr 0xffffff7f8748c000, size 32768)

last unloaded kext at 7897611396123: com.apple.driver.usb.cdc 5.0.0 (addr 0xffffff7f8746d000, size 28672)

loaded kexts:

com.apple.filesystems.afpfs 11.1

com.apple.nke.asp-tcp 8.0.2

com.apple.driver.AudioAUUC 1.70

com.apple.driver.AppleHWSensor 1.9.5d0

com.apple.driver.AGPM 110.23.30

com.apple.driver.ApplePlatformEnabler 2.7.0d0

com.apple.driver.X86PlatformShim 1.0.0

com.apple.filesystems.autofs 3.0

com.apple.driver.AppleMikeyHIDDriver 131

com.apple.AGDCPluginDisplayMetrics 3.16.2

com.apple.driver.AppleHV 1

com.apple.iokit.IOUserEthernet 1.0.1

com.apple.driver.AppleUpstreamUserClient 3.6.4

com.apple.driver.AppleHDA 280.12

com.apple.iokit.IOBluetoothSerialManager 6.0.2f2

com.apple.driver.AppleMikeyDriver 280.12

com.apple.driver.AGDCBacklightControl 3.16.2

com.apple.driver.pmtelemetry 1

com.apple.GeForce 10.2.8

com.apple.driver.AppleIntelHD4000Graphics 10.3.0

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.driver.eficheck 1

com.apple.driver.AppleThunderboltIP 3.1.1

com.apple.driver.AppleSMCPDRC 1.0.0

com.apple.driver.AppleLPC 3.1

com.apple.driver.AppleIntelFramebufferCapri 10.3.0

com.apple.driver.AppleMuxControl 3.16.21

com.apple.driver.AppleMCCSControl 1.5.3

com.apple.driver.AppleSMCLMU 211

com.apple.driver.AppleOSXWatchdog 1

com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0

com.apple.driver.AppleUSBTCKeyboard 254

com.apple.driver.AppleUSBTCButtons 254

com.apple.filesystems.apfs 748.41.3

com.apple.filesystems.hfs.kext 407.30.1

com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1

com.apple.BootCache 40

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0

com.apple.driver.AppleSDXC 1.7.6

com.apple.driver.AirPort.Brcm4360 1220.18.1a2

com.apple.driver.AppleAHCIPort 329

com.apple.driver.AppleSmartBatteryManager 161.0.0

com.apple.driver.AppleACPIButtons 6.1

com.apple.driver.AppleRTC 2.0

com.apple.driver.AppleHPET 1.8

com.apple.driver.AppleSMBIOS 2.1

com.apple.driver.AppleACPIEC 6.1

com.apple.driver.AppleAPIC 1.7

com.apple.driver.AppleIntelCPUPowerManagementClient 220.0.0

com.apple.nke.applicationfirewall 183

com.apple.security.TMSafetyNet 8

com.apple.security.quarantine 3

com.apple.IOBufferCopyEngineTest 1

com.apple.driver.AppleIntelCPUPowerManagement 220.0.0

com.apple.driver.AppleThunderboltPCIUpAdapter 2.1.3

com.apple.driver.AppleHIDKeyboard 203

com.apple.security.SecureRemotePassword 1.0

com.apple.kext.triggers 1.0

com.apple.driver.AppleSSE 1.0

com.apple.driver.DspFuncLib 280.12

com.apple.kext.OSvKernDSPLib 526

com.apple.iokit.IOSerialFamily 11

com.apple.nvidia.driver.NVDAGK100Hal 10.2.8

com.apple.nvidia.driver.NVDAResman 10.2.8

com.apple.driver.AppleBacklightExpert 1.1.0

com.apple.driver.AppleHDAController 280.12

com.apple.iokit.IOHDAFamily 280.12

com.apple.iokit.IOAudioFamily 206.5

com.apple.vecLib.kext 1.2.0

com.apple.driver.AppleSMBusPCI 1.0.14d1

com.apple.iokit.IOAcceleratorFamily2 376.6

com.apple.iokit.IOSurface 209.2.2

com.apple.driver.AppleGraphicsControl 3.16.21

com.apple.driver.AppleSMBusController 1.0.18d1

com.apple.driver.X86PlatformPlugin 1.0.0

com.apple.driver.IOPlatformPluginFamily 6.0.0d8

com.apple.AppleGPUWrangler 3.16.2

com.apple.AppleGraphicsDeviceControl 3.16.21

com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0

com.apple.iokit.IONDRVSupport 517.22

com.apple.iokit.IOGraphicsFamily 517.22

com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 6.0.2f2

com.apple.iokit.IOBluetoothHostControllerUSBTransport 6.0.2f2

com.apple.iokit.IOBluetoothHostControllerTransport 6.0.2f2

com.apple.iokit.IOBluetoothFamily 6.0.2f2

com.apple.driver.AppleUSBMultitouch 261

com.apple.driver.usb.IOUSBHostHIDDevice 1.2

com.apple.driver.usb.networking 5.0.0

com.apple.driver.usb.AppleUSBHostCompositeDevice 1.2

com.apple.driver.usb.AppleUSBHub 1.2

com.apple.filesystems.hfs.encodings.kext 1

com.apple.driver.AppleThunderboltDPInAdapter 5.0.2

com.apple.driver.AppleThunderboltDPAdapterFamily 5.0.2

com.apple.driver.AppleThunderboltPCIDownAdapter 2.1.3

com.apple.iokit.IOAHCIBlockStorage 301.40.2

com.apple.driver.AppleThunderboltNHI 4.5.6

com.apple.iokit.IOThunderboltFamily 6.6.3

com.apple.iokit.IO80211Family 1200.12.2

com.apple.driver.mDNSOffloadUserClient 1.0.1b8

com.apple.driver.corecapture 1.0.4

com.apple.iokit.IOAHCIFamily 288

com.apple.driver.usb.AppleUSBEHCIPCI 1.2

com.apple.driver.usb.AppleUSBEHCI 1.2

com.apple.driver.usb.AppleUSBXHCIPCI 1.2

com.apple.driver.usb.AppleUSBXHCI 1.2

com.apple.driver.usb.AppleUSBHostPacketFilter 1.0

com.apple.iokit.IOUSBFamily 900.4.1

com.apple.driver.AppleUSBHostMergeProperties 1.2

com.apple.driver.AppleEFINVRAM 2.1

com.apple.driver.AppleEFIRuntime 2.1

com.apple.iokit.IOHIDFamily 2.0.0

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.sandbox 300.0

com.apple.kext.AppleMatch 1.0.0d1

com.apple.iokit.IOBufferCopyEngineFamily 1

com.apple.driver.DiskImages 480.30.2

com.apple.driver.AppleFDEKeyStore 28.30

com.apple.driver.AppleEffaceableStorage 1.0

com.apple.driver.AppleKeyStore 2

com.apple.driver.AppleUSBTDM 439.30.4

com.apple.driver.AppleMobileFileIntegrity 1.0.5

com.apple.iokit.IOUSBMassStorageDriver 140.30.1

com.apple.iokit.IOSCSIBlockCommandsDevice 404.30.2

com.apple.iokit.IOSCSIArchitectureModelFamily 404.30.2

com.apple.iokit.IOStorageFamily 2.1

com.apple.driver.AppleCredentialManager 1.0

com.apple.driver.KernelRelayHost 1

com.apple.iokit.IOUSBHostFamily 1.2

com.apple.driver.usb.AppleUSBCommon 1.0

com.apple.driver.AppleBusPowerController 1.0

com.apple.driver.AppleSEPManager 1.0.1

com.apple.driver.IOSlaveProcessor 1

com.apple.iokit.IOReportFamily 31

com.apple.iokit.IOTimeSyncFamily 650.5

com.apple.iokit.IONetworkingFamily 3.4

com.apple.driver.AppleACPIPlatform 6.1

com.apple.driver.AppleSMCRTC 1.0

com.apple.driver.AppleSMC 3.1.9

com.apple.iokit.IOPCIFamily 2.9

com.apple.iokit.IOACPIFamily 1.4

com.apple.kec.pthread 1

com.apple.kec.Libm 1

com.apple.kec.corecrypto 1.0



EOF

Model: MacBookPro10,1, BootROM MBP101.00F2.B00, 4 processors, Intel Core i7, 2.3 GHz, 8 GB, SMC 2.3f36

Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In

Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020

Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54333531533642465238432D50422020

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (7.21.190.16.1a2)

Bluetooth: Version 6.0.2f2, 3 services, 18 devices, 1 incoming serial ports

Network Service: Wi-Fi, AirPort, en0

PCI Card: pci1b21,612, AHCI Controller, Thunderbolt@195,0,0

Serial ATA Device: APPLE SSD SM256E, 251 GB

Serial ATA Device: ST3000DM001-1ER166, 3 TB

USB Device: USB 2.0 Bus

USB Device: Hub

USB Device: FaceTime HD Camera (Built-in)

USB Device: USB 2.0 Bus

USB Device: Hub

USB Device: Hub

USB Device: Apple Internal Keyboard / Trackpad

USB Device: BRCM20702 Hub

USB Device: Bluetooth USB Host Controller

USB Device: USB 3.0 Bus

USB Device: Hub

USB Device: Hub

USB Device: USB 2.0 Hub [MTT]

USB Device: Keyboard Hub

USB Device: Apple Keyboard

Thunderbolt Bus: MacBook Pro, Apple Inc., 23.4

Thunderbolt Device: d2, LaCie, 1, 7.4

[doublepost=1517434670][/doublepost]

It looks like a GPU issue but the "etc etc etc" could contain important information.

Your model had a "Repair Extension Program for Video Issues." The program has ended but you may want to contact Apple to see if they can run the diagnostic test mentioned in the below link on your MBP. If you can get them to run the program and it turns out that it's not the GPU, then the kernel panic report may have important information as I mentioned. You can try running the computer in safe mode as the computer will not load 3rd-party kernel extensions, etc. that are the cause of most non-hardware related kernel panics. If it works in safe mode when it didn't before, you have a software issue.

If it is the GPU then you should get quotes from Apple-authorized service providers as they would likely quote a lower price. But GPU repairs that Apple did for the 2011 model typically failed later - I don't know if the same is true of the 2012 GPU issues.

https://www.apple.com/support/macbookpro-videoissues/

https://support.apple.com/en-us/HT201262

I’ve managed to start up in safe mode and it seems a little more stable, but saying that a normal start up sometimes works. Is there anyway within Safe Mode to determine if anything is effected?

Also if safe mode does seem to be okay how do i go about isolating the problem, a resin tall of Sierra with a time machine backup or something else?

I only have one login item within login items and thats mail.

One observation is that the fans are not going crazy in safe mode which they’ve been doing for months!

 

[treekram]

In the kernel panic report, there are no 3rd-party kernel extensions in the backtrace so it's more likely than not the GPU issue which prompted the warranty extension program is the cause of that specific kernel panic than any software issue. So, I think a visit to the genius bar is a good idea. Ask them if they can run the diagnostic program for the 2012 15" Retina GPU issues. If I recall correctly there was at least one person here in this forum who reported that the diagnostic program said their MBP didn't qualify for the repair (when it was active) but who really believed that the GPU was faulty.

A program like EtreCheck will help to identify the startup items, launch agents, launch daemons, user login items, plug-ins that run without the user explicitly starting an app. Any of these items may cause issues and one of these may be causing the fan issue. You can use the "Activity Monitor" app to see which process is using the CPU - which in turn is the likely cause of the fan running so much. If you find a suspect item, you'd have to deactivate or de-install it and see if it changes anything.

https://etrecheck.com/

 

[Jezthomp]

In the kernel panic report, there are no 3rd-party kernel extensions in the backtrace so it's more likely than not the GPU issue which prompted the warranty extension program is the cause of that specific kernel panic than any software issue. So, I think a visit to the genius bar is a good idea. Ask them if they can run the diagnostic program for the 2012 15" Retina GPU issues. If I recall correctly there was at least one person here in this forum who reported that the diagnostic program said their MBP didn't qualify for the repair (when it was active) but who really believed that the GPU was faulty.

A program like EtreCheck will help to identify the startup items, launch agents, launch daemons, user login items, plug-ins that run without the user explicitly starting an app. Any of these items may cause issues and one of these may be causing the fan issue. You can use the "Activity Monitor" app to see which process is using the CPU - which in turn is the likely cause of the fan running so much. If you find a suspect item, you'd have to deactivate or de-install it and see if it changes anything.

https://etrecheck.com/

Would a fresh reinstall also fix these problems if it is indeed a software issue?
As safe mode seems okay, i assume a fresh install of Sierra also works in that way, otherwise the screen would go off during that process?

Might try that before a genius visit...

 

[Samuelsan2001]

Would a fresh reinstall also fix these problems if it is indeed a software issue?
As safe mode seems okay, i assume a fresh install of Sierra also works in that way, otherwise the screen would go off during that process?

Might try that before a genius visit...

Give it a try but its sounding like a dgpu issue to be honest. The kernel extensions that deal with your dgpu are almost certainly turned off in safe mode but I have been unable to clarify that.

 

[treekram]

Would a fresh reinstall also fix these problems if it is indeed a software issue?
As safe mode seems okay, i assume a fresh install of Sierra also works in that way, otherwise the screen would go off during that process?

Might try that before a genius visit...

A fresh install would likely solve your high CPU usage. You would then add your additional software one-by-one, making sure you have versions compatible with High Sierra and either deciding to drop an app if it causes issues or trying to troubleshoot it. It may also be that the high CPU usage exacerbates a possible GPU problem.

However, it likely won't solve the root cause of whatever caused your kernel panic. I did have an issue once with my 2012 Mini and Yosemite versions later than 10.10.2 which caused GPU (for the Mini it's a iGPU, not a dGPU) kernel panics - which stopped once I installed El Capitan - and maybe, if you your problems only occurred after you installed High Sierra, reverting back may help. But I don't think this is the case with your MBP as Apple acknowledges there were GPU issues with at least some of the 2012 15" retina MBP's.

I did find this article on the web which looks to involve the 2014 MBP's with the NVidia GPU and the kernel panic report looks similar to what you have. There aren't that many people (if any?) on this forum with the 2014 MBP who has the same issue so I don't know what to make of it.

http://blog.scoopz.com/2014/05/13/retina-macbook-pro-screen-going-blankblack-intermittently/

So I think you should take a trip to the Genius Bar, if not overly inconvenient to see what they have to say.

 

[Jezthomp]

Reinstalled and still happening.

Now need to decide whether to pay them to check.

Its going to be a few hundred to sort i think and is it worth it on an almost 6ry old computer?

 

[jerryk]

Reinstalled and still happening.

Now need to decide whether to pay them to check.

Its going to be a few hundred to sort i think and is it worth it on an almost 6ry old computer?

It would not be worth it to me. But, only can decide if it is worth it to you. Personally, with a system that old my thought would be "what will break next?"

 

[treekram]

Reinstalled and still happening.

Now need to decide whether to pay them to check.

Its going to be a few hundred to sort i think and is it worth it on an almost 6ry old computer?

A visit to the Genius Bar would be free. If it is the GPU, Apple would usually replace the whole logic board and one post says Apple quoted $575 (as of Jan. 26, 2018) for this. I haven't seen a definitive explanation of the 2012 issue but with the earlier MBP's with dGPU issues the problem was with the solder used to attach the dGPU to the logic board and more often than not the replacement ended up failing again down the road.
https://discussions.apple.com/thread/8215109

If your MBP is in otherwise good shape and if it is the GPU issue, if it were me, I would sell the MBP (parts are worth something) and get an Apple-refurbished 2015 15" MBP - they have those for $1700 with 16GB of memory vs. 8GB you have now with the same size SSD (but significantly faster). If you still have the original battery, the cost of Apple replacing it is $199 so you could count that cost as part of keeping the 2012 MBP. At one point, people were able to get a newer model if the battery needed service - this situation has been fluid and I think I saw somewhere that this was no longer being done.
https://www.macrumors.com/2017/07/24/mid-2012-macbook-pro-top-case-battery-constraint/

EDIT: If you do get a replacement MBP 2016 or later, you're going to have to spend extra to be able to connect your LaCie d2 as there are no Thunderbolt 1/2 ports on the MBP >= 2016.

 

[sublunar]

The keyword to use at the Apple Store is satisfaction. If you're told about the repair plan being over you can say something along the lines of it not being a satisfactory state of affairs for a computer that you expect to last 6 years. It might be worth phoning Apple support and running it by them to see if you can get some sort of satisfaction code to take to the Apple Store - it's like giving the Genius folks more wiggle room to go through the expense to repair - or do some sort of deal like give you a sizeable discount off a new replacement (this is just fishing at this point though).

At that age, yes, paying money to repair a 2012 might be a false economy depending on your budget and getting a newer model might be feasible if you can afford that instead. You've had more than your money's worth from the 2012 model and there's plenty of deals from retailers for newer models from time to time.

 

[l.a.rossmann]

Not to spam, but I will point to my post in this thread as to how to solve this problem. It is very similar to how Apple resolved these issues during their extended warranty program, IMO. https://forums.macrumors.com/threads/worth-replacing-logic-board-2012-mp-15.2108531/#post-25882695