In Outlook 2010 and previous versions, when making a call to access data in an Outlook store, programmatic calls to access data would result in errors if the data file (.pst or .ost) was corrupt. Developers were thus able to handle the exceptions and continue the execution,
In Outlook 2013, this behaviour changed and Outlook 2013 and newer versions will crash instead of returning an exception when programmatic calls are made to access data in corrupt data files.
The crash here is deliberate and its purpose is to catch store corruptions. Letting the Outlook session continue with a corrupt store, will only lead to other crashes down the line that will be more difficult to track down. Crashing the client when a corrupt store is accessed provides a single point of failure to diagnose the problem.