X670E Ace Bios Problems

B

BiscuitBomber

Active member
Joined
Oct 19, 2022
Messages
166
Hardware:
Processor: 7950X
Motherboard: MSI X670E Ace
GPU: EVGA 3080 TI FTW3
MEMORY: G.SKILL Trident Z5 Neo RGB Series AMD EXPO 32GB (2 x 16GB) 288-Pin PC RAM DDR5 6000 (PC5 48000)
PSU: EVGA 1000W P6
Cooler: 360 Phanteks AIO MPH

After updating my BIOS today on my PC. When booting up I was getting BIOS Code A6 and the RAM light was staying Amber. This didn't occur on the previous BIOS 7D69v13. I attempted to clear CMOS but same issue. I ended up downgrading my BIOS back to 7D69v13. I opened a ticket with MSI, but just a heads up in case anyone else runs into this. Before 7D69v142 I had zero issues with RAM and bootup problems.


----------------
EDIT Title
Alan J T
 
Last edited by a moderator:
Sort by date Sort by votes
So I decided to try out Buildzoids AM5 Memory timmings for Hynix memory. Worked nicely and dropped my latency nicely. I have to say MSI Bios is a pain. I changed the memory settings in the OC menu. When I booted into Windows and ran zentimmings I notice only some of the settings changed. Wasn't till I went into the settings menu and changed them under the AMD OC menu did the rest change and stick. Why can't they just have everything to do with OC/Timmings in the OC Menu and the rest in the Settings menu.

1727226905193.png
 
Upvote 0 Downvote
I'm not so sure this will be stable if the previous screen wasn't

