Have you tried using recover to check your file for damage. Not only can a crash like this be due to a damaged file. But a damaged file might produce the crash that you are reporting here.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- The recovered copy may behave differently even if recover reports "no problems found".
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).
That, at this point is a possibility, but one that is unproven. Wonder if FMDiff would report anything here that Recover was unable to detect?