Regular MBP crashes pointing to EXC_BAD_ACCESS (Code Signature Invalid) with amfid and airportd processes

Question

Level 1

7 points

Regular MBP crashes pointing to EXC_BAD_ACCESS (Code Signature Invalid) with amfid and airportd processes

My wife has a 2014 MacBook Pro (non-Retina), which is on the latest version of Catalina (Big Sur won't work on an MBP of this age). All is fine but it's regularly crashing.

I have the crash reports - it looks as if 2 crashes are occurring at the same time.

First of all, the process amfid crashes, followed (pretty simultaneously) with airportd. amfid appears to crash first but sometimes it's just airportd, which is what makes me think that may be behind it.

Here's some of the crash data - I'm hoping someone can throw some more light on this (let me know if you need any more of the crash relkrt content).

Process:               airportd [592]
Path:                  /usr/libexec/airportd
Identifier:            airportd
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
Responsible:           airportd [592]
User ID:               0

Crashed Thread:        Unknown
 
Exception Type:        EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes:       0x0000000000000032, 0x00007fffe0088138
Exception Note:        EXC_CORPSE_NOTIFY
 
Termination Reason:    Namespace CODESIGNING, Code 0x2

Process:               amfid [589]
Path:                  /usr/libexec/amfid
Identifier:            amfid
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
Responsible:           amfid [589]
User ID:               0

Crashed Thread:        Unknown
 
Exception Type:        EXC_BAD_ACCESS (Code Signature Invalid)
Exception Codes:       0x0000000000000032, 0x00007fffe0088c8c
Exception Note:        EXC_CORPSE_NOTIFY
 
Termination Reason:    Namespace CODESIGNING, Code 0x2

MacBook Pro

Posted on Jan 25, 2021 5:41 AM

Reply

Answer 1

jeremy_v

Community Specialist

Jan 27, 2021 8:12 AM in response to dartiss

Hey there dartiss,

We understand you have a MacBook Pro that is experiencing kernel panics. We'll be happy to help.

The best troubleshooting steps for issues like this can be found here: If your Mac restarted because of a problem

This article will guide you through a few things like checking hardware, testing in safe mode, and reinstalling the OS.

In addition to those steps, we'd also like to recommend creating a new test user account to see if the issue happens there. This will let us know if the issue is system-wide or isolated to one account. Reference this page: Set up users, guests, and groups on Mac

Let us know how that goes or if you have any questions.

Reply

Answer 2

dartiss Author

Level 1

7 points

Jan 27, 2021 8:28 AM in response to jeremy_v

Thanks Jeremy.

The laptops SSD failed last week and I had to switch it out and rebuild the OS from scratch. The crashes were occurring before this happened (for about the previous 6 months but it's now occurring more often). So, I think some of those troubleshooting steps can be crossed off.

In fact, looking down that article you linked to (thank you!), I can eliminate all of those too. Right now, it's pretty much just the basics installed and just WiFi switched on (BT off) and no additional hardware connected. As it's a rebuild (from total scratch) it's a new user. Is the new SSD not compatible? The one I've put is the original Apple SSD (I upgraded it years ago as it was too small for my usage but, now my wife is using it, that's no longer an issue).

Right now, I'm stuck. Although getting a little old now, it's in great condition and everything seems to work bar these annoying and persistent crashes. She's a teacher having to do home-learning, so having it crash regularly in the middle of video calls with students is not... great.

Any further suggestions will be appreciated.

Reply

Regular MBP crashes pointing to EXC_BAD_ACCESS (Code Signature Invalid) with amfid and airportd processes

Similar questions