PCIe bug with M2_1 slot on X870E Tomahawk

J

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!
 
Sort by date Sort by votes
I just noticed that even when it says its at pcie 4.0 x4 in Crystal it still benchmarks at pcie 1.0 speed. So the bug seems to go even deeper.
 
Upvote 0 Downvote
Under RAID1 with disks in M2_1 and M2_2 with PCIE switch for M2_2 in full x4 for PCIe (USB4 disabled), i am seeing in BIOS both NVMe's in negotiated speeds of x4. Regardless on which PCIe gen i chose the x4 shoes the same on A41(beta) version of BIOS.
I also did several tests and under PCIe Gen2 for M2_1 only and leaving the auto for M2_2 the speed is double versus any other mods selected, but still not as fast when once in awhile kicked in the PCIe Gen4 on both. In other words, in Windows if it shows Gen3 for M2_1 and Gen4 for M2_2 the speed is way slower than manually setting the PCIe Gen2 in M2_2. Also that weird setting set, it survives reboots.
Here is what i mean:
M2_1_gen2.png


To compare my results under RAID1 with all on Auto, look for my prior posts and you'll see the the speeds are half. At least, while they'll fix it, you can go with M2_1 @Gen2 and double your speeds meanwhile rather than being stuck at Gen1. Heck, i tried to use Gen1 manually, that didn't worked, so something is getting this thing stuck in Gen1 continuously, with iffy unknown behaviors going in Gen4. I'll get a Gen5 NVMe, next week. Let's see what drama from other nvme's will show from that move.
 
Upvote 0 Downvote
I have problem with tomahawk and msi spatium m560. PCIe 1.0 x4. Speeds 930mb/s. there is no problem with second drive kingston KV3 4tb - PCIe 4.0x4.
After ticket support send me bios 41 and now everiting its OK. Now m560 work as PCIe 5.0 x4 and soeed is 10000+ MB/s. No errors ot boot. Speeds are OK.
 
Upvote 0 Downvote
bodonanc158f02e3 said:
I have problem with tomahawk and msi spatium m560. PCIe 1.0 x4. Speeds 930mb/s. there is no problem with second drive kingston KV3 4tb - PCIe 4.0x4.
After ticket support send me bios 41 and now everiting its OK. Now m560 work as PCIe 5.0 x4 and soeed is 10000+ MB/s. No errors ot boot. Speeds are OK.
Click to expand...
Yes Beta BIOS A41 solves the problem for the Tomahawk, it's not been released to the public yet.
Hopefully the Godlike will get a fix soon as well.
 
Upvote 0 Downvote
I've also had the problem with speeds, and I downloaded the Beta BIOS A41, which solved the problem (just normal flash BIOS without CMOS reset).

I have two Samsung 990 PRO drives, one on the M2_1 port and the other on the M2_2 port. With USB 4.0 disabled, both M.2 drives now show as 4x4 in Samsung Magician, and the tested speeds are good.

No problems with the beta BIOS either. The only thing I had to do was manually set the RAM speed to 6000 MHz because after the update, it was reset to 4800 MHz.

Hope this update will work for everyone.
 
Upvote 0 Downvote
daniel.mcgowan1160b02f1 said:
I installed it and it has been a nightmare. first up, no, it did not solve the problem. PCIe 1.0x4 mode.

Second, i now have lots of other problems. I can very rarely get a monitor to pick anything up until after Windows boots up now, so I have been struggling to get into the BOIS. i also just installed a 5090, so this might be the black screen issue people have been complaining about? So a different problem? don't know. Anyway, in my attempts to get into the BIOS by restarting a bunch of times i ended up getting a lot of "CPU and DDR error" messages so i could no longer get into anything at all. Playing with different ram sticks taking them in and out sometimes got me that error, sometimes "boot error" message, and sometimes it actually works. I was able to flash the new BIOS by using a usb and the button on the back so that way I didn't need a monitor to work to flash it. And I used a monotor plugged into the mobo instead of my 5090 to eventually get a screen. anyway, that was a PITA. I dont know what caused what or if there are now overlapping problems, but now that i have the new BIOS installed and restarted a few times.... its still 1.0x 4 mode. so. thats great.
Click to expand...
Sounds like a 5090 problem, there have been many similar issues about black screens etc
 
