Turned out, Blender 2.91 doesn't accept export LIBGL_DRIVERS_PATH anymore. All other issues are resolved with current Blender 2.91.

Here is a very much simplified version:

Yes I am aware of precision errors. Just too bad scaling doesn't help. So the only workaround would be to leave the camera in the origin and move everything else?

This is another explanation of the problem. Unfortunately without an reply.

Unfortunately scaling this certain scene down does not resolve the issue. Also have a look at the black artefacts on the plane. Those are also coming from missing alpha precision.
Updated version here: https://www.dreisicht.net/share/searchwing/3d/blender/master/master_master_08_bugreport.blend

I guess the reason is, that the object is too far from origin (719.817 m, -1112.15 m, 222.678 m). So the z-precision of cycles is not enough at this point.

In D2613#117099, @Gottfried Hofmann (gottfried) wrote:

What is the status of this patch? It seems super useful for the visualization folk...

But if I want to render collection a in layer a, and collection b in layer b, there is no way to do that, unless I put them in different scenes?

Oh sorry, then I mixed it up with render layers. Are those implemented yet?

Can't confirm on d3870471edd7

Confirm on same windows 10 and GTX 1080 Ti.

Thanks, wasn't aware of this!

If I switch from experimental to supported feature set, it doesn't crash, as well as disabling Adaptive subdivision!

I was able to reproduce on two more PCs

Perhaps I was unclear about the steps, because I can reproduce it on another pc.

Looks like this helps so far! I just get after about 8 hours of rendering a "Blender has stopped working" dialog from windows

cant redow with the newest build either. Topic closed.

sorry my fault, I mean Remesh modifier.

actually I've had a few bugs with the decimate modifier, and this one was the only one, wich I could redo.