Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

TigerMSTR

macrumors 6502
Original poster
Sep 30, 2014
320
188
Tl;dr: Less than 48 hours getting my MacBook keyboard replaced, my Mac crashed for the first time ever. I’m pretty certain that it’s due to a failing SSD. Is it possible that my MacBook’s SSD was damaged during the repair? Can I expect the damaged SSD to be covered under the 90 day warranty for the keyboard repair?


Full story: Around two months ago I got my MacBook Pro keyboard serviced under the keyboard repair program.

Within 48 hours of getting my Mac back from the repair centre, my Mac experienced its first ever kernel panic while waking from sleep. However I had recently installed a lot of software development utilities, which includes kernel extensions, so I assumed that my software was the reason for the crash and didn’t stress too much over the situation. In particular, I found that other people using the Intel HAXM kext, which I had also installed, were reporting virtually identical symptoms, so I felt pretty confident that the HAXM kext was the culprit

However over time the crashes have gotten more frequent (from once a week, to multiple times a day) to the point where the Macintosh occasionally would not start up at all. This is when I started suspecting a hardware issue. I removed the Intel HAXM kext (which I suspected was triggering the kernel panics), and the symptoms still persisted, confirming that the KAXM kext was not the culprit.

I finally put the Mac into diagnostics mode, and the diagnostics test reported that the flash storage might be failing. I then pulled up the kernel panic logs that I had saved, and upon closer inspection, I found that the NVME storage drivers started triggering kernel panics less than 48 hours after the keyboard repair. The failure of the NVME drivers strongly strongly indicates a hardware issue with the SSD, and the timing (less than 48 hours after the keyboard repair) obviously indicates that the keyboard repair likely triggered the issue. There was no evidence of any NVME driver issues prior to the the date of the keyboard repair.

So long story short, I got my MacBook keyboard serviced, and within 48 hours I experience my first ever kernel panic. The kernel panics initially happened around once a week, but it worsened overtime to the point where the SSD appears to be totally dead.

Obviously I’m now suspecting that the SSD or logic board were somehow damaged during the keyboard repair. It seems awfully unlikely that my storage would suddenly start failing just 24 hours after a hardware repair, unless some damage was done by whoever repaired the computer. Can anyone that’s more familiar with hardware confirm that the flash storage might have been damaged in the repair? Perhaps an electrostatic issue?

Also, I’m wondering if this will be covered under Apple’s 90 day warranty for hardware service. My understanding is that the 90 day warranty typically covers only failure related to the parts that were replaced. So if the keyboard was replaced, it would typically only cover damage to the keyboard within the first 90 days. Can anyone share some insight into the likelihood of Apple acknowledging that the keyboard repair probably damaged the SSD?
 
From personal experience, you will get push back from the genuises at the Apple Store, but if you insist, as long as you are within 90 days, they will likely replace the SSD for you for free. There's no way for them to prove that they didn't damage the SSD (or logic board) while replacing the keyboard, it could be anything from physical damage to ESD during the repair. Nobody can prove it either way, but as long as you are within your 90 day warranty, make the most of it.

In my case I ended up having to call Apple three times beyond the initial Apple Store visit to get the repair to be free, including one escalation, but in the end, I did get a new logic board for free from Apple when my RAM started failing within weeks of their battery replacement.
 
I would wipe the machine and do a fresh os install. see if the errors continue.

As I tell my students: correlation does not equal causation.

Joe
 
  • Like
Reactions: macintoshmac
Admittedly, kernel panics would not necessarily be the expected outcome of SSD failure. Have you shared the logs somewhere?
 
I would wipe the machine and do a fresh os install. see if the errors continue.

As I tell my students: correlation does not equal causation.

Joe

Yeah that's been done already. Drive was wiped and the OS was reinstalled. The problem persisted
 
Tl;dr: Less than 48 hours getting my MacBook keyboard replaced, my Mac crashed for the first time ever. I’m pretty certain that it’s due to a failing SSD. Is it possible that my MacBook’s SSD was damaged during the repair? Can I expect the damaged SSD to be covered under the 90 day warranty for the keyboard repair?


