Microsoft Outlook Application Crash due to UCRTBASE.DLL

Anonymous
2020-12-07T17:43:25+00:00

Windows 10 Build 2004

Outlook crashes intermittently and generates the following Application Event Log error.

Event 1000, Application Error (11:06AM, 12/7/2020) Faulting application name: OUTLOOK.EXE, version: 16.0.13426.20308, time stamp: 0x5fc6ea9b Faulting module name: ucrtbase.dll, version: 10.0.19041.546, time stamp: 0x73123758 Exception code: 0xc0000409 Fault offset: 0x0009edbb Faulting process id: 0x41c0 Faulting application start time: 0x01d6ccaedccaa9fa Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\OUTLOOK.EXE Faulting module path: C:\WINDOWS\System32\ucrtbase.dll Report Id: f8791f7b-faf7-452a-8ff2-7268662a6db2 Faulting package full name: Faulting package-relative application ID:

I have run SFC /SCANNOW

I have completely uninstalled and reinstalled Microsoft Office 365

Here are the properties of the failing file:

Windows for home | Windows 10 | Performance and system failures

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

69 answers

Sort by: Most helpful
  1. Anonymous
    2021-01-15T09:15:00+00:00

    Same issues seen here as well, we have maybe 8 users out of 15 that have the issue.  All on latest Windows and Outlook.  Most are using older machines with HDD, but there are a couple that have had a few crashes with SSD.  Rest of the company not really affected and have SSD.

    Also have open ticket with Microsoft but slow going with the usual bits they ask us to try gettign in the way.

    From looking around the internet, there are various other programs with issues in the last few months and the UCRTBASE.dll file.  I can see it was modified on several of our machines in December which conincided with some patches being applied, but not clear which one changed it.

    Crashes outlook mainly when replying to emails, but some have had crashes with outlook just idling.

    Same as other posts, the usual troubleshooting mentioned has been done.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2021-01-15T08:06:44+00:00

    Thanks for your reply.

    If I make any progress, or get any insights in the problem, I will communicate it on this item as well.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2021-01-14T17:12:29+00:00

    Do you have any suggestion about the cause or the solution yet?

    We are experiencing the same issue on many of our workstations since yesterday (Outlook crashes suddenly after typing a few words)

    Restarting Windows, updating Office 365 to the latest version, nothing helps.

    A strange thing is that the problem doesn't occur on ALL of our workstations, despite they're all created from the same image.

    In the Eventlog an Event with EventID 1000 is recorded containing because of the crash:

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

    Faulting module path: C:\WINDOWS\System32\ucrtbase.dll

    But why isn't Outlook not using it's own ucrtbase.dll which is in the same folder as Outlook.exe:

    C:\Program Files (x86)\Microsoft Office\root\Office16\UCRTBASE.DLL

    Does it create a version incompatibility conflict?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2021-01-12T14:11:42+00:00

    Thanks for the reply.  We are noticing the issue generally diminish, but still have problems here and there.  If I come across anything ground-breaking I'll be sure to post here.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2021-01-08T02:34:27+00:00

    We have also been fighting this issue for one client in particular. It comes and goes. 

    I have been using Sysinternals tools to try and narrow it down. Can you tell me what version of Microsoft Distributable C++ 2015-2019 x64 is installed on the troubled workstations?

    14.20.27508.1 is what we have on the bad systems over here. Still havent completely verified it yet, but its a hunch. 

    Thanks!

    Was this answer helpful?

    0 comments No comments