WarpedTrekker wrote: I'm having the same issue with this board. Stuck at code 63, and happens every day, almost every time I turn it on. BIOS 3.30. Not going to flash back due to concerns it will make things worse. But since they haven't released a new BIOS in two months, I'm ripping this board out and selling it and buying another brand.

Hmm... flashing back might be easier.

Looking back, the problems I ran into had nothing to do with any flashing gone wrong. It's just v3.30 not working right.

Still on v2.30. All working fine.

I can now say that it must have been a bios version 3.30 issue.

The problem persisted after the procedure as described above.

Now, with version 2.30 installed, all my bootproblems are over.

You can be shure that from now on I will take those rules into account :-)

Re-flashing 3.30 made a huge difference.

The problem is not entirely gone though. It still occasionally hangs on 63, but till now it didn't need a bios reset. A simple restart made it boot.

I assume a flashback to v2.30, followed by v3.30, could possibly take care of that.

Thanks! It's been a great help.

well firstly

never ever flash from windows ,ever ..........

also before flashing a bios you must reset the old bios to safe/default settings (so no xmp etc)

also my preferred way is minimal ram fitted eg 1 stick (less chance of corruption)

now if you want to flash back i suggest flashing to the bridge bios first and then earlier version if you want

Hmm... first time it booted. Second time, after setting xmp: no problems. 3rd time reboot: stuck on code 63 :-(

After that it rebooted succesfully. 3 X already without bios-reset. You could call that improvement :-)

Is it possible to flashback to whatever bios-version you want, with this usb flashback method?

I did the 2.20 & 3.30 updates the first time from windows & a usb-stick in the frontpanel. Maybe not the best methods. I was thinking, if problems persist, would it be a good idea to go back to 2.20 & start off from there? Especially because 2.20 was required for 3.30.

OK. I'll try that.

first id try a re-flash of latest bios

use the usb flashback method

it might be you had a bad bit of code written to bios rom

Hi,

I'm new here & also quite a newbie when it comes to 'deep computering'. I've built 2 rigs before without any problems, but now I've got one with my newly built - x399 Taichi, threadripper 1900x, Geforce 1080TI, G.Skill F4-2400C15Q-32GIS, Windows 10 Pro 1803 - machine.

I recently updated bios-version from v1.50, via 2.30 to 3.30 because I was trying to do a ram-upgrade. On the higher xmp-settings it started acting weird, so a bios-upgrade seemed a good thing to do.

Under v1.50 all was working fine with G.Skill F4-2400C15Q-32GIS which, I know, is not on the qvl list.

After the bios update, booting randomly stuck at code 63. No post.

I initially thought it might have to do with the new ram I was fumbling with, but when I put the g.skills back in, the same behaviour occurred.

If it stucks at 63, I hold the powerbutton to switch the pc off, pull the powercord out & reset bios with the clear cmos button. After that, sometimes it boots, sometimes not.

If the machine boots, it works like it's supposed to do.

Does anyone have any idea what I could do?

1st thing that comes to my mind is 'back to bios v1.50 when all was still hunky dory'.

Is that an option? Can I flash the bios back from 3.30 to v1.50?