Upvote 0 Downvote
kikee2312ad02b0 said:
I've also had the problem with speeds, and I downloaded the Beta BIOS A41, which solved the problem (just normal flash BIOS without CMOS reset).

I have two Samsung 990 PRO drives, one on the M2_1 port and the other on the M2_2 port. With USB 4.0 disabled, both M.2 drives now show as 4x4 in Samsung Magician, and the tested speeds are good.

No problems with the beta BIOS either. The only thing I had to do was manually set the RAM speed to 6000 MHz because after the update, it was reset to 4800 MHz.

Hope this update will work for everyone.
Click to expand...
Yeah, thanks for confirming it’s fixed too in the beta. I did so much testing on it for days, I need a break now.
 
Upvote 0 Downvote
I will probably install the beta since people have confirmed it has fixed the issue. But in case anyone was wondering msi support just answered my ticket saying they are currently working on the issue and a bios update should be available in the next 1-2 weeks
 
Upvote 0 Downvote
traviskubast12c802b3 said:
I will probably install the beta since people have confirmed it has fixed the issue. But in case anyone was wondering msi support just answered my ticket saying they are currently working on the issue and a bios update should be available in the next 1-2 weeks
Click to expand...
Was their answer only about the tomahawk? I need a fix for the Godlike and i just got a response to install the currently posted BIOS file which we already know doesnt work. And they should also know doesnt work. So that is super frustrating. support quality seeme to vary a lot based on who gets your ticket and my guy is clueless. if they ever give us a beta for the godlike i might need someone else to post it for me so i can just bypass them.
 
Upvote 0 Downvote
daniel.mcgowan1160b02f1 said:
Was their answer only about the tomahawk? I need a fix for the Godlike and i just got a response to install the currently posted BIOS file which we already know doesnt work. And they should also know doesnt work. So that is super frustrating. support quality seeme to vary a lot based on who gets your ticket and my guy is clueless. if they ever give us a beta for the godlike i might need someone else to post it for me so i can just bypass them.
Click to expand...
Although I'm now using my SSD in M2_2 so don't have the problem on my Godlike, I've just replied to their last response saying the BIOS 1A30 doesn't solve the problem, hopefully they'll respond again.
If they do send me a Beta BIOS I'll upload it to Dropbox/OneDrive and post a link.
We might get a fix eventually!
 
Upvote 0 Downvote
daniel.mcgowan1160b02f1 said:
Was their answer only about the tomahawk? I need a fix for the Godlike and i just got a response to install the currently posted BIOS file which we already know doesnt work. And they should also know doesnt work. So that is super frustrating. support quality seeme to vary a lot based on who gets your ticket and my guy is clueless. if they ever give us a beta for the godlike i might need someone else to post it for me so i can just bypass them.
Click to expand...
my ticket was for the Tomahawk and they didn’t mention the Godlike. Hopefully they have a fix coming for that as well. This has definitely been frustrating.
 
Upvote 0 Downvote
traviskubast12c802b3 said:
I will probably install the beta since people have confirmed it has fixed the issue. But in case anyone was wondering msi support just answered my ticket saying they are currently working on the issue and a bios update should be available in the next 1-2 weeks
Click to expand...
They probably might have other stuff to implement with the M2.1 fix, such as WiFi & LAN port fixes too, since it has issues with drop outs and disabling itself. Atm, I use the beta with the onboard LAN & WiFi disabled and use an external USB to 2.5GB Ethernet adapter.
 
Upvote 0 Downvote
Krisk7157302df said:
They probably might have other stuff to implement with the M2.1 fix, such as WiFi & LAN port fixes too, since it has issues with drop outs and disabling itself. Atm, I use the beta with the onboard LAN & WiFi disabled and use an external USB to 2.5GB Ethernet adapter.
Click to expand...
I didn’t see anything about the LAN and WIFI issue. Good to know.
 
Upvote 0 Downvote
I'm now one full week on the beta 2A41 BIOS and the M.2_1 issue has never come back up. My Samsung 990 Pro registers and performs at 4x4 consistently without any change or fluctuation. No LAN or wifi issues, either.

