F5F Stay Refreshed Hardware Desktop Device powered up, yet screen remains empty.

Device powered up, yet screen remains empty.

Device powered up, yet screen remains empty.

B
byDani_SMP
Member
59
07-12-2023, 03:16 PM
#1
I just assembled a new PC today. It’s a Gigabyte B550I Aorus Pro AX Rev 1.1 equipped with a 5600G processor and Corsair Vengeance RGB 3600Mhz C16 chipset. No graphics card was included. The system uses a Platinum 560W power supply connected to an UPS. I updated the BIOS to the latest release. After that, I installed Windows 11 Pro and downloaded all the necessary drivers from Gigabyte’s site so I could download updates and internet access. The installation process caused the computer to restart several times. I also installed Gigabyte Fusion RGB and Corsair Icue for motherboard and RAM diagnostics, as well as Core Temp and CPU-Z for performance monitoring. During setup, the processor idle temperature was 32°C and RAM was running at its default speed of 3200MHz. I discovered Goodgame Empire was already installed after using Core Temp. To clean up, I removed the RAM, disconnected the keyboard and mouse, and all connected USB devices to prevent the PC from recognizing them as boot devices. I cleared the CMOS by touching the two-pin jumper with a screwdriver; however, the CMOS battery is not accessible since it’s behind an unremovable IO panel cover. I then installed the GPU and connected it to another monitor using a different HDMI cable.
B
byDani_SMP
07-12-2023, 03:16 PM #1

I just assembled a new PC today. It’s a Gigabyte B550I Aorus Pro AX Rev 1.1 equipped with a 5600G processor and Corsair Vengeance RGB 3600Mhz C16 chipset. No graphics card was included. The system uses a Platinum 560W power supply connected to an UPS. I updated the BIOS to the latest release. After that, I installed Windows 11 Pro and downloaded all the necessary drivers from Gigabyte’s site so I could download updates and internet access. The installation process caused the computer to restart several times. I also installed Gigabyte Fusion RGB and Corsair Icue for motherboard and RAM diagnostics, as well as Core Temp and CPU-Z for performance monitoring. During setup, the processor idle temperature was 32°C and RAM was running at its default speed of 3200MHz. I discovered Goodgame Empire was already installed after using Core Temp. To clean up, I removed the RAM, disconnected the keyboard and mouse, and all connected USB devices to prevent the PC from recognizing them as boot devices. I cleared the CMOS by touching the two-pin jumper with a screwdriver; however, the CMOS battery is not accessible since it’s behind an unremovable IO panel cover. I then installed the GPU and connected it to another monitor using a different HDMI cable.

_
_GummyBunny_
Junior Member
14
07-12-2023, 03:16 PM
#2
I encountered an issue and needed to keep my clear CMOS button for about 30 seconds before it resolved.
_
_GummyBunny_
07-12-2023, 03:16 PM #2

I encountered an issue and needed to keep my clear CMOS button for about 30 seconds before it resolved.

E
Exo_Notic
Junior Member
6
07-12-2023, 03:16 PM
#3
I understand it might seem odd, but I resolved the problem once by unplugging the power cord and pressing the power button, then leaving it for a few minutes.
E
Exo_Notic
07-12-2023, 03:16 PM #3

I understand it might seem odd, but I resolved the problem once by unplugging the power cord and pressing the power button, then leaving it for a few minutes.

C
coolcol7
Junior Member
9
07-12-2023, 03:16 PM
#4
I don’t recognize the CMOS button. I’ve pressed the jumper pins for over 30 seconds. I tried taking out the power cord already. It seems the BIOS might have triggered the issue or something got damaged by radiation. Before re-flashing, I need to confirm the required BIOS version. For example, does 5600G require AGESA V2 1.2.0.8? And what about 1.2.0.7?
C
coolcol7
07-12-2023, 03:16 PM #4

I don’t recognize the CMOS button. I’ve pressed the jumper pins for over 30 seconds. I tried taking out the power cord already. It seems the BIOS might have triggered the issue or something got damaged by radiation. Before re-flashing, I need to confirm the required BIOS version. For example, does 5600G require AGESA V2 1.2.0.8? And what about 1.2.0.7?

A
AWSOMO3000
Member
166
07-12-2023, 03:16 PM
#5
If you haven’t done it yet, reinstall the GPU now.
A
AWSOMO3000
07-12-2023, 03:16 PM #5

If you haven’t done it yet, reinstall the GPU now.

K
KaWizK
Member
54
07-12-2023, 03:16 PM
#6
The latest update to 1.2.0.8 could resolve the issue you're facing.
K
KaWizK
07-12-2023, 03:16 PM #6

The latest update to 1.2.0.8 could resolve the issue you're facing.

9
905xA
Senior Member
667
07-12-2023, 03:16 PM
#7
After assembling the PC, I first updated the BIOS to the newest release, version F17b, which includes AGESA V2 1.2.0.8. It’s not clear if this specific version is required for the 5600G, since the documentation mentions 1.2.0.8 is intended for the 5800X3D. The motherboard ships with a F15 BIOS containing AGESA 1.2.0.5, and any subsequent BIOS releases have "b" or "e" appended to denote beta or experimental status. This pattern suggests that F15 represents the final stable release, while later versions are labeled as beta or experimental.
9
905xA
07-12-2023, 03:16 PM #7

After assembling the PC, I first updated the BIOS to the newest release, version F17b, which includes AGESA V2 1.2.0.8. It’s not clear if this specific version is required for the 5600G, since the documentation mentions 1.2.0.8 is intended for the 5800X3D. The motherboard ships with a F15 BIOS containing AGESA 1.2.0.5, and any subsequent BIOS releases have "b" or "e" appended to denote beta or experimental status. This pattern suggests that F15 represents the final stable release, while later versions are labeled as beta or experimental.

L
LorrenK
Senior Member
703
07-12-2023, 03:16 PM
#8
I've seen a few clips of that now, and it seems you might need to swap out the CPU or motherboard. If you have an extra one nearby, give it a try. You could also double-check the connections.
L
LorrenK
07-12-2023, 03:16 PM #8

I've seen a few clips of that now, and it seems you might need to swap out the CPU or motherboard. If you have an extra one nearby, give it a try. You could also double-check the connections.