![]() |
Error code a8 on Taichi z270 |
Post Reply ![]() |
Author | |
mbaren ![]() Newbie ![]() Joined: 25 Feb 2017 Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() Posted: 25 Feb 2017 at 11:07pm |
Hi there -
I recently got a Taichi z270 board. It works... sort of. Basically, every time I power up, it almost immediate shows an error code of a8, which is unfortunately not in the Dr. Debug documentation. And it hangs immediately - no chance to get into UEFI or anything. Then, if I immediate power off and power back up, the CPU fan spins up, stops, and then starts again, and the whole things boots as normal. So I can use my PC, but obviously something is a little off. I've done the whole "clear CMOS" thing, which seems to be a suggested response to a whole lot of errors, but it didn't fix the issue. Any ideas? I'm kinda lost here. |
|
![]() |
|
Xaltar ![]() Moderator Group ![]() ![]() Joined: 16 May 2015 Location: Europe Status: Offline Points: 27188 |
![]() ![]() ![]() ![]() ![]() |
Could you provide a full list of system specs including power supply brand and model, it is also helpful if you identify any old components that have gone into your build.
Clear CMOS works for a (seemingly) wide variety of issues, the reality is that it works with UEFI related issues which makes the number of times it is suggested make a little more sense. The vast majority of issues we see here on the forums are either compatibility, PSU or UEFI related. In addition, does this happen every time you power on or only from cold boot (the system being turned on for the first time in over several hours)? Error a0-a7 are storage related so I would try disconnecting your drives and testing to see if you can get into the UEFI (reproducing the issue without storage/drives connected).
|
|
![]() |
|
![]() |
|
mbaren ![]() Newbie ![]() Joined: 25 Feb 2017 Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() |
Thanks for the response!
So, I figured it out - it's actually a RAM issue. It seems that my Corsair ram sticks (CMK16GX4M2B3000C15) are not officially supported by this board. So even though the board will read their XMP profile (which is for 3000MHz), this problem occurs when I attempt to use it. If I shut off XMP, the issue goes away. That's a bit of a bummer, but at least I figured it out. FWIW, here's my full build: i5-7500 ASRock 270 Taichi Corsair Vengeance LPX 16GB (2x8) DDR4-3000 (CMK16GX4M2B3000C15) Intel 520s SSD Samsung 850 EVO SSD Gigabyte GeForce GTX 750ti EVGA SuperNova G2 650W 80+ Gold Certified Fully-Modular ATX Power Supply
... and some USB devices Also, with regards to your question about when it happens - yes, it happens booting cold, or not-so-cold. The problem is pretty consistent all around. Anyway, in the interest of being thorough I wish ASRock would update its documentation to include the a8 code, and of course hopefully a future bios update will make my memory compatible, but at least everything's working okay now. |
|
![]() |
|
Xaltar ![]() Moderator Group ![]() ![]() Joined: 16 May 2015 Location: Europe Status: Offline Points: 27188 |
![]() ![]() ![]() ![]() ![]() |
Thanks for posting back, the Z270 boards are still very new and will be receiving updates for a while before all the kinks are worked out. Luckily it seems they are less buggy than Skylake was at launch
![]() |
|
![]() |
|
![]() |
|
parsec ![]() Moderator Group ![]() ![]() Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
![]() ![]() ![]() ![]() ![]() |
So a memory, or really yet another DDR4 XMP profile issue. I've used XMP profiles with every mother board with DDR2 and DDR3 memory I've owned, but DDR4... I wouldn't use the XMP profile, or I should say I can't use them, nothing but problems. What I use that works for me with DDR4 memory is the DRAM Tweaker feature in the DRAM Configuration screen. It looks like it just reads and lets you apply some of the XMP data/settings from the memory, but must be only a subset of the XMP data. Give that feature a try. An A8 POST code? The Ax codes are generally SATA and storage drive related. Might be the memory that AHCI uses causes that failure when using the XMP profile. ![]() |
|
![]() |
|
mbaren ![]() Newbie ![]() Joined: 25 Feb 2017 Status: Offline Points: 5 |
![]() ![]() ![]() ![]() ![]() |
Thanks! Yeah, I may give that a try this weekend.
|
|
![]() |
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 |