The only nagging problem is the "0d" error when restarting via Windows (something about monitoring software and the embedded controller not clearing on restart). This is apparently a problem on most x870/x870e boards and maybe not even unique to MSI - ASUS appears to have addressed the same problem with a fix for monitoring software toggle directly in their BIOS. So for now the only option is to just put it to sleep or shut it down completely. Hope MSI comes up with solution sooner than later.
 
Upvote 0 Downvote
daniel.mcgowan1160b02f1 said:
I installed it and it has been a nightmare. first up, no, it did not solve the problem. PCIe 1.0x4 mode.

Second, i now have lots of other problems. I can very rarely get a monitor to pick anything up until after Windows boots up now, so I have been struggling to get into the BOIS. i also just installed a 5090, so this might be the black screen issue people have been complaining about? So a different problem? don't know. Anyway, in my attempts to get into the BIOS by restarting a bunch of times i ended up getting a lot of "CPU and DDR error" messages so i could no longer get into anything at all. Playing with different ram sticks taking them in and out sometimes got me that error, sometimes "boot error" message, and sometimes it actually works. I was able to flash the new BIOS by using a usb and the button on the back so that way I didn't need a monitor to work to flash it. And I used a monotor plugged into the mobo instead of my 5090 to eventually get a screen. anyway, that was a PITA. I dont know what caused what or if there are now overlapping problems, but now that i have the new BIOS installed and restarted a few times.... its still 1.0x 4 mode. so. thats great.
Click to expand...
I bit the bullet and installed 1A30 today.
I've not had any of the problems you had - the display came back on after the memory training, I entered the BIOS and reconfigured my settings. Restarted and all is good.
The M2_1 port isn't a problem for me anymore as I'm using M2_2 for my drive now, but I am keeping my ticket active regarding the problem
 
Upvote 0 Downvote
b933930151502d6 said:
I bit the bullet and installed 1A30 today.
I've not had any of the problems you had - the display came back on after the memory training, I entered the BIOS and reconfigured my settings. Restarted and all is good.
The M2_1 port isn't a problem for me anymore as I'm using M2_2 for my drive now, but I am keeping my ticket active regarding the problem
Click to expand...
Yup, A30 did not solve the m.2_1 issue but to follow up, the other problems I mentioned were unrelated; they just coincidentally occurred around the same time as I installed A30 making troubleshooting more confusing. Apologies if that caused more confusion when I asked if others had issues. I put my old GPU back in and all my other problems went away, so my other problems were caused by NVIDIA (isn't it amazing how everyone seems to be releasing unfinished and buggy products these days?). My guess is the BIOS error codes of "Boot Error" plus "CPU & DDR Error" were caused by my forcing a restart mid bootup or something because I couldn't see anything on the screen. I now have a workaround for those other issues and I am using the A30 bios again. It wont solve the m.2 problem, but it is safe to use and I assume probably solved something else, or else they would not have updated it.
 
Upvote 0 Downvote
daniel.mcgowan1160b02f1 said:
Yup, A30 did not solve the m.2_1 issue but to follow up, the other problems I mentioned were unrelated; they just coincidentally occurred around the same time as I installed A30 making troubleshooting more confusing. Apologies if that caused more confusion when I asked if others had issues. I put my old GPU back in and all my other problems went away, so my other problems were caused by NVIDIA (isn't it amazing how everyone seems to be releasing unfinished and buggy products these days?). My guess is the BIOS error codes of "Boot Error" plus "CPU & DDR Error" were caused by my forcing a restart mid bootup or something because I couldn't see anything on the screen. I now have a workaround for those other issues and I am using the A30 bios again. It wont solve the m.2 problem, but it is safe to use and I assume probably solved something else, or else they would not have updated it.
Click to expand...
One issue I've seen with A30 (and A27) is that no bootable USB devices are available, another user has posted on here somewhere.
USB Hard Disk and USB Key show up as boot options but are not available to boot from
I don't use USB to boot but this will be a problem for some - my Macrium recovery is on one of the internal NVMe drives and I have a Windows 24H2 installer in another partition so don't need to USB boot anything
 
Upvote 0 Downvote
Back
Top