Problem
It happened more than once in different systems from our environment therefore it was adopted as part of our post-refresh activities.
After a system refresh (from production to quality or development) we started to face short-dumps at different times when different transaction codes were triggered, similar to below:
Analysis
The cause of this issue (in our case a general system error scenario in refreshed system) was single enqueue/dequeue objects related programs (the ones generated by system whenever an object like this is activated) were out of sync to enque/dequeue main program (it has an assignment in it to all enqueue/dequeue object generated). It happened due to copy/transport of these programs between systems involved in system refresh (from production to quality/development). ONLY dictionary objects must be copied,tThe function modules will be generated during activation of enqueue objects.
Solution
To clean up this situation you can do the following:
Use report RADENALL to generate the enqueue object. On the selection screen choose the enqueue object and check box "DELFIRST". The function modules will be deleted before generating the enqueue object again. It can be that this does not help in case of these double modules. In this case you can call the report without selection of an enqeue object.
You can start it without any special selection. It is essential that "DELFIRST" is checked.
If you start the report for all enqueue objects it will take about 20 minutes. It should be done in a time with not so many users inside because deleting some of the central enqueue objects will most likely cause some issues if they work.