Outlook 2013 mail/cal item crash

Question

Hello, hope someone can help.
We have recently updated our standard Outlook mail accounts to Exchange. With the change my outlook has been upgraded from 2010 to 2013.
Anyway, after a great deal of kafuffle in configuring exchange, downloading clients, uninstalling, installing and re-installing I finally have Outlooks 2013 booting up in to safe mode. I should point out that I'm running on a 64bit Windows 7 OS, with 32bit
office 2010 and now 32bit Outlook 2013 - I realise this to be far from perfect but it's all I've got!
Now I can boot into safe mode just fine, but opening up a mail item, creating new mail, opening or creating new calendar items all crash Outlook. After going through many help articles on the MS sites and forums, this lead me to believe it was a problem
with the reading pane and/or an add-on. I have since removed ALL add-ons with the exception of "Microsoft VBA for Outlook Add in" which isn't able to be disabled.
I have also noted that in the "Customise ribbon" menu there are no options in the drop-downs, and resetting all ribbon customisations gives the same crash.
Instead of posting a ream of error reports and the like, I thought I’d just post the highlights of my day so far:
This one is the most common: Faulting module name: MSVCR100.dll, version: 10.0.40219.325, time stamp: 0x4df2be1e
This is often paired with the following highlights in another log entry:
Fault bucket , type 0 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: OUTLOOK.EXE P2: 15.0.4551.1004 P3: 5253ad6f P4: wwlib.dll P5: 15.0.4517.1505 P6: 51bfe546 P7: c0000005 P8: 00010b92
The .wer file it created contains:
Version=1
EventType=APPCRASH
EventTime=130329718195521589
ReportType=2
Consent=1
UploadTime=130329718196411640
ReportIdentifier=6a5ce541-7223-11e3-9938-e02a820394a2
IntegratorReportIdentifier=6a5ce540-7223-11e3-9938-e02a820394a2
WOW64=1
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=OUTLOOK.EXE
Sig[1].Name=Application Version
Sig[1].Value=15.0.4551.1004
Sig[2].Name=Application Timestamp
Sig[2].Value=5253ad6f
Sig[3].Name=Fault Module Name
Sig[3].Value=wwlib.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=15.0.4517.1505
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=51bfe546
Sig[6].Name=Exception Code
Sig[6].Value=c0000005
Sig[7].Name=Exception Offset
Sig[7].Value=00010b92
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.48
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=2057
...add in a whole heap of loaded module lines...
LoadedModule[151]=C:\windows\system32\DSROLE.DLL
LoadedModule[152]=C:\Program Files (x86)\Microsoft Office\Office15\outlph.dll
LoadedModule[153]=C:\windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[154]=C:\windows\system32\tquery.dll
LoadedModule[155]=C:\windows\System32\StructuredQuery.dll
LoadedModule[156]=C:\windows\system32\hlink.dll
LoadedModule[157]=C:\Program Files (x86)\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[158]=C:\windows\system32\apphelp.dll
Sec[0].Key=LCID
Sec[0].Value=1033
Sec[1].Key=skulcid
Sec[1].Value=1033
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Outlook
AppPath=C:\Program Files (x86)\Microsoft Office\Office15\OUTLOOK.EXE
Some of the things I have attempted have been removing .pst and .ost files. Starting with blank files, starting with no files at all and spoofing a user account just to get an empty outlook. I've used MsConfig in safe mode, stopping system services and add
ins. I'm convinced it's something to do with the ribbon but seeing as I've ran out of ideas and solutions to try, I thought I would seek some help.
Many thanks for you time in looking at this.

Answer 1

Hi,
You mentioned you have tried rebooting in Safe Mode. Please note there is a little difference between
Safe Mode and Clean Boot.
Basically, the purpose of Clean Boot is mainly to troubleshoot software compatibility issues. To perform clean-boot troubleshooting, you must take a number of actions, and then restart the computer after each action.
This article below explains more information about Clean Boot:
http://www.thewindowsclub.com/what-is-clean-boot-state-in-windows
So here I suggest we perform a clean boot to troubleshoot this issue. Hope this can find out the issue cause.
Regards,
Melon Chen
TechNet Community Support