Question A6 code on motherboard, only lasts until 3rd reset button on case

[Avizzo]

Hi all, Avizzo here.

I know the A6 code on my motherboard (X870E MSI Carbon) is regarding the booting sequence, or attempting to “find” the boot drive. This is for the first boot-up of the day, which always is the one time a day I need to turn on my PC.

This ain’t my first rodeo building computers and I’d like to say I know what I’m doing. This situation is just new to me, but should easily be able to follow any instructions or recommendations.

I press the reset button on my case, and it will appear with the A6 code again. Without fail, the third time it finds the boot drive. On the third attempt, everything loads and I also have no computer issues.

I have two potential thoughts on what it could be. I saw some other threads regarding it being with the RAM overclocked? I honestly don’t know how that could affect booting into Windows. Especially since the RAM is overclocked to 8000Mhz (I used the QVL list to find RAM tested with my motherboard). If it was the RAM being overclocked, why would it always work on the third try? And the computer is completely stable while in-use.

This one seems goofy as I’ve never encountered this problem ever on any prior motherboard or in the BIOS. But I believe (it’s been a few weeks since I’ve build the PC, haven’t had much of a chance to play/test anything) the M.2 SSD with the OS is installed in the third slot on the board? I save the higher speed slot for my priority games that I play for faster loading times in those. I’d rather take longer to boot into Windows than the games themselves.

Maybe it’s the way my brain visualizes it, but I was thinking potentially the motherboard starts in the fastest SSD slot, doesn’t detect Windows, then gives the A6 code? Then it goes from leftmost to the right, and that’s when it finds the OS on the third drive? The only reason why this wouldn’t make sense is because you select the boot drive inside the BIOS, which it is already appropriately setup.

Fortunately, this problem isn’t hindering me from using my machine, but it’s an inconvenience and I was curious for a solution. I was thinking of just saying “Frick it” and putting the OS drive in the faster speed slot, but I’m avoiding it unless there’s nothing else to try.

Thank you as always to the Tom’s Hardware community for any help!

 

[helpstar]

is the bios up to date?
which psu are you using?
did you check the ram speed in windows, if it's set like you did in bios?
try a lower speed like jedec timings
check windows with dism commands
which ssd are you using? check for firmware updates and the ssd itself with its manufacturer's tool

 

[Avizzo]

is the bios up to date?
which psu are you using?
did you check the ram speed in windows, if it's set like you did in bios?
try a lower speed like jedec timings
check windows with dism commands
which ssd are you using? check for firmware updates and the ssd itself with its manufacturer's tool

Hi, helpstar.

My BIOS is up to date.

I’m on a Seasonic GX-1200. If you know the answer, what does the PSU/wattage have to do with booting into Windows?

In case this gets asked, I’m on a 4090 and 9800X3D.

Task Manager displays the 8000Mhz speeds, yes.
Not sure what JEDEC Timings are, but I assume it’s in relation to the “Memory Try It!” feature for MSI boards. I will take a look tonight and update when I’m home.

All SSDs are Samsung. I will use the Samsung Magician app tonight to check for firmware updates. I will also update about this later tonight.

Thank you for the suggestions!

 

[helpstar]

Seasonic GX-1200

if the voltage is not stable, the pc won´t boot or eventually can´t detect the boot drive in time
just for testing, disable the Hybrid Silent Fan Control on the back of the PSU

are you using the 12VHPR cable for the GPU?

are all cables from the PSU zjr ones which were delivered with it?



jedec timings/tables are just the non overclocked frequencies and timings a RAM has built in, when you don´t set an XMP or EXPO profile in BIOS

the BIOS version on the motherboard is V1.A30?

 

[Avizzo]

if the voltage is not stable, the pc won´t boot or eventually can´t detect the boot drive in time
just for testing, disable the Hybrid Silent Fan Control on the back of the PSU

are you using the 12VHPR cable for the GPU?

are all cables from the PSU zjr ones which were delivered with it?



jedec timings/tables are just the non overclocked frequencies and timings a RAM has built in, when you don´t set an XMP or EXPO profile in BIOS

the BIOS version on the motherboard is V1.A30?

Hi, helpstar.

Thanks for the infomation! I’ll be home soon to supply the rest of the infomation.

The “Hybrid” fan setting is off since I want max performance for the 4090 and 9800X3D.

I am using the 12VHPR cable and all included PSU cables with the PSU.

I’ll have to verify the BIOS version later. Usually they’re labeled differently than that, at least the file/folder is.

 

[Avizzo]

if the voltage is not stable, the pc won´t boot or eventually can´t detect the boot drive in time
just for testing, disable the Hybrid Silent Fan Control on the back of the PSU

are you using the 12VHPR cable for the GPU?

are all cables from the PSU zjr ones which were delivered with it?



jedec timings/tables are just the non overclocked frequencies and timings a RAM has built in, when you don´t set an XMP or EXPO profile in BIOS

the BIOS version on the motherboard is V1.A30?

Good morning, helpstar.

Sorry for the late reply. I did some testing and stuff last night and went to bed shortly after. Planned on replying right now.

I doubt it's coincidence, as it happened when I came home and stopped after I updated it. But I was, up until 3-4 days ago, up to date on my BIOS. I did a BIOS update, as everything else (SSD firmware, etc.) was up to date. Since the update, I turned on and off my PC last night a few separate times within an hour interval of one another, and the computer never gave the A6 code!

So, it seems like the prior BIOS had some type of issue locating the source of the OS drive.

Thank you for all of the extra information that I can use in the future, as well as explaining new things to me. If for any magical reason this resumes, I will reopen another thread.

For anyone else who might have this issue and have the same board, update to 7E49v1A3 (or the 1A30 file is named "E7E49AMSI.1A30").