Gigabyte am5 motherboard ddr5 not posting when rebooting

[Finnedsgang]

Hi everyone I’ve a big problem with my motherboard and ddr 5 combo
Gigabyte b650 Aorus elite X ax + gskill trident Z rgb ddr5 6000mhz cl36 (mb officially support memories)

When I try to restart the pc, and xmp is enabled, it never posts. Bios is not loading, no screen, stays there forever with DRam/Cpu led on mb blinking alternatively and fan spinning. When in th I have to shutdown the pc manually (long pressing the button) and this time it posts normally with xmp enabled. This behavior is non present with xmp disabled, but it acts like this also when trying to update the bios.

I’ve tried different ram, and also a different mb but I always have this issue. The only thing unchanged is the cpu.
I thought it was a memory training problem, but it’s always like this, also if I disable memory context memory

I also tried to disable xmp and running at 6000 manually, but I have the same issue

 

[TheLostSwede]

Does this happen when you run basic JEDEC 4800 MHz specs?

 

[Finnedsgang]

No, if I set all to default, it works fine except the bios update, for that I need to use qflash+ button otherwise at the reboot it makes the same thing

 

[jxdking]

I believe AGESA 1.0.0.7c has fixed this issue. However, this issue might re-occur with some recent bios. Find a non-beta bios with AGESA 1.0.0.7c.

Also, not all DDR5 kits doing that. Only Samsung or G.Skill kit are affected with this bug. You may consider returning the ram kit to get a decent 6000MT/s CL30 one, from other brands.

 

[Finnedsgang]

Any suggestion on a valid kit ?

This is my fw. Seems the latest one

 

[WonkoTheSaneUK]

Any suggestion on a valid kit ?

I've had no issues with Kingston's Fury Beast DDR5.
But I'm on a Gigabyte X670 Aorus Pro X with BIOS F24c

 

[jxdking]

Any suggestion on a valid kit ?

This is my fw. Seems the latest one

Try F5a.

 

[Finnedsgang]

I will try this bios, but had the same issue with the default one. F1 something

 

[ir_cow]

I believe AGESA 1.0.0.7c has fixed this issue. However, this issue might re-occur with some recent bios. Find a non-beta bios with AGESA 1.0.0.7c.

Also, not all DDR5 kits doing that. Only Samsung or G.Skill kit are affected with this bug. You may consider returning the ram kit to get a decent 6000MT/s CL30 one, from other brands.

That does remind me I had a similar problem with a few kits back in December. None of them where G.SKILL or Samsung. Only on 1.0.0.7c though. Newer BIOS didn't give me this problem. Might just be a Gigabyte thing. I suggest updating to the newest BIOS and see if that fixes it.

 

[Finnedsgang]

That does remind me I had a similar problem with a few kits back in December. None of them where G.SKILL or Samsung. Only on 1.0.0.7c though. Newer BIOS didn't give me this problem. Might just be a Gigabyte thing. I suggest updating to the newest BIOS and see if that fixes it.

Unfortunately I’m on the latest bios

 

[kapone32]

Try to remove the MB battery for about 1 minute and put it back in. Gigabyte boards have a notorious bug where if you update the BIOs or do a cold shutdown that when you try again the battery does not have the info and therefore refuses to turn the board on. Try that and let us know what happened.

 

[Finnedsgang]

Try to remove the MB battery for about 1 minute and put it back in. Gigabyte boards have a notorious bug where if you update the BIOs or do a cold shutdown that when you try again the battery does not have the info and therefore refuses to turn the board on. Try that and let us know what happened.

Tried this, but didn't solved the issue. After the first reboot, using XMP, endless blinking of two led as before.

 

[kapone32]

Tried this, but didn't solved the issue. After the first reboot, using XMP, endless blinking of two led as before

Ok at least it is registering. Another question would be, does the board have Dual Bios with a switch? At this point I would try to reset the BIOS using the USB Flash. Of course there is also the fact that AM5 boards are optimized for Expo and not XMP. I can't tell you if that is the issue but I have no problems. Just as a side bar did you do the first or 2nd XMP profile?

 