Full story: Around two months ago I got my MacBook Pro keyboard serviced under the keyboard repair program.

Within 48 hours of getting my Mac back from the repair centre, my Mac experienced its first ever kernel panic while waking from sleep. However I had recently installed a lot of software development utilities, which includes kernel extensions, so I assumed that my software was the reason for the crash and didn’t stress too much over the situation. In particular, I found that other people using the Intel HAXM kext, which I had also installed, were reporting virtually identical symptoms, so I felt pretty confident that the HAXM kext was the culprit

However over time the crashes have gotten more frequent (from once a week, to multiple times a day) to the point where the Macintosh occasionally would not start up at all. This is when I started suspecting a hardware issue. I removed the Intel HAXM kext (which I suspected was triggering the kernel panics), and the symptoms still persisted, confirming that the KAXM kext was not the culprit.

I finally put the Mac into diagnostics mode, and the diagnostics test reported that the flash storage might be failing. I then pulled up the kernel panic logs that I had saved, and upon closer inspection, I found that the NVME storage drivers started triggering kernel panics less than 48 hours after the keyboard repair. The failure of the NVME drivers strongly strongly indicates a hardware issue with the SSD, and the timing (less than 48 hours after the keyboard repair) obviously indicates that the keyboard repair likely triggered the issue. There was no evidence of any NVME driver issues prior to the the date of the keyboard repair.

So long story short, I got my MacBook keyboard serviced, and within 48 hours I experience my first ever kernel panic. The kernel panics initially happened around once a week, but it worsened overtime to the point where the SSD appears to be totally dead.

Obviously I’m now suspecting that the SSD or logic board were somehow damaged during the keyboard repair. It seems awfully unlikely that my storage would suddenly start failing just 24 hours after a hardware repair, unless some damage was done by whoever repaired the computer. Can anyone that’s more familiar with hardware confirm that the flash storage might have been damaged in the repair? Perhaps an electrostatic issue?

Also, I’m wondering if this will be covered under Apple’s 90 day warranty for hardware service. My understanding is that the 90 day warranty typically covers only failure related to the parts that were replaced. So if the keyboard was replaced, it would typically only cover damage to the keyboard within the first 90 days. Can anyone share some insight into the likelihood of Apple acknowledging that the keyboard repair probably damaged the SSD?
I would wipe the machine and do a fresh os install. see if the errors continue.

As I tell my students: correlation does not equal causation.

Joe

@PROFESS0R said it best. Correlation does not equal causation. Perform a fresh install by downloading a fresh copy of the latest macOS and check again. If it persists, you can then push the issue with Apple.
 
  • Like
Reactions: TigerMSTR
Admittedly, kernel panics would not necessarily be the expected outcome of SSD failure. Have you shared the logs somewhere?

Why do you suggest that?

I'm pasting the crash logs below.

Notice the "panic(cpu 0 caller 0xffffff7f9a604b30): nvme: "Fatal error occurred." line. It looks like the NVME drivers are crashing, which indicates some sort of hardware fault.

Furthermore, diagnostics mode has identified the SSD as likely failing

If you can identify any other potential issues here though, please do share

Code:
Anonymous UUID:     XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

Thu Dec  5 18:44:07 2019

