Only FMI can read the content of the DMP files so you have to open a support ticket with them to see what they can make of it.
Sounds like you are re-using the recovered file; that's usually not a good idea. You can save yourself a lot of future grief (and time too) by using a backup instead of recovering the file.
What is in the Windows application event log leading up to the FMS crash? There is usually a clue there.
What is the FMI?
I recover the file and than make a copy of the file to start using it.
Bellow, the message from Windows:
Stopped responding and was closed
A problem caused this program to stop interacting with Windows.
Faulting Application Path: C:\Program Files\FileMaker\FileMaker Pro 15\FileMaker Pro.exe
Problem Event Name: AppHangB1
Application Name: FileMaker Pro.exe
Application Version: 126.96.36.199
Application Timestamp: 5706f6ea
Hang Signature: 0000
Hang Type: 134217984
OS Version: 6.3.9600.2.0.0.272.7
Locale ID: 1046
Additional Hang Signature 1: 00000000000000000000000000000000
Additional Hang Signature 2: 0000
Additional Hang Signature 3: 00000000000000000000000000000000
Additional Hang Signature 4: 0000
Additional Hang Signature 5: 00000000000000000000000000000000
Additional Hang Signature 6: 0000
Additional Hang Signature 7: 00000000000000000000000000000000
Extra information about the problem
Bucket ID: 25042ff06d0afa52527eb313a91d2dbe (129098329808)
FMI = FileMaker Inc
So you are not using FileMaker Server, but FileMaker Pro to host the file.
Copying the file after the recovery doesn't really help, if the file is 'sick' then recovery can help but it is an iffy process.
You may be better served by using FileMaker Server to host your file, that's going to be a bit more stable.
Peer to peer hosting is fragile. Where do you keep the file, on a shared folder? Any Anti-virus or backup running? All these things can damage your file.