F5F Stay Refreshed Hardware Desktop ASUS X570-F isn't working. VGA and boot LED remain unresponsive.

ASUS X570-F isn't working. VGA and boot LED remain unresponsive.

ASUS X570-F isn't working. VGA and boot LED remain unresponsive.

Pages (2): 1 2 Next
B
BerkSahin
Member
106
01-13-2019, 07:46 PM
#1
This configuration has worked smoothly for nine months. The system was shut down yesterday normally. This morning, when it started up, the board remained stuck in post mode—both the white VGA and green BOOT LEDs illuminated, but no display appeared. I've attempted various fixes: swapped GPUs (using two different PCI slots), changed the CPU to a Ryzen 5 2600, adjusted memory, tried single-card setups, reset the CMOS multiple times, and even connected the display via HDMI instead of DisplayPort. Clearing the CMOS battery helped temporarily. I flashed the BIOS with the latest version and some older ones, but the process always led to the same post state. Occasionally, the board would briefly post, showing a message about VGA card support or CPU fan errors after resetting BIOS settings. In both cases, pressing F1 brought it back to a recognized state. Now I suspect the motherboard—or possibly the BIOS—is the root cause. My understanding of motherboards is limited, so I’m unsure what else to try next. ASUS offered to investigate but said it would take at least ten days. Before accepting their help, I wanted suggestions for something simple to test first that might resolve the problem. Thanks!
B
BerkSahin
01-13-2019, 07:46 PM #1

This configuration has worked smoothly for nine months. The system was shut down yesterday normally. This morning, when it started up, the board remained stuck in post mode—both the white VGA and green BOOT LEDs illuminated, but no display appeared. I've attempted various fixes: swapped GPUs (using two different PCI slots), changed the CPU to a Ryzen 5 2600, adjusted memory, tried single-card setups, reset the CMOS multiple times, and even connected the display via HDMI instead of DisplayPort. Clearing the CMOS battery helped temporarily. I flashed the BIOS with the latest version and some older ones, but the process always led to the same post state. Occasionally, the board would briefly post, showing a message about VGA card support or CPU fan errors after resetting BIOS settings. In both cases, pressing F1 brought it back to a recognized state. Now I suspect the motherboard—or possibly the BIOS—is the root cause. My understanding of motherboards is limited, so I’m unsure what else to try next. ASUS offered to investigate but said it would take at least ten days. Before accepting their help, I wanted suggestions for something simple to test first that might resolve the problem. Thanks!

K
KingDuffers
Junior Member
2
01-15-2019, 07:06 PM
#2
It seems like a pretty flawed build, but only slightly so. It looks like it could be working just fine. That suggests any obvious issues are probably minor. I’m leaning toward thinking a solder joint might be the problem. If it performs well initially, they should run it through several tests. Unless those early successes were with a different component (like a verified GPU or CPU), then inconsistencies will likely appear later.
K
KingDuffers
01-15-2019, 07:06 PM #2

It seems like a pretty flawed build, but only slightly so. It looks like it could be working just fine. That suggests any obvious issues are probably minor. I’m leaning toward thinking a solder joint might be the problem. If it performs well initially, they should run it through several tests. Unless those early successes were with a different component (like a verified GPU or CPU), then inconsistencies will likely appear later.

A
220
01-17-2019, 07:32 AM
#3
I succeeded twice by using the original hardware; one time with only a single memory stick, the other was different but similar. I suspect there might be a problem with the board itself, as the issue persists since last night when it stopped passing the orange DRAM light. I have another machine with a Gigabyte X570 mini ITX board, so I’m considering swapping it out to confirm.
A
AssassinJayden
01-17-2019, 07:32 AM #3

I succeeded twice by using the original hardware; one time with only a single memory stick, the other was different but similar. I suspect there might be a problem with the board itself, as the issue persists since last night when it stopped passing the orange DRAM light. I have another machine with a Gigabyte X570 mini ITX board, so I’m considering swapping it out to confirm.

E
Eagleteamer
Junior Member
11
01-19-2019, 08:49 PM
#4
I’ve resolved the problem by changing the motherboard while keeping all original components. The system now starts properly, indicating the issue was with the Asus board. I adjusted the BIOS version temporarily, and a Gigabyte X570I is functioning well. Windows is still sluggish, but I suspect the problem lies in settings or drivers. It’s time to replace the motherboard.
E
Eagleteamer
01-19-2019, 08:49 PM #4