*** Panic Report ***
panic(cpu 0 caller 0xffffff7f9a604b30): nvme: "Fatal error occurred. ID=0xffffffff ARG1=0xffffffff ARG2=0xffffffff ARG3=0xffffffff EDD0=0xffffffff EDD1=0xffffffff EDD2=0xffffffff EDD3=0xffffffff EDD4=0xffffffff EDD5=0xffffffff EDD6=0xffffffff EDD7=0xffffffff NANDV=0x1, DRAMV=0x1, SSDC=512GB. FW Revision=16.14.01\n"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/IONVMeFamily/IONVMeFamily-387.270.1/IONVMeController.cpp:5334
Backtrace (CPU 0), Frame : Return Address
0xffffff915c07ba10 : 0xffffff80175af57d
0xffffff915c07ba60 : 0xffffff80176eb065
0xffffff915c07baa0 : 0xffffff80176dc79a
0xffffff915c07bb10 : 0xffffff801755c9d0
0xffffff915c07bb30 : 0xffffff80175aef97
0xffffff915c07bc50 : 0xffffff80175aede3
0xffffff915c07bcc0 : 0xffffff7f9a604b30
0xffffff915c07be20 : 0xffffff8017c5e997
0xffffff915c07be90 : 0xffffff8017c5e8b9
0xffffff915c07bec0 : 0xffffff80175ee715
0xffffff915c07bf40 : 0xffffff80175ee2b5
0xffffff915c07bfa0 : 0xffffff801755c0ce
      Kernel Extensions in backtrace:
         com.apple.iokit.IONVMeFamily(2.1)[5B883761-5506-3B6C-8370-6C624743BDBD]@0xffffff7f9a5f7000->0xffffff7f9a636fff
            dependency: com.apple.driver.AppleMobileFileIntegrity(1.0.5)[17A7EC3A-8985-3FD5-B08E-F1EF3DBE2ABC]@0xffffff7f983c6000
            dependency: com.apple.iokit.IOPCIFamily(2.9)[4CEDE29C-2826-337B-8A0B-00C6F5270D9B]@0xffffff7f97e95000
            dependency: com.apple.driver.AppleEFINVRAM(2.1)[EA211A61-0A0D-3B82-B027-DF65A108E4AD]@0xffffff7f9859c000
            dependency: com.apple.iokit.IOStorageFamily(2.1)[C733FB96-7C76-3174-9B7F-C8BE0E9E65C2]@0xffffff7f981bc000
            dependency: com.apple.iokit.IOReportFamily(47)[B0D3B0E7-4325-3EE3-817A-AD594AB286A6]@0xffffff7f98ae0000

BSD process name corresponding to current thread: kernel_task

Mac OS version:
18G1012

