F5F Stay Refreshed Hardware Desktop No display after POST

No display after POST

No display after POST

Pages (2): 1 2 Next
Z
zamys
Senior Member
690
11-20-2025, 07:37 AM
#1
Hello everyone!
This is my first visit, and I’m trying to figure out this odd "anomaly."
While setting up my new PC (details below), I encountered a rather suspicious but still annoying issue when trying to start it.
The main challenge is that after a POST, I sometimes don’t see any display on my monitor, even though the monitor is powered on. I have to switch it back to HDMI input manually—though it was always connected via HDMI—and then it smoothly launches into Windows. This step isn’t reliable; occasionally I hit a 00 or A6 debug code while the 'Boot' LED stays on, and I’m forced to keep restarting until I finally get in.
When I attempt to boot into BIOS, the problem is even more severe. Once the PC powers on, the monitor shows no HDMI input. Even when I repeatedly press the BIOS key (Del) while still having no output, I’m stuck on one of those debug codes.
I tried restarting the PC, navigating through Windows Update → Special settings → Recovery, and then restarting again to boot into BIOS. The experience was similar: the PC restarts, the LED turns off, and I’m trapped on a debug code like '08'. It feels like I’m locked out of the BIOS.
I’ve also tried reseating the GPU, checking the PSU, and even re-seating the SSD. According to Gigabyte’s manual, there are two pins on the motherboard that can be shorted to reset CMOS—though I’m not sure if that worked after touching them with a screwdriver.
The PC has an X870E AORUS ELITE WIFI7 with BIOS version F7 (not F8a).
I went to a service center, and surprisingly, they were able to boot it into BIOS instantly. Should I worry more about my monitor, the HDMI cable, or the power outlet? They suggested a possible GPU/Motherboard driver or chipset incompatibility, but I doubt that’s the case.
When I returned home, I was still stuck in BIOS because I got a black screen right away. I figured I might have an APU, so I changed the HDMI connection from the GPU to the motherboard’s I/O. That fixed the issue partially: I could finally enter BIOS, make changes, save them, and exit.
After restarting in Windows, I swapped the HDMI cable back into the GPU, and everything worked perfectly—except for the fact that when the PC starts up, the monitor still shows no display (black screen) and immediately jumps into Windows without letting me boot into BIOS.

