I don’t remember 100% but did this back in September.
I think what you need to do is give the file a very specific filename and then drop it on a filesystem the UEFI has access to. That made it work.
I am not sure if I used a USB stick in the end or not to get it to work.
Yes, even for my ASUS board I have to DL the BIOS file, rename it to be what the board is looking for, then place it on a FAT32 partition in some accessible location.
If I unzip the file I download from their site and just plop it into a USB drive, the board says it doesn’t see the file.
I’ve had ASUS and Gigabyte boards and always flashed from USB stick.
IIRC, there are two processes: one where you plug the USB stick in, press F2 or Delete to go to UEFI GUI and then select the firmware file there.
The other is where you plug a USB into a certain port and it flashes the firmware on boot without requiring mouse or keyboard interaction.
I think I’ve only done the first type but not entirely sure. I would prefer not to flash the firmware of a running system from a custom branded software inside the OS. I don’t trust hardware manufacturers to write good enough desktop apps that won’t break my system.
My new PC isn’t very stable… Keeps crashing on me. This last time it won’t boot back into windows anymore. I get this display.
And from here I can’t do crap…
I’ve tried resetting BIOS back to default.
Edit. Booting on the Win11 USB and reverting to last restore point worked…
Might be time to consider doing a return to the manufacturer before it gets worse.
Wheels
Since I bought the parts and put it together myself, it’s not as easy as just RMA it. If it is a hardware issue, I must first find out which hardware is causing the instability.
But it’s most likely some settings I need to figure out.
Did you just enable the XMP? Sometimes it needs a little additional truning.
I just tried using Ryzen Master and selected a Gaming setup.
But I just realized I may have updated the BIOS with a file for the Taichi Lite… I had some issues with updating the BIOS, and maybe that was it…?
I will try flashing it again, and double check that I’m using the correct file.
How did it go Troll? Hopefully you got it all fixed up…
Had to go to bed.
But I have established the fact that I did indeed install the BIOS for the Taichi Lite Mobo, not the Taichi that I have… Stupid user! 
That’s more like it!
Probably explains why the UEFI Instant Flash tool couldn’t find the ROM file and why I had to use the flashback feature of the Mobo to force flash it…
The same thing happened this time around, probably because I forced the Mobo to identify as a Lite.
Easy fixes are the best fixes. I’m kinda surprised it worked at all!
Me too!
But the Taichi Lite isn’t that much different.
Glad I didn’t brick the whole thing…
Well, seems like using the correct BIOS really improved things… Who’d a thought, right? 
Running a PBO on the CPU and EXPO1 on the RAM, and it seems to be holding…so far.
Yeah, you’re lucky that apart from the LEDs the Taichi and Taichi Lite are the electrically the same.
Yeah, still, it didn’t seem to like the Lite BIOS… Then again, it was another version too.
So…it was a PEBKAC.
Those can be easy to fix if you identify it as such and can overcome it!
If my PC had a Tech Log, maintenance would write; The PC had a faulty user component. Appropriate dose of shame applied.
The fact that the firmware flashing tool let you flash that at all doesn’t reflect too kindly on the manufacturer.
It probably is because both of them are basically the same. The only difference is that the Taichi lite is pretty bare bones whereas the Taichi has LEDs, a backplate, better VRM cooling as well as a GPU release lever. Still shouldn’t be possible of course but apart from the LEDs there’s no difference that should matter.
