The ASRock thread [support/feedback/etc]

A problem with Crucial BX100 SSDs on AMD SATA ports 1 and 2 on X370 Taichi was reported earlier. The engineers in Taiwan managed to get their hands on one of those SSDs. Although they could not reproduce the issue, they are providing a beta BIOS for testing:
https://1drv.ms/u/s!Ap4vsEUrPToyhVGtc0PCiL_-h5NM

Thanks for that. I'll give it a go this weekend and report back.

It also seems hit and miss on the MX100 drive I have too. If the system has been powered down for a few days and then switched back on it comes up with a message to say there's no boot drive. I have to hit reset then it works fine. Seems like some power/sleep issue on a cold boot
 
Yeah I tried it. For me very similar to previous Beta. The board is in the main solid. But not fully memory compatable yet.

Taichi is back in stock now for those looking to buy one or my bundles.
 
Thanks 8Pack - was hoping this new bios would have made some headway with the memory issues. Oh well.
its seems according to reddit
it wasnt anything much other than rewriting the code part to report it as 1004 in hwinfo

someone on asrock support forum (a user not an official asrock rep) said they were some quote
"under advanced settings you will now find Dram Timings overclock and ohm adjustment"
 
its seems according to reddit
it wasnt anything much other than rewriting the code part to report it as 1004 in hwinfo

someone on asrock support forum (a user not an official asrock rep) said they were some quote
"under advanced settings you will now find Dram Timings overclock and ohm adjustment"

Shall continue to stick with 1.94A for now then.
 
Well I've tried BIOS 2.20 and it still hasn't fixed the missing BX100 SSD on SATA3_1 & 2 ports

Even my MX100 intermittently goes missing (currently on SATA3_1). Normally after a full system shutdown, I then switch on 24-48hrs later and the initial boot doesn't detect the MX100, I reset, and it detects fine until the next full shutdown/start up

My BX100 has been on SATA3_5 port since the initial problems and has been fine on this port never disappeared once. Seems to be an issue with SATA3_1 & SATA3_2 ports
 
Well I've tried BIOS 2.20 and it still hasn't fixed the missing BX100 SSD on SATA3_1 & 2 ports

Even my MX100 intermittently goes missing (currently on SATA3_1). Normally after a full system shutdown, I then switch on 24-48hrs later and the initial boot doesn't detect the MX100, I reset, and it detects fine until the next full shutdown/start up

My BX100 has been on SATA3_5 port since the initial problems and has been fine on this port never disappeared once. Seems to be an issue with SATA3_1 & SATA3_2 ports
Thanks for testing. I will share your feedback with the engineers in Taiwan.
 
Thanks for testing. I will share your feedback with the engineers in Taiwan.

Doh sorry! Just realised I had downloaded the 2.20 BIOS from the asrock website as well. I had flashed it with the official BIOS, not the one you linked me to! :o

Was there a difference between the 2.20 BIOS you linked to and the 2.20 BIOS on the website? If so I'll reflash tonight when I get home from work and report back!

Sorry about that!
 
Well I've tried BIOS 2.20 and it still hasn't fixed the missing BX100 SSD on SATA3_1 & 2 ports

Even my MX100 intermittently goes missing (currently on SATA3_1). Normally after a full system shutdown, I then switch on 24-48hrs later and the initial boot doesn't detect the MX100, I reset, and it detects fine until the next full shutdown/start up

My BX100 has been on SATA3_5 port since the initial problems and has been fine on this port never disappeared once. Seems to be an issue with SATA3_1 & SATA3_2 ports

Hmm.... I have a Asus Prime X370 board with the same issue. I also have a Crucial SSD (MX100). So it it's either something common to all AMD AM4 mobo or something common with Crucial SSDs?
 
Doh sorry! Just realised I had downloaded the 2.20 BIOS from the asrock website as well. I had flashed it with the official BIOS, not the one you linked me to! :o

Was there a difference between the 2.20 BIOS you linked to and the 2.20 BIOS on the website? If so I'll reflash tonight when I get home from work and report back!

Sorry about that!
Yep, it's a different version, 2.20C.
 
Yep, it's a different version, 2.20C.

whoops! :o I'll flash it to that tonight and report back!

Hmm.... I have a Asus Prime X370 board with the same issue. I also have a Crucial SSD (MX100). So it it's either something common to all AMD AM4 mobo or something common with Crucial SSDs?

Over on the Asrock forums there have been reports of other SSD's other than crucial. I believe Mushkin was one of those mentioned, which shared the same controller as the BX100 (Silicon Motion) but the MX100 are Marvell I believe so it might be something altogether different
 
So I've tried the 2.20C BIOS for the Taichi and fingers crossed (everything crossed) my BX100 SSD is now connected to SATA3_2 and has not disappeared in the last 3 full shutdowns and restarts!! So I'll keep an eye on this and the MX100 (currently on SATA3_1) and see how it goes

Thanks to the AsRock engineers back in Taiwan! What ever they did, it seems to have worked so far! The best test will be when I do a full shut down tonight and switch it back on in 24-48 hours.
 
So I've tried the 2.20C BIOS for the Taichi and fingers crossed (everything crossed) my BX100 SSD is now connected to SATA3_2 and has not disappeared in the last 3 full shutdowns and restarts!! So I'll keep an eye on this and the MX100 (currently on SATA3_1) and see how it goes

Thanks to the AsRock engineers back in Taiwan! What ever they did, it seems to have worked so far! The best test will be when I do a full shut down tonight and switch it back on in 24-48 hours.
Sounds good. But better test it a few days.

In Taiwan they could now see intermittent detection issues with a BX100 with firmware MU01. They also tested the same SSD on an Asus X370 board, and saw the same issue there. Since the problem happens only with the drive connected to the ports coming from the CPU, it might be some issue that would have to be fixed by AMD.

Let's see how it works with firmware MU02(?) and BIOS 2.20C on your system...
 
Back
Top Bottom