|
X399 Taichi 1.70 BIOS error code loop |
Post Reply 
|
Page 123 4> |
| Author | |
Garrett1028 
Newbie 
Joined: 16 Nov 2017 Location: colorado Status: Offline Points: 1 |
 Post Options
 Thanks(0)
 Quote Reply
 Topic: X399 Taichi 1.70 BIOS error code loopPosted: 16 Nov 2017 at 12:36pm |
|
Same issue here, with bios 1.7 and 1.8
1900x Threadripper /399 Taichi board, 2x crucial sata M.2 drives, 2x rx580 GPUs in crossfire |
|
 |
|
|
kotodama
Newbie
Joined: 06 Oct 2017 Status: Offline Points: 2 |
Post Options
Thanks(0)
Quote Reply
Posted: 09 Nov 2017 at 2:57am |
|
Same issue with the new 1.80 BIOS as well.
|
|
|
|
|
Blemis
Newbie
Joined: 04 Nov 2017 Status: Offline Points: 1 |
Post Options
Thanks(0)
Quote Reply
Posted: 04 Nov 2017 at 9:26pm |
|
I have a similar issue with 1.7. When I use my u.2 drive (intel 750) in the u.2 port, and then turn on nvme raid it will not post. The bios error code says it's a pci error. Turn off nvme raid and it works fine. If I put the 750 into an add on card, instead of the u.2 port same result. Looks like this was just a quickly implemented poorly tested bios raid.
|
|
|
|
|
wolrah
Newbie
Joined: 29 Oct 2017 Location: Colo Spgs Status: Offline Points: 5 |
Post Options
Thanks(0)
Quote Reply
Posted: 03 Nov 2017 at 12:27am |
|
Sorry for the late update, work got in the way...
I installed two new PCIe SSDs in slots 1 and 2. I was able to boot with out issue. I built a RAID 0 array with both and installed windows. Ran this configuration with and without a SATA SSD in slot 3. No problem either way. Currently running the RAID 0 in 1 and 2 with slot 3 open. I also have a RAID 0 array with two seagate 3TB drive, a standalone 2TB disk and a standalone 2.5" 256GB SATA SSD. To me this confirms the SATA vs. NVMe and issues with BIOS 1.7. I can't afford to have my system down for an RMA, I will discuss further with tech support.
|
|
|
X399 Taichi, 1950x, 64GB GskillRGB, 980 Ti, Storage = WIP
|
|
|
|
|
jackfrost
Newbie
Joined: 24 Oct 2017 Status: Offline Points: 5 |
Post Options
Thanks(0)
Quote Reply
Posted: 02 Nov 2017 at 11:03pm |
|
I have 3 PCIe SSDs in the m.2 slot working fine, with raid enabled on 2 of them for a raid0 boot drive.
The issue only seems to apply to SATA m.2 drives, i have multiple 2.5 sata devices plugged in just fine. Of course, I can't have secure boot enabled with the amd raid... windows says rcbottom.sys fails digital signature check. PS: Don't install the samsung NVMe driver if you use samsung nvme drives and the amd raid, it might completely screw your install... it did mine.
|
|
|
|
|
wolrah
Newbie
Joined: 29 Oct 2017 Location: Colo Spgs Status: Offline Points: 5 |
Post Options
Thanks(0)
Quote Reply
Posted: 31 Oct 2017 at 4:44am |
|
Quick update, 2 PCIe SSDs should be in tomorrow... if they work I'll re-purpose the SATA SSDs and close my ticket with ASRock. I won't mind the extra performance.
 |
|
|
X399 Taichi, 1950x, 64GB GskillRGB, 980 Ti, Storage = WIP
|
|
|
|
|
wolrah
Newbie
Joined: 29 Oct 2017 Location: Colo Spgs Status: Offline Points: 5 |
Post Options
Thanks(0)
Quote Reply
Posted: 31 Oct 2017 at 2:30am |
|
During the course of working on this issue, and posting here, I learned about the various interfaces avalable to the M.2 form factor. I was not aware that some M.2 devices use a SATA interface over PCIE. My new SSDs are, in fact, SATA. I may try to get a hold of a true PCIE SSD and see if slots 1 or 2 will work (at least let me into BIOS)
free-eagle, I have not used any other version than 1.7. Thank you for following up with your experience.  I would try to downgrade, but I have some work that needs to be done. I'll update if I can get my hands on a true PCIE SSD. FYI, I did open a ticket with ASRock, very quick to respond. They obviously want me to, unplug all, clear CMOS, re-seat... if this does not work, they are already proposing an RMA... but from what I see, it feels like a BIOS issue, not my particular board. I'll update as we move forward.
|
|
|
X399 Taichi, 1950x, 64GB GskillRGB, 980 Ti, Storage = WIP
|
|
|
|
|
free-eagle
Newbie
Joined: 19 Oct 2017 Status: Offline Points: 17 |
Post Options
Thanks(0)
Quote Reply
Posted: 29 Oct 2017 at 9:58pm |
|
i know, i did this several times to be sure the error is bios 1.7 related :-)
|
|
|
X399 Taichi (Bios 2.0), TR 1920X, 32 GB GSKILL F4-3600C16D-16GTZSW, 2x Samsung 960 Pro 512GB (RAID 0),Crucial 1 TB SSD, 2x 4TB Seagate HDD (RAID 1), Zotac 1080TI AMP Extreme, Windows 10 Pro (1709)
|
|
|
|
|
MisterJ
Senior Member 
Joined: 19 Apr 2017 Status: Offline Points: 1097 |
Post Options
Thanks(0)
Quote Reply
Posted: 29 Oct 2017 at 9:43pm |
|
free-eagle, you can flash back to 1.50 if you like. If this works, please open a ticket and tell ASRock. Be sure to use Instant Flash from the BIOS. I suggest doing an F9, F10, then flash, then another F9 and F10. Enjoy, John.
|
|
|
Fat1 X399 Pro Gaming, TR 1950X, RAID0 3xSamsung SSD 960 EVO, G.SKILL FlareX F4-3200C14Q-32GFX, Win 10 x64 Pro, Enermx Platimax 850, Enermx Liqtech TR4 CPU Cooler, Radeon RX580, BIOS 2.00, 2xHDDs WD
|
|
|
|
|
free-eagle
Newbie
Joined: 19 Oct 2017 Status: Offline Points: 17 |
Post Options
Thanks(0)
Quote Reply
Posted: 29 Oct 2017 at 2:32pm |
|
I think at the moment bios 1.7 is the problem.
in my configuration before 1.7 the sata m2 ssd worked in all slots. in bios 1.7 the sata ssd works only in slot 3. in slot 1 and 2 i have real nvme ssd´s and they work fine there.
|
|
|
X399 Taichi (Bios 2.0), TR 1920X, 32 GB GSKILL F4-3600C16D-16GTZSW, 2x Samsung 960 Pro 512GB (RAID 0),Crucial 1 TB SSD, 2x 4TB Seagate HDD (RAID 1), Zotac 1080TI AMP Extreme, Windows 10 Pro (1709)
|
|
|
|
|
Post Reply
|
Page 123 4> |
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