Motherboard won't post - please help!

According to MSI website, BIOS version 7B85v16 (Release Date 2019-03-06) also supports "new upcoming CPUs".

It's going to be risky, since you don't have a stable system, but you may want to try downgrading the BIOS to version 7B85v16 (using Flash BIOS Button) and see if that enables you to POST. If the problem really is a bad BIOS version, then you're likely going to need to update the BIOS anyway (if that's even possible given that the cause of the problem hasn't yet been identified).

Obviously, try all the safer options first to see if those solve the issue.

You need the beta bios 17M for ryzen 3000 CPUs, bios v16 upcoming CPUs was for raven ridge CPUs.
 
Sorry to not have clarified this earlier - the beta 17M bios is the version that I have been using so that is not the cause of the issue. I have RMA'd my motherboard to see if that gets me anywhere. They may at least be able to confirm if it is operational with any older generation CPUs. Thanks all for your input.
 
Pleased to report that the RMA was fairly painless and the supplier sent back a brand new board with v17 (non-beta) pre-flashed and the build has been stable from the first boot. Bloody weird - I'm still none the wiser as to why it wasn't working before, it just seems like a lottery with the motherboard. Hope other's are as lucky as I have been.
 
Pleased to report that the RMA was fairly painless and the supplier sent back a brand new board with v17 (non-beta) pre-flashed and the build has been stable from the first boot. Bloody weird - I'm still none the wiser as to why it wasn't working before, it just seems like a lottery with the motherboard. Hope other's are as lucky as I have been.

Good result, how long was you without a board for?
 
Pleased to report that the RMA was fairly painless and the supplier sent back a brand new board with v17 (non-beta) pre-flashed and the build has been stable from the first boot. Bloody weird - I'm still none the wiser as to why it wasn't working before, it just seems like a lottery with the motherboard. Hope other's are as lucky as I have been.
Glad to hear yours is working.

Do you know if there was any difference in the version number between the two motherboards?

What's the version number of the one that is working now without any issues?
 
Good result, how long was you without a board for?

I was without it for 3 days I think. As it happened I was actually on holiday last week so this all happened while I was away. Part of the reason I was happy to do it as I didn't really have anything to lose.

I'm afraid I don't know the version number of my board or how to find out without physically locating it on the board. CPU-Z says it's Rev. 51 if that means anything. As far as I know the only difference between the two boards is that one of them was flashed by the supplier and the other by myself. Perhaps they did it using m-flash using an older generation CPU and it was this that was more successful than using Flashback+.
 
I'm afraid I don't know the version number of my board or how to find out without physically locating it on the board. CPU-Z says it's Rev. 51 if that means anything. As far as I know the only difference between the two boards is that one of them was flashed by the supplier and the other by myself. Perhaps they did it using m-flash using an older generation CPU and it was this that was more successful than using Flashback+.
The version number is printed on the motherboard between the two x16 PCIe slots (just above the 2nd PCIe x16 slot):
m2a1.jpg
 
Last edited:
Thanks a lot for checking.

@Journey, are you onto something here? Version 1.1 working, but version 1.0 has issues with current BIOS?

All of the ones I have upgraded to the newer BIOS have been hardware Ver: 1.1. It's a shame that MSI don't provide a revision history for the hardware like the other manufacturers I work with do. Sometimes it can be something like the brand of a capacitor changing, other times it could be something like the SPI flash chip being changed, which is a bigger deal.
 
Back
Top Bottom