Question No signal from known working Gpu in known working motherboard

[LarryMan]

Hello everyone! I am having a very strange no signal problem with my pc.

Pc:
Mtb: Gigabyte ab350-n gaming wifi
Cpu: ryzen 7 3700x
Gpu: Gigabyte GeForce RTX 4060 OC Low Profile
Psu: corsair Rm 750x
Ssd: kingston nvme 500gb
ram: corsair 16gb 3200MHz
Os: windows 11 24H2

It seems like the system is having problems detecting the card as it won't output any signal at any time. However i can hear the pc boot into windows and I can see my keyboard and mouse light up. I can even hear the beep from pressing win+ctrl+shift+b to try and reboot my gpu driver. Any other gpu that i install in my ab350n motherboard works fine. I am typing through this pc right now with a gtx 1650 installed.

The 4060 works fine in 3 other computers that I have tested. I have the same cpu (ryzen 7 3700x) in one of the computers that this card works in.

I have tried 3 different psu:s.
2 different sets of ram.
2 different displayport cables and 2 different hdmi cables.
I have installed the latest drivers available on Nvidias webbsite.
I have tried unistalling all drivers using Display Driver Unistaller in safe mode and then reconnecting my 4060.
I installed the latest available bios from gigabytes webbsite (f53g).
I have tried changing plenty of setting in the bios like disabling fast boot and csm.
I tried resetting the bios by removing the battery and shorting the pins. It did reset the bios but still no signal.
I have tried to use another ssd with windows 10 installed (I took this ssd from one of the computers where the gpu was detected and working).
I have tried to boot the system with everything unplugged(keyboard, mouse, headset and ethernet cable).
I even managed to boot into safe mode with the 4060 installed hoping that it would display a signal there (it did not).

After removing the 4060 I then installed my gtx 1650 which manages to boot every time without issue. Now with a display output I went into Event viewer to see if there where any errors regarding my 4060 not working. However there is nothing that even mentions my 4060 as if it was never even in the system. Going into device manager and checking hidden devices shows no sign of the 4060.
Another weird detail is that with the 1650 installed i could acces the bios and if I enable Secure boot, the 4060 will cause the pc to get stuck in a boot loop(all the fans and leds turns on for 5 sec and then turns off). I don't know if that is relevant but i though that I should mention it.
There is nothing wrong with my display or my video cables as I do get a display with any other gpu I install (gtx 1650, gtx 1050, gtx 1060). The cables going into the card are seated perfactly as well as the card itself in the pcie slot on the motherboard. I am not using any pcie-riser cables. The screen is not only black after booting into windows but all the time meaning I can not acces the bios with the 4060 installed.
If anyone has any idea of what is going on I would be eternally grateful . Kind regards, LarryMan.

​

 

[drivinfast247]

Update motherboard to latest stable version.

Are you in Legacy or UEFI mode?

 

[LarryMan]

Thank you for the reply!
As stated I am currently on f53g for the motherboard and before that I was on f53d which was when I first installed the 4060.
I guess I could try and go down the list of every bios that still supports the ryzen 3000 series cpu. I am ready to try anythings but I have avoided this since the card did not work on either of these versions.

Right now I am in uefi but i have also tried csm/legacy mode with but still no signal.
// LarryMan

 

[DRagor]

If your mobo allows install both 4060 and 1650 together (monitors to 1650). Then you can start searching Device manager if 4060 is detected.

 

[LarryMan]

If your mobo allows install both 4060 and 1650 together (monitors to 1650). Then you can start searching Device manager if 4060 is detected.

Gigabyte ab350n has only one pcie slot unfortunately.
I could see the card in hidden devices when i booted through the ssd with windows 10 . From there i went into the event viewer for the card but it simply showed the date and time where it was installed in the working pc with this ssd and no mention of when i Installed it in the ab350n motherboard.

 

[DRagor]

Unfortunate.
Does 1650 works fine with Secure boot enabled? Did you let the 4060 boot loop for a while with Secure boot? Maybe it would self-fix if you let it.

 

[beyondlogic]

Hello everyone! I am having a very strange no signal problem with my pc.

Pc:
Mtb: Gigabyte ab350-n gaming wifi
Cpu: ryzen 7 3700x
Gpu: Gigabyte GeForce RTX 4060 OC Low Profile
Psu: corsair Rm 750x
Ssd: kingston nvme 500gb
ram: corsair 16gb 3200MHz
Os: windows 11 24H2

It seems like the system is having problems detecting the card as it won't output any signal at any time. However i can hear the pc boot into windows and I can see my keyboard and mouse light up. I can even hear the beep from pressing win+ctrl+shift+b to try and reboot my gpu driver. Any other gpu that i install in my ab350n motherboard works fine. I am typing through this pc right now with a gtx 1650 installed.

The 4060 works fine in 3 other computers that I have tested. I have the same cpu (ryzen 7 3700x) in one of the computers that this card works in.

I have tried 3 different psu:s.
2 different sets of ram.
2 different displayport cables and 2 different hdmi cables.
I have installed the latest drivers available on Nvidias webbsite.
I have tried unistalling all drivers using Display Driver Unistaller in safe mode and then reconnecting my 4060.
I installed the latest available bios from gigabytes webbsite (f53g).
I have tried changing plenty of setting in the bios like disabling fast boot and csm.
I tried resetting the bios by removing the battery and shorting the pins. It did reset the bios but still no signal.
I have tried to use another ssd with windows 10 installed (I took this ssd from one of the computers where the gpu was detected and working).
I have tried to boot the system with everything unplugged(keyboard, mouse, headset and ethernet cable).
I even managed to boot into safe mode with the 4060 installed hoping that it would display a signal there (it did not).

After removing the 4060 I then installed my gtx 1650 which manages to boot every time without issue. Now with a display output I went into Event viewer to see if there where any errors regarding my 4060 not working. However there is nothing that even mentions my 4060 as if it was never even in the system. Going into device manager and checking hidden devices shows no sign of the 4060.
Another weird detail is that with the 1650 installed i could acces the bios and if I enable Secure boot, the 4060 will cause the pc to get stuck in a boot loop(all the fans and leds turns on for 5 sec and then turns off). I don't know if that is relevant but i though that I should mention it.
There is nothing wrong with my display or my video cables as I do get a display with any other gpu I install (gtx 1650, gtx 1050, gtx 1060). The cables going into the card are seated perfactly as well as the card itself in the pcie slot on the motherboard. I am not using any pcie-riser cables. The screen is not only black after booting into windows but all the time meaning I can not acces the bios with the 4060 installed.
If anyone has any idea of what is going on I would be eternally grateful . Kind regards, LarryMan.

​

use only drivers for nvidia

game driver

Driver Version: 566.36 do not use any driver beyond that they are unstable trash.

thats last known stable driver for 4000 series atm cause nvidia screwed up the drivers.

 

[LarryMan]

Unfortunate.
Does 1650 works fine with Secure boot enabled? Did you let the 4060 boot loop for a while with Secure boot? Maybe it would self-fix if you let it.

1650 works fine with secure boot enabled. I probably waited 10 minutes once with the 4060 stuck in bootloop before I gave up on that. Should i have waited longer?

 

[DRagor]

1650 works fine with secure boot enabled. I probably waited 10 minutes once with the 4060 stuck in bootloop before I gave up on that. Should i have waited longer?

10 mins should be enough if it were to work.
Since both the card and mobo are Gigabyte sending question to Gigabyte support might be worth a try.

 

[LarryMan]

use only drivers for nvidia

game driver

Driver Version: 566.36 do not use any driver beyond that they are unstable trash.

thats last known stable driver for 4000 series atm cause nvidia screwed up the drivers.

I have only used nvidia game drivers while I have been troubleshooting this issue. I began with the latest drivers which did not give me a signal.

Sorry I forgot to add that I have also tried the driver which the card was automatically given when installed in every other pc where it works. That driver was 560.94. Installing that on my pc did also not give me a signal. I have also tried another driver which was newer than 560.94 but older than the newest 572.83. I believe it was 572.60 which also did not give me a signal. Thank you for the suggestion. //LarryMan

 

[LarryMan]

10 mins should be enough if it were to work.
Since both the card and mobo are Gigabyte sending question to Gigabyte support might be worth a try.

I have actually written to gigabyte but it has been a week since that so decided to try and get help here while i wait. //LarryMan

 

[beyondlogic]

I have only used nvidia game drivers while I have been troubleshooting this issue. I began with the latest drivers which did not give me a signal.

Sorry I forgot to add that I have also tried the driver which the card was automatically given when installed in every other pc where it works. That driver was 560.94. Installing that on my pc did also not give me a signal. I have also tried another driver which was newer than 560.94 but older than the newest 572.83. I believe it was 572.60 which also did not give me a signal. Thank you for the suggestion. //LarryMan

try following

• Above 4G Decoding: In the BIOS, ensure "Above 4G Decoding" is enabled.
  
  
• Resizable BAR Support: Make sure "Resizable BAR Support" is set to "Auto" in the BIOS.
  
  
• CSM Support: Disable "CSM Support" in the BIOS.

 

[LarryMan]

try following

• Above 4G Decoding: In the BIOS, ensure "Above 4G Decoding" is enabled.
  
  
• Resizable BAR Support: Make sure "Resizable BAR Support" is set to "Auto" in the BIOS.
  
  
• CSM Support: Disable "CSM Support" in the BIOS.

Thank you for the suggestion! Unfortunately I have tested this with no luck. I actually have these exact settings right now. One strange thing I noticed while doing these changes in the bios is when after im done in bios and switch to the 4060 the csm would almost always be enabled again when I switch back to my 1650 and go back into bios. However once or twice the csm was still disabled when switching to the 1650 and I still nhad no signal on the 4060. //LarryMan

 

[beyondlogic]

Thank you for the suggestion! Unfortunately I have tested this with no luck. I actually have these exact settings right now. One strange thing I noticed while doing these changes in the bios is when after im done in bios and switch to the 4060 the csm would almost always be enabled again when I switch back to my 1650 and go back into bios. However once or twice the csm was still disabled when switching to the 1650 and I still nhad no signal on the 4060. //LarryMan

try a diffent 8 pin connector to gpu. all the power gets to that card threw that 1 pin connector.

try a diffrent port on the hdmi sometimes there fickle. or diffrent display port make sure the case is not obscuring the gpu.

https://preview.redd.it/is-it-bad-i...bp&s=66622a965c7b69fc7a15312c9f1dc073b039b86e

 

[LarryMan]

try a diffent 8 pin connector to gpu. all the power gets to that card threw that 1 pin connector.

try a diffrent port on the hdmi sometimes there fickle. or diffrent display port make sure the case is not obscuring the gpu.

https://preview.redd.it/is-it-bad-i...bp&s=66622a965c7b69fc7a15312c9f1dc073b039b86e

I have tried every port on the 4060 (2 hdmi and 2 DP) in 2 different monitors and I have actually tried with 3 different psu:s. I have also tested the system outside of the case to prohibit any grounding issue and also like you mentioned the possibility of the case blocking the cable from being properly connected. Thanks again for the suggestion! //LarryMan

 

[stonecarver]

Os: windows 11 24H2

Do you have a spare SSD. It seems to be showing up here and there as a last resort go find Windows ISO of pre 24 H2 meaning 23 H2 and fresh install with the RTX 4060.

You have did a great job trying everything up to now. I seem to notice a pattern with older Ryzen and 24 H2.

Up to you but worth a go if all else has failed.

 

[beyondlogic]

Do you have a spare SSD. It seems to be showing up here and there as a last resort go find Windows ISO of pre 24 H2 meaning 23 H2 and fresh install with the RTX 4060.

You have did a great job trying everything up to now. I seem to notice a pattern with older Ryzen and 24 H2.

Up to you but worth a go if all else has failed.

thats a good point didnt think the os version could be a issue.

 

[LarryMan]

Do you have a spare SSD. It seems to be showing up here and there as a last resort go find Windows ISO of pre 24 H2 meaning 23 H2 and fresh install with the RTX 4060.

You have did a great job trying everything up to now. I seem to notice a pattern with older Ryzen and 24 H2.

Up to you but worth a go if all else has failed.

Thank you for the reply! I did try to boot through a spare ssd with windows 10 installed which I took from one of the computers where the card was detected without any issues. Since this also did not work I kind of assumed that it was not a windows issue. I do have another nvme ssd which I belive to have windows 11 24 H2 aswell. I could try a clean windows install there as it does not contain anything I care about. I could try 23H2 as you mentioned. What patterns have you noticed with the ryzen cpus? //LarryMan

 

[stonecarver]

What patterns have you noticed with the ryzen cpus?

GPU detection that sometimes needs 23 H2 to get the ball rolling as in a working Windows 11 with the GPU + drivers than do an in place upgrade to 24 H2 and life goes on.

Like I said if nothing else works keep this on the back burner or just try.

 

[LarryMan]

GPU detection that sometimes needs 23 H2 to get the ball rolling as in a working Windows 11 with the GPU + drivers than do an in place upgrade to 24 H2 and life goes on.

Like I said if nothing else works keep this on the back burner or just try.

Okey I will try the 23H2 tomorrow when I have the time. I am pretty much at the "when nothing else works" point so I will try anything. Thanks for the suggestion. //LarryMan

 

[LarryMan]

I downloaded Windows 11 23h2 today but it did not resolve my no signal issue. Still stuck in bootloop if secure boot is enabled and disabling it makes me boot into windows but with no display as i can hear Windows succesfully boot and I can once again press win+ctrl+shift+b and hear that driver reboot beep. Going into device manager again with the 1650 and viewing hidden devices did not show the 4060 and event viewer does not mention anything regarding the card.

Another fun fact. I installed yet another gpu in the ab350n mtb, this time a rx6600 sapphire pulse which also gives no signal and boot loop if secure boot is enabled. I do not know what this means.
I mean how do you even explain this? has anyone heard of a motherboard that works with some cards but some don't? Are they not compatible in some way? I am really out of ideas.
//LarryMan

 

[DRagor]

I mean how do you even explain this? has anyone heard of a motherboard that works with some cards but some don't? Are they not compatible in some way? I am really out of ideas.

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).

 

[LarryMan]

Update.

The Issue has been resolved.

TLDR: it was the cpu.

spoiler: I am a f****** idiot.
I wrote to gigabyte as some people here suggested althought I had basically already given up on ever figuring out what the issue was. Gigabyte support seems to be very hit or miss. It does not say if it is the same person that replys to your questions but it always felt like it was someone new based on the grammer and the amount of enthusiasm the support seemed to show. On average it took about 10 days for Gigabyte to answer a single question and sometimes they would ask you to try something that you already had stated to have tried in the original question. So all in all I probably had a disscussion with them for over 2 months. In the end they wrote '' the mobo is broken'' but with no explanation to why since it seemed to work fine with every other gpu installed in it but at this point I was also rather certain that it had to be the mobo.

Anyways. Convinced that it had to be the motherboard I bought the cheapest mini itx that I could find on amazon which ended up being a Gigabyte a520i ac. Strangely I was met with a no signal from my 4060 upon my first startup which was awesome (not). I popped in my 1650 and went into the bios and found a setting called ''Pcie Bifurcation'' which I believe allows you to change the amount of lanes the cpu uses on the different pcie components. I set this to ''4x4x4x4" and switched to my 4060. THIS GAVE ME A SIGNAL. Hurray, I tought.
However I decided to go into gpuz to check if the gpu was running correctly and noticed that it was only running on x4 lanes from the cpu which was thanks to the bifurcation setting. The 4060 can run on x8 lanes. So back I went into the bios and switched the bifurcation setting to default which made me lose signal once again. 1650 installed again and went into gpuz and it was only running on x8 lanes when it should be running at x16. Strange.

With the 1650 installed in my spare pc, gpuz showed that it was running on x16 like it should. This was when i realized that the 1650 had probably always been running with x8 lanes with my ryzen 7 3700x and that I should try and switch the cpu once again. To my absolute surprise, with my old ryzen 5 1600x the 1650 was suddenly running with x16 lanes and with the 4060 installed I did not have to touch the pcie bifurcation setting and it was running at its full x8 lanes.

If I am being completaly honest, I was 100% sure that I had already tried switching cpu but that it did not resolve my issue. However when I was troubleshooting this I would sometimes be deep into the night and trying what felt like 100 different things to get a signal so it could be possible that i either forgot to ever switch the cpu or that I forgot that I did get a signal from the 1600x but since it did not work with my 3700x I simply kept troubleshooting. In the end I think the fact that the cpu seemed to work without issue was the reason why I overlooked it. I do not know computers well enough to explain what is wrong with my cpu but it seems as if it is unable to use all of its lanes when comunicating with the gpu wich made it unable to communicate at all with the 4060 unless the bifurcation setting was changed. I do not understand how it was able to use 8 lanes on the 1650 but only 4 on the 4060. I have sent back the a520i and life is good.
Sorry for the long explenation but I have always preffered reading a long explenation rather than a short one.

LarryMan.