10-12-2023 08:16 AM
Hi all,
Just hoping someone can help me here please.
So I have a Maximus XI Code that been working perfectly with my ROG 4080,
Now unfortunately I had to send my 4080 for repair as the power connector melted but that's another story.
So I had my pc running fine with the intel integrated graphic card but now since the repair will take a while I got myself a second hand Gigabyte GTX 1080 went to install it onto the MB but when booting the pc I keep getting a black screen and no signal on the monitor.
The 1080 is working fine on another pc that I tested so I know is not the GPU.
The bios of the mb is the v2004.
Any suggestions please?
Do I need to disable the onboard intel graphic card to get the 1080 to work?
Even though when I swapped from my old 2080 to the 4080 it did everything automatically.
I also removed the old Nvidia drivers for the 4080 but still nothing.
Thanks in advance
Solved! Go to Solution.
10-12-2023 11:39 AM
Booting with code A0 is sounding better.
You shouldn't need to install anything else but you may have to fiddlle with it.
Try turning on your monitor before or as it's booting.
If that doesn't help....
Try entering the bios with the onboard graphics, on the Boot tab check what CSM is set to, if it's enabled, disable it.
If it's disabled, try enabling it.
10-12-2023 08:31 AM - edited 10-12-2023 08:31 AM
Hello Alessio088
Have you tried clearing the cmos?
Power down your pc, press and hold the clear cmos button on the back of the motherboard for 3 seconds.
Try booting up.
10-12-2023 08:40 AM
The clear cmos button is the one with a single green circular arrow.
10-12-2023 08:59 AM
Ok did that but still no display and qcode showing A2 now while it was showing 90 before I clear the cmos
10-12-2023 09:16 AM - edited 10-12-2023 09:16 AM
Thank you
Double check the pcie power cables are fully secured and try different outputs on the GTX 1080 with your monitor cable.
If that doesn't get you display, try different monitor cables Displayport and HDMI if you have them.
10-12-2023 10:01 AM
Thanks,yeah I tried different power cables already only need to try a different hdmi cable.
Also tried a different pcie slot but same result
Would the codes say anything to you?
When it boots correctly via on board graphic card the qcode shows A0
10-12-2023 10:13 AM - edited 10-12-2023 10:13 AM
Well, you're getting code A2 and code 90 because of no display. Code A0 is what you want to see, this means your pc is working as it should.
I was hoping it would at least boot with an HDMI cable, then I'd be inclined to think you may need the Nvidia firmware update for displayport 1.3/1.4.
It wouldn't hurt to try this.
Let your GTX 1080 installed with the pcie power cables connected and boot with the onboard graphics. Then try the firmware update, it will tell you if a firmware update is needed.
NVIDIA Graphics Firmware Update Tool for DisplayPort 1.3 and 1.4 Displays
10-12-2023 10:27 AM
Ok I'll try that,does the 1080 need to be powered and inserted in the mb slot too?
Because I'm not sure it will boot like that,I didn't try but I tried to disconnect the hdmi cable and plug it in the on board one but the display stayed black.
Or if I need to have the 1080 plugged with both power and MB can I do it while idling on windows?
10-12-2023 11:23 AM
Right so I've managed to have the 1080 plugged in and booting from the onboard I've downloaded and ran the firmware updater which found the 1080 and said that it needed updating so did that rebooted the pc and swapped the cable back onto the 1080 but it still showing a black screen strangely it shows code A0 now but still no screen,is there something else I need to install?
Tried with a brand new port cable as well but still same.
10-12-2023 11:39 AM
Booting with code A0 is sounding better.
You shouldn't need to install anything else but you may have to fiddlle with it.
Try turning on your monitor before or as it's booting.
If that doesn't help....
Try entering the bios with the onboard graphics, on the Boot tab check what CSM is set to, if it's enabled, disable it.
If it's disabled, try enabling it.