A crash can damage a database file, BUT a damaged file can crash so it may be that your file was damaged before you tried to export data from it.
I suggest taking a back up copy made prior to this crash (if you have one) and running a recover on it to check it for possible damage. If it turns out to be damaged and you have multiple backups taken at different times (as should be the case for all database files), you may need to recover older and older back up copies until you find one that recovers "clean".
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).