PCIe bug with M2_1 slot on X870E Tomahawk

jlsmith.01712b902af

New member
Joined
Feb 16, 2025
Messages
14
So, the M.2_1 slot keeps reverting to PCIe 1 x 4 on a cold boot, sometimes just a reboot from within Windows. Manually setting it to Gen 4 or 5 within the BIOS will get it to run full speed until the next shut down/cold boot, then it's back to 1 x 4 again. Basically, I have to keep switching between gen 4 and 5 setting on every boot or it's stuck at 1 x 4. Auto is also broken. Samsung 990 Evo Plus 1TB.

I've seen another user on Reddit with the exact same issue. Same board, different drive. Anyone using this board, check your drive speed!
 
Yes the M2_1 speed bug. Has it been fixed though? Reading through all the posts it looks like only 1 person said that they have not had the issue since installing A52 firmware, no one else has either confirmed or denied... and earlier MSI was saying bios update could not fix it and was having people RMA their motherboards...
I think that was only in reference to the Godlike, not the Tomahawk. Even for the Godlike though, I think the jury is still out on whether an RMA really is necessary, as the issue does appear fixable with a BIOS update.
 
That problem was solved long ago and is not likely to be a problem in any current Retail board being sold.
The problem you are talking was about 7800X3D, i'm talking about 9800X3D, and this is still ongoing problem. You can check for a huge reddit thread with daily CPU Dying:
9800X3D Failures/Death Megathread.
There is more than 200 cases i would guess as of now. And it's seems like it's the voltage issue.
That's why i'm so touchy on this topic.

Also the MSI decided instead of actually give a proper description to remove the "recommended" part.

So if i just have EXPO(memory) enable to run at the default expo profile, aka 6000 MT, CL 30, should i use the AMD Overclock and let the values at Auto, or should i just use the Mobo voltage, aka the Auto ?
 
Also the MSI decided instead of actually give a proper description to remove the "recommended" part.
Ya, they got pestered by myself and other mods to fix the description

Now the reason they recommend it for that bios version is if you use the non AMD Voltage setting, you may experience a problem of the CPU getting locked as a LOW Speed, lets say, ie 1200MHz or lower instead of the base 3600MHz

And this is only if you change the CPU voltage for overclocking or undervolting
SOC is not affected
 
Ya, they got pestered by myself and other mods to fix the description

Now the reason they recommend it for that bios version is if you use the non AMD Voltage setting, you may experience a problem of the CPU getting locked as a LOW Speed, lets say, ie 1200MHz or lower instead of the base 3600MHz

And this is only if you change the CPU voltage for overclocking or undervolting
SOC is not affected
The Godlike has dual BIOS, might have to switch to the other one to install this, at least if it goes south I can switch back!
 
Yes the M2_1 speed bug. Has it been fixed though? Reading through all the posts it looks like only 1 person said that they have not had the issue since installing A52 firmware, no one else has either confirmed or denied... and earlier MSI was saying bios update could not fix it and was having people RMA their motherboards...
I'm confident it is fixed, as I was given the beta A41 originally before sharing it and it fixed it for me after many long hour tests over 7 days and using it for over a month. The new A52 Bios has the fixed included and have been using that since last week with zero M2.1 speed drops or lower drive benchmark tests, as I do one on every boot up atm.
 
I'm confident it is fixed, as I was given the beta A41 originally before sharing it and it fixed it for me after many long hour tests over 7 days and using it for over a month. The new A52 Bios has the fixed included and have been using that since last week with zero M2.1 speed drops or lower drive benchmark tests, as I do one on every boot up atm.
it depends on the motherboard. There has never been any sign of any attempted fixes made for the Godlike and that is a board MSI said to RMA (an RMA will not fix it). Only the Tomahawk is fixed. The Godlike is still just as [***CENSORED***] as it always was. MSI support ghosted me when i ask about what is going on with the Godlike. And no idea on the stats of any other boards but i would not be surprised if they ignored every other board too.
 
I updated my x870e to 7E59v2A5 and is running fine with a T705 (with integrated heatsink) at PCIe 5.0 x4 speeds. Been 24 hours, have performed multiple cold and warm starts and comes up each time as expected.
Speeds seem to be good, but I did manage to push the temperature up to 75°C on the drive.
View attachment 200882

Wait a minute, while I have not had the link speed issue since vA41 either (now on vA52), but my RND4K Q32T16 scores seemed extremely poor. I was looking for something to compare with, and found yours in this very thread. My first drive (C) is a T705 gen5 1TB with integrated heatsink, and my second drive (D) is a Silicon Image XS70 4TB gen4. I looked at my old benchmarks from an older bios (Feb 2025), and both drives show normal Q32T16 performance like how it needs to be. The issue is with both drives, not just one, so it's not even drive specific.

Any ideas why guys?

Now on vA52:
now.png


