Kernel Panic - Macbook Pro Retina Early 2013

[wkip12]

Hi Mac gurus

Im after some expert advice and help. Im very willing to learn and listen to anything sent my way! My mbp r early 2013 is experiencing a lot of kernel panics all of a sudden. I have wiped, restarted, reinstalled OS to no avail. I have botted into diagnostic mode to test hardware and that comes up all fine. Ill be honest I dont really understand what a kernel panic is, sorry! So im not too sure what to look out for or what makes it happen, I thought it was Chrome but uninstalled that and it is still happening, seems to happen often when I put the computer to sleep or shut it down perhaps. I went to the mac store but they werent very helpful and due to its age it is now a vintage model and said they werent obliged to look at it.

I have been keeping a list of the most recent KP. If anyone is able to decipher this and teach me how to read it or what to look out for, and what is going wrong with the machine I would be eternally gratefull!
Thanks for any help in advance!
W

Anonymous UUID: 25899940-407A-13B9-F8A6-40257B331846

Thu Mar 7 22:36:28 2019

*** Panic Report ***
panic(cpu 0 caller 0xffffff7fa4c5c83d): "GPU Panic: mux-regs 3 0 a0 d9 9 8 severity 3 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 1:f power-state 0 3D busy HDA idle system-state 1 power-level 20:20 connect-change 0 : NVRM[0/1:0:0]: Read Error 0x00000144: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xffffff9148fcc000 0x0e7150a2, D0, P1/4\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.28.4/src/AppleMuxControl/kext/GPUPanic.cpp:170
Backtrace (CPU 0), Frame : Return Address
0xffffff81067109b0 : 0xffffff80233aeb0d
0xffffff8106710a00 : 0xffffff80234e8653
0xffffff8106710a40 : 0xffffff80234da07a
0xffffff8106710ab0 : 0xffffff802335bca0
0xffffff8106710ad0 : 0xffffff80233ae527
0xffffff8106710bf0 : 0xffffff80233ae373
0xffffff8106710c60 : 0xffffff7fa4c5c83d
0xffffff8106710cc0 : 0xffffff7fa405ce6d
0xffffff8106710d40 : 0xffffff7fa412ad81
0xffffff8106710da0 : 0xffffff7fa641ea43
0xffffff8106710dd0 : 0xffffff7fa4063529
0xffffff8106710e80 : 0xffffff7fa3ff76e1
0xffffff8106710ea0 : 0xffffff8023a5c6a5
0xffffff8106710ee0 : 0xffffff7fa3cb3a3e
0xffffff8106710f30 : 0xffffff7fa612ca7c
0xffffff8106710f50 : 0xffffff7fa6135aa5
0xffffff8106710f70 : 0xffffff80234d982c
0xffffff8106710fd0 : 0xffffff802335be4d
Kernel Extensions in backtrace:
com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7fa3c95000->0xffffff7fa3cc9fff
com.apple.driver.AppleACPIPlatform(6.1)[E44E285D-01ED-3E8B-A21D-FC792AFC9DB9]@0xffffff7fa6125000->0xffffff7fa61c0fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[67079254-1B34-31D2-8C7B-B138E26BFDD8]@0xffffff7fa47ab000
dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7fa3c95000
dependency: com.apple.driver.AppleSMC(3.1.9)[4523E39C-6A5A-3352-BE3B-2B3BD9B70251]@0xffffff7fa47b4000
com.apple.driver.AppleMuxControl(3.28.4)[EFC6EE53-4EB1-34F5-B6E4-43429F691B51]@0xffffff7fa4c4e000->0xffffff7fa4c60fff
dependency: com.apple.driver.AppleGraphicsControl(3.28.4)[B940D328-A2B1-3906-972C-289E86DFDE48]@0xffffff7fa4c1d000
dependency: com.apple.iokit.IOACPIFamily(1.4)[67079254-1B34-31D2-8C7B-B138E26BFDD8]@0xffffff7fa47ab000
dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7fa3c95000
dependency: com.apple.iokit.IOGraphicsFamily(530.14)[D44517BE-2B53-3BD5-826E-4E78B55E3B73]@0xffffff7fa3f7d000
dependency: com.apple.AppleGraphicsDeviceControl(3.28.4)[E80DEB91-2401-31C2-901F-CA63B4342337]@0xffffff7fa3fe5000
com.apple.nvidia.driver.NVDAResman(12.0)[AE94AB7B-ECE1-31E6-8165-08FF46E8CF81]@0xffffff7fa3ff0000->0xffffff7fa42c9fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7fa3c95000
dependency: com.apple.iokit.IONDRVSupport(530)[693B770C-4748-33DC-B497-CF8C103DDD0E]@0xffffff7fa3fd5000
dependency: com.apple.iokit.IOGraphicsFamily(530.14)[D44517BE-2B53-3BD5-826E-4E78B55E3B73]@0xffffff7fa3f7d000
dependency: com.apple.AppleGraphicsDeviceControl(3.28.4)[E80DEB91-2401-31C2-901F-CA63B4342337]@0xffffff7fa3fe5000
com.apple.nvidia.driver.NVDAGK100Hal(12.0)[7F98B4E9-CEB0-3354-A034-2D90A819E58B]@0xffffff7fa6326000->0xffffff7fa64d3fff
dependency: com.apple.nvidia.driver.NVDAResman(12.0.0)[AE94AB7B-ECE1-31E6-8165-08FF46E8CF81]@0xffffff7fa3ff0000
dependency: com.apple.iokit.IOPCIFamily(2.9)[5C9A453F-559B-3683-9E81-D288D13A33CE]@0xffffff7fa3c95000

