|
Asrock x399 Taichi stuck at code 63 |
Post Reply 
|
| Author | |
mamb0062 
Newbie 
Joined: 23 Aug 2018 Status: Offline Points: 8 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: Asrock x399 Taichi stuck at code 63Posted: 23 Aug 2018 at 8:30pm |
|
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? Edited by mamb0062 - 23 Aug 2018 at 8:31pm |
|
 |
|
|
datonyb
Senior Member 
Joined: 11 Apr 2017 Location: London U.K. Status: Offline Points: 3139 |
Post Options
Thanks(0)
Quote Reply
Posted: 23 Aug 2018 at 9:12pm |
|
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
|
|
|
[url=https://valid.x86.fr/jpg250]
 [/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
|
|
|
|
mamb0062
Newbie
Joined: 23 Aug 2018 Status: Offline Points: 8 |
Post Options
Thanks(0)
Quote Reply
Posted: 23 Aug 2018 at 9:29pm |
|
OK. I'll try that. |
|
|
|
|
mamb0062
Newbie
Joined: 23 Aug 2018 Status: Offline Points: 8 |
Post Options
Thanks(0)
Quote Reply
Posted: 23 Aug 2018 at 10:52pm |
|
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.
Edited by mamb0062 - 23 Aug 2018 at 11:04pm |
|
|
|
|
datonyb
Senior Member
Joined: 11 Apr 2017 Location: London U.K. Status: Offline Points: 3139 |
Post Options
Thanks(0)
Quote Reply
Posted: 24 Aug 2018 at 12:10am |
|
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
|
|
|
[url=https://valid.x86.fr/jpg250]
[/url]3800X, powercolor reddevil vega64, gskill tridentz3866, taichix370, evga750watt gold |
|
|
|
|
mamb0062
Newbie
Joined: 23 Aug 2018 Status: Offline Points: 8 |
Post Options
Thanks(0)
Quote Reply
Posted: 24 Aug 2018 at 2:41am |
|
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.
Edited by mamb0062 - 24 Aug 2018 at 2:59am |
|
|
|
|
mamb0062
Newbie
Joined: 23 Aug 2018 Status: Offline Points: 8 |
Post Options
Thanks(0)
Quote Reply
Posted: 25 Aug 2018 at 7:30am |
|
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.
|
|
|
|
|
Perceptron
Newbie
Joined: 03 Oct 2018 Status: Offline Points: 1 |
Post Options
Thanks(0)
Quote Reply
Posted: 03 Oct 2018 at 8:31am |
|
Hi,
there might be really something wrong with version 3.30. My RAM kit is not on QVL list and it took me some time to make it work stable at 3000Mhz first on version 1.80 then on 2.00. Yesterday I've upgraded from 2.00 through 2.30 to 3.30 using Instant Flash. After I've restored (manually) my stable timings on 3000 XMP profile my board got stuck on 63 error code. After CMOS reset I've made few other tries, but with no success, same symptoms different debug codes. So I've downgraded to 2.30 everything was ok, then upgraded to 3.20, again all (settings same as always) was ok. After 1 full pass on MemTest86 with no error on 3.20 I've decided to make one more approach to 3.30. To my surprise so far (Memtest still going) everything looks ok on same settings. Is it possible 3.20 is a bridge version for 3.30? If after few MemTest passes & reboots there still be no errors I will try to reproduce again bad way (2.30 -> 3.30) |
|
|
AMD Threadripper 1920X
G.Skill 4x8GB 3000Mhz x399 Taichi |
|
|
|
|
WarpedTrekker
Newbie
Joined: 18 Jul 2018 Status: Offline Points: 76 |
Post Options
Thanks(0)
Quote Reply
Posted: 18 Oct 2018 at 10:29am |
|
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.
|
|
|
|
|
mamb0062
Newbie
Joined: 23 Aug 2018 Status: Offline Points: 8 |
Post Options
Thanks(0)
Quote Reply
Posted: 22 Oct 2018 at 9:12pm |
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.
|
|
|
|
|
Post Reply
|
|
Tweet
|
| Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |
Topic Options
WarpedTrekker wrote: