For what it's worth from my experience of the MSI board the LLC they use to at least seem to stick a lot closer to what is set in the bios. When I had the original bios that pushed 1.35v the worst I saw it go was 1.356v-1.358v and that was under load like cinebench/prime95 etc. On the new bios where it was set to 1.3v, the worst it got was 1.306 or so.This is my concern, who is OK to use now?
This leaves ASRock and MSI?
With all the issues Asus are having I keep seeing reference to them being less stable than ASRock. If ASRock is the benchmark for poor stability that really doesn't encourage me. Plus at least the Steel Legend, maybe others, seems to have slightly worse than expected m.2 performance (probably not noticeable if you don't run benchmarks).
Which leaves MSI? I bet a few days after I finished a build with an MSI board there would be reports of how with MSI the 1.3v limit doesn't work but with MSI when it goes it takes out the CPU, motherboard, RAM, PSU and for some reason the GPU...
Of course this is assuming the HWinfo values are correct, but considering level1techs got the same result on a different MSI board while properly measuring that makes me think it might be.
So I don't think MSI are saints in terms of getting the original voltage correct, they at least might be better at sticking to the values they're showing.
It's not just requiring fat32, the process also just seemed to need to like certain USB drives too. You can find countless reports on the internet of people struggling to get usb flashback work on motherboards from loads of different manufacturers because they're just incredibly picky with what they accept.Just read the bios flash process in the manual and there's no mention of format the drive in fat 32 which is likely to be the problem.
This is poor
What most people recommend is a USB2 smallish sized (ie 16gb-32gb or something) FAT32 MBR partitioned(which requires a bit of messing since windows defaults to GPT partitions now with their usb drive format feature) empty USB drive with only the bios file renamed on. But even that doesn't always seem guaranteed.
It's such a messy feature.
Last edited: