Gigabyte am5 motherboard ddr5 not posting when rebooting

[DemomanCA]

@DemomanCA which issue? this thread of full of different things.

Having the same issue as OP, on soft restart only, CPU and Mem ez debug lights immediately start flashing alternatively,

Reset the cmos first, then do a bios reflash, seeing a lot of gigabyte mobos being bad recently.

Yeah, done this, Tried with F8, F31, F32f (and F32d, but it's been pulled now). Even did the battery pull suggested up the thread a bit.

Unstable during memory training most likely. But when it posts, get into windows, is it at XMP or defaults?

I was thinking this, but it's like it doesn't even get to that, it immediatly start flashing alternativly between CPU and DRAM lights, with no bios codes (the code display doesn't even turn on). I've played with mem oc before, and it usually locks on 15 bios code when I push it too far, which makes sense, that's the code just after the northbridge init.


I'm actually starting to think something else is at play here. A new thing it's doing now is on a cold start, hitting the power button lights up the RGB, and spins some of the fans, but not all of them. It sits in this state until I push the power button again, at which point the remaining fans spin up, the BIOS code display lights up and starts outputting codes, and it boots fine. Maybe there was a ITE flash or something in between all this that went wrong, given the fans are doing weird stuff, and one of the bios updates mentions improved fan speed support.

I'll keep digging.

 

[RJARRRPCGP]

I'm actually starting to think something else is at play here. A new thing it's doing now is on a cold start, hitting the power button lights up the RGB, and spins some of the fans, but not all of them. It sits in this state until I push the power button again, at which point the remaining fans spin up

Were you able to update the BIOS? If that's with the BIOS update that's supposed to fix the fan issue, then I would check the PSU and test it with a different PSU.
If a known good-spec'ed PSU, then that could be a rare case of a bad PSU cap. I know that the symptom of having to press the power button multiple times, has been associated with bad PSU caps.

 

[eidairaman1]

Were you able to update the BIOS? If that's with the BIOS update that's supposed to fix the fan issue, then I would check the PSU and test it with a different PSU.
If a known good-spec'ed PSU, then that could be a rare case of a bad PSU cap. I know that the symptom of having to press the power button multiple times, has been associated with bad PSU caps.

Yup not booting up from cold is a sign for sure

 

[DemomanCA]

Were you able to update the BIOS? If that's with the BIOS update that's supposed to fix the fan issue, then I would check the PSU and test it with a different PSU.
If a known good-spec'ed PSU, then that could be a rare case of a bad PSU cap. I know that the symptom of having to press the power button multiple times, has been associated with bad PSU caps.

Yeah, I can reflash bios's. Just need to:
Reset to defaults, restart, hangs with flashing lights
Hold power, then power up again
Get into bios, initiate bios update
Off it goes, new bios loads.
Touch ANYTHING, boom, flashy lights on soft reset.

 

[Launcestonian]

That totally is bollocks, might aswell sell it for donor parts only.

Got it sorted. Method > redownload bios > use another USB port > in Q-Flash menu - disable "Keep DMI data" check box... goes ahead & does what it is suppose to do.

 

[DemomanCA]

Got it sorted. Method > redownload bios > use another USB port > in Q-Flash menu - disable "Keep DMI data" check box... goes ahead & does what it is suppose to do.

Hm, I haven’t technically tried this method.

 

[eidairaman1]

Got it sorted. Method > redownload bios > use another USB port > in Q-Flash menu - disable "Keep DMI data" check box... goes ahead & does what it is suppose to do.

Sounds like that board is a pita

 

[DemomanCA]

Rounding off my experience here (cause I hate it when I search forums and the ending's not there).

I think my mobo is cooked. Tried another CPU, different ram, and it's the same thing.

I really don't want to hang a B650E Tachyon on my display shelf.

 

[RJARRRPCGP]

I think my mobo is cooked. Tried another CPU, different ram, and it's the same thing.

I really don't want to hang a B650E Tachyon on my display shelf.

Yeah, at this point, I suspect a faulty SMD component of unknown on the motherboard.

 

[eidairaman1]

Rounding off my experience here (cause I hate it when I search forums and the ending's not there).

I think my mobo is cooked. Tried another CPU, different ram, and it's the same thing.

I really don't want to hang a B650E Tachyon on my display shelf.

Only options:

Frame it.

Send it to a pcb repair place like northridgefix.

Sell it as a cannibalization motherboard.

 

[DemomanCA]

Yeah, although hunting down what exactly is fried would be a nightmare I think, plus I'm in Aus, so I'd say repairs/postage would be approaching new mobo territory

 

[Launcestonian]

Sounds like that board is a pita

It was last year, but better now although no board is perfect.

Rounding off my experience here (cause I hate it when I search forums and the ending's not there).

I think my mobo is cooked. Tried another CPU, different ram, and it's the same thing.

I really don't want to hang a B650E Tachyon on my display shelf.

That's why I avoid the E versions of newer generation AMD chipsets. For my end usage the extra connectivity they offer is not worth the inevitable extra board wiring complexity - more working components, more can go wrong.

 

[danc]

Rounding off my experience here (cause I hate it when I search forums and the ending's not there).

I think my mobo is cooked. Tried another CPU, different ram, and it's the same thing.

I really don't want to hang a B650E Tachyon on my display shelf.

tachyon b650e is a prized board. it is up there with asus gene, well maybe a bit less because asus is still tops with amd bios update.

the warm reboot problem is probably caused by you running some monitoring software in windows. i think this bug was introduced in some amd agesa update.

asus made their own workaround in their newer bios. they are the only ones who did this so far while pending for amd to fix it.

ASUS ROG Crosshair X670E Overclocking & Discussion...

I might as well start this thread now. Initially it will be sort of a placeholder as final specs are yet to be revealed. What we know is; for starters there will be two ASUS Crosshair boards, the X670E HERO and the X670E EXTREME, here is a recent stream from Asus North America presenting both...

www.overclock.net

for gigabtye, i guess you dont do warm reboot or not use monitoring software from asus, corsair, lian li, hwinfo.

 

[eidairaman1]

Its been a rash of GA boards having the problem

 

[danc]

Its been a rash of GA boards having the problem

not just GA, i think all AM5 boards have this problem, somewhere along the way, this happens, probably a mix of agesa, windows updates and monitoring software sdk

Asus hinted as much so

ASUS ROG Crosshair X670E Overclocking & Discussion...

I might as well start this thread now. Initially it will be sort of a placeholder as final specs are yet to be revealed. What we know is; for starters there will be two ASUS Crosshair boards, the X670E HERO and the X670E EXTREME, here is a recent stream from Asus North America presenting both...

www.overclock.net

 

[Launcestonian]

not just GA, i think all AM5 boards have this problem, somewhere along the way, this happens, probably a mix of agesa, windows updates and monitoring software sdk

Asus hinted as much so

ASUS ROG Crosshair X670E Overclocking & Discussion...

I might as well start this thread now. Initially it will be sort of a placeholder as final specs are yet to be revealed. What we know is; for starters there will be two ASUS Crosshair boards, the X670E HERO and the X670E EXTREME, here is a recent stream from Asus North America presenting both...

www.overclock.net

Still better than using Arrow lake platform.

 

[Harlow]

When I try to restart the pc, and xmp is enabled, it never posts.

I suggest checking stability by setting EXPO to lower speeds starting at DDR5-5000 (5000MT/s) instead of trying the highest speed of 6000MT/s (which I suspect may be the case).

If the PC is stable at 5000MT/s, increase the memory overclock to 5200MT/s and try again. Keep increasing the speed in 200MT/s steps until it hangs, then reduce by 200MT/s and run a full MemTest86 run (several hours). Even a single error impiles the RAM is not 100% stable. You should be able to find a bunch of XMP/EXPO settings in the SPD chips on your DIMMs. I use AIDA64 to display SPD timings. They provide a handy guide when using manual settings.

You can also try relaxing the CL(CAS) setting at 6000MT/s by one or two clock cycles. As an example, if the kit is CL36 at 6000MT/s, manually set CL to 37 or 38 for all DIMMs. If the system boots at 6000MT/s, check you've slowed down the timings sufficiently by running MemTest86.

Not all combinations of CPU, BIOS and RAM are stable when overclocked. Similarly, not all applications benefit much by overclocking RAM. If your system is stable at 5800MT/s or 5600MT/s, you haven't lost any significant amount of performance.

I regard the mobo's QVL for RAM as a guide only, not an absolute guarantee you can achieve the quoted maximum speed every time. It's a bit like expecting a car to reach the manufacturer's quoted top speed in all circumstances, regardless of road conditions, head winds, number of passengers, hills, etc.

when windows starts along with RGB Aura from GIgabyte, the LEDS become White

I had problems in December 2022 with Armory Crate on my Asus X670 board + 7950X and I haven't touched it since. Check for known bugs in Aura. Try running without it.

 

[skills2k7]

This reminds me of a very-strange issue that my Asus A7V8X-X developed, (2003, Via KT400) where if I used an older T'bred with an unlocked multi and the multi is not at the default, the exact same thing happens, just a black screen on reboot! So, that was with socket 462. Happens when I drop the CPU core multi, even with FSB stable!

Now, back to recent-era-hardware:

Have you tried power cycling the monitor while it's supposed to reboot? There seems to be a very strange issue where some monitors crash on display mode change.

I noticed an issue with my Samsung Odyssey G40B, where it seems to give up, unless I power cycle it during a UEFI-BIOS reboot! Note that the monitor also seems to have an issue, where it may crash the system during a display-mode-change!

Oh my god this worked! I've been troubleshooting this issue for weeks and cant believe that the fix was so simple, Can confirm that I can boot PC fine if monitor is powered off first, thanks for the advice!

 

[DemomanCA]

I'm here to announce my shame. For mine, I had the damn switch that only spins up the fans to test your water cooling on. I didn't realise I'd bumped it. I'm an idiot.

 

[eidairaman1]

I'm here to announce my shame. For mine, I had the damn switch that only spins up the fans to test your water cooling on. I didn't realise I'd bumped it. I'm an idiot.

At least you don't have to rma because gigabyte are a pita with that by denying fault or claiming it was user fault

 

[DemomanCA]

At least you don't have to rma because gigabyte are a pita with that by denying fault or claiming it was user fault

Yeah RMA was never gonna happen. I don't even think it was an Australian release. Plus try and tell someone with a straight face you had a tachyon and didn't OC it

I also hate it when people solve something and don't reply to forums saying so

 

[dannyandpenny]

i had this problem no restart and what i found is that Memory integrity was the problem

i had this problem no restart and what i found is that Memory integrity was the problem

in core isolation windows

 

[Palladium]

This reminds me of a very-strange issue that my Asus A7V8X-X developed, (2003, Via KT400) where if I used an older T'bred with an unlocked multi and the multi is not at the default, the exact same thing happens, just a black screen on reboot! So, that was with socket 462. Happens when I drop the CPU core multi, even with FSB stable!

Now, back to recent-era-hardware:

Have you tried power cycling the monitor while it's supposed to reboot? There seems to be a very strange issue where some monitors crash on display mode change.

I noticed an issue with my Samsung Odyssey G40B, where it seems to give up, unless I power cycle it during a UEFI-BIOS reboot! Note that the monitor also seems to have an issue, where it may crash the system during a display-mode-change!

I had a old Gigabyte NF6100 S939 mobo where I have to repeatedly power cycle the AC power to the PSU until it cold boots, but from some weird reason it will work flawlessly afterwards as long as the AC power is kept on.