Hi, I am at the same spot you are now. I believe our machines are more than able to handle this and it has something to do with our graphics cards and memory. It seems to be that we need to make sure it is the built-in graphics card that is used and not the dedicated GPU. I got past a similar issue with TAILS OS on USB.
One thing that almost gets me further is the use of CTRL-ALT-F2 just before the langage screen displays. Hit it a couple of times, maybe pressing a letter on the keyboard in between. You get a prompt. Anaconda.
Using the bottom of the official troubleshooting page you mention type the following to enter a rescue mission. Unfortunately on my machine, this also exits no matter what option is chosen. Try it on yours.
pkill -9 anaconda
anaconda --rescue
2) One tip I have is from a similar issue with TAILS OS on USB. When I entered the Grub menu on it using "e" I have to alter the setup variables by adding:
nouveau.modeset=0
Modeset.blacklist=nouveau
and I delete:
livemedia=removeable
We need to find these for the Qubes install it seems.
I have Acer Nitro 5 Win 10 with Linux on VirtualBox where I modified the ISO.