PC fails to start without resetting the CMOS, and entering ASRock BIOS isn't possible.
PC fails to start without resetting the CMOS, and entering ASRock BIOS isn't possible.
Okay, so some additional testing notes: Re-flashing previous BIOS versions results in the same behavior Re-seating the CPU doesn't affect the results Trying to run the system off of the iGPU gives the same results Here's the big win - I was able to get into the BIOS by entering setup AFTER the system tries to re-boot once the CMOS is cleared. (Trying to enter setup from the "UEFI defaults have been loaded" screen results in a black screen, but trying to enter setup from the normal boot process AFTER that disappears allows me into the BIOS.) Trying to enter the BIOS normally still results in the same behavior of a black screen. The memory was detected and was running at 4800 speed, which is lower than its rated 6000, but it could be manually configured. I tried changing from Auto PCIe speed to Gen3 and Gen4 but it didn't seem to make a difference in the results, making me think that it's not a PCIe issue. The question I think I have here now is should I be seeing any info on the 4070 Ti in the ASRock BIOS? If so, it doesn't seem to be anywhere, but because it's a PCIe device that could be normal. And the fact that the iGPU also displays the exact same issue makes me feel like it's not the GPU itself.
ASRock has addressed my inquiry, advising me to replace the motherboard. (I didn’t realize I’d already handled the return process for this exact board.) Disappointing!
Quick update for anyone reading this in ~the future~ because I know Google helps: I returned the ASRock motherboard to Newegg and got an ASUS ROG Strix Z690-I ITX board - it worked right off the bat on my test bench: With the GPU, with the iGPU, with every permutation of NVMe and RAM installed. So ultimately I didn't solve the issue with the ASRock board . If you're running into this and you found the ASRock forum post of the guy who solved it by swapping in a whole new processor, I don't know what's up with him either, it doesn't make any sense to me with the error codes they were getting, and I'm sorry I couldn't be more help. Ultimately my solution is about returning what I had for new hardware and I know that doesn't work for everyone, but if you can and you're similarly bashing your head against it, I can say that the board I mentioned does work with this hardware configuration.