AMD Overclock menu should stay untouched (it's the menu with the warning to accept), only thing allowed here is maybe nitro parameters for very advanced users.

please use only the MSI Overclock page

if you use both menus some settings will overlap in unpredictable ways, at the end you don't know exactly what will be used. Stick with just the MSI menu and ignore the AMD OC menu entirely.
This is particularly dangerous with voltages.
 
Last edited:
Upvote 0 Downvote
Michele P said:
I'm not so sure this will be stable if the previous screen wasn't

AMD Overclock menu should stay untouched (it's the menu with the warning to accept), only thing allowed here is maybe nitro parameters for very advanced users.

please use only the MSI Overclock page

if you use both menus some settings will overlap in unpredictable ways, at the end you don't know exactly what will be used. Stick with just the MSI menu and ignore the AMD OC menu entirely.
This is particularly dangerous with voltages.
Click to expand...
Have no fear I know what I'm doing. I came from Gibabyte and their BIOS menus where much easier to follow. It just makes no sense that I change all my memory timmings in the OC Menu and only some show changed in zen timmings, yet are all changd in the BIOS.
 
Upvote 0 Downvote
ht_addict said:
Have no fear I know what I'm doing. I came from Gibabyte and their BIOS menus where much easier to follow. It just makes no sense that I change all my memory timmings in the OC Menu and only some show changed in zen timmings, yet are all changd in the BIOS.
Click to expand...
U3q4R8z.png


if you start touching things in the AMD Overclocking you don't know what will happen, some settings will overlap and things set in the MSI menu will be overwritten by settings in this other AMD menu, or viceversa it's random.

so don't touch the AMD Overclocking... and if you did, maybe better clrmos and start from scratch

Everything you need is already in MSI OC menu
 
Last edited:
Upvote 0 Downvote
Michele P said:
Check if there's something logged in the event viewer during the failed boot process, if it is able to log anything.
Click to expand...
About 175 a lot is internet connection issues for start-up stuff and that's a normal start-up as to failed will have to wait till it happens again
 
Upvote 0 Downvote
Michele P said:
Everything you need is already in MSI OC menu
Click to expand...
No, everything you need is in the working AMD menu!
nobody needs the faulty MSI menu!
To this day, nobody understands why MSI wants to make something of its own and then is so stupid and fails to keep both points synchronized.
The AMD menu is the interface to the Agesa, the faulty MSI thing links to the interface, just leave the junk out.
 
Upvote 0 Downvote
daedric.kaie159902e6 said:
No, everything you need is in the working AMD menu!
nobody needs the faulty MSI menu!
To this day, nobody understands why MSI wants to make something of its own and then is so stupid and fails to keep both points synchronized.
The AMD menu is the interface to the Agesa, the faulty MSI thing links to the interface, just leave the junk out.
Click to expand...
you are clearly the one who get banned every time throwing toxicity on this forum, get a life, trust me.
I suggest you to buy Asus xD
 
Upvote 0 Downvote
It is true that it is super counter-intuitive. In fact, some settings do not have an effect at all. If you try to cap the voltage in the OC settings of the MOBO to, say, 1.2, it looks like it doesn't care what do you set in most other settings like PPT. By the way: there are multiple places you can set power limits, and none appear to work then. Also, what does it mean if I use vcore override + AMD overclocking? I would expect it to cap the max voltage and let AMD handle the offsets (reduce voltages under load and so on). Apparently this does not happen, and you can be frying your CPU over 100 degrees (max temp throttle is not respected either).
 
Upvote 0 Downvote
MSI understood that ACE was too good and not X870E ACE apprently... sad to loose the ACE series, it was the only interesting board from MSI to me.
 
Upvote 0 Downvote
Quick update, Bios J3 installed, so far so good, always same settings but... have been quite busy with other things
So here's the story, maybe you can find it interesting if you have an AIO and/or LED problems on this motherboard.

After 2 years I started noticing my EK AIO Elite wasn't cooling the CPU as expected.
My idle temps usually were about 47/50 {with a tamb of 26/28 degrees in this hot season)
In the last weeks the idle temperature rised to 55, even with the pump maxed out, clearly something wasn't right.
Cleaned all dust filters but didn't improve anything.
Until few days ago, all of a sudden I was idling at 65 degrees, unacceptable.
Turned off the pc and started searching for leaks.
Luckly it wasn't the case but I couldn't trust the AIO anymore, so I ordered a Galahad 2 trinity performance and in the meanwhile, I started inspecting the old AIO.

The EK AIO apparently is fine: RPM of the pump 3200rpm detected in bios/howinfo, I can feel/hear the pump running and few bubbles guggling when changing rpm.
Everything nominal except for a couple things:
- the pump block gests hot, and I mean VERY hot to the touch (speaking of sensors HWinfo reports the usual 40ish degrees on the cpu cores, but CPU IOD hotspot is way too high)
- and the radiator is even more weird, I can feel warm air being expelled only from the portion fo the radiator where the tubes are attached, as if the water isn't reaching the entire radiator and flows only in the first third, if that makes sense.

Repasted, mounted the new AIO and immediately the idle temperatures went down to 42/44. A clear improvement and at first a was very happy because CPU was running cold again (if not better than before)
The more interesting change is on the CPU IOD hotspot sensor: now hwinfo reads 38/39, even lower than the cores temperatures, WTF???? (maybe there's a correlation between this sensor placement and the old AIO overheating)

But happiness didn't last long, because after all this work the shocking discovery:

THE LEDs ON THE MB STOPPED WORKING
and also the ARGB controlled devices attached to the MB connectors of course.

Maybe I accidentally touched the switch on the bottom of the mb? no, it was on
Maybe the ARGB lights are turned off inside the new bios? tried on/off/on again no changes

I lost an entire day trying to figure out what was wrong.

Windows detected an unidentified USB device, likely the mb RGB controller (not the new galahad controller because it was disconnected while diagnosing the problem)
Mystic light was detecting something abnormal on the firmware
MSI center could not find any firmware update
The manual FW updater could not find the device at all


I was panicking.

Then I did this:

Detach every ARGB connected to mb pins.
CLRMOS
Unplug power
wait 5-10 min
Attach power
Press CLRMOS again (after a couple failed boots I managed to enter bios and set everything as usual)

The LEDs on the MB started working again!

The problematic usb device disappeared from the windows device list, cause it's being correctly detected now.
So I proceeded to update the LED Firmware, what a better occasion
This time MSI Center detected the newest firmware and updated
Then again: clrmos, unplug power, wait 5-10min
Everything was nominal after the firmware update.

At this point I decided to connect again all my 3 ARGB connectors to the MB (while pc was turned off), and I confirm everything is working again as expected.
the 3 argb connectors are used to sync the lian li hub, the galahad aio, and the case led strip

Two "intense" days for sure.

I don't know what is the problem on the old EK AIO, could be anything from clogging to liquid permeation. I exclude a pump failure: I can see the sensor reading nominal rpms and the water is definitely flowing. I don't know how much water is left or if there's an obstruction somewhere.
The AIO is refillable, but first I want to ear EK support

Hope you liked the story
A "thrilling" experience worth sharing, but I don't wish on anyone

EDIT: adding pictures, all leds working again 🥳
I usually keep the leds on the fans off, that's why I decided to don't swap the stock performance fans on the radiator, those are special fans with better static pressure than the SLV2
And pls don't pay attention to the ugly seasonic PCIe power cable: I tried twice with the white ones from cable mod but both started glitching after few months of use (black screen fans at 100% bug because of the poor quality sensor cables).
This is the ONLY cable working good for me, and I don't want to touch it anymore, not even by mistake. Also, the connector wears off if you change too many cables (if you didnt know), better not taking other risks.

tQ6RGon.jpeg
StkTbVe.png
 
Last edited:
Upvote 0 Downvote
I believe that in recent bios updates, circa middle 2024, they messed ace boards horribly
these are three posts with the same problems, including mine
I hope this is not the hardware issue

Idk, were there more posts about this problem? Basically, if you suddenly turn off the power (not the pc, the power, for example the tumbler on the power supply), the board will stuck on code 00 (x570 ace) or code 10 (x670e ace). I have two x670e ace and the problem persists on them both. My local repairment center did a lot of tests, they said it 100% the board, so I bought the identical board, hoping the problem will fix. On 7D69v1I (the latest non-beta bios for x670e ace) the problem persists.
 
Upvote 0 Downvote
Me and my local repairment center produced a lot of videos about the problem. There was a clear difference between my first board and this one. On the first board there were codes 10/99, on this one there is only code 10. It fixed itself after couple of hours without power and after clearing cmos, but I believe it is not about MCR. On the first board with codes 10/99 it was fixing in a couple of minutes, you just turning off the pc normally when 99 occurs and it will load fine on the next boot. With the second one you really need to wait about couple of hours without power, because code 10 doesn't allow you to turn off the pc at all, and I believe not everyone fixed this, when they started to for example removing their memory modules. That is not how I was fixing it. I was at my local rural area when build my PC and there were power losses about once a week, not everyone are having this problem because power losses are particularly rare in large cities.
 
Upvote 0 Downvote
You can try to imitate power loss on your x670e ace with 7D69v1I bios by clicking the tumbler on a power supply, and say is this true for you or not. But if this is true, your board may die, its not impossible, but its pretty hard to save it from the code 10 orange/red state. I really hope they will fix it on 7D69v1J.
 
Upvote 0 Downvote
I tried to manually edit the DRAM settings tonight, it was a disaster despite me religiously copying all the numbers and doublechecking if I did anything wrong. Probably did and missed something otherwise I won't be posting here.

The 00 bug still hit and there was no change but when I turned it off again and turned it back on it won't POST anymore. Tried the back CMOS button a couple of times while my PC is unplugged but it didn't work so I had to stick a screwdriver in the JBAT1 pins. It also did not work and instead gave me an Ad debug error. Last resort was taking out my second DRAM while keeping slot 2 occupied and it went back to the BIOS like a charm.

Turned EXPO off permanently too and restored defaults, hopefully MSI fixes this soon. My X670E Ace worked earlier this year even with long boot times.
 
Upvote 0 Downvote
theaushwits151d02d3 said:
ut its pretty hard to save it from the code 10 orange/red state. I really hope they will fix it on 7D69v1J.
Click to expand...
Unplug the PSU hold down the PC power button for 10 to 15 seconds and then hold in the Clear Cmos on the back of IO for over 60 seconds
 
Upvote 0 Downvote
Back
Top