Some suggestions from others include:
- Debug codes like 99 point to Super IO initialization issues; 00 suggests CPU problems; A6 hints at SSD or booting issues.
- The tech suggested a possible motherboard + GPU driver/chipset incompatibility.
- Others mentioned the PSU, HDMI cable, and monitor as potential culprits.
- My monitor is a VG1B series TUF gaming model (31.5", 165Hz curved), which worked fine before. The tech’s monitor was outdated (using an HDMI adapter into a VGA).
- Considering the PC booted in service, I’m leaning toward the monitor, HDMI cable, or power outlet being the problem, but I’m not sure what to focus on right now.

Anyone have insights or solutions for this strange behavior?
Z
zamys
11-20-2025, 07:37 AM #1

Hello everyone!
This is my first visit, and I’m trying to figure out this odd "anomaly."
While setting up my new PC (details below), I encountered a rather suspicious but still annoying issue when trying to start it.
The main challenge is that after a POST, I sometimes don’t see any display on my monitor, even though the monitor is powered on. I have to switch it back to HDMI input manually—though it was always connected via HDMI—and then it smoothly launches into Windows. This step isn’t reliable; occasionally I hit a 00 or A6 debug code while the 'Boot' LED stays on, and I’m forced to keep restarting until I finally get in.
When I attempt to boot into BIOS, the problem is even more severe. Once the PC powers on, the monitor shows no HDMI input. Even when I repeatedly press the BIOS key (Del) while still having no output, I’m stuck on one of those debug codes.
I tried restarting the PC, navigating through Windows Update → Special settings → Recovery, and then restarting again to boot into BIOS. The experience was similar: the PC restarts, the LED turns off, and I’m trapped on a debug code like '08'. It feels like I’m locked out of the BIOS.
I’ve also tried reseating the GPU, checking the PSU, and even re-seating the SSD. According to Gigabyte’s manual, there are two pins on the motherboard that can be shorted to reset CMOS—though I’m not sure if that worked after touching them with a screwdriver.
The PC has an X870E AORUS ELITE WIFI7 with BIOS version F7 (not F8a).
I went to a service center, and surprisingly, they were able to boot it into BIOS instantly. Should I worry more about my monitor, the HDMI cable, or the power outlet? They suggested a possible GPU/Motherboard driver or chipset incompatibility, but I doubt that’s the case.
When I returned home, I was still stuck in BIOS because I got a black screen right away. I figured I might have an APU, so I changed the HDMI connection from the GPU to the motherboard’s I/O. That fixed the issue partially: I could finally enter BIOS, make changes, save them, and exit.
After restarting in Windows, I swapped the HDMI cable back into the GPU, and everything worked perfectly—except for the fact that when the PC starts up, the monitor still shows no display (black screen) and immediately jumps into Windows without letting me boot into BIOS.

Some suggestions from others include:
- Debug codes like 99 point to Super IO initialization issues; 00 suggests CPU problems; A6 hints at SSD or booting issues.
- The tech suggested a possible motherboard + GPU driver/chipset incompatibility.
- Others mentioned the PSU, HDMI cable, and monitor as potential culprits.
- My monitor is a VG1B series TUF gaming model (31.5", 165Hz curved), which worked fine before. The tech’s monitor was outdated (using an HDMI adapter into a VGA).
- Considering the PC booted in service, I’m leaning toward the monitor, HDMI cable, or power outlet being the problem, but I’m not sure what to focus on right now.

Anyone have insights or solutions for this strange behavior?

N
Nickinvasion
Junior Member
32
11-20-2025, 07:37 AM
#2
Welcome to the forums, newcomer! I actually brought the PC into a PC service, surprisingly enough, the tech there was able to instantly boot it up into the BIOS as well. The only change between your place and the repair shop is the power source (the wall outlet). You might have a grounding issue. Do you feel a mild tingling sensation when you touch the metal part of your case and your bare feet are touching a tiled floor? Besides that, try flashing the BIOS to F8a and see if it helps. Also, disable the iGPU in BIOS, then use DDU to remove all GPU drivers (Intel, AMD, Nvidia), and manually install the driver from Nvidia's support site via an elevated command—Right click installer > Run as Administrator.
N
Nickinvasion
11-20-2025, 07:37 AM #2

Welcome to the forums, newcomer! I actually brought the PC into a PC service, surprisingly enough, the tech there was able to instantly boot it up into the BIOS as well. The only change between your place and the repair shop is the power source (the wall outlet). You might have a grounding issue. Do you feel a mild tingling sensation when you touch the metal part of your case and your bare feet are touching a tiled floor? Besides that, try flashing the BIOS to F8a and see if it helps. Also, disable the iGPU in BIOS, then use DDU to remove all GPU drivers (Intel, AMD, Nvidia), and manually install the driver from Nvidia's support site via an elevated command—Right click installer > Run as Administrator.

J
joshlammin
Member
55
11-20-2025, 07:37 AM
#3
Hello,
I’m not experiencing any tingling feeling at all. The computer is completely quiet, with no electrical noise. We’re dealing with a wooden floor.
My main worry about updating the BIOS to F8a is that it might damage the motherboard or cause a total black screen, which would make my issue ten times worse. That’s something I’ve been thinking about.

BIOS version F7 included several fixes and updates:
- Checksum: 21B2
- AMD AGESA 1.2.0.3e patchA added for new CPU support
- TPM2.0 out-of-bounds read vulnerability (CVE-2025-2884) fixed
- AMD CPU microcode signature verification vulnerability (CVE-2024-36347) addressed, including Ryzen 9000 series support
- Improved memory compatibility

BIOS version F8a:
- Checksum: 2DBB
- AMD AGESA 1.2.0.3f updated
- Improved system stability and performance

Would this update help with my situation?
Right now, I can only access the BIOS through the CPU’s built-in iGPU. I’m unsure how it would work if I were inside the BIOS with the HDMI connected to the motherboard.
J
joshlammin
11-20-2025, 07:37 AM #3

Hello,
I’m not experiencing any tingling feeling at all. The computer is completely quiet, with no electrical noise. We’re dealing with a wooden floor.
My main worry about updating the BIOS to F8a is that it might damage the motherboard or cause a total black screen, which would make my issue ten times worse. That’s something I’ve been thinking about.

BIOS version F7 included several fixes and updates:
- Checksum: 21B2
- AMD AGESA 1.2.0.3e patchA added for new CPU support
- TPM2.0 out-of-bounds read vulnerability (CVE-2025-2884) fixed
- AMD CPU microcode signature verification vulnerability (CVE-2024-36347) addressed, including Ryzen 9000 series support
- Improved memory compatibility

BIOS version F8a:
- Checksum: 2DBB
- AMD AGESA 1.2.0.3f updated
- Improved system stability and performance

Would this update help with my situation?
Right now, I can only access the BIOS through the CPU’s built-in iGPU. I’m unsure how it would work if I were inside the BIOS with the HDMI connected to the motherboard.

I
Its_Towxis
Junior Member
4
11-20-2025, 07:37 AM
#4
Nope, I do not feel any kind of tingling sensation whatsoever, the PC is also silent, not making any electrical noise or anything. We are talking about a wooden floor.
If you have a wooden floor, it defeats the purpose of you even touching the case and trying to identify a grounding issue, the old school way.
My concern with updating the BIOS to F8a is me bricking the motherboard or just completely getting a black screen, making my problem x10 worse, but it ran through my mind.
You're covered under warranty, if the board is bricked, you either reflash it using the Q-Flash Plus button and/or if that fails, you RMA the board.
Do you think this update would help me in my case?
Part of the process of troubleshooting is to go through the process of trying things till you come to a solution. I can't say whether it'll make things worse or better but I've included it as a suggestion to solve your issue. To add, the fixes mentioned are but a handful of things BIOS devs do behind the scenes. They've only included things that make sense to a laymen. If you went studying the microcode, maybe you'd find the other changes that came about with the latter BIOS version. Likely to plug in another hole.
I
Its_Towxis
11-20-2025, 07:37 AM #4

Nope, I do not feel any kind of tingling sensation whatsoever, the PC is also silent, not making any electrical noise or anything. We are talking about a wooden floor.
If you have a wooden floor, it defeats the purpose of you even touching the case and trying to identify a grounding issue, the old school way.
My concern with updating the BIOS to F8a is me bricking the motherboard or just completely getting a black screen, making my problem x10 worse, but it ran through my mind.
You're covered under warranty, if the board is bricked, you either reflash it using the Q-Flash Plus button and/or if that fails, you RMA the board.
Do you think this update would help me in my case?
Part of the process of troubleshooting is to go through the process of trying things till you come to a solution. I can't say whether it'll make things worse or better but I've included it as a suggestion to solve your issue. To add, the fixes mentioned are but a handful of things BIOS devs do behind the scenes. They've only included things that make sense to a laymen. If you went studying the microcode, maybe you'd find the other changes that came about with the latter BIOS version. Likely to plug in another hole.

C
Cobblestone07
Junior Member
47
11-20-2025, 07:37 AM
#5
If you own a wooden floor, it undermines the whole idea of touching the case and checking for grounding problems, the traditional method.
C
Cobblestone07
11-20-2025, 07:37 AM #5

If you own a wooden floor, it undermines the whole idea of touching the case and checking for grounding problems, the traditional method.

S
silvertooth98
Member
181
11-20-2025, 07:37 AM
#6
I updated the BIOS to version F8a, but the issue remains, unfortunately. Since my PC functioned properly in the tech shop, it's hard to pinpoint the exact cause—could be the HDMI cable, monitor, peripherals, or even the home wall outlets after that event? Any suggestions?
S
silvertooth98
11-20-2025, 07:37 AM #6

I updated the BIOS to version F8a, but the issue remains, unfortunately. Since my PC functioned properly in the tech shop, it's hard to pinpoint the exact cause—could be the HDMI cable, monitor, peripherals, or even the home wall outlets after that event? Any suggestions?

G
53
11-20-2025, 07:37 AM
#7
Hello everyone again. I’m experiencing a strange problem with my VG328 monitor (believed to be from the ASUS VG1B line). Despite being able to hear the Windows startup sound through my headset, there’s no display whatsoever—no BIOS splash screen, no Windows interface, and even the HDMI/VGA inputs aren’t working. It’s a 31.5-inch curved monitor with 1080p at 165Hz, using only an HDMI port from my RTX 5080. I’m using it with my current setup, but everything seems to be stuck in standby or fails to activate.

This issue started after a recent Nvidia driver update, which I installed cleanly. Previously, I managed to get a display, though the experience wasn’t perfect. When I powered on the PC, the monitor would show “No HDMI input,” go into standby, and wouldn’t wake up unless I pressed a button on the screen itself. The most annoying part is that even with the BIOS key pressed repeatedly, it doesn’t detect any signal or display.

I’ve noticed this problem only with dedicated GPU setups, but not with my older system using an RTX 3060Ti. ChatGPT suggested it might be a “handshake/firmware incompatibility.” A technician at a PC service center was able to boot into BIOS immediately. Should I consider replacing the monitor? Yet, it still works perfectly with my older hardware.

Current system details:
- Ryzen 7 9800X3D
- X870E AORUS ELITE WIFI7 rev 1.1
- Latest BIOS version F8a
- Kingston Fury 2x16GB DDR5 RAM
- X1 1TB MP700 Pro Gen5 SSD
- Gigabyte RTX 5080 Gaming OC
- Corsair RM850x (2024, 3.1/5.1 compatible)
- Monitor: VG328 (ASUS VG1B series), 1080p@165Hz (HDMI only)

OS: Windows 11 24H2
G
goldengaming33
11-20-2025, 07:37 AM #7

Hello everyone again. I’m experiencing a strange problem with my VG328 monitor (believed to be from the ASUS VG1B line). Despite being able to hear the Windows startup sound through my headset, there’s no display whatsoever—no BIOS splash screen, no Windows interface, and even the HDMI/VGA inputs aren’t working. It’s a 31.5-inch curved monitor with 1080p at 165Hz, using only an HDMI port from my RTX 5080. I’m using it with my current setup, but everything seems to be stuck in standby or fails to activate.

This issue started after a recent Nvidia driver update, which I installed cleanly. Previously, I managed to get a display, though the experience wasn’t perfect. When I powered on the PC, the monitor would show “No HDMI input,” go into standby, and wouldn’t wake up unless I pressed a button on the screen itself. The most annoying part is that even with the BIOS key pressed repeatedly, it doesn’t detect any signal or display.

I’ve noticed this problem only with dedicated GPU setups, but not with my older system using an RTX 3060Ti. ChatGPT suggested it might be a “handshake/firmware incompatibility.” A technician at a PC service center was able to boot into BIOS immediately. Should I consider replacing the monitor? Yet, it still works perfectly with my older hardware.

Current system details:
- Ryzen 7 9800X3D
- X870E AORUS ELITE WIFI7 rev 1.1
- Latest BIOS version F8a
- Kingston Fury 2x16GB DDR5 RAM
- X1 1TB MP700 Pro Gen5 SSD
- Gigabyte RTX 5080 Gaming OC
- Corsair RM850x (2024, 3.1/5.1 compatible)
- Monitor: VG328 (ASUS VG1B series), 1080p@165Hz (HDMI only)

OS: Windows 11 24H2

F
118
11-20-2025, 07:37 AM
#8
Maintain focus by staying within a single thread.
F
FantasticMan08
11-20-2025, 07:37 AM #8

Maintain focus by staying within a single thread.

B
Brandon_En
Member
246
11-20-2025, 07:37 AM
#9
Yes, the signs are quite similar.
B
Brandon_En
11-20-2025, 07:37 AM #9

Yes, the signs are quite similar.

O
oreoblahst
Member
62
11-20-2025, 07:37 AM
#10
Return to F7B is a recognized problem for X870E Aorus Elite Wifi7. On Reddit.com r/gigabyte you'll find discussions about it. I experienced the same problem on F4 bios and the F7 stable bios; it's missing on F7B. I can't comment on other models, but F7B has remained quite stable for me.
Created an account to assist others and give back the favor.
O
oreoblahst
11-20-2025, 07:37 AM #10

Return to F7B is a recognized problem for X870E Aorus Elite Wifi7. On Reddit.com r/gigabyte you'll find discussions about it. I experienced the same problem on F4 bios and the F7 stable bios; it's missing on F7B. I can't comment on other models, but F7B has remained quite stable for me.
Created an account to assist others and give back the favor.

Pages (2): 1 2 Next