The only reasonable way to do this is to load your crash dump into the debugger and provide characters, i.e. .pdb files. This can be tricky because pdb files may not have enough information. Companies such as Microsoft provide public PDB files that do not have information about local var names and other data. PDBs, which with full details are called public PDBs.
Sometimes the stack gets corrupted, and this leads to a "loss of control." The code gets the return address, that is, some garbage, loads this value into EIP and starts executing instructions from there. In this case, the accident occurs very soon, after only a few “instructions” have been completed.
I mean, you need to find out if your EIP points to any code.