[Finnedsgang]

My fault, i used EXPO , not XMP . My DDR kit is EXPO certified.
No double Bios, from what i can read in the specifications, the motherboard is this one

The strange thing is that the EXPO is active once you shutdown completely after the failed reboot.

 

[jxdking]

My fault, i used EXPO , not XMP . My DDR kit is EXPO certified.
No double Bios, from what i can read in the specifications, the motherboard is this one

The strange thing is that the EXPO is active once you shutdown completely after the failed reboot.

Did you try F5a bios?

F5c is for the next gen Zen5 support, it may not be mature yet.

 

[The Krull]

hello, only a question: hard reset or software reset? ty for your time

 

[Finnedsgang]

Did you try F5a bios?

F5c is for the next gen Zen5 support, it may not be mature yet.

Yes, just installed. When I try to reboot or shut down the pc (Start>restart or shutdown system) the system close Windows10 programs and folders, and all the leds on the fans, and then it stays like this in the pic forever. (More than 1 hour before I manually shutted down pushing 3s the turnon button on the case

So

hello, only a question: hard reset or software reset? ty for your time

Soft reset, via windows (Start button> Restart/ shutdown)

 

[jxdking]

Yes, just installed. When I try to reboot or shut down the pc (Start>restart or shutdown system) the system close Windows10 programs and folders, and all the leds on the fans, and then it stays like this in the pic forever. (More than 1 hour before I manually shutted down pushing 3s the turnon button on the case

So

Soft reset, via windows (Start button> Restart/ shutdown)

I got this issue on both MSI and ASUS boards with some G.Skill Samsung kits before. Bios update at some point fixed this issue. Also swapping out the memory kit with other Hynix based kits also fixed the reboot issue. Is that possible to try with other memory kits?

 

[Finnedsgang]

I just ordered this one kit Corsair Dominator Platinum CMT32GX5M2X6000C36, is overpriced, but it's the only kit sold from amazon (in case it doesn't work I can ask for a refund easily) with Hynix modules and in the compatibility List.

​

 

[Finnedsgang]

Just installed the new kit, and i have the same issue. When I click on reboot from Windows, Windows shut down and then the system goes in a catathonic state. DRAM and CPU leds on the MB blinking alternatively. The fans are spinning at max speed. Don't know if it's a symptom of something but when the PC boots normally, all the RGB leds are in rainbow mode at first, than when windows starts along with RGB Aura from GIgabyte, the LEDS become White as per my indication. When I reboot, the RGB leds are staying white.

i've another ram kit arriving tomorrow, Kingston FURY Beast 32GB (2x16GB) 6000MT/s DDR5 CL36 KF560C36BBEAK2-32 and will have a check to them.

​

 

[ir_cow]

How long are you waiting after? The boot cycling can easily be 1 minute after enabling XMP/EXPO for the first time. Also are they in the correct slots?

 

[Finnedsgang]

about 10 minutes , I will leave for the entire night just to be sure...
Slots are A2-B2 for dual channel

Just returned after some hours and was still in the same status. LED blinking, and no posting

 

[ir_cow]

You don't need more than 1 min really :/ . So you tried 3 memory kits so far and a different motherboard?

 

[Finnedsgang]

You don't need more than 1 min really :/ . So you tried 3 memory kits so far and a different motherboard?

Exactly
I found a topic on Reddit with a lot of guys that have the same errors than me.
Seems a very known error with all major mb brands except asrock

https://www.reddit.com/r/AMDHelp/s/QHhpHkND7l

Seems the only one who found a fix is doing it disabling memory context restore and changing the memory fail retry count to 3/4 or 0. While I know where memory context is (I tied disabling many times) I don’t know where to change the memory fail retry count. Any idea ?
what does memory fail retry count do

 

[ir_cow]

The other option you can try is instead of using auto voltages, manually set the DRAM, SoC and MEMIO voltage. I suspect of or more of these are not getting set correctly on auto causing it to not boot. I get the same results for memory overclocking when it fails to boot.