Question Wins won't boot after BIOS upgrade on Gigabyte B450M DS3H - except when power cycling before start

[mister1]

Because of occasional BSoD in Win10 I decided to upgrade BIOS on my motherboard Gigabyte B450M DS3H-CF. CPU is ryzen7 2700.

I updated BIOS it via USB and Q-flash in BIOS. First update was F3 -> F32 then to F40 and then to recommended F62. Before update I also updated drivers on AMD chipset, as required. After upgrade, I enter BIOS and selected Load Optimized Defaults, as recommended in instructions by Gigabyte. After save & restart, system normally booted into Wins and everything seemed fine...

Until I send PC to sleep/suspend mode. When I woke the system up, Wins did not booted, only black screen remained. I pressed reset button to restart PC, but to my surprise, after Gigabyte screen with BIOS option it didn't boot into Win OS, instead I got black screen with sign: REBOOT AND SELECT PROPER BOOT DEVICE OR INSERT BOOT MEDIA IN SELECTED BOOT DEVICE AND PRESS A KEY

I restarted PC several times, same problem, Wins won't boot. I entered to BIOS to see BOOT Option #1 and it seems that my HDD is recognized there. Fast boot is disabled.

Then I shut it down completely, disconnect it from power and checked SATA cables around HDD. Everything looked fine. After that I powered it on again. This time, on so-called cold reboot, system booted into Wins normally. So now I can only boot into wins if I perform cold reboot.

Any idea how to fix this problem??

 

[Lutfij]

Welcome to the forums, newcomer!

Did you clear the CMOS after verifying that the BIOS was flashed successfully?

and then to recommended F62
The latest BIOS listed on your board's support site is F67b;
https://www.gigabyte.com/Motherboard/B450M-DS3H-rev-1x/support#support-dl-bios

Please list the specs to your build like so;
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model.

 

[mister1]

Welcome to the forums, newcomer!

Did you clear the CMOS after verifying that the BIOS was flashed successfully?

and then to recommended F62
The latest BIOS listed on your board's support site is F67b;
https://www.gigabyte.com/Motherboard/B450M-DS3H-rev-1x/support#support-dl-bios

Please list the specs to your build like so;
CPU:
CPU cooler:
Motherboard:
Ram:
SSD/HDD:
GPU:
PSU:
Chassis:
OS:
Monitor:
include the age of the PSU apart from it's make and model.

Thank you for the reply,

So to answer your questions, first my PC specs :

CPU: ryzen7 2700
CPU cooler: YD2700BBAFBOX
Motherboard: GIGABYTE B450M DS3H-CF, AM4, SATA3
Ram: 16 GB, 2 sticks, G.SKILL Aegis
SSD/HDD: WD SSD M.2 NVMe gen3 & SEAGATE Barracuda SATA3 (ST2000DM008)
GPU: Radeon RX 570
PSU: Chieftac iArena 600W ATX
OS: WIN 10 64bit
Monitor: Dell
include the age of the PSU apart from it's make and model: around 4 yrs old

Next, when I mentioned recommended F62, I was relating to GIGABYTE official BIOS descriptions. I'm well aware that latest version is in fact F67b, but I wasn't sure if I should upgrade it to the latest version, considering my CPU and components aren't that new and also not sure how stable the latest version is. But it certainly is one of the options on my TODO list to try, if latest BIOS version fixes my booting problem. Do you think it's worth trying? I just never feel comfortable updating BIOS as I've seen cases with GIGABYTE boards getting bricked because of failures at BIOS upgrade...

Finally, no I did not clear the CMOS after verifying that the BIOS was flashed successfully as this was not mentioned in instructions from Gigabyte support. In fact I've never done it before, not even sure how to do it. You find it necessary?

Update: There seems to be a problem with detecting my disk with Wins. So I have 2 drives, one storage SATA3 disk and another smaller WD SSD M.2 NVMe (this one has Wins). When booting is successful (on cold boot), in BIOS I see normal Boot sequence:

• Windows Boot Manager (WD disk)
• P0: storage disk (SATA 3)
• WD disk

However, on failed boot case, in BIOS I can only see Boot sequence:

• P0: storage disk SATA 3 (without wins)

It seems the other disk with Wins OS does not get detected until I disconnect board from power and cold start it. Not sure what to do to fix that.

 

[mister1]

Thank you for the reply,

So to answer your questions, first my PC specs :

CPU: ryzen7 2700
CPU cooler: YD2700BBAFBOX
Motherboard: GIGABYTE B450M DS3H-CF, AM4, SATA3
Ram: 16 GB, 2 sticks, G.SKILL Aegis
SSD/HDD: WD SSD M.2 NVMe gen3 & SEAGATE Barracuda SATA3 (ST2000DM008)
GPU: Radeon RX 570
PSU: Chieftac iArena 600W ATX
OS: WIN 10 64bit
Monitor: Dell
include the age of the PSU apart from it's make and model: around 4 yrs old

Next, when I mentioned recommended F62, I was relating to GIGABYTE official BIOS descriptions. I'm well aware that latest version is in fact F67b, but I wasn't sure if I should upgrade it to the latest version, considering my CPU and components aren't that new and also not sure how stable the latest version is. But it certainly is one of the options on my TODO list to try, if latest BIOS version fixes my booting problem. Do you think it's worth trying? I just never feel comfortable updating BIOS as I've seen cases with GIGABYTE boards getting bricked because of failures at BIOS upgrade...

Finally, no I did not clear the CMOS after verifying that the BIOS was flashed successfully as this was not mentioned in instructions from Gigabyte support. In fact I've never done it before, not even sure how to do it. You find it necessary?

Update: There seems to be a problem with detecting my disk with Wins. So I have 2 drives, one storage SATA3 disk and another smaller WD SSD M.2 NVMe (this one has Wins). When booting is successful (on cold boot), in BIOS I see normal Boot sequence:

• Windows Boot Manager (WD disk)
• P0: storage disk (SATA 3)
• WD disk

However, on failed boot case, in BIOS I can only see Boot sequence:

• P0: storage disk SATA 3 (without wins)

It seems the other disk with Wins OS does not get detected until I disconnect board from power and cold start it. Not sure what to do to fix that.

Another update: I checked FW on WD M.2 drive and it is latest one. Not sure what else I can try except perhaps clearing CMOS...