Outlook 2016 constantly crashes

Anonymous
2017-12-08T22:25:36+00:00

Faulting application name: OUTLOOK.EXE, version: 16.0.8730.2122, time stamp: 0x5a222abb

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000

Exception code: 0xc0000005

Fault offset: 0xfffffffe

Faulting process id: 0x2a34

Faulting application start time: 0x01d37069d095c726

Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE

Faulting module path: unknown

Report Id: a811e1c7-e652-4b0a-938d-9d419d45acfc

Faulting package full name: 

This error is thrown prior to the other:

Faulting application name: SettingSyncHost.exe, version: 10.0.17046.1000, time stamp: 0x98440592

Faulting module name: Windows.Security.Authentication_unloaded, version: 10.0.17046.1000, time stamp: 0xf4a22809

Exception code: 0xc0000005

Fault offset: 0x0000000000012070

Faulting process id: 0x1d38

Faulting application start time: 0x01d37069cb7cf0ca

Faulting application path: C:\WINDOWS\system32\SettingSyncHost.exe

Faulting module path: Windows.Security.Authentication

Report Id: ce26f2b5-ad3f-4a6f-b98f-367b91c7b9f4

Faulting package full name:

Microsoft 365 Insider | Outlook | Windows

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

58 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2017-12-13T21:37:33+00:00

    Sorry I was referring to Windows Insider build number.  I am running Office version 1711 build 8370.2127.

    I am not running and insider build of Office but am experiencing consistent crashing of Office on my current windows build. It is occurring nearly every hour with the same error as the original post. This crash is occurring across Office applications. 

    I reinstalled Office and am still experiencing the same results. 

    Faulting application name: WINWORD.EXE, version: 16.0.8730.2127, time stamp: 0x5a2a2bf5

    Faulting module name: Windows.Security.Authentication_unloaded, version: 10.0.17046.1000, time stamp: 0xf4a22809

    Exception code: 0xc0000005

    Fault offset: 0x0000000000012070

    Faulting process id: 0x59ec

    Faulting application start time: 0x01d3744535315583

    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\WINWORD.EXE

    Faulting application name: lync.exe, version: 16.0.8730.2127, time stamp: 0x5a2a2daf

    Faulting module name: Windows.Security.Authentication_unloaded, version: 10.0.17046.1000, time stamp: 0xf4a22809

    Exception code: 0xc0000005

    Fault offset: 0x0000000000012070

    Faulting process id: 0x5ab4

    Faulting application start time: 0x01d374453720049d

    Faulting application path: C:\Program Files\Microsoft Office\root\Office16\lync.exe

    Faulting module path: Windows.Security.Authentication

    Was this answer helpful?

    0 comments
  2. Anonymous
    2017-12-13T22:00:16+00:00

    Things get confusing when you're running Windows Insider. I'd say post in the Windows Insider forum and see if anyone else is using Windows Insider and the retail version of Outlook. It's possible it's the interaction of Outlook and Windows Insider.

    I don't know how many others on this thread are running Windows Insider as well. Most people don't give that info up front so it takes some time here to find out all the parameters :)

    Are you able to get to File>Support>Contact Support in Outlook? That should connect you with support and the team.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2017-12-13T23:51:07+00:00

    I am running Insider - I would say it is an issue with that Windows build 17046 specifically as that is when it started for me. You will see more feedback in the feedback hub, lots more people reporting the same crash related to Security.Authentication_unloaded there.  

    Would be nice for Office and Windows to work together on this and get a fix going as Office definitely has an issue which a lot of people are seeing.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2017-12-14T00:15:02+00:00

    Hi David,

    Did you post it also in the Windows Insider's forum? I'll pass along the info about Windows Insider to the team as well.

    Thanks

    Was this answer helpful?

    0 comments
  5. Anonymous
    2017-12-14T00:42:08+00:00

    It appears that this is a Windows Insider issue. The person I spoke with said that she thought a Windows Insider fix went out last week.

    Give that a try.

    Was this answer helpful?

    0 comments