Yes, that is correct, I’m on the “Release Preview” ring. I have posted about this in the Feedback Hub App (for whatever good that is likely to do) and will post to the Insiders Forum (although there are already several posts about this issue there). But
given how widespread the problem is, and the fact that it outdates 2004 by quite a while, I suspect that the timing is a coincidence.
If anything, 2004 perhaps makes the problem even worse? Yesterday I couldn’t work on my Surface for more than 5 minutes before the screen would suddenly go black and I’d have to reboot. Eventually I did a clean reset, and it has been better since then. It
has only crashed twice so far this morning. Option 4 doesn’t fix the issue for me, and there doesn’t seem to be a CsEnabled registry key on my Windows build (is that possible?).
My next step will be to reinstall 1909 – if only to prevent Microsoft using that as an excuse. But maybe then some of the work arounds in this thread will help. If not, I’m going to have to return the device. It’s borderline unusable as is. And there seems
to be little point getting a replacement if Microsoft is unwilling or unable to fix the problem.