求助，本人win7 64位系统，突然不能打开outlook 2010/2013 ,重装了32位和64位的office 2010/2013,都不行，最后装了office 2007才可以使用，到现在也不知道为什么，求助啊。
其中一个log
Two are three times a week Outlook crashes when sending email with the following error
Log Name: Application
Source: Application Error
Date: 15/01/2015 10:00:58
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ********.***.local
Description:
Faulting application name: OUTLOOK.EXE, version: 15.0.4667.1000, time stamp: 0x543d3698
Faulting module name: mso.dll, version: 15.0.4675.1002, time stamp: 0x5474349b
Exception code: 0xc0000602
Fault offset: 0x011b1687
Faulting process id: 0x11dc
Faulting application start time: 0x01d030a6e4aa1ee7
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE
Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll
Report Id: 66ad29a2-9c9d-11e4-b53c-082e5f1727fc
Event Xml:
<Event xmlns
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2015-01-15T10:00:58.000000000Z" />
<EventRecordID>10015</EventRecordID>
<Channel>Application</Channel>
<Computer>Events-HP8200.ICI.local</Computer>
<Security />
</System>
<EventData>
<Data>OUTLOOK.EXE</Data>
<Data>15.0.4667.1000</Data>
<Data>543d3698</Data>
<Data>mso.dll</Data>
<Data>15.0.4675.1002</Data>
<Data>5474349b</Data>
<Data>c0000602</Data>
<Data>011b1687</Data>
<Data>11dc</Data>
<Data>01d030a6e4aa1ee7</Data>
<Data>C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE</Data>
<Data>C:\Program Files (x86)\Common Files\Microsoft Shared\Office15\mso.dll</Data>
<Data>66ad29a2-9c9d-11e4-b53c-082e5f1727fc</Data>
</EventData>
</Event>
Any clues on a fix?
Answers
Question
Sign in to vote
0
Sign in to vote
Hi,
Thanks for your question.
This issue might occurs due to lots of reasons. Do you have a virus scanner installed which integrates itself with Outlook? If yes, please try to disable it, and then try again. You might opt to uninstall the virus scanner temporarily to make sure it will not interfere the testing.
Also, lots of Office crash issues are caused by third-party add-ins. You might want to have a check and see if you have any integrated with your Outlook client which might cause the issue.
Since the issue occurs randomly ("Two are three times a week"), Office Safe Mode will not be effective here, just manually disable all third-party add-ins in Outlook FILE>Options>Ass-Ins, use outlook for a period of time, then verify result.
Regards,
Ethan Hua
TechNet Community Support
It‘s recommended to download and install Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office programs.
Edited by Ethan HuaMicrosoft contingent staff, Moderator Wednesday, January 21, 2015 8:24 AM
Proposed as answer by Ethan HuaMicrosoft contingent staff, Moderator Monday, February 02, 2015 2:15 AM
Marked as answer by Ethan HuaMicrosoft contingent staff, Moderator Tuesday, February 03, 2015 2:09 AM
I was not able to identify a root cause unfortunately. I thought it might‘ve been related to a Windows update(s) done back in November as that is when the issue started, but even after rolling back all the Windows updates, the user still had the issue.
A strange thing did fix the issue for another user (I‘ve jinxed it now). I uninstalled the 32bit version of Office using the uninstall Microsoft Fixit (they were running on 64bit Windows 7 Pro), installed the 64bit version, and then uninstalled the 64bit version and reinstalled the 32bit. Since then (about 2 months now) they haven‘t reported the issue, and checking their Event Viewer, I confirmed the computer isn‘t logging the error anymore.
It is quite strange because I had already done complete uninstalls and reinstalls of the 32bit Office for users having this issue with no luck, but after having the 64bit version installed and then going back to 32bit the issue stopped.
Marked as answer by tsi.james Monday, December 0
1, 2014 6:12 PM