This article explains how you can generate a so-called full memory dump from ECSTA and make it available for analysis.
Please use these settings only if it really is a crash.
The debug logs from ECSTA are also required in the event of a crash:
Microsoft Windows Error Reporting
If the telephony service/ECSTA has crashed and this is also visible in Windows Error Reporting, the following path can be used to check whether Windows itself has created a dump:
It should be noted that Windows does create a file for each crash. However, if the service crashes several times for the same reason, these files are not filled.
A filled memory dump has an approximate size of 150 MB – 2 GB. If the files have only a few KB, they are empty and useless for analysis.
If crash dumps are not written, this can be enforced with the following article:
Dump via ECSTA
Alternatively, it is possible to have ECSTA write a dump itself.
This is only possible if the operating system still allows it.
Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\ESTOS\ECSTA_Name
Click in the menu Edit -> New -> DWORD-Value (32-Bit).
Enter "DUMP" as the name.
- Enter "2" as the value (decimal).
- After the key is set, the ECSTA must be restarted, the easiest way to do this is to restart the telephony service.
- In the event of a future crash, a full memory dump is written to the log file directory of ECSTA.