MB issue (I think)

[YusExa]

First build ever, BIOS refuses to update and freezes everytime I try and do so. Won't let me access windows either because it freezes when trying to boot. Was updating from F2 and trying to update to F5c and F4. Neither worked.

The MB is a Gigabyte, B650 Elite AX.
Yes I tried setting the BIOS settings to default settings. No XMP was not on.

Other parts: 

7600x
6750xt
G.skill trident 6000mhz cl36 (4200 at the time of event)
Rmx 750

Someone on reddit seemed to have the same issue but I am not sure if there is a fix for it or not. Anyone know?
 

[RONOTHAN##]

Maybe try removing the RAM and do it through BIOS flashback (I guess Q-Flash since it's a Gigabyte board), just in case the RAM is faulty? I've used that board before, did the same update cycle (F2 to F5b) and it worked perfectly. I'd assume it's probably an issue elsewhere. 

[YusExa]

Right got you. I just didn't think that would be the issue since there was no debug light for it. Guess it's not the most credible debug source? 

[RONOTHAN##]

15 minutes ago, YusExa said:

Right got you. I just didn't think that would be the issue since there was no debug light for it. Guess it's not the most credible debug source? 

The debug LEDs are always just an indicator, they're never 100% accurate about anything. Even if you've got a POST code, it's generally more accurate but never quite 100%. I've seen bad RAM light up the CPU, RAM, and GPU LEDs before, as well as have the RAM LED turn off and get stuck with no LEDs lit. With a POST code, I've had bad CPU mounts light up code 55 on Intel (Memory not detected), and faulty GPUs go through the entire POST procedure without stopping on a single code, just never output an image. 

 

It generally will point you in the right direction if the system won't turn on, but knowing the order in which the LEDs turn on and off, the duration in which they stay light, and the amount of time between lighting up is pretty important to determining which component is faulty. Plus, if the system turns on, those debug lights tell you nothing about if a particular component is unstable. 

 

 

Also, make sure to quote so we get a notification

[YusExa]

46 minutes ago, RONOTHAN## said:

The debug LEDs are always just an indicator, they're never 100% accurate about anything. Even if you've got a POST code, it's generally more accurate but never quite 100%. I've seen bad RAM light up the CPU, RAM, and GPU LEDs before, as well as have the RAM LED turn off and get stuck with no LEDs lit. With a POST code, I've had bad CPU mounts light up code 55 on Intel (Memory not detected), and faulty GPUs go through the entire POST procedure without stopping on a single code, just never output an image. 

 

It generally will point you in the right direction if the system won't turn on, but knowing the order in which the LEDs turn on and off, the duration in which they stay light, and the amount of time between lighting up is pretty important to determining which component is faulty. Plus, if the system turns on, those debug lights tell you nothing about if a particular component is unstable. 

 

 

Also, make sure to quote so we get a notification

Ah I see. Well Ill get on that as soon as I can. Thank you for the pointer!

[YusExa]

11 hours ago, RONOTHAN## said:

The debug LEDs are always just an indicator, they're never 100% accurate about anything. Even if you've got a POST code, it's generally more accurate but never quite 100%. I've seen bad RAM light up the CPU, RAM, and GPU LEDs before, as well as have the RAM LED turn off and get stuck with no LEDs lit. With a POST code, I've had bad CPU mounts light up code 55 on Intel (Memory not detected), and faulty GPUs go through the entire POST procedure without stopping on a single code, just never output an image. 

 

It generally will point you in the right direction if the system won't turn on, but knowing the order in which the LEDs turn on and off, the duration in which they stay light, and the amount of time between lighting up is pretty important to determining which component is faulty. Plus, if the system turns on, those debug lights tell you nothing about if a particular component is unstable. 

 

 

Also, make sure to quote so we get a notification

Update: Trying this soltuion today and I noticed that when tring to switch around the ram sticks to try and note the fautly stick, the debug light would cycle though every LED before setting on the Boot LED. I tried updating to F4 since it wasn't a beta BIOS but that still hasn't worked. Trying to update BIOS freezes the computer and trying to access the boot menu freezes the computer as well.

[YusExa]

1 minute ago, YusExa said:

Update: Trying this soltuion today and I noticed that when tring to switch around the ram sticks to try and note the fautly stick, the debug light would cycle though every LED before setting on the Boot LED. I tried updating to F4 since it wasn't a beta BIOS but that still hasn't worked. Trying to update BIOS freezes the computer and trying to access the boot menu freezes the computer as well.

Could be the CPU so I am gonna try reseating that.

[YusExa]

38 minutes ago, YusExa said:

Could be the CPU so I am gonna try reseating that.

Update 2: Upon checking RAM and reseating the CPU, the computer said there WAS a BIOS issue and it had to reset. So maybe it was my CPU. I tried updating BIOS and it froze again. Awesome. 

[RONOTHAN##]

2 hours ago, YusExa said:

the debug light would cycle though every LED before setting on the Boot LED.

That's completely normal. The way the debug LEDs work is that they light up during their particular phase of the POST procedure, that way if it crashes that particular LED will stay illuminated. 

 

1 hour ago, YusExa said:

Upon checking RAM and reseating the CPU, the computer said there WAS a BIOS issue and it had to reset.

Most boards are programmed to reset the BIOS if they detect a CPU or RAM change, so this is probably what happened. 

 

 

What I would be trying though is the RAM-less BIOS update process. Follow this guide for how to do it:

It's done on what appears to be a Z490 Xtreme, but the process should be the same on all Gigabyte boards. See if that fixes anything, if not I would start returning things until the issue starts going away. 

[YusExa]

30 minutes ago, RONOTHAN## said:

That's completely normal. The way the debug LEDs work is that they light up during their particular phase of the POST procedure, that way if it crashes that particular LED will stay illuminated. 

 

Most boards are programmed to reset the BIOS if they detect a CPU or RAM change, so this is probably what happened. 

 

 

What I would be trying though is the RAM-less BIOS update process. Follow this guide for how to do it:

It's done on what appears to be a Z490 Xtreme, but the process should be the same on all Gigabyte boards. See if that fixes anything, if not I would start returning things until the issue starts going away. 

Sounds good. I just don't have an LED indicator letting me know when the procees is done. Just my fans light up for a second and that's about it. Thank you regardless. 

 

[YusExa]

On 5/6/2023 at 10:24 PM, YusExa said:

First build ever, BIOS refuses to update and freezes everytime I try and do so. Won't let me access windows either because it freezes when trying to boot. Was updating from F2 and trying to update to F5c and F4. Neither worked.

The MB is a Gigabyte, B650 Elite AX.
Yes I tried setting the BIOS settings to default settings. No XMP was not on.

Other parts: 

7600x
6750xt
G.skill trident 6000mhz cl36 (4200 at the time of event)
Rmx 750

Someone on reddit seemed to have the same issue but I am not sure if there is a fix for it or not. Anyone know?
 

The issue in this case was a human error. With this particular board, I needed to conduct a proper and correctly executed BIOS flash before installing anything. There are videos that neatly describe how to conduct this process. Once completed, the computer booted and ran fine for the most part.