I have a QHY10, hopefully some of this may be helpful. I'm not suggesting it will fix anything but at least you should be able to verify some functionality.
Also these cameras have some different methods of reading the sensor depending on the exposure length. I can't remember the exact numbers but it depends on the download mode plus exposure length. Very short exposures are read from the sensor in two halves, which I think happens up to 9 secs or so. I have read reports of this causing problems but not seen it with mine, I don't use bias for calibration because of it though, just flats, darks and dark flats (30 second flats took some careful setup of the light box)
Anyway try this out, I've attached some screen shots.
1. Get NINA, just because the latest version has a QHY SDK included that I know works with my QHY10.
2. Connect the camera and power it up. You should be able to select the QHY10 directly without using the ASCOM driver. The driver info should be QHYCCD SDK and the driver version something similar to the attached image. It refers to the SDK versions here:
https://www.qhyccd.com/html/prepub/l...tml#!log_en.md
In my case its 21.03.13 - make sure its after that one, previous versions had an issue in the USB driver for older QHY cameras for a few revisions. Version 20.06.26 has it listed in known issues in the release notes so don't use that one obviously..
3. Set the cooler temperature (I use -10 in the example). Note that the details on power level and chip temperature are generally wrong until you set it and turn it on.
4. Once you've hit the target temperature put a cover on the camera to take some darks, in the camera settings you can enable and disable the overscan area (see pic). Take a 60 second dark with it on and then with it off, you should see the difference in the images (in the examples attached its the area down the right side of the image). In mine I had the lights on and don't think the cover was that light proof, sodon't worry if you don't get the same purplish color as mine.
If all goes well and you can see the overscan area when its enabled and not when its not then at least the camera / driver is working.
Hope it works out, other than the incredibly slow download of images (21 secs per image in standard mode with 1x1 binning), its a nice camera. 6.05um pixel size and aps-c sensor suits my setup and the usual conditions here in melbourne pretty well for me.