F5F Stay Refreshed Hardware Desktop Error encountered during startup. Assembly process failed.

Error encountered during startup. Assembly process failed.

Error encountered during startup. Assembly process failed.

W
Wolkyr
Junior Member
4
11-18-2024, 07:02 PM
#1
I've shared this with a good friend in the PC Master Race. I gathered all components, checked online listings, and sent him everything needed to place an order. After a few days, the parts arrived. We met up, had a drink, and started assembling. The machine booted but didn't start properly. The MOBO kept flashing a red LED in a specific pattern: CPU LED, DRAM LED, CPU LED—staying on the CPU red light forever. I tried reseating RAM, swapping RAM sticks, rewiring power connectors, and even checking for bent pins or BIOS issues. I also looked into BIOS updates via QFLASH, but the PC would only boot for a few seconds before shutting down. My main theory is the RAM was clocked at 6000MHz, and the 1.0 revision of MOBO might not support those speeds with the default BIOS. Fortunately, it's a Gigabyte model that usually allows BIOS updates without direct access. I attempted clearing the CMOS, but it didn't help much. I'm open to any tips or fixes you have. Here are my specs: CPU—AMD Ryzen 7800X3D; Fan—Noctua NH-U-12S; MOBO—Gigabyte x670; RAM—Corsair 2x32GB, 6000MHz CL30 DDR5; SSD—Samsung 990 2TB NVMe; GPU—4060TI; PSU—Corsair RM850e; Case—Thermaltake V200.
W
Wolkyr
11-18-2024, 07:02 PM #1

I've shared this with a good friend in the PC Master Race. I gathered all components, checked online listings, and sent him everything needed to place an order. After a few days, the parts arrived. We met up, had a drink, and started assembling. The machine booted but didn't start properly. The MOBO kept flashing a red LED in a specific pattern: CPU LED, DRAM LED, CPU LED—staying on the CPU red light forever. I tried reseating RAM, swapping RAM sticks, rewiring power connectors, and even checking for bent pins or BIOS issues. I also looked into BIOS updates via QFLASH, but the PC would only boot for a few seconds before shutting down. My main theory is the RAM was clocked at 6000MHz, and the 1.0 revision of MOBO might not support those speeds with the default BIOS. Fortunately, it's a Gigabyte model that usually allows BIOS updates without direct access. I attempted clearing the CMOS, but it didn't help much. I'm open to any tips or fixes you have. Here are my specs: CPU—AMD Ryzen 7800X3D; Fan—Noctua NH-U-12S; MOBO—Gigabyte x670; RAM—Corsair 2x32GB, 6000MHz CL30 DDR5; SSD—Samsung 990 2TB NVMe; GPU—4060TI; PSU—Corsair RM850e; Case—Thermaltake V200.

M
maddisonteague
Junior Member
3
11-18-2024, 07:02 PM
#2
It's not correct. The RAM serves as the base speed in DDR5, but once you go overclock it, you need to identify the exact model for the motherboard properly.
M
maddisonteague
11-18-2024, 07:02 PM #2

It's not correct. The RAM serves as the base speed in DDR5, but once you go overclock it, you need to identify the exact model for the motherboard properly.

G
gemoore
Junior Member
46
11-18-2024, 07:02 PM
#3
This suggests a dead motherboard or an incorrectly configured flash drive for Q-Flash. It might stem from the motherboard rejecting the flash drive, mismatched BIOS settings (like WiFi vs. regular mode), or incorrect file configurations.
G
gemoore
11-18-2024, 07:02 PM #3

This suggests a dead motherboard or an incorrectly configured flash drive for Q-Flash. It might stem from the motherboard rejecting the flash drive, mismatched BIOS settings (like WiFi vs. regular mode), or incorrect file configurations.

T
tydall
Member
137
11-18-2024, 07:02 PM
#4
I’m still trying to understand your point. The full name of the MOBO is x670 Aorus Elite AX, and I wasn’t certain if XMP was set up automatically. That was just an educated guess.
T
tydall
11-18-2024, 07:02 PM #4

I’m still trying to understand your point. The full name of the MOBO is x670 Aorus Elite AX, and I wasn’t certain if XMP was set up automatically. That was just an educated guess.

S
saukeuchiuchi
Senior Member
621
11-18-2024, 07:02 PM
#5
I've noticed this on other forums too. I attempted a USB 2.0 drive again, opting for a 3.0 model instead. I downloaded the driver from Gigabytes for the right mainboard and double-checked everything. Would a dead MOBO still display different LED codes based on installed components? Specifically, I realized I hadn't reconnected the CPU power connectors after installing the cooling solution. The MOBO only showed the CPU LED and skipped the DRAM LED, which helped me identify my mistake quickly.
S
saukeuchiuchi
11-18-2024, 07:02 PM #5

I've noticed this on other forums too. I attempted a USB 2.0 drive again, opting for a 3.0 model instead. I downloaded the driver from Gigabytes for the right mainboard and double-checked everything. Would a dead MOBO still display different LED codes based on installed components? Specifically, I realized I hadn't reconnected the CPU power connectors after installing the cooling solution. The MOBO only showed the CPU LED and skipped the DRAM LED, which helped me identify my mistake quickly.

W
WastedSpace
Member
156
11-18-2024, 07:02 PM
#6
I've experienced it before. It's rare, yet it occurs occasionally.
W
WastedSpace
11-18-2024, 07:02 PM #6

I've experienced it before. It's rare, yet it occurs occasionally.

X
x15Ghost15x
Member
183
11-18-2024, 07:02 PM
#7
keep bios names short and follow 7+3 ascii rules. Use fat32 format for the USB drive.
X
x15Ghost15x
11-18-2024, 07:02 PM #7

keep bios names short and follow 7+3 ascii rules. Use fat32 format for the USB drive.

I
IkBenHetBram
Senior Member
735
11-18-2024, 07:02 PM
#8
I'll remember this. I'm planning to talk to my friend later today to try and resolve the issue
I
IkBenHetBram
11-18-2024, 07:02 PM #8

I'll remember this. I'm planning to talk to my friend later today to try and resolve the issue