BSD process name corresponding to current thread: firefox

Mac OS version:
18D109

Kernel version:
Darwin Kernel Version 18.2.0: Thu Dec 20 20:46:53 PST 2018; root:xnu-4903.241.1~1/RELEASE_X86_64
Kernel UUID: 1970B070-E53F-3178-83F3-1B95FA340695
Kernel slide: 0x0000000023000000
Kernel text base: 0xffffff8023200000
__HIB text base: 0xffffff8023100000
System model name: MacBookPro10,1 (Mac-C3EC7CD22292981F)

System uptime in nanoseconds: 15813387371618
last loaded kext at 2895337640823: com.apple.driver.usb.cdc.acm 5.0.0 (addr 0xffffff7fa6de6000, size 32768)
loaded kexts:
com.apple.filesystems.msdosfs 1.10
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AudioAUUC 1.70
com.apple.fileutil 18.306.12
com.apple.filesystems.autofs 3.0
com.apple.driver.AppleMikeyHIDDriver 131
com.apple.driver.AppleMikeyDriver 282.10
com.apple.driver.ApplePlatformEnabler 2.7.0d0
com.apple.driver.AGPM 110.23.46
com.apple.driver.X86PlatformShim 1.0.0
com.apple.driver.AppleGraphicsDevicePolicy 3.28.4
com.apple.AGDCPluginDisplayMetrics 3.28.4
com.apple.driver.AppleHDAHardwareConfigDriver 282.10
com.apple.driver.AppleHV 1
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.driver.AppleHDA 282.10
com.apple.driver.AppleUpstreamUserClient 3.6.5
com.apple.iokit.IOBluetoothSerialManager 6.0.10f1
com.apple.driver.pmtelemetry 1
com.apple.GeForce 12.0.0
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleIntelHD4000Graphics 12.0.4
com.apple.driver.AppleThunderboltIP 3.1.2
com.apple.driver.eficheck 1
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.AGDCBacklightControl 3.28.4
com.apple.driver.AppleSMCPDRC 1.0.0
com.apple.nvidia.NVDAStartup 12.0.0
com.apple.driver.AppleSMCLMU 212
com.apple.driver.AppleMuxControl 3.28.4
com.apple.driver.AppleLPC 3.1
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleFIVRDriver 4.1.0
com.apple.driver.AppleIntelSlowAdaptiveClocking 4.0.0
com.apple.driver.AppleIntelFramebufferCapri 12.0.4
com.apple.driver.AppleBacklight 170.12.11
com.apple.driver.AppleMCCSControl 1.5.6
com.apple.iokit.IOBluetoothUSBDFU 6.0.10f1
com.apple.driver.AppleUSBTCKeyEventDriver 254
com.apple.driver.AppleUSBTCButtons 254
com.apple.driver.AppleUSBTCKeyboard 254
com.apple.driver.AppleFileSystemDriver 3.0.1
com.apple.driver.AppleVirtIO 2.1.3
com.apple.filesystems.hfs.kext 407.200.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.BootCache 40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0
com.apple.AppleSystemPolicy 1.0
com.apple.filesystems.apfs 945.241.4
com.apple.driver.AirPort.Brcm4331 800.21.30
com.apple.driver.AppleSDXC 1.7.6
com.apple.iokit.AppleBCM5701Ethernet 10.3.3
com.apple.driver.AirPort.Brcm4360 1400.1.1
com.apple.private.KextAudit 1.0
com.apple.driver.AppleAHCIPort 329.200.2
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 190
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 220.0.0
com.apple.driver.usb.cdc.acm 5.0.0
com.apple.driver.usb.serial 6.0.0
com.apple.driver.usb.cdc.ecm 5.0.0
com.apple.kext.triggers 1.0
com.apple.iokit.IOAVBFamily 710.1
com.apple.plugin.IOgPTPPlugin 700.7
com.apple.driver.DspFuncLib 282.10
com.apple.kext.OSvKernDSPLib 527
com.apple.driver.AppleSSE 1.0
com.apple.nvidia.driver.NVDAGK100Hal 12.0.0
com.apple.nvidia.driver.NVDAResman 12.0.0
com.apple.AppleGPUWrangler 3.28.4
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.AppleHDAController 282.10
com.apple.iokit.IOHDAFamily 282.10
com.apple.driver.AppleThunderboltEDMSink 4.2.0
com.apple.driver.AppleThunderboltDPOutAdapter 5.5.8
com.apple.driver.AppleSMBusPCI 1.0.14d1
com.apple.driver.AppleGraphicsControl 3.28.4
com.apple.driver.X86PlatformPlugin 1.0.0
com.apple.driver.IOPlatformPluginFamily 6.0.0d8
com.apple.iokit.IOSlowAdaptiveClockingFamily 1.0.0
com.apple.iokit.IOAcceleratorFamily2 404.2.2
com.apple.iokit.IOSurface 255.1
com.apple.AppleGraphicsDeviceControl 3.28.4
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.iokit.IONDRVSupport 530
com.apple.driver.AppleSMBusController 1.0.18d1
com.apple.iokit.IOGraphicsFamily 530.14
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 6.0.10f1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 6.0.10f1
com.apple.iokit.IOBluetoothHostControllerTransport 6.0.10f1
com.apple.iokit.IOBluetoothFamily 6.0.10f1
com.apple.driver.AppleUSBMultitouch 263
com.apple.driver.AppleUSBAudio 315.6
com.apple.driver.usb.IOUSBHostHIDDevice 1.2
com.apple.iokit.IOAudioFamily 206.5
com.apple.vecLib.kext 1.2.0
com.apple.driver.usb.cdc 5.0.0
com.apple.driver.usb.networking 5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice 1.2
com.apple.driver.usb.AppleUSBHub 1.2
com.apple.iokit.IOSerialFamily 11
com.apple.filesystems.hfs.encodings.kext 1
com.apple.driver.AppleThunderboltDPInAdapter 5.5.8
com.apple.driver.AppleThunderboltDPAdapterFamily 5.5.8
com.apple.driver.AppleThunderboltPCIDownAdapter 2.1.4
com.apple.driver.AppleXsanScheme 3
com.apple.driver.AppleThunderboltNHI 4.7.6
com.apple.iokit.IOThunderboltFamily 6.8.1
com.apple.iokit.IOAHCIBlockStorage 301.200.2
com.apple.iokit.IOEthernetAVBController 1.1.0
com.apple.iokit.IO80211Family 1200.12.2
com.apple.driver.mDNSOffloadUserClient 1.0.1b8
com.apple.driver.corecapture 1.0.4
com.apple.driver.AppleUSBMergeNub 900.4.2
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.2
com.apple.driver.AppleUSBHostMergeProperties 1.2
com.apple.driver.AppleEFINVRAM 2.1
com.apple.driver.AppleEFIRuntime 2.1
com.apple.iokit.IOSMBusFamily 1.1
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.security.quarantine 3
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.DiskImages 493.0.0
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleEffaceableStorage 1.0
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleUSBTDM 456.230.1
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.kext.CoreTrust 1
com.apple.iokit.IOUSBMassStorageDriver 145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice 408.200.1
com.apple.iokit.IOSCSIArchitectureModelFamily 408.200.1
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.IOTimeSyncFamily 700.7
com.apple.iokit.IONetworkingFamily 3.4
com.apple.iokit.IOReportFamily 47
com.apple.driver.AppleACPIPlatform 6.1
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

 