Kernel version:
Darwin Kernel Version 18.7.0: Sat Oct 12 00:02:19 PDT 2019; root:xnu-4903.278.12~1/RELEASE_X86_64
Kernel UUID: DFB5D0E2-3B41-3647-A48B-D704AFCC06B4
Kernel slide:     0x0000000017200000
Kernel text base: 0xffffff8017400000
__HIB  text base: 0xffffff8017300000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 1161292291584
last loaded kext at 264536191942: com.apple.filesystems.msdosfs    1.10 (addr 0xffffff7f9ae4c000, size 69632)
loaded kexts:
com.intel.kext.intelhaxm    7.5.1
com.apple.filesystems.msdosfs    1.10
com.apple.driver.AudioAUUC    1.70
com.apple.fileutil    20.036.15
com.apple.driver.ApplePlatformEnabler    2.7.0d0
com.apple.driver.AGPM    110.25.11
com.apple.driver.X86PlatformShim    1.0.0
com.apple.filesystems.autofs    3.0
com.apple.driver.AppleUpstreamUserClient    3.6.5
com.apple.driver.AppleHDAHardwareConfigDriver    282.54
com.apple.driver.AppleHDA    282.54
com.apple.driver.AppleGraphicsDevicePolicy    3.50.14
com.apple.AGDCPluginDisplayMetrics    3.50.14
com.apple.driver.AppleHV    1
com.apple.iokit.IOUserEthernet    1.0.1
com.apple.iokit.IOBluetoothSerialManager    6.0.14d3
com.apple.driver.pmtelemetry    1
com.apple.driver.AppleIntelPCHPMC    2.0.1
com.apple.driver.AppleThunderboltIP    3.1.2
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AppleIntelKBLGraphics    12.1.0
com.apple.driver.ACPI_SMC_PlatformPlugin    1.0.0
com.apple.driver.AppleCameraInterface    6.8.0
com.apple.driver.AGDCBacklightControl    3.50.14
com.apple.driver.AppleIntelKBLGraphicsFramebuffer    12.1.0
com.apple.driver.AppleOSXWatchdog    1
com.apple.driver.AppleSMCLMU    212
com.apple.driver.AppleFIVRDriver    4.1.0
com.apple.driver.AppleIntelSlowAdaptiveClocking    4.0.0
com.apple.driver.AppleGFXHDA    100.1.414
com.apple.driver.eficheck    1
com.apple.driver.AppleBacklight    170.12.12
com.apple.driver.AppleMCCSControl    1.5.9
com.apple.filesystems.apfs    945.275.8
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.driver.AppleTopCaseHIDEventDriver    138.4
com.apple.driver.AirPort.BrcmNIC    1400.1.1
com.apple.private.KextAudit    1.0
com.apple.driver.AppleSmartBatteryManager    161.0.0
com.apple.driver.AppleACPIButtons    6.1
com.apple.driver.AppleRTC    2.0
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleACPIEC    6.1
com.apple.driver.AppleAPIC    1.7
com.apple.nke.applicationfirewall    202
com.apple.security.TMSafetyNet    8
com.apple.kext.triggers    1.0
com.apple.driver.DspFuncLib    282.54
com.apple.kext.OSvKernDSPLib    528
com.apple.driver.AppleGraphicsControl    3.50.14
com.apple.iokit.IOAVBFamily    760.6
com.apple.plugin.IOgPTPPlugin    740.2
com.apple.iokit.IOEthernetAVBController    1.1.0
com.apple.driver.AppleSSE    1.0
com.apple.iokit.IOBluetoothHostControllerUARTTransport    6.0.14d3
com.apple.iokit.IOBluetoothHostControllerTransport    6.0.14d3
com.apple.driver.IOPlatformPluginLegacy    1.0.0
com.apple.AppleGPUWrangler    3.50.14
com.apple.driver.AppleHDAController    282.54
com.apple.iokit.IOHDAFamily    282.54
com.apple.driver.AppleThunderboltEDMSink    4.2.0
com.apple.driver.AppleThunderboltDPOutAdapter    5.6.9
com.apple.AppleGraphicsDeviceControl    3.50.14
com.apple.iokit.IOAcceleratorFamily2    404.14
com.apple.iokit.IOSurface    255.6.1
com.apple.driver.AppleSMBusPCI    1.0.14d1
com.apple.driver.AppleIntelLpssUARTv1    3.0.60
com.apple.driver.AppleIntelLpssUARTCommon    3.0.60
com.apple.driver.AppleOnboardSerial    1.0
com.apple.iokit.IOSkywalkFamily    1
com.apple.driver.X86PlatformPlugin    1.0.0
com.apple.driver.IOPlatformPluginFamily    6.0.0d8
com.apple.iokit.IOSlowAdaptiveClockingFamily    1.0.0
com.apple.iokit.IOAudioFamily    206.5
com.apple.vecLib.kext    1.2.0
com.apple.driver.AppleBacklightExpert    1.1.0
com.apple.iokit.IONDRVSupport    530.51
com.apple.driver.AppleSMBusController    1.0.18d1
com.apple.iokit.IOGraphicsFamily    530.67
com.apple.driver.AppleXsanScheme    3
com.apple.iokit.IOSerialFamily    11
com.apple.filesystems.hfs.encodings.kext    1
com.apple.driver.AppleActuatorDriver    2450.1
com.apple.driver.AppleHIDKeyboard    208
com.apple.driver.AppleHSBluetoothDriver    138.4
com.apple.driver.IOBluetoothHIDDriver    6.0.14d3
com.apple.iokit.IOBluetoothFamily    6.0.14d3
com.apple.driver.AppleMultitouchDriver    2450.1
com.apple.driver.AppleInputDeviceSupport    2440.2
com.apple.driver.AppleHSSPIHIDDriver    55.1
com.apple.driver.AppleThunderboltDPInAdapter    5.6.9
com.apple.driver.AppleThunderboltDPAdapterFamily    5.6.9
com.apple.driver.AppleThunderboltPCIDownAdapter    2.1.5
com.apple.driver.AppleHPM    3.4.1
com.apple.driver.AppleIntelLpssI2CController    3.0.60
com.apple.driver.AppleHSSPISupport    55.1
com.apple.driver.AppleThunderboltNHI    4.7.9
com.apple.iokit.IOThunderboltFamily    6.8.6
com.apple.iokit.IO80211Family    1200.12.2
com.apple.driver.mDNSOffloadUserClient    1.0.1b8
com.apple.driver.corecapture    1.0.4
com.apple.driver.AppleIntelLpssSpiController    3.0.60
com.apple.driver.AppleIntelLpssDmac    3.0.60
com.apple.iokit.IONVMeFamily    2.1.0
com.apple.driver.usb.AppleUSBHostPacketFilter    1.0
com.apple.iokit.IOUSBFamily    900.4.2
com.apple.driver.AppleIntelLpssGspi    3.0.60
com.apple.driver.AppleIntelLpssI2C    3.0.60
com.apple.driver.usb.AppleUSBXHCIPCI    1.2
com.apple.driver.usb.AppleUSBXHCI    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.260.3
com.apple.driver.AppleMobileFileIntegrity    1.0.5
com.apple.iokit.IOUSBMassStorageDriver    145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice    408.250.3
com.apple.iokit.IOSCSIArchitectureModelFamily    408.250.3
com.apple.iokit.IOStorageFamily    2.1
com.apple.kext.CoreTrust    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    47
com.apple.iokit.IOTimeSyncFamily    740.2
com.apple.iokit.IONetworkingFamily    3.4
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
 
