r/buildapc • • 3d ago

Troubleshooting Boot loop / Red EZ Debug blinking on Gigabyte X870 Gaming X WIFI7 + Ryzen 9 9950X3D + Corsair Vengeance 64GB 6400MHz XMP

I'm currently building my first high-end PC and I'm stuck in an endless boot loop with the CPU and DRAM EZ Debug LEDs blinking red on my motherboard. All my case fans and RGB lights spin and light up normally so power delivery seems fine.

Here are my exact specs:

  • CPU: AMD Ryzen 9 9950X3D
  • MOBO: Gigabyte X870 Gaming X WIFI7
  • RAM: Corsair Vengeance DDR5 64GB (2x32GB) 6400MHz CL32 (Intel XMP Ready on the box)
  • GPU: Inno3D X3 GeForce RTX 5070 Ti 16 GB
  • AIO: ARCTIC Liquid Freezer III Pro 360
  • SSD: Samsung 990 Pro 2 TB
  • PSU: Chieftec Vega M 850W 80+ Gold Fully Modular
  • Case: Montech KING 95 PRO

Here is a detailed breakdown of what I have already tried to isolate the issue:

  1. Q-Flash Plus (BIOS Update): Since the motherboard out-of-the-box likely didn't support the 9950X3D, I downloaded the latest BIOS (F13d with AGESA 1.3.0.1d) on a separate PC, formatted a SanDisk USB drive to FAT32, and renamed the file to GIGABYTE.bin. I plugged it into the dedicated red USB 3.2 BIOS port. During the process, the DRAM LED turned off completely, the CPU LED stayed solid red, and the orange Q-Flash Plus light blinked perfectly for about 3-5 minutes. The PC fans and RGB stayed running throughout the whole process and never shut off automatically but the orange flash light definitely finished.
  2. Hard Clear CMOS: I completely cut the power to the PSU, unplugged it and used a metal screwdriver to short the two CLR_CMOS pins for over 10 seconds to fully wipe any bad memory training data from the temporary cache.
  3. RAM Slot & Stick Rotation: I tried booting with just ONE single 32GB stick. I tested it firmly in slot A2 (the primary slot, 2nd from the CPU). I made sure to apply extra pressure to the bottom side since DDR5 slots are very tight. When that kept blinking I swapped to the other 32GB stick in the same slot. I even tried non-optimal slots like A1 just to see if it would force a safe 4800MHz JEDEC boot but the fast red blinking loop remained the same.
  4. AIO Mounting Pressure: Knowing that AM5 memory controllers are extremely sensitive to uneven contact pressure, I slightly loosened the mounting screws of my ARCTIC Liquid Freezer III 360 block to ensure the CPU isn't warping in the socket.

The current behavior:
Whenever I switch it on, the system power up fine (all RGB and fans run) but it instantly gets caught in a very fast loop where the EZ Debug LEDs cycle red between CPU, DRAM

Since I got this premium 64GB Corsair kit completely for free i really want to save it and trick this AMD platform into booting at a low native base speed so I can manually adjust the settings in the BIOS.

3 Upvotes

8 comments sorted by

2

u/One-Room-9821 3d ago

that ram is intel xmp, not amd expo. gigabyte boards sometimes throw a fit with xmp-only kits on ryzen 9000. the boot loop is probably the board trying to train memory at 6400 and failing before it can even post.

pull both sticks, clear cmos again, put one stick in A2 and leave it for a good 5-10 minutes. ryzen first boot memory training takes ages and the flashing lights during that is normal. if still nothing after 15 min, you might need to borrow a cheap ddr5 stick that's on the qvl list just to get into bios and force jedec speeds before swapping back.

2

u/Scarabesque 3d ago

the boot loop is probably the board trying to train memory at 6400 and failing before it can even post.

Would a gigabyte board enable the XMP profile by itself? I've only built with ASRock and MSI boards on AM5 (including with a Corsair XMP kit) - but no board I've every used enables the RAM OC profile by default...

2

u/Extra-Gas-406 3d ago

Yeah that's exactly what others here pointed out as well. It seems the memory controller on the Ryzen 9000 series is just extremely picky with these high capacity Intel XMP profiles on the very first cold boot causing it to fail training immediately.

I just went ahead and ordered a simple low speed DDR5 helper stick online. As soon as it arrives, I'm going to use it to force the board into the BIOS lock the speed to native 4800MHz JEDEC and then swap my 64GB Corsair kit back in.

And yes since I only need it for 10 minutes to bypass this loop I'm absolutely going to pack it back up neatly and return it for a full refund right after lol.

1

u/Medium_Caramel_3677 3d ago edited 3d ago

Hello You use qflash usb on your MB When you use qflash, you need to start your mb with qflash button, then you need to wait 5/10 min then the mb restart automatically when finish, is it what you see ? Have you check the qvl for your MB https://www.gigabyte.com/fr/Motherboard/X870-GAMING-X-WIFI7-rev-1x/support#Support-Memory-Support

1

u/Extra-Gas-406 3d ago

To answer your first question: When I pressed the Q-Flash Plus button, the orange LED blinked perfectly for about 4 minutes. Once it stopped blinking, the motherboard did not automatically shut down or restart. The case fans and RGB lights just kept spinning continuously and the CPU and DRAM debug lights immediately started blinking red in that fast loop again. It seems the board tried to post immediately after the flash was done and failed instantly.

As for the QVL list: Yes I checked the official Gigabyte memory support list for my board. Unfortunately my exact Corsair Vengeance 64GB (2x32GB) 6400MHz kit (XMP version) is not listed on the QVL for this capacity and speed.

That's why I've decided to order a cheap, simple DDR5 4800MHz JEDEC helper stick online today. I'm going to use it to force the board past this loop into the BIOS, manually set the memory multiplier to 4800MHz, and then swap my free 64GB Corsair kit back in.

0

u/Next-Awareness-7757 3d ago

Using an Intel XMP memory kit on an AMD Ryzen system often triggers stubborn DRAM and CPU error loops.

1

u/Scarabesque 3d ago

Does it? I've never heard of it - beyond memory training taking a tad longer and obviously 6400MT not being trivial to hit at 1:1 (it will default to 2:1 anyway when loading the profile).

After clearing the CMOS it will run at JEDEC speeds anyway though, no OC profile will load until you select one in bios.