Outlook 2013 keep crashing with MSVCR100.dll


Joined
Jan 24, 2017
Messages
4
Reaction score
0
Hello,
I have issue with Outlook 2013 and keep crashing.
(OS Windows 7 x64 / Office 2013 x86)

Error I get in Event log:
Faulting application name: OUTLOOK.EXE, version: 15.0.4569.1503, time stamp: 0x52b0b282
Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e
Exception code: 0xc0000005
Fault offset: 0x0008cc77
Faulting process id: 0x13b4
Faulting application start time: 0x01d276155c7ac8a6
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE
Faulting module path: C:\Windows\system32\MSVCR100.dll
Report Id: 9e4323ac-e208-11e6-8e5e-507b9db8cd12

----

I tried:
- Starting in Safe Mode, start to crush after open an email

- Disable all add-ons(Without 'Microosft VBA for Outlook Addin', I just can not disable it).
- Deleting mail profile and create new one
- Repairing of MS Office via Contron Panel
- Microsoft Office Configuration Analyzer Tool (OffCAT) don`t find errors
- Remove MS office with option 2(https://support.office.com/en-us/ar...rom-a-PC-9dd49b83-264a-477a-8fcc-2fdf5dbf61d8) and install again.

Last installed software was Acrobat Reader DC, and it has Windows update from last month and I update them.

I tried all of this things and still crash.

Word is also crashing but with ntdll.dll(I will start a new topic for it - https://www.office-forums.com/threads/word-2013-keep-crashing-with-ntdll-dll.2349840/). Excel, PowerPoint And Skype for Business are working.
 
Ad

Advertisements

macropod

Microsoft MVP
Joined
Mar 2, 2012
Messages
521
Reaction score
48
This is not actually a Microsoft Office problem; it just happens to occur when you run Outlook (msvcr100.dll) or Word (ntdll.dll). msvcr100.dll is part of the Microsoft Visual C++ libraries, which numerous applications use. ntdll.dll is a core Windows API file. The fact both are causing problems suggests you've recently installed some incompatible software or a faulty update (e.g. for a display/printer driver, etc.). Doing a System Restore to a date before the problem began should resolve the issue.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top