Jamf-Connect Related Crash?

New Contributor

Hi there,

Trying to investigate an issue with our intel MacBooks all of a sudden crashing lately, the fans will go off like crazy and then freeze, machine then reboots- this has happened on 3 separate occasions to one end user- the log file shows

Not sure if Jamf-Connect has anything to do with it? I've attached the log file below.

Any assistance is appreciated! 


Process:               SecurityAgentHelper-x86_64 [411]
Path:                  /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle/Contents/XPCServices/SecurityAgentHelper-x86_64.xpc/Contents/MacOS/SecurityAgentHelper-x86_64
Identifier:            com.apple.SecurityAgentHelper.x86_64
Version:               1.0 (1)
Build Info:            SecurityAgentHelper-55467140002000000~1
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
Responsible:           SecurityAgent [404]
User ID:               92

PlugIn Path:             /Library/Security/SecurityAgentPlugins/JamfConnectLogin.bundle/Contents/MacOS/JamfConnectLogin
PlugIn Identifier:       com.jamf.connect.login
PlugIn Version:          2.6.0 (2)

Date/Time:             2022-07-20 14:27:28.773 -0400
OS Version:            macOS 11.6.6 (20G624)
Report Version:        12
Bridge OS Version:     6.5 (19P5071)
Anonymous UUID:        43EE2845-3C36-4BE5-BA08-FC796F6531A7

Time Awake Since Boot: 17 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000525252522d48
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [411]