X670E Ace Bios Problems

B

BiscuitBomber

Active member
Joined
Oct 19, 2022
Messages
167
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
Some feedback from my side. Please note it is not for the ACE X670, but for the "MAG B850 Tomahawk Max Wifi", which I am currently making ready for a customer, where I have installed the latest 1.2.0.3c beta Bios (2A22). This custom build was 10000000% stable since I first touched and fine tuned the BIOS configuration. Working now nearly 5 days stable, without any weird power fluctuations, smart fan feature working as expected, 32GB Memory (2x16) 10000% stable at 6400 CL36 @1.35V / 1.25 SoC ... No quirks or problems which gives me high hopes also for the 1M1 for the Ace. Once I have finished this custom build I will take care of my own Ace :)
 
Upvote 0 Downvote
OK... interesting... AS___k "thinks" they have fixed their issues with X3D CPUS and them burning.
Steve from GN posted a new video on it. Seems like this is an AS__k specific fault? We will see... GN is preparing a full investigative report on it. GN is not convinced yet that the newly released 3.25 has completely fixed the issue.
Just wanted to let you all know that this seems to be AS___k specific issue... (cause in the past weeks/months we all had our own theories.)
If you want to take a look at the interview :
 
Last edited:
Upvote 0 Downvote
sblantipodi said:
Gamer nexus is preparing a lot of investigations but we have seen very very few results for those investigations
Click to expand...
Takes time my friend.... if you want to do it right and go down the rabbit hole... important message still is -- seem to be AS___k specific issue. Only one or two cases on GB and then nothing. (mind me --- have not searched till I have reached end of the internet yet).
 
Upvote 0 Downvote
Dave_Toast said:
Installed the new BIOS, looks like the EXPO on bug/00 code with amber light will never be fixed.
Click to expand...

I don't think it can be fixed with any bios update, I suspect we degraded our CPU's just enough when we ran with those default unsafe voltages spikes before the more sensitive X3D chips finally showed the problem by burning up.
 
Upvote 0 Downvote
sblantipodi said:
Do you mean VSOC higher than 1.3V?
Click to expand...

Yes, been like 8-9 months before the first X3D started burning and revealed the problem.

All those months the 7600X, 7700X, 7900X, 7950X were slowly degrading with the VSOC spikes (now depending on mainboard brands some spiked more aggressive then others), slowly cooked our IMC's.

That is modern tech, rushed out the gate, improper testing and specs at the limit straight from the box.
 
Upvote 0 Downvote
sherbrovideo15a102de said:
I don't think it can be fixed with any bios update, I suspect we degraded our CPU's just enough when we ran with those default unsafe voltages spikes before the more sensitive X3D chips finally showed the problem by burning up.
Click to expand...
So you suspect it's a CPU problem? The BIOS and my 7800X3D runs fine, it's just I can't turn on EXPO anymore for at least 1.5 years now. I tried setting things manually and it still didn't work.
Will never buy a MSI mobo again as well as Asrock. Asus have their own problems so I guess I'm stuck with Gigabyte.
 
Upvote 0 Downvote
...except gigabyte had troubles with high vsoc even after the 1.0.0.7c agesa update... the specific release that introduced the soc limit at 1.3V for the first time.
Buildozoid was going crazy in one of his old video working on a gigabyte: soc was set manually at 1.2V but the GB mobo decided to run it at 1.35 for reasons, overriding both the user value and even the 1.3V limit,... it was a pretty dangerous bug (in fact they nuked the bios from their support pages after a while)
The high soc was responsible for some burnt cpu, but imho it wasn't the main cause... at least not the only cause. The early batches likely experienced a significant failure rate as well, but AMD will not admit something like that.

it can't be helped. All vendors, with no exceptions, have had problems in the past, or will have them... more or less serious. But most of the time, it is AMD causing the issues.

Im not so sure this issue of failed reboot with expo enabled is caused by long term use with high vsoc anyway.,.. my idea is that there's something bugged around smbus, or similar, that prevents the system from reading expo data correctly from the ram stick in particular situations
When this expo restart problem appeared for the first time, I remember somebody claimed that older bios weren't effected, but we are talking about very old bios, from 1 year ago or more... I can't recommend such a dramatic roll back just to see if the expo restart bug disappears.
 
Last edited:
Upvote 0 Downvote
Dave_Toast said:
So you suspect it's a CPU problem? The BIOS and my 7800X3D runs fine, it's just I can't turn on EXPO anymore for at least 1.5 years now. I tried setting things manually and it still didn't work.
Will never buy a MSI mobo again as well as Asrock. Asus have their own problems so I guess I'm stuck with Gigabyte.
Click to expand...

Yes I repeat, I believe I have degraded my Integrated Memory Controller inside the CPU because of those voltage spikes. For me it took around half a year to happen in my 7700X and for you I guess it was faster with your X3D version since the extra cache is even more sensitive and I don't know how much time you used the unsafe bios versions, in theory it only takes one time to be unsafe and degradation can happen.

Gigabye had the problem as well, all vendors had it, especially Asus those seemed to have spiked the most aggressive number wise.

Now my CPU runs fine, EXPO on runs fine but whatever I do I can't restart the computer if my ram speed is above 4800 MT/s. If you can't even use EXPO whatsoever then your damage is even greater.

A new CPU will fix the problem, even with my current mainboard and ram kit is my suspicion but I'm not okay with spending more money or waiting a month plus without a working PC.

AMD was unsafe, mainboards vendors were unsafe. Guess you need to wait two years before jumping into a new platform in this 'modern' tech times but even now just look at the scandal with the 9000 series (second gen on AM5) and say ASRock mainboards.
 
Last edited:
Upvote 0 Downvote
sherbrovideo15a102de said:
Yes, been like 8-9 months before the first X3D started burning and revealed the problem.

All those months the 7600X, 7700X, 7900X, 7950X were slowly degrading with the VSOC spikes (now depending on mainboard brands some spiked more aggressive then others), slowly cooked our IMC's.

That is modern tech, rushed out the gate, improper testing and specs at the limit straight from the box.
Click to expand...

I don't know if that is correct, my launch day 7950X has survived three mobos and still performs as new
 
Upvote 0 Downvote
Back
Top