Feb 2025 (didn't record which bios I was on), but same exact HW. See how much higher the Q32T16 perf is
then.png
 

Attachments

  • now.png
    now.png
    147.1 KB · Views: 19
  • 1745951404720.png
    1745951404720.png
    1 MB · Views: 19
it depends on the motherboard. There has never been any sign of any attempted fixes made for the Godlike and that is a board MSI said to RMA (an RMA will not fix it). Only the Tomahawk is fixed. The Godlike is still just as [***CENSORED***] as it always was. MSI support ghosted me when i ask about what is going on with the Godlike. And no idea on the stats of any other boards but i would not be surprised if they ignored every other board too.
Yeah it does, yet this thread is the Tomahawk one though, which is the MB I own.
 
Hi guys, is it normal to have the cpu vddio voltage like +0.24 all the time? For example I set 1.4v on bios but it reads 1.424

Also how do you disable USB4 or how do you disable lane sharing? I have the carbon wifi
 
Last edited:
Haha, I just took a look at the 2A52 bios description on the site, and it turns out they clarified the famous line about "AMD overclocking settings". Their solution? Remove the line entirely, so no more problems, people won't complain anymore... "Move along dear customers, nothing to see here!"
 
Last edited:
Haha, I just took a look at the 2A52 bios description on the site, and it turns out they clarified the famous line about "AMD overclocking settings". Their solution? Remove the line entirely, so no more problems, people won't complain anymore... "Move along dear customers, nothing to see here!"
An update to a bug but introduce another bug... terrible. BIOS update suppose to make the board perform better, especially those auto mode settings. Now the whole world is left guessing "what-if".
 
An update to a bug but introduce another bug... terrible. BIOS update suppose to make the board perform better, especially those auto mode settings. Now the whole world is left guessing "what-if".
What bug are you talking about? To my knowledge the last bios didn't introduce any bug, they just wrote an incomprehensible description. And instead of clarifying it, they deleted it.

Apart from that the 2A52 bios works perfectly, I have exemplary stability with Expo + undervolting with Curve Optimizer while keeping the default settings. Rock stable bios.
 
Ya, they got pestered by myself and other mods to fix the description

Now the reason they recommend it for that bios version is if you use the non AMD Voltage setting, you may experience a problem of the CPU getting locked as a LOW Speed, lets say, ie 1200MHz or lower instead of the base 3600MHz

And this is only if you change the CPU voltage for overclocking or undervolting
SOC is not affected
Mate can i ask you, if i use PBO on just Enable, i mean let the PBO does it magic, and not do manual overclock, do i need to set the CPU Core Voltage to AMD Overclock or Auto is safer?
Does i need to go for manual voltage values ?
 
Getting back to the original topic of this thread....
Just received my most recent response from the support team regarding the M2_1 issue for the Godlike Model:

AGENT [Unfortunately, there is no BIOS update that will address the issue you are having with the board. our team was not able to find or duplicate issue.]

I call this BS as so many of us have had this issue across all of their X870E platform Not even sure what to say at this point really with a trouble ticket opened up now for 9-10 weeks, and clearly seeing the Tomahawk users got a Bios update that fixed it.
 
Getting back to the original topic of this thread....
Just received my most recent response from the support team regarding the M2_1 issue for the Godlike Model:

AGENT [Unfortunately, there is no BIOS update that will address the issue you are having with the board. our team was not able to find or duplicate issue.]

I call this BS as so many of us have had this issue across all of their X870E platform Not even sure what to say at this point really with a trouble ticket opened up now for 9-10 weeks, and clearly seeing the Tomahawk users got a Bios update that fixed it.
Not able to find or duplicate the issue!?!? what the actual F!??? I have personally went through THREE DIFFERENT godlike boards, and an extensive data collection effort on Reddit. And every single Godlike board in existence has the same problem! I have yet to find a single instance where I could NOT duplicate the issue! Even everyone who thought they did not have the issue but was able to read English and follow basic instructions went back and verified they also have the issue. It is the same issue they already solved on the Tomahawk! how are are they so incompetent! *end rant*

What are our actual options at this point? There is a moderator that reads these forums and has a connection to MSI, right? I think that is how this originally got attention on the Tomahawk? can that moderator help us out here and tell them they are full of it and tell them to just apply the same fix to the Godlike too? or do we literally need to sue them?
 
Getting back to the original topic of this thread....
Just received my most recent response from the support team regarding the M2_1 issue for the Godlike Model:

AGENT [Unfortunately, there is no BIOS update that will address the issue you are having with the board. our team was not able to find or duplicate issue.]

I call this BS as so many of us have had this issue across all of their X870E platform Not even sure what to say at this point really with a trouble ticket opened up now for 9-10 weeks, and clearly seeing the Tomahawk users got a Bios update that fixed it.
The level of bullshit it takes to dare to respond that they "cannot replicate the issue"... While ALL buyers complain about it, and it's THE MOST EXPENSIVE MOTHERBOARD ON THE MARKET at around $1300. This may be the crux of the problem, it's probably so expensive that the number of buyers of the Godlike must be much lower than that of the Tomahawk. Basically, Godlike buyers are just a drop in the ocean of their customers, so they prioritize the cards they sell the most. I don't see any other reason for this nonsense. They just think the problem (complaining buyers) will go away on its own, so why bother?
 
What bug are you talking about? To my knowledge the last bios didn't introduce any bug, they just wrote an incomprehensible description. And instead of clarifying it, they deleted it.

Apart from that the 2A52 bios works perfectly, I have exemplary stability with Expo + undervolting with Curve Optimizer while keeping the default settings. Rock stable bios.
Your last message indicated no short of bug. This is a good one: https://forum-en.msi.com/index.php?...1-slot-on-x870e-tomahawk.409663/page-22#posts
 
Back
Top