Outlook for Mac keeps crashing - what's the fix please?

Anonymous
2023-10-31T08:43:53+00:00

Hi

I am using Outlook (latest version) on a Macbook Air running Monterey (latest version - 12.7.1). 
ie all software is up to date.



Outlook keeps unexpectedly closing/crashing, for no apparent reason.  --

-- Below are two examples of the first part of the kind of error message it gives me, from two Microsoft Error Reports.

 (It is too many characters to be able to paste one errror message in full!). They then go on to list various Threads and Thread States?

Please could someone help? I'm afraid I am not at all technical! Many thanks. 
 :)

Microsoft Error Reporting log version: 2.0

Error Signature:

Exception: EXC_BAD_ACCESS

ExceptionEnumString: 1

Exception Code: KERN_INVALID_ADDRESS (0x0000000000000000)

Date/Time: 2023-10-30 16:24:33 +0000

Application Name: Microsoft Outlook

Application Bundle ID: com.microsoft.Outlook

Application Signature: OPIM

Application Bitness: x64

Application Version: 16.78.2.23102103

Crashed Module Name: HxCore

Crashed Module Version: 16.0.16910.33813

Crashed Module Offset: 0x000000000076beb7

Blame Module Name: HxCore

Blame Module Version: 16.0.16910.33813

UnsymbolicatedChecksum: A1CD7A2C2CC0ABC6AFB4B546C7F38348

Blame Module Offset: 0x000000000076beb7

StackHash: 78c1a9eedb24ad6f_1_bk_oom_phx

Application LCID: 2057

Extra app info: Reg=en Loc=0x0809

Build Type: Release

Crashed thread Stack Pointer: 0x_0000700001d308b0

Crashed thread: 6

Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
ExceptionEnumString: 1
Exception Code: KERN_INVALID_ADDRESS (0x0000000000000000)
Date/Time: 2023-10-31 08:55:15 +0000
Application Name: Microsoft Outlook
Application Bundle ID: com.microsoft.Outlook
Application Signature: OPIM
Application Bitness: x64
Application Version: 16.78.2.23102103
Crashed Module Name: HxCore
Crashed Module Version: 16.0.16910.33813
Crashed Module Offset: 0x000000000076beb7
Blame Module Name: HxCore
Blame Module Version: 16.0.16910.33813
UnsymbolicatedChecksum: A1CD7A2C2CC0ABC6AFB4B546C7F38348
Blame Module Offset: 0x000000000076beb7
StackHash: 78c1a9eedb24ad6f_1_bk_oom_phx
Application LCID: 2057
Extra app info: Reg=en Loc=0x0809
Build Type: Release
Crashed thread Stack Pointer: 0x_0000700005dc18b0
Crashed thread: 8

Outlook | MacOS | Legacy Outlook for Mac | For home

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2023-10-31T11:13:17+00:00

Hello AndreaM1971,

Thank you for posting to Microsoft Community.

I understand that you have an issue where the Outlook app for Mac is crashing on startup. My apologies for the inconvenience that this is causing you.

Based on the error description, could you kindly try setting up your account in a new Outlook profile and see if issue persists: For reference: Manage profiles or identities in Outlook for Mac - Microsoft Support (Do not delete the current profile as yet to prevent any data loss).

If the issue persists, you may have to uninstall and re-install the outlook app. Please refer to steps below. (Please backup the outlook folders before moving to trash).

  • In Finder >go to the Applications folder
  • Drag/Move the Microsoft Outlook app to the trash.
  • Restart your Mac.
  • Run this installer to reinstall Microsoft Outlook Install package.

Looking forward to your response.

Sincerely,

Ashraf.

Was this answer helpful?

10+ people found this answer helpful.
0 comments No comments

45 additional answers

Sort by: Most helpful
  1. Anonymous
    2024-03-05T00:59:20+00:00

    I am having the EXACT same issue - crashing when launching outlook on macbook running Sonoma 14.3.1

    just started happening today - March 4, 2024.

    i have tried all the suggestions and no luck.

    please help as this is VERY frustrating.

    thanks

    ~A

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2024-02-20T16:07:39+00:00

    On the Mac, run terminal and enter this command to disable new Outlook on Mac.

    defaults write com.microsoft.Outlook EnableNewOutlook -int 0

    Open Outlook and it will be the old version which works fine.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2023-12-22T18:57:19+00:00

    Hello Ashraf,

    I am running Mac OS Sonoma and Outlook keeps crashing.

    It barely starts up and closes.

    It shows the same Error report.

    I tried all of your suggestions but it did not help.

    Do you have a solution for it ?

    Thanks

    Carlos

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2023-11-14T22:17:21+00:00

    Same here..
    This was often the case in the past. Then it was better.

    With the new version it's really bad now.

    Outlook crashes every few minutes.. working is hardly possible anymore

    Microsoft Error Reporting log version: 2.0

    Error Signature:

    Exception: EXC_BAD_ACCESS

    ExceptionEnumString: 1

    Exception Code: KERN_INVALID_ADDRESS (0x0000000000000078)

    Date/Time: 2023-11-14 22:14:04 +0000

    Application Name: Microsoft Outlook

    Application Bundle ID: com.microsoft.Outlook

    Application Signature: OPIM

    Application Bitness: x64

    Application Version: 16.78.3.23102801

    Crashed Module Name: libboringssl.dylib

    Crashed Module Version: unknown version

    Crashed Module Offset: 0x0000000000002eb4

    Blame Module Name: unknown

    Blame Module Version: 16.78.3.231028

    UnsymbolicatedChecksum: 20A09A95CBC1A07EDB2757413F218274

    Blame Module Offset: unknown

    StackHash: 4106ff87aff7f6be_1_0x0000000000002eb4_bk_phx_arm

    Application LCID: 1031

    Extra app info: Reg=en Loc=0x0407

    Build Type: Release

    Crashed thread Stack Pointer: 0x_000000016f54e3a0

    Crashed thread: 23

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments