Outlook Crashes Shortly After Starting

Anonymous
2021-05-25T00:04:58+00:00

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

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

84 answers

Sort by: Most helpful
  1. Anonymous
    2021-06-08T15:14:01+00:00

    THIS:

    MAC OS 10.13.6 - Can't upgrade any further, machine doesn't support it

    Outlook 16.43.0.201108 - I have also tried to uninstall and run older versions

    Has anyone made any contact to anyone else besides Qian, is he able to help us?

    Simply put, something happened to Outlook and it won't run, we can't upgrade Outlook or Mac OS any further due to the hardware. Everything was working, then Outlook just started blowing up.

    Essentially microsoft office 365 has become subscription ransomware

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2021-06-03T19:25:32+00:00

    No mate.

    16.47 requires 10.14. I have 22 Macs on 10.13.6.

    Can't update the OS. Need it fixed on 10.13.6.

    On your spec page Office 2016 is specced to run on 10.10.x and above.

    Please fix it. We're paying a FORTUNE for this per month. People are working remotely it's a pain to have to fix them all.

    You need to fix it. Meaning Microsoft.

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2021-06-03T15:12:08+00:00

    I am in a similar situation running 10.13.6 and therefore saying "use the web version of outlook" is not a fully viable solution.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2021-05-28T10:57:19+00:00

    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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2021-05-27T23:26:32+00:00

    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

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments