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: Oldest
  1. 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
  2. Anonymous
    2021-01-11T19:14:21+00:00

    I apologize for the delay. I've listed the installed versions from two of our troubled workstations below. Unfortunately, the exact version that you mentioned isn't listed.

    SYSTEM #1

    Microsoft Visual C++ 2005 Redistributable 8.0.61001

    Microsoft Visual C++ 2005 Redistributable 8.0.59193

    Microsoft Visual C++ 2005 Redistributable (x64) 8.0.61000

    Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17

    Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161

    Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.17

    Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.4148

    Microsoft Visual C++ 2008 Redistributable – x86 9.0.30729.6161

    Microsoft Visual C++ 2010 x64 Redistributable – 10.0.40219

    Microsoft Visual C++ 2010 x86 Redistributable – 10.0.40219

    Microsoft Visual C++ 2012 Redistributable (x64) – 11.0.50727

    Microsoft Visual C++ 2012 Redistributable (x64) – 11.0.61030

    Microsoft Visual C++ 2012 Redistributable (x86) – 11.0.50727

    Microsoft Visual C++ 2012 Redistributable (x86) – 11.0.61030

    Microsoft Visual C++ 2013 Redistributable (x64) – 12.0.30501

    Microsoft Visual C++ 2013 Redistributable (x86) – 12.0.30501

    Microsoft Visual C++ 2015 Redistributable (x64) – 14.0.24123

    Microsoft Visual C++ 2015 Redistributable (x86) – 14.0.24123

    SYSTEM #2

    Microsoft Visual C++ 2010 x86 Redistributable – 10.0.40219

    Microsoft Visual C++ 2012 Redistributable (x86) – 11.0.60610

    Microsoft Visual C++ 2013 Redistributable (x86) – 12.0.30501

    Microsoft Visual C++ 2015 Redistributable (x86) – 14.0.23026

    Last week, I went so far as to reformat one troubled system and recreate the local profile on another (i.e., straw grasping exercise). Surprisingly, the reformatted PC is worse than before and the jury is still out on the other, but I don't hold out much hope due to the results of the former.

    I, too, am coming to a similar conclusion. The DLL (ucrtbase.dll) is part of the Microsoft Visual C++ redistributable, so it's just a matter of determining if its an update to that causing issues and/or an update to Office 2016 and/or Windows that isn't jiving well.

    Thank you.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. 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
  4. 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
  5. Anonymous
    2021-01-14T18:16:30+00:00

    The only consistency we've been able to nail down is that the faulting module is always that DLL, which is a software component of Microsoft Visual C++. The rest has truly been a head scratcher because it only affects a subset of our users, Office and Windows versions seemingly do not matter, and we have honestly tried just about every Google solution out there:

    • Outlook in Safe Mode
    • Roll back Office to known working version
    • Roll back Windows to known working version
    • Deployment Image Servicing and Management (DISM)
    • System File Checker (SFC)
    • Disable hardware acceleration
    • Recreate Outlook OST file
    • Recreate Outlook profile
    • Recreate Windows profile
    • Reformat computer

    We finally bit the bullet and reached out to Microsoft and are actively working with them. Depending on the results there, I will make sure to update everyone here and all of the other message boards I've posted on.

    Thank you.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments