Hi community
One month ago I built a new PC. It consists of the MSI B450 Gaming PLUS (mATX) Motherboard, the AMD Ryzen 5 3600, a Radeon RX 570 and runs on 16GB RAM. I knew I had to update the BIOS before using the system since the B450 mainboards don't have stock support of the Ryzen 3000 CPUs. So that's what I did using the "Flash BIOS button" and the system ran just fine for about a month. Than I ran into some Windows issues and decided to reinstall Windows 10. After yet some other issues I figured to run another clean installation, make sure all the drivers are fine and also check the BIOS.
I think I was on BIOS version 7B86v1A from 2019-07-23 once I initiated the update. This time I wanted to flash from the UEFI BIOS. It seems something went wrong. After more than 15 minutes nothing happened (I think the screen was black) so I decided to restart. The screen stayed black because it didn't get any input (that's what my monitor said).
Now I thought the BIOS was bricked and tried to restore the system by using the BIOS Flashback+ feature as when I first updated my BIOS. I downloaded the latest BIOS (7B86v1B from 2019-08-30) and ran used the button. The red LED flashed 3 times and stayed red thereafter. I called the support. They told me the stick was not being recognized and I will have to try another one. I tried 3 in total. All in FAT32, smallest one was 16 GB. I always had the BIOS renamed as "MSI.ROM" in the root of the stick. Always got the same result.
So I removed the BIOS battery and tried it again. Now I get a consistent red LED on the EZ Debug. It says CPU error which makes sense since the stock BIOS didn't support the CPU in the first place. But now when I try to run the BIOS update using the Flash BIOS button. The BIOS Flashback LED doesn't light up at all and only the EZ Debug LED complaints about the CPU. Should I run an earlier BIOS update first? Do I have to remove CPU, GPU, RAM or anything else before proceeding? Or is there anything else you think could be the issue here? I have no clue what's going on. Someone claimed the stick has to be MBR enabled. I tried that though. Maybe I did something wrong.
PLEASE HELP!
One month ago I built a new PC. It consists of the MSI B450 Gaming PLUS (mATX) Motherboard, the AMD Ryzen 5 3600, a Radeon RX 570 and runs on 16GB RAM. I knew I had to update the BIOS before using the system since the B450 mainboards don't have stock support of the Ryzen 3000 CPUs. So that's what I did using the "Flash BIOS button" and the system ran just fine for about a month. Than I ran into some Windows issues and decided to reinstall Windows 10. After yet some other issues I figured to run another clean installation, make sure all the drivers are fine and also check the BIOS.
I think I was on BIOS version 7B86v1A from 2019-07-23 once I initiated the update. This time I wanted to flash from the UEFI BIOS. It seems something went wrong. After more than 15 minutes nothing happened (I think the screen was black) so I decided to restart. The screen stayed black because it didn't get any input (that's what my monitor said).
Now I thought the BIOS was bricked and tried to restore the system by using the BIOS Flashback+ feature as when I first updated my BIOS. I downloaded the latest BIOS (7B86v1B from 2019-08-30) and ran used the button. The red LED flashed 3 times and stayed red thereafter. I called the support. They told me the stick was not being recognized and I will have to try another one. I tried 3 in total. All in FAT32, smallest one was 16 GB. I always had the BIOS renamed as "MSI.ROM" in the root of the stick. Always got the same result.
So I removed the BIOS battery and tried it again. Now I get a consistent red LED on the EZ Debug. It says CPU error which makes sense since the stock BIOS didn't support the CPU in the first place. But now when I try to run the BIOS update using the Flash BIOS button. The BIOS Flashback LED doesn't light up at all and only the EZ Debug LED complaints about the CPU. Should I run an earlier BIOS update first? Do I have to remove CPU, GPU, RAM or anything else before proceeding? Or is there anything else you think could be the issue here? I have no clue what's going on. Someone claimed the stick has to be MBR enabled. I tried that though. Maybe I did something wrong.
PLEASE HELP!