Why is Outlook on my Mac suddenly crashing consistently?

Anonymous
2024-03-19T22:22:31+00:00

I have been trying to open Outlook on my MacBook Pro all day, and it has consistently crashed. I was just using Outlook last night and had not made any changes to apps or settings since trying to open Outlook this morning. MacBook is running Sonoma 14.3.1. Never any issues until now. Consistent error messages....even after uninstalling and re-installing...per Microsoft support which was not very helpful.

Below is the most recent message I received (minus hundreds of lines due to character limits).

Microsoft Error Reporting log version: 2.0

Error Signature:

Exception: EXC_CRASH (SIGTRAP)

ExceptionEnumString: 50331648

Exception Code: 0x00000001 (0x0000000000000000)

Date/Time: 2024-03-19 22:11:55 +0000

Application Name: Microsoft Outlook

Application Bundle ID: com.microsoft.Outlook

Application Signature: OPIM

Application Bitness: x64

Application Version: 16.83.1.24031813

Crashed Module Name: merp

Crashed Module Version: 16.83.24031813

Crashed Module Offset: 0x000000000000559c

Blame Module Name: Microsoft Outlook

Blame Module Version: 16.83.24031813

UnsymbolicatedChecksum: DCA9BCB06082872F879C6092737B3813

Blame Module Offset: 0x0000000000034334

StackHash: 3334bf3e6cfb5dc_50331648_main_phx_arm

Application LCID: 1033

Extra app info: Reg=en Loc=0x0409

Build Type: Release

Crashed thread Stack Pointer: 0x_000000016afdd9d0

Crashed thread: 0

uncaught ObjC exception, reason: The window has been marked as needing another Update Constraints in Window pass, but it has already had more Update Constraints in Window passes than there are views in the window.

<OLToolbarValidatingWindow: 0x12505d640> 0x282 (642) {{0, 89}, {1696, 990}} en

OS Information

Operating System: Mac OS X 14.3.1 (Build 23D60)

CPU: ARM64e, Logical CPU Count: 12

Physical Memory: 16384 MB

Device_model: Mac14,10

Screen: 1728.000000 x 1117.000000, bitsPerPixel = 24, frame = 0.000000, 0.000000, 1728.000000, 1117.000000

CrashedApp_Virtual_Memory_Size_MB: 406330.625000

CrashedApp_Resident_Memory_Size_MB: 456.703125

CrashedApp_Memory_Footprint_MB: 158.661926

ErrorReportingDeviceUUID: 483A116B-B39F-5CBD-82C1-D981E3B9C0DA

ErrorReportingUUID: 44C40BF0-BDD8-402C-A229-42DB172A9594

ULS UUID: EA80B636-3297-4FFC-A9B9-B49947795BF0

CrashedLogSessionId: EA80B636-3297-4FFC-A9B9-B49947795BF0

TimeFromLaunch: 0 hours, 0 minutes, 5 seconds

CrashedSessionDuration: 5

Total errors on this client: 210

Microsoft Application Information:

SHSuffixKey_1: _arm

AudienceChannel: CC

Audience: Production

SHSuffixKey_0: _phx

PreviewEnabled: true

AudienceGroup: Production

Outlook | MacOS | Legacy Outlook for Mac | For business

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

44 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-04-19T12:42:26+00:00

    I've finally found a workaround that works for me. NOTIFICATIONS. Specifically, Notifications in Apple's System Settings.

    Do these steps:

    BEFORE you launch Microsoft Outlook, go to your Mac's System Settings, click on Notifications, scroll down to Microsoft Outlook, turn off "Allow notifications" by setting the top right button to the off position, quit System Settings, launch Microsoft Outlook (it should now open without a problem), go back to your Mac's System Settings, click on Notifications, scroll down to Microsoft Outlook, turn on "Allow notifications" by setting the top right button to the on position, then quit System Settings. You'll have to do these steps EVERY TIME you want to launch Outlook. (Or, if you don't need the Mac to alert you when you get notifications, you could just leave the "Allow notifications" off, and not have to worry about going into System Settings and doing these steps every day.)

    Over the last few days, I've done these steps on both of my M1 MacBook Pros in my office that have this issue, and it's been a successful workaround.

    Like many others on this thread, my problem started on or around March 19, so Microsoft did something on that day, or an Apple Sonoma update broke some Microsoft programming. And, it's seemingly got something to do with Notifications at the system level.

    So, Microsoft (or Apple) needs to figure out a fix.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-04-09T10:24:09+00:00

    After a week of normal, it started crashing again. Help -> Contact Support is actively helping (again) but it's like they've never seen the problem before. Lots of requests for error reports, screen recording of the crashing, and efforts to identify plug-ins etc. Not convinced this is going somewhere...

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-04-09T08:59:26+00:00

    Had this problem for a couple of weeks and suddenly it started working again. Sadly, no idea why. Sharing this news in case it brings some hope that this too shall pass (maybe).

    Yup, same here. Except mine went back to crashing. So I reverted to Legacy mode until Microsoft can fix this thing

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-04-05T19:32:33+00:00

    Same problem here. I reinstalled 3 or 4 times and it still doesn't work.

    And when I switch to Legacy, I lose all the emails that are on the computer and only get whatever is on the server (I use POP for a variety of reasons).

    Very frustrating!

    Was this answer helpful?

    0 comments
  5. Anonymous
    2024-04-05T19:24:45+00:00

    But you are right! Now my Outlook works just normally... I guess it will not stay like that 🥴

    Was this answer helpful?

    0 comments