SIG$SEGV is short for signal segment violation. Technically, it is described as an incorrect use of pointer or a buffer overflow (memory problems). It is a bug, whenever it happens, but it is difficult to relate the cause to any one particular issue. Based on previous call records, it has happened in the past with distributed solver and rezoning, but is not limited to these applications.
If you are using a distributed solver then please uncheck that option and then run the analysis.
For recovering the data, was the database file saved?