Outlook Crashes Shortly After Starting

I've been running the Office aps for quite a while, and this just started happening. Shortly after I ope Outlook, I get a message saying "There was a problem with Microsoft Office and your recent work might be lost." I have tried restrating the computer and also re-installing Office. I'm running OS 10.13.6 (the latest version that my old computer will support).


The first part of the error report is:


Microsoft Error Reporting log version: 2.0

Error Signature:
Exception: EXC_BAD_ACCESS
ExceptionEnumString: 1
Exception Code: KERN_INVALID_ADDRESS (0x0000000000000000)
Date/Time: 2021-05-24 23:53:33 +0000
Application Name: Microsoft Outlook
Application Bundle ID: com.microsoft.Outlook
Application Signature: OPIM
Application Bitness: x64
Application Version: 16.43.0.20110804
Crashed Module Name: OutlookCore
Crashed Module Version: 16.43.0.201108
Crashed Module Offset: 0x000000000014710a
Blame Module Name: OutlookCore
Blame Module Version: 16.43.0.201108
UnsymbolicatedChecksum: 8BC5BFFD2940F64C6085EBDA9FE093A3
Blame Module Offset: 0x000000000014710a
StackHash: 4f401b8c62430da7-dm_1_bk
Application LCID: 1033
Extra app info: Reg=en Loc=0x0409
Build Type: Release
Crashed thread Stack Pointer: 0x_00007000017516c0
Crashed thread: 2


* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

Hi GlenEffertz,

Thank you for choosing Microsoft community.

Please make sure your Outlook for Mac has been updated to the latest version. See Update history for Office 2016 for Mac - Office release notes | Microsoft Docs.

If it's already the latest update, create an Outlook for Mac identity to check if it helps. See Manage profiles or identities in Outlook for Mac - Office Support (microsoft.com).

If the above methods don't help, you may consider using the Outlook Reset Preferences tool to reset all Outlook preferences to their default settings. See OutlookResetPreferences.

You may also contact the dedicated in-app support team. This team has richer experience with Outlook for Mac issues. To do so, click Help > Contact Support to communicate with the engineers there directly.

Hope it helps! If any update, welcome to share with us.

Thanks & Stay safe,

Qian

---------------------------
* Beware of scammers posting fake support numbers here.
* We are happy and always here to help you, and share the Microsoft 365 for business online information with you.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I am running the latest version of Office 2016. I tried creating a new identity, then resetting preferences. Neither helped. Outlook doesn't stay open long enough for me to click Help. Is there another way to contact the support tem?

Thanks,

Glen

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I am experiencing this same issue at work as of 5/27/2021. Multiple people started reporting this issue a few days ago. Here are some facts I have gathered. Are there any solutions?

This is happening to users on Macintosh computers only, with these specs:

  • Mac OS 10.13.6

  • Outlook Version 16.43.20110804

 

Other facts:

  • It is not happening to everyone with those computer specs, only some of our users

  • Users with issues have various sizes of mailboxes, anywhere from 1GB to 40GB

  • Users with issues have various size inboxes, from 200 items up to 40,000 items

  • Users with issues are from various departments within the company, nothing really in common

  • Word, Excel, Teams, etc, all appear to be running fine

  • If we setup a new computer with OS 10.15.x and the latest/newest version of outlook, the issue does not reoccur

  • If we setup the user on a PC with Outlook, the issue does not reoccur

6 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I've tested the same user account with OSX 10.15.7 and Outlook 16.42 and the same issue happens. (with 16.49.20101102 the error is solved) There is no really a clear explanation for what to look for in the logs.

So for me its obvious, that Microsoft did change something in Office365 which makes the latest Version of Outlook on OSX 10.13.6 crash and becoming useless now. MICROSOFT PLEASE UNDO THIS! Thanks.

Microsoft Error Reporting log version: 2.0

Error Signature:

Exception: EXC_BAD_ACCESS

ExceptionEnumString: 1

Exception Code: KERN_INVALID_ADDRESS (0x0000000000000000)

Date/Time: 2021-05-27 17:55:44 +0000

Application Name: Microsoft Outlook

Application Bundle ID: com.microsoft.Outlook

Application Signature: OPIM

Application Bitness: x64

Application Version: 16.43.0.20110804

Crashed Module Name: OutlookCore

Crashed Module Version: 16.43.0.201108