Why do you suggest that?

I'm pasting the crash logs below.

Notice the "panic(cpu 0 caller 0xffffff7f9a604b30): nvme: "Fatal error occurred." line. It looks like the NVME drivers are crashing, which indicates some sort of hardware fault.

Furthermore, diagnostics mode has identified the SSD as likely failing

If you can identify any other potential issues here though, please do share

Well you know, it could be a software issue e.g. a recently applied OSX update causing an incompatibility with the specific SSD, or due to overheating or some other problem, in which case the actual drive might be perfectly fine. Or it could be an issue with the PCI controller on the motherboard. So not necessarily an SSD failure. SSD failure would be more likely to show up as read/write errors, data corruption, or slowdowns.

The particular kernel panic here does seem to be widely reported over the last few months and it seems related to wake/sleep and power nap.

There's an SSD repair program for some MBPs which might also be related: https://support.apple.com/en-ca/13-inch-macbook-pro-solid-state-drive-service.

Have you checked the SSD's SMART status for clues?

Either way, just from sheer timing you can argue this should be covered under your 90 days. Obviously, make a full backup right away if you haven't already.
 
  • Like
Reactions: macintoshmac
Just go with a fresh Mojave install if you prefer that, or the latest Catalina and see if it resolves the issues you are facing, before you visit Apple.
 
I would wipe the machine and do a fresh os install. see if the errors continue.

As I tell my students: correlation does not equal causation.

Joe
I was reading about a joke Abraham Lincoln once told jurors. A boy comes running to his father, yelling that his sister was in the hay loft with the hired hand, and they’d just taken off their clothes, and now the two were fixing to pee on the hay.

You got the facts exactly right, the father tells his son. But your conclusion is all wrong.
 
Last edited:
  • Like
Reactions: macintoshmac
The particular kernel panic here does seem to be widely reported over the last few months and it seems related to wake/sleep and power nap.

Do you have any more details about this? My issue also seems to be rated to wake and sleep. However, my Mac isn’t turning on anymore, and diagnostics mode did report a potentially failing storage, so it might not be exactly the same issue that’s been reported
 
I experienced very similar issues likes your after a keyboard repair. My macbook worked without failure for a week, but when I went to render a video on it I started to get kernel panics and reboots. It would only happen when I utilized the video card, I manually made the macbook use the internal gfx chip and it would work fine during the export.

I was about to return the macbook to the repair centre when it hit me, maybe there is an issue with one of the fans in my macbook. I did a SMC reset and NVRAM/PRAM reset and when I rebooted the left fan would again work normally. I have never encountered a single reboot/kernel panic afterwards.

Seems like the topcase repair messed up something in the SMC controller that prevented the left fan to use the correct RPM.
 
Do you have any more details about this? My issue also seems to be rated to wake and sleep. However, my Mac isn’t turning on anymore, and diagnostics mode did report a potentially failing storage, so it might not be exactly the same issue that’s been reported

I don't know anything more about it personally, but if you run a Google search for "IONVMeController.cpp:5334" you'll be awash with hits, mostly (all?) from the last few months.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.