T73680 is not using scene gravity (scene properties -> no checkmark at "gravity") but using the gravity settings inside Mantaflow. Also it says that using this property the gravity is 10 times stronger...
T73474 is a bug report concerning real word size setting...
T72949 mentions the initial velocity not to be used by the Mantaflow emission object...

No, that's definitly not what I expected ;-)
And if I apply the scale there's still the same render issue.

This is the file without cache. It's much smaller now.
Next time I will upload the files directly here.

@Clément Foucault (fclem) It works fine again with version: 2.81 (sub 3), branch: master, commit date: 2019-08-24 15:59, hash: rB6bb2912704ba
Thanks for fixing the problem :-)

@Clément Foucault (fclem) It works fine if I'm using the OpenGL render dll.

Okay. I will do that and try it out tomorrow when I'm back in the office.
By the way on this machine:
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: Intel(R) HD Graphics 4000 Intel 4.0.0 - Build 10.18.10.4358
the file works perfectly fine...

@Clément Foucault (fclem)
I'm starting blender with a double-click on "blender.exe" in the windows explorer. Can you please tell me how to start blender with the softwaregl option?

There's no chance to check if a driver's update could fix the crash. I'm working on a laptop that belongs to a big company. Driver's update are done by the administrators.
And yes, other operations (extruding and even selecting a ring of vertices) let blender crash. The same file works perfectly fine under 2.80!

What a difference 6 days make. Sorry for not doing this first. It works well as expected.

Thanks for the heads up. You can’t load as fast as the bugs are fixes ?

@Sergey Sharybin (sergey), it seems, that you were right. If I create a plane track on the 64 bit system, save it, open it on the 32 bit system and click on the plane track, blender crashes immediately. The same is vise versa. With the build dated 24.04.2015 the problem seems to be solved.
Thanks again!

@Sergey Sharybin (sergey), yes, I'm working on two different Computers most of the time. One with Win Vista 32 bit and one with Win7 64 bit. Maybe that's the reason. I will try with one of the next builds.
Currently I'm busy so maybe it will take a while until I will report.
Thanks a lot for helping and fixing!

@Sergey Sharybin (sergey), I'm sorry but testing it a bit more intensive I saw the plane track which wasn't active and not visible opposit to the trackers. Clicking a bit "in the wild" activatet the plane track.
But even without image-sequence (footage) an picture for the plane track did not crash the version a8adeeb (Windows 32 bit).
Anyway, I share the file in which I created a new plane, saved a few times, deleted tracks an tracked again, changed the picture for the plane track. Hope it helps.

@Sergey Sharybin (sergey), I've tried to crash the build 2.74a from this night, but yet I was not able to crash it :)
If it crashes again I will try to figure out how to reproduce the crash. One thing: I did not join tracks. Maybe it's because of the picture of the plane track. It is on a external stick.
If I now open the saved file with 2.74a and without the stick the plane track is not shown at all (which will of course don't cause any error). If I close blender, plug in the stick and start again, the plane track is shown after opening the file.