I’ve resolved the problem by changing the motherboard while keeping all original components. The system now starts properly, indicating the issue was with the Asus board. I adjusted the BIOS version temporarily, and a Gigabyte X570I is functioning well. Windows is still sluggish, but I suspect the problem lies in settings or drivers. It’s time to replace the motherboard.

L
Lorddoom139
Posting Freak
956
01-20-2019, 01:26 AM
#5
It might not be fully resolved yet. The issue seems to be with the "barely doesn’t work" versus "barely works" phrasing. The motherboard could be the culprit, but other factors are possible. It depends on whether you can fix those stutters. Edited January 19, 2022 by Bombastinator
L
Lorddoom139
01-20-2019, 01:26 AM #5

It might not be fully resolved yet. The issue seems to be with the "barely doesn’t work" versus "barely works" phrasing. The motherboard could be the culprit, but other factors are possible. It depends on whether you can fix those stutters. Edited January 19, 2022 by Bombastinator

P
PrestonNguyen
Member
218
01-22-2019, 06:58 PM
#6
I believe you're correct about the need to install the 2600 on the new motherboard for BIOS updates to F30 to support the 5900x. At that time, Windows performed adequately. After booting with the 5900x, Windows became quite slow and prone to stutters but still functional. I later updated Nvidia drivers, followed by Windows drivers (around ten in total, including an AMD update). This process required a restart; now the system is even worse and frequently displays blue screens after logging in. It seems the CPU might be faulty or the drivers are severely compromised. Regarding the other motherboard, I thought it was defective since it remained stuck in post despite different hardware being installed. I feel like I'm battling two separate issues. Update: I successfully logged in and encountered a blue screen beforehand. It might be worth trying to swap the CPUs again to determine if the problems continue. If they are driver-related, the outcome should be similar.
P
PrestonNguyen
01-22-2019, 06:58 PM #6

I believe you're correct about the need to install the 2600 on the new motherboard for BIOS updates to F30 to support the 5900x. At that time, Windows performed adequately. After booting with the 5900x, Windows became quite slow and prone to stutters but still functional. I later updated Nvidia drivers, followed by Windows drivers (around ten in total, including an AMD update). This process required a restart; now the system is even worse and frequently displays blue screens after logging in. It seems the CPU might be faulty or the drivers are severely compromised. Regarding the other motherboard, I thought it was defective since it remained stuck in post despite different hardware being installed. I feel like I'm battling two separate issues. Update: I successfully logged in and encountered a blue screen beforehand. It might be worth trying to swap the CPUs again to determine if the problems continue. If they are driver-related, the outcome should be similar.

A
aDa_
Junior Member
16
01-22-2019, 07:30 PM
#7
Blue screens often lead to small error messages. They might help identify the problem. Crash happens frequently after startup, using a lot of memory in this instance. It seems like a random occurrence. Blue screens are annoying, but some issues are worse—this one was just one of them. Keep moving forward. Edited January 19, 2022 by Bombastinator
A
aDa_
01-22-2019, 07:30 PM #7

Blue screens often lead to small error messages. They might help identify the problem. Crash happens frequently after startup, using a lot of memory in this instance. It seems like a random occurrence. Blue screens are annoying, but some issues are worse—this one was just one of them. Keep moving forward. Edited January 19, 2022 by Bombastinator

B
B_Mathias99
Member
70
01-22-2019, 08:56 PM
#8
I'm not familiar with how blue screens produce minidumps, but I can help you retrieve them. There are tools and methods to capture these logs for analysis. Would you like guidance on that?
B
B_Mathias99
01-22-2019, 08:56 PM #8

I'm not familiar with how blue screens produce minidumps, but I can help you retrieve them. There are tools and methods to capture these logs for analysis. Would you like guidance on that?

G
GynBurst
Member
52
01-23-2019, 04:38 AM
#9
The instructions are available in the highlighted sections of the troubleshooting guides.
G
GynBurst
01-23-2019, 04:38 AM #9

The instructions are available in the highlighted sections of the troubleshooting guides.

W
WreckerSG
Member
201
01-23-2019, 12:29 PM
#10
That's great to hear! Everything seems to be running smoothly now. I'll keep an eye out for any further issues.
W
WreckerSG
01-23-2019, 12:29 PM #10

That's great to hear! Everything seems to be running smoothly now. I'll keep an eye out for any further issues.

Pages (2): 1 2 Next