X399 Taichi CSM bug - code 0E |
Post Reply | Page <12 |
Author | |
Tangles
Newbie Joined: 11 Apr 2018 Status: Offline Points: 11 |
Post Options
Thanks(0)
|
I have sent ASRock a service request. It'd be good to have some more solid confirmations for them - are you guys both willing and able to confirm that after a BIOS reset that disabling the CMS causes the error to be thrown? It might take a couple of reboots if you haven't changed any other settings... mine did boot after disabling CSM and I even got as far as installing win10 but then it threw the code again next boot and I had to reset the BIOS to get it going again.
Your RAM, SSD, and PSU specs might be handy too, JayB33
|
|
lowdog
Newbie Joined: 16 Apr 2017 Location: Australia Status: Offline Points: 194 |
Post Options
Thanks(1)
|
Yeah!!!!!! Asrock need their bios programers to sort this out, unbelievable Asrock can let this issue slide without addressing it at the coding level.
|
|
X399 Fat Pro Gaming bios 3.10 - TR4 1900X - 64GB G-SKILL TridentZ F4-3200C14Q-64GTZ @ 3133MHz - Vega 64 AIO with EK block - WC Custom loop - 1500W Silverstone PSU - yay
|
|
Tangles
Newbie Joined: 11 Apr 2018 Status: Offline Points: 11 |
Post Options
Thanks(0)
|
Thanks for the reply! I actually haven't disabled IOMMU - with the newest win10 builds (1703 / 1709) it boots fine off the USB. I can see how the same incompatibility with previous versions of windows might exist with your rescue disk though
Definitely something is buggy with disabling CSM.
Edited by Tangles - 13 Apr 2018 at 2:13pm |
|
JayB33
Newbie Joined: 04 Dec 2017 Status: Offline Points: 69 |
Post Options
Thanks(1)
|
I get the same error code when disabling CSM and IOMMU both together on my x399 Pro Gaming Fata1ity. See:
http://forum.asrock.com/forum_posts.asp?TID=7022&KW=&PID=42865&title=x399-taichi-raid-win10-install#top I wanted to enable RAID but I didn't get any further because I simply don't want to disconnect any of my SATA drives, which is what ASRock suggested as the likely remedy. I need all my SATA drives. Fix the 0E BIOS error please! Edited by JayB33 - 12 Apr 2018 at 10:25pm |
|
Tangles
Newbie Joined: 11 Apr 2018 Status: Offline Points: 11 |
Post Options
Thanks(0)
|
Tried a lot of things... got windows to install, then rebooted and bam, code 0E. Have tried different RAM, and a different graphics card to no effect.
I'm officially over it, I'll use my two 960 drives in standalone until there's a fix. Not really ideal
Edited by Tangles - 13 Apr 2018 at 2:07pm |
|
Tangles
Newbie Joined: 11 Apr 2018 Status: Offline Points: 11 |
Post Options
Thanks(0)
|
Edited by Tangles - 13 Apr 2018 at 6:09am |
|
Tangles
Newbie Joined: 11 Apr 2018 Status: Offline Points: 11 |
Post Options
Thanks(0)
|
AMD released an update back on the 2nd Oct 2017 that was supposed to enable booting from NVMe RAID. That coincides with a BIOS update from ASRock that enabled NVMe RAID, so I think I can safely assume v2.00 should support booting from NVMe RAID. According to AMD's announcement, disabling CSM is a requirement of doing this:
The NVMe RAID does not show up as a bootable device so it doesn't appear it's possible without disabling CSM.
Edited by Tangles - 13 Apr 2018 at 2:06pm |
|
Tangles
Newbie Joined: 11 Apr 2018 Status: Offline Points: 11 |
Post Options
Thanks(0)
|
EDIT: This thread is now about a bug when disabling CSM on the X399 Taichi, which is a required step in making an NVMe RAID array bootable. Myself and other users can consistently replicate an issue where the board does not boot and gives code 0E after disabling CSM. It may be intermittent as I was able to get the board to boot on one occasion, even as far as installing windows 10, but then upon reboot the code was thrown, and it wouldn't boot again.
Edited by Tangles - 13 Apr 2018 at 2:05pm |
|
Post Reply | Page <12 |
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 |