Check if the recognized operating system GPU is functioning properly on the compatible motherboard.
Check if the recognized operating system GPU is functioning properly on the compatible motherboard.
I downloaded Windows 11 23h2 today yet my no signal problem persists. I’m still stuck in a bootloop when secure boot is active, and turning it off lets me boot into Windows but without a display—Windows starts properly, and the driver reboot beep works again. Checking the device manager with hidden devices didn’t reveal the 4060 card, and the event viewer doesn’t mention anything about the card.
Also, I recently added another GPU to the Ab350n MTB—a RX6600 Sapphire Pulse—which also causes no signal and a boot loop if secure boot is enabled. I’m not sure what this means.
How do you even describe this situation? Have anyone encountered a motherboard that supports some cards but not others? Are there compatibility issues at play? I’m really stuck.
//LarryMan
This has been a trend last few years unfortunately. In theory all mobos and GPUs from last about 15 years should be compatible. In practice it becomes more and more a gamble. Especially when there is big age difference but not only that, you can easily find videos at yt where brand new mobo model fails to work with brand new GPU model (but it works with same GPU from other manufacturer).
Update.
The problem has been fixed.
TLDR: it was the CPU.
Spoiler: I’m a total mess.
I contacted Gigabyte as some advice was given, but I was already giving up on understanding what was wrong. Their support seemed inconsistent—sometimes they replied to one person, other times to another. On average, it took around ten days for them to respond to a single question. They often asked me to try something I’d already mentioned in the original post. Overall, it felt like a lengthy discussion that lasted over two months. Eventually, they stated the motherboard was faulty. No details were given as to why, though it seemed to work with other GPUs installed.
Anyway, I became convinced it was the motherboard I purchased. I bought the cheapest mini ITX model I found on Amazon, which turned out to be a Gigabyte A520i AC. Interestingly, my 4060 showed no signal during startup—something unexpected. After checking the BIOS, I found a setting called “Pcie Bifurcation” that might control CPU lane usage. I adjusted it to “4x4x4x4” and tried again. This time I got a signal.
I then checked GPU-Z and noticed the GPU was only using 4 lanes from the CPU, thanks to the bifurcation setting. The 4060 supports up to 8 lanes. I changed the BIOS back to default, which lost the signal. After reinstalling the 1650 and running GPU-Z, it correctly showed 16 lanes.
That was when I realized the 1650 had always been set to 8 lanes with my Ryzen 7 3700X. I should have switched the CPU again. To my surprise, using my old Ryzen 5 1600X with the 1650 worked—no need to adjust the PCIE bifurcation setting. With the 4060 installed, GPU-Z confirmed it was running at 16 lanes.
To be honest, I was certain I’d tried CPU switching but it didn’t fix the issue. During my troubleshooting sessions, often late at night, I tried many things to get a signal. It’s possible I forgot to change the CPU or that I had already received a signal from the 1600X. Since it didn’t work with the 3700X, I kept trying. In the end, I think the CPU issue was overlooked because the GPU seemed to function without problems.
I don’t have deep computer knowledge to explain what’s wrong, but it appears the CPU couldn’t utilize all its lanes properly when communicating with the GPU—unless the bifurcation setting was altered. I’m puzzled about how the 1650 could run at 16 lanes while the 4060 only had 8. I’ve sent back the A520i and everything is fine now.
Apologies for the lengthy explanation—I usually prefer detailed ones over short ones.
LarryMan.