Gigabyte am5 motherboard ddr5 not posting when rebooting

[Finnedsgang]

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.

Do you know the correct values for this?

p.s. thanks for your help

 

[Launcestonian]

Do you know the correct values for this?

p.s. thanks for your help

Dial in 1.35v for each of these as a minimum except set SoC to no more than 1.25v for now or even leave it on auto, if no success, shift DRAM & MEMIO up to the next increment - should be something like 1.36v or thereabouts. Sometimes you gotta account for voltage droop. But 1.35v should get it booting.
If you can get into windows, run windows memory diagnostic app as a bare minimum for daily windows use, but I strongly recommend more RAM testing apart from just that.

 

[sanpechuda]

I have a problem similar to you. This is my setup
- CPU ryzen5 7600
- MB gigabyte b650m-d3hp (latest bios F24c)
- ram corsair cmk32gx5m2b5600c40 (2*16) native4800/ xmp5600
- VGA RX480
- Windows 11
- cooling THERMALTAKE TH240 V2 ARGB SYNC

When I use XMP-5600
- After setting XMP in bios and then save&reboot, I found that most of it can boot Windows the first time.
- If I click shut down Windows, I still can power on to boot Windows.
- However, if I clicked restart Windows, I could not boot Windows or enter bios anymore. The display is black (no signal) and the LED on the VGA card is turned off too.
- While restarting, I heard the sound of one beep from a buzzer.
- The only solution to enter Bios again is to reset CMOS, then back to default bios at native 4800.

When I use native-4800
- If I click shut down Windows, I still can power on to boot Windows.
- if I clicked restart Windows, sometimes I could not boot Windows. However, this is different from the XMP case. I can only shut it down by holding the power button, and then power it on again. This is always guaranteed to boot Windows.
- While restarting, I did not hear any sound from a buzzer. excluding the sound of a short beep when success POST.

 

[Caring1]

I have a problem similar to you. This is my setup
- CPU ryzen5 7600
- MB gigabyte b650m-d3hp (latest bios F24c)
- ram corsair cmk32gx5m2b5600c40 (2*16) native4800/ xmp5600
- VGA RX480
- Windows 11
- cooling THERMALTAKE TH240 V2 ARGB SYNC

When I use XMP-5600
- After setting XMP in bios and then save&reboot, I found that most of it can boot Windows the first time.
- If I click shut down Windows, I still can power on to boot Windows.
- However, if I clicked restart Windows, I could not boot Windows or enter bios anymore. The display is black (no signal) and the LED on the VGA card is turned off too.
- While restarting, I heard the sound of one beep from a buzzer.
- The only solution to enter Bios again is to reset CMOS, then back to default bios at native 4800.

When I use native-4800
- If I click shut down Windows, I still can power on to boot Windows.
- if I clicked restart Windows, sometimes I could not boot Windows. However, this is different from the XMP case. I can only shut it down by holding the power button, and then power it on again. This is always guaranteed to boot Windows.
- While restarting, I did not hear any sound from a buzzer. excluding the sound of a short beep when success POST.

Probably a fault with the old GPU, the rx480.

 

[ir_cow]

Probably a fault with the old GPU, the rx480.

Can't be if it works without XMP

 

[Caring1]

Can't be if it works without XMP

I considered that, but he's resetting the CMOS, not just setting the Bios to default values.
It's only a guess.

 

[Super Firm Tofu]

I have/had the same problem with my X670 Aorus Elite AX (with modern GPUs, both Radeon and Nvidia) so this is definitely a thing with GB boards.

 

[sanpechuda]

Probably a fault with the old GPU, the rx480

When the problem happened on the XMP-5600 case
- I have tried to remove rx480 and use only igpu of CPU, but the problem still exists.
- I have also tried to remove all unnecessary devices (have only MB+cpu+ram, no HD, no rx480) to check if I can enter BIOS. then the display still has no signal (cannot enter bios).
- Sometimes bios can enter recovery mode with itself, but sometimes not. The final solution is to reset CMOS.

For more information while using in native mode-4800
- Overall use is good, windows is stable, and it has never had BSOD.
- There is something strange about the sleep state. I found the LED of the cooling CPU fan (connected from D_LED2 on MB) is sometimes turned off, and sometimes not turned off. (while the cooling fan is always turned off). However it does not affect to the wake-up process, I can always wake up to Windows.

p.s.
- I have already checked the RAM kit with a memory test of Windows, and no defect was found.
- Someone said that the problem is at cooling RGB led, he recommended removing the D_LED2 line. I have tried but the issue still exists.
- I've been wondering about the rx480 driver issue as well. However, if I can get into Windows, in the device manager, I can see both VGA adapters with good properties in both 4800 and 5600 modes. The problem with 5600 is that I can't restart it (the problem will happen instantly after restart (except shut down) and must be fixed by clearing CMOS only).
- Now I feel like I'm forced to use it in 4800 native with default bios mode, I can use it smoothly. There's just a slight weirdness about the sleep state as I mentioned above.

 

[sanpechuda]

The latest bios F30 (released 24/May/2024) still has not fixed the issue
- Update AMD AGESA 1.1.7.0 Patch A for next-gen. Ryzen processors support

 

[Finnedsgang]

I give up. Nothing works. I also updated to latest f30 bios of 4 days ago.

Based on the experience of so many people I think amd have a very big big problem with this platform.

I’m thinking right now to switch back to Intel for the next upgrade and not because of the performance of a oced ram but because honestly I don’t think it’s fair for a company like Amd to leave the platform in such a state….

 

[Waldorf]

@Finnedsgang
prepare a usb stick for bios-flashback with latest bios.

reset bios to default, shutdown, and use the flashback with the same bios, after its done, dont let it boot, load defaults, reboot, and do a "normal" flash (same bios).
force shutdown after loading defaults again, remove psu plug, remove battery, discharge residue (hold power button for 10s) and leave it out for 1-2h.
battery in, psu plug in, and power up, THEN try EXPO settings.

 

[Legacy Ivy Terascale]

might be the CMOS battery

 

[Waldorf]

@Legacy Ivy Terascale
if you had read the first post, OP stated 2 MB where used, so both have bad batteries? right.

 

[kapone32]

@Legacy Ivy Terascale
if you had read the first post, OP stated 2 MB where used, so both have bad batteries? right.

It's not that the battery is bad. There is a bug with GB (some) where if you update the BIOS. You can face an issue where the board seems to be on but nothing is happening. If you unplug the PC and remove the battery for up to 2 minutes so that the power drains it resets the board. I had a X470 Gaming 7 that had that issue, I let it sit for 3 years and one day I tried that hack and touche the board was back.

 

[Waldorf]

@kapone32
sure, but then say so (like you did), and not just lazily say "its the battery".

besides that one of the steps i recommended for fix, included removing battery and leaving it out for a while..

 

[Finnedsgang]

Dial in 1.35v for each of these as a minimum except set SoC to no more than 1.25v for now or even leave it on auto, if no success, shift DRAM & MEMIO up to the next increment - should be something like 1.36v or thereabouts. Sometimes you gotta account for voltage droop. But 1.35v should get it booting.
If you can get into windows, run windows memory diagnostic app as a bare minimum for daily windows use, but I strongly recommend more RAM testing apart from just that.

Hey! Im trying to manually adjust the voltage and timings manually (all) and don’t want to talk too early but seems it’s working !

I’ve the vcore soc on 1,35 honestly now, I will try to lower to 1.30 and .25 (as it runs hot!) and see if it’s stable. But WTF why Amd ? Why?

UPDATE 05/31/24
Maybe i Spoke too much, yesterday i had a hanging during the reboot

The ram test were all ok...

 

[sanpechuda]

Hey! Im trying to manually adjust the voltage and timings manually (all) and don’t want to talk too early but seems it’s working !

I’ve the vcore soc on 1,35 honestly now, I will try to lower to 1.30 and .25 (as it runs hot!) and see if it’s stable. But WTF why Amd ? Why?

UPDATE 05/31/24
Maybe i Spoke too much, yesterday i had a hanging during the reboot

The ram test were all ok...

When you restart Windows in XMP mode, do you have a problem rebooting (black screen and cannot enter BIOS)?
However, if you restart Windows in native mode(4800/5200), is it ok?

 

[Finnedsgang]

Exactly

 

[Waldorf]

@Finnedsgang
you want help, yet didnt care to fill out your sys info (select to make it visible).
ignoring that 1.35

 

[Panther_Seraphin]

SoC at 1.35 is chip killing territory do not use it beyond benchmarking!

The behaviour you are experiencing is definately a failed RAM OC.
Can I ask if Memory Context Restore is enabled when this is happening? If it is on please turn it off for some testing. I would like to see if the board will reliably reboot at that point. In theory it should be retrying to stabilise timings with it off at every reboot. Be advised the reboot time will be long (up to 5 minutes per reboot)

VDIMM can be pushed fairly high on DDR5 so putting that up to around 1.4 isnt terrible and I had it behaving like you describe with it down around 1.3 at my timings.

 

[Launcestonian]

Hey! Im trying to manually adjust the voltage and timings manually (all) and don’t want to talk too early but seems it’s working !

I’ve the vcore soc on 1,35 honestly now, I will try to lower to 1.30 and .25 (as it runs hot!) and see if it’s stable. But WTF why Amd ? Why?

UPDATE 05/31/24
Maybe i Spoke too much, yesterday i had a hanging during the reboot

The ram test were all ok...

The only way you could be getting 1.35 SOC as an option is with an old bios. AMD chopped that out & max was to be 1.30, there was a fiasco of sorts about this problem quite some time ago.
With more information that you provided, updating the bios is an urgent priority imo. Then see how the testing goes.

 

[Finnedsgang]

My mistake, I had on 1,30.
now on 1,25v and some times now when rebooting it stays on the windows cycling logo.I’m on the latest available Bios f30 (24th of may release)

Its quite different from the past as previously it stopped without posting and with dram/cpu mb led blinking

UPDATE: I tried to put soc on auto, but at first I was able to enter in widows. But it was very unstable and slow (menu start not responsive, 5 second to open a folder ecc) then when I rebooted the blinking led returned

I’m beginning to think it’s connected to this value (ps I’ve 1.35v on the other indicators, 6000mhz manual on dram clocks, and timings set as the expo ones, 36-36-36-96

@Finnedsgang
you want help, yet didnt care to fill out your sys info (select to make it visible).
.., ignoring that 1.35

Hi, sorry for that, where I have to add my sys info? In the first step, I added the mb and memory sticks used. The cpu is a 7900x and the gpu a 4090
Fsp Hydro 1000w as PSU

 

[Waldorf]

@Finnedsgang
not in post, meant your profile. go to your account > system specs, select yes in the first row, then add all your hw info.

 

[Finnedsgang]

@Finnedsgang
not in post, meant your profile. go to your account > system specs, select yes in the first row, then add all your hw info.

Done.

btw. System doesn’t seem stable anymore. tried auto, 1.25, 1.26 and 1.27 v on soc, but windows is unresponsive

 

[Waldorf]

can you set it on auto, and use an offset (+) and add little to the point where it works?

cant remember: increased vdimm to max allowed for kit?