Crashed Module Offset: 0x000000000014710a

Blame Module Name: OutlookCore

Blame Module Version: 16.43.0.201108

UnsymbolicatedChecksum: 8BC5BFFD2940F64C6085EBDA9FE093A3

Blame Module Offset: 0x000000000014710a

StackHash: 4f401b8c62430da7-dm_1_bk_oom

Application LCID: 1031

Extra app info: Reg=en Loc=0x0407

Build Type: Release

Crashed thread Stack Pointer: 0x_00007000082646c0

Crashed thread: 11

Last ObjC Exception Reason (may or may not be related to crash): -[NSOpenGLPixelFormat initWithAttributes:] failed in CGLChoosePixelFormat due to error 10002 (invalid pixel format)

Microsoft Error Reporting log version: 2.0

Error Signature:

Exception: EXC_BAD_ACCESS

ExceptionEnumString: 1

Exception Code: KERN_INVALID_ADDRESS (0x0000000000000000)

Date/Time: 2021-05-26 11:46:05 +0000

Application Name: Microsoft Outlook

Application Bundle ID: com.microsoft.Outlook

Application Signature: OPIM

Application Bitness: x64

Application Version: 16.43.0.20110804

Crashed Module Name: OutlookCore

Crashed Module Version: 16.43.0.201108

Crashed Module Offset: 0x000000000014710a

Blame Module Name: OutlookCore

Blame Module Version: 16.43.0.201108

UnsymbolicatedChecksum: 8BC5BFFD2940F64C6085EBDA9FE093A3

Blame Module Offset: 0x000000000014710a

StackHash: 4f401b8c62430da7-dm_1_bk

Application LCID: 1031

Extra app info: Reg=en Loc=0x0407

Build Type: Release

Crashed thread Stack Pointer: 0x_000070000551c6c0

Crashed thread: 14

5 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I've 2 Macs: one with the latest version of every thing and an old iMac (iMac 27-inch, Mid 2010) with old versions (MacOS 10.13.6 and Outlook 16.43.20110804). They are both behaving the same which suggests it is a back end change made by Microsoft on Tuesday.

I've kept on pressing auto-restart so Microsoft should have lots of logs to analyse. It is different threads that crash and it does make some progress with each run but doesn't stay up long enough to compose and email.

1 person found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I've 2 Macs: one with the latest version of every thing and an old iMac (iMac 27-inch, Mid 2010) with old versions (MacOS 10.13.6 and Outlook 16.43.20110804). They are both behaving the same which suggests it is a back end change made by Microsoft on Monday or Tuesday (AST) so maybe Sunday on Monday US time.

I've kept on pressing auto-restart so Microsoft should have lots of logs to analyse. It is different threads that crashes each time and it does make some progress with each run but doesn't stay up long enough to compose an email. This make it not fit for purpose and in breach of Australian consumer law.

Please fix this ASAP

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

@Peter-Aus:

You can get the logs if you disconnect the iMac from the Internet. Then Outlook should be able to start normally. Then you can enable the logging mechansim by going to Window menu -> Sync Errors -> Gear icon -> "Turn on logging for troubleshooting". After the enhanced logging mechanism is enabled you can reconnect your iMac to the internet and get the logs. This way you can send the enhanced logs to the microsoft support team.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Hi everyone,

We have the same issue here, about 8 users impacted. We are on Sierra for most users and can't upgrade yet.

Outlook crashes if connected to internet, if the computer is offline, outlook runs fine, so it seems that the crashes occurs during the synchronisation process.

Any help would be appreciated, Microsoft support didn't helped at all (Sierra is "too old" for support).

I can provide logs or anything relevant.

2 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

The problem is related to an appointment the user was invited to and is in his/her calendar.

It might be also related to renaming some items inside the recurring calendar group. At some point it disconnects from the recurrency-group. But I wasn’t able to figure out how to reproduce the error.

If you are able to identify which calendar entry it is and delete it, then outlook shouldn't crash anymore.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

I tried deleting the few future entries in my calendar, and also some past ones, but still no luck.

I also disconnected shared calendars without success.

This is driving me crazy!

3 people found this reply helpful

·

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

* Please try a lower page number.

* Please enter only numbers.

* Please try a lower page number.

* Please enter only numbers.

 
 

Question Info


Last updated March 12, 2024 Views 4,833 Applies to: