Update: The problem looks like a command buffer overflow in the driver, caused by certain shader commands. That's why it only happened with certain postprocessing shaders.

I think we can implement a workaround so that it does not happen anymore even with the current nVidia Win32K drivers. Unfortunately this is too late for the upcoming update that I don't want to delay further. But it will be addressed after that.