[casperes1996]

I'll help you understand - If you just want the conclusion about the issue, you can skip to the last paragraph, but I'm afraid it's not a happy answer.

The kernel is the lowest level of the operating system, interacting with the actual hardware on the computer so higher level software doesn't have to.
A kernel panic is when this software layer lands in a situation it cannot recover from. You've likely had apps crash before. A kernel panic is the result of a similar crash but to the kernel instead of an app.
There can be many reasons for kernel panics, so reading the log is necessary to understand the nature of the issue, whether it is severe or not, and possible steps to prevent it going forward.

The line "BSD process name corresponding to current thread: firefox" tells you which program the CPU was doing work for when the panic happened. However, in this specific instance, I do not blame Firefox for anything. Any program could've triggered the panic and your initial thought that Chrome was responsible was likely not entirely unfounded, since any program activating the GPU can/will cause a panic for you, and if Firefox does so, Chrome likely did too.

That conclusion comes from this part:

panic(cpu 0 caller 0xffffff7fa4c5c83d): "GPU Panic: mux-regs 3 0 a0 d9 9 8 severity 3 WS-ready 1 switch-state 0 IG FBs 0 EG FBs 1:f power-state 0 3D busy HDA idle system-state 1 power-level 20:20 connect-change 0 : NVRM[0/1:0:0]: Read Error 0x00000144: CFG 0xffffffff 0xffffffff 0xffffffff, BAR0 0xc0000000 0xffffff9148fcc000 0x0e7150a2, D0, P1/4\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.28.4/src/AppleMuxControl/kext/GPUPanic.cpp:170

As mentioned, the kernel handles communication between the hardware and the higher levels of software. Here we are told that this specific panic is a GPU panic. - That's the vital information here.


Conclusion:
Your GPU is dying. The hardware diagnostics says it is fine, but it clearly isn't. Perhaps diagnostics would find the issue if re-run a few times, since it may not necessarily surface every time the GPU is issued, but only some of the time. The situation is really unfortunate, but you may not be entirely out of luck just yet:
There were some issues with early 2013 GPUs, see this:
https://discussions.apple.com/thread/7932844
Unfortunately the repair programme has ended. You can avoid the issue by forcing the use of the iGPU only, but at the cost of GPU performance (see the link above - there's a link to a github page in the first answer for a tool that lets you force iGPU)

 

[treekram]

A kernel panic happens when the OS encounters an inconsistency which it cannot resolve so the decision is made to reboot the computer. Before it reboots the computer it writes the relevant information about the panic to a file.

In your case, I see a couple of possible issues. One is Firefox - that's the program that was running when the kernel panic occurs. This may be due to a bug in Firefox or it just happened to be the program that was running at the time. If it is Firefox that's the problem, what you would see is that the line which says "BSD process name corresponding to current thread: firefox" would appear consistently in your kernel panic logs.

However, I suspect that it could be an issue with your GPU. It appears you have the 15" model - because "com.apple.nvidia.driver.NVDAResman" is in the stacktrace. The early 2015 15" MBP were the subject of a warranty extension (long since ended). Apple no longer has the specifics of this warranty extension program available although it's probably accessible on a website that archives old pages. But this is a link that describes the program:
https://www.idownloadblog.com/2016/02/19/apple-repair-extension-macbook-pro-video-issues/

When you say the "mac store" - is that the Apple Store - if so, that's a shame because when the extension was in effect, they were able to determine whether specific computers were affected although people who were having problems said Apple said their computer was not affected and the people were dubious about this claim. You might be able to take it to an Apple-authorized service provider to try to determine if your computer has this problem but there's a good likelihood you'd have to pay for that.

At the very top of the report, just after "*** Panic Report ***", if your kernel panic reports consistently say ""GPU Panic" and if it consistently says "BuildRoot/Library/Caches/com.apple.xbs/Sources/AppleGraphicsControl/AppleGraphicsControl-3.28.4/src/AppleMuxControl/kext/GPUPanic.cpp:170" just after that, then that's a pretty clear indication that the GPU is a problem.

When did you start having these problems? At one point, it seemed that certain OS updates (starting from about High Sierra 10.13.3?) were triggering a lot of these kernel panics but the people having the problems for the most part did not report their resolution so I can't say one way or the other if it was software related. If you just started having them just after the recent 10.14.3 supplemental update, then perhaps it could be a software issue. But if you've been having them for a while now, it would be harder to pinpoint the OS as a problem. Also, as this hardware gets older, its more likely that it's a hardware issue.

The previous post came up as I was writing this and you can see we have much the same conclusions.

 

[casperes1996]

The previous post came up as I was writing this and you can see we have much the same conclusions.

Yep . Regarding this though:

When did you start having these problems? At one point, it seemed that certain OS updates (starting from about High Sierra 10.13.3?) were triggering a lot of these kernel panics but the people having the problems for the most part did not report their resolution so I can't say one way or the other if it was software related. If you just started having them just after the recent 10.14.3 supplemental update, then perhaps it could be a software issue. But if you've been having them for a while now, it would be harder to pinpoint the OS as a problem. Also, as this hardware gets older, its more likely that it's a hardware issue.

When did you start having these problems? At one point, it seemed that certain OS updates (starting from about High Sierra 10.13.3?) were triggering a lot of these kernel panics but the people having the problems for the most part did not report their resolution so I can't say one way or the other if it was software related. If you just started having them just after the recent 10.14.3 supplemental update, then perhaps it could be a software issue. But if you've been having them for a while now, it would be harder to pinpoint the OS as a problem. Also, as this hardware gets older, its more likely that it's a hardware issue.

This was never a software issue. It is correct that for many it surfaced after a software update, but the issue was always in hardware. The relation to the software updates were just that during a software update, temperatures may rise a bit - and parts of the hardware that may not have been used extensively before may be utilized differently in the new update.
The extra heat could push the hardware over the edge that it was already standing at, or the new ways the hardware was being accessed could bring to the surface the already existing issue, but in any case, it's hardware.

 

[treekram]

Yep . Regarding this though:
This was never a software issue. It is correct that for many it surfaced after a software update, but the issue was always in hardware. The relation to the software updates were just that during a software update, temperatures may rise a bit - and parts of the hardware that may not have been used extensively before may be utilized differently in the new update.
The extra heat could push the hardware over the edge that it was already standing at, or the new ways the hardware was being accessed could bring to the surface the already existing issue, but in any case, it's hardware.

I would not disagree with you that just going through the OS update process could have exercised the hardware enough to trigger the defect. But what I'm saying is of all the people who reported these problems after whatever update it was (again I think it was 10.13.3), I think one person reverted back to Sierra and didn't have a recurrence of kernel panics and nobody else reported definitive results - either 1) continued kernel panics after reverting; 2) no kernel panics after reverting or 3) no problems after some later OS update. Nobody came back with a major rant saying how Apple is a scumbag company for allowing this to happen which is what I would expect if indeed they couldn't get their problem fixed. So to me, it remains a mystery. But if somebody has this problem now AND can identify a specific OS update that triggered the problem AND can easily revert back, they may want to try reverting back before spending money on repairs or a new computer. But I think at this point, considering the age of these computers, it is more likely a hardware issue.