PCIe bug with M2_1 slot on X870E Tomahawk

Status
Not open for further replies.

jlsmith.01712b902af

New member
Joined
Feb 16, 2025
Messages
15
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!
 
Godlike BIOS 1A3 is available, who's going to be the brave soul to test it and report back here?

I can't test the PCI drive slot now as I've moved my SSD to M2_2


I hope this BIOs update also addresses some of the DD3 issues people have been experiencing with this board.
 
Godlike BIOS 1A3 is available, who's going to be the brave soul to test it and report back here?

I can't test the PCI drive slot now as I've moved my SSD to M2_2

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.
 
Godlike BIOS 1A3 is available, who's going to be the brave soul to test it and report back here?

I can't test the PCI drive slot now as I've moved my SSD to M2_2

Move it back to _1 slot!
I have a Tomahawk one. :D and the driver they released on 18 is not working, only the beta driver seems to work (as some ppl here says) but im keen to wait for the official release.... which seems it take some time...
 
I guess the new bios for the Godlike is the equivalent of the new bios that just came out for the Tomahawk and Carbon. Same description on the official website. It won't fix the M2_1 issue. The A41 on the Tomahawk is still in beta, we'll have to wait at least for the next update... What a shitshow.
 
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.
Same here for the Tomahawk version with the latest official BIOS, the one get out on 18 March. And if it pass more than few hours since ive shut down, when i start the computer, it goes into BIOS instead of starting the Windows. As i said, im waiting for the official update of the beta now.
 
Same here for the Tomahawk version with the latest official BIOS, the one get out on 18 March. And if it pass more than few hours since ive shut down, when i start the computer, it goes into BIOS instead of starting the Windows. As i said, im waiting for the official update of the beta now.
Why don't you just flash the beta ? It seems to work and the feedback is mostly positive. People have been using it for several days with no issues.
 
Move it back to _1 slot!
I have a Tomahawk one. :D and the driver they released on 18 is not working, only the beta driver seems to work (as some ppl here says) but im keen to wait for the official release.... which seems it take some time...
I'll leave it where it is, only had this PC a month. Not keen on removing/re-inserting the GPU. Although it was the easiest drive swap I've ever done I don't want to do it often
 
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.
Think I'll skip this one for now. My new 9100 is in the second slot and not causing problems
 
Why don't you just flash the beta ? It seems to work and the feedback is mostly positive. People have been using it for several days with no issues.
It only works for standalone NVMe's. Under RAID, the M2_1 slot still reverts back to the slowest speed. So if you have say, M2_1 and M2_2 used, the M2_2 is fine and is steady at x4 even before A41 beta, but for M2_1 is still random up to x4 mainly stays in x1.
 
I have closed the ticket for the Tomahawk X870E PCIe M2.1 1.0 x4 speed drop using the beta A41 Bios.

After 5 days of testing and heavy usage and benchmarks, it never occurred again and all reports were 5.0 x4 for my single drive (Crucial T705) and benchmark figures were to be expected for the NVME read/writes.

Good luck to Godlike and Carbon users of the X870E chipset, as I’m sure the fix will apply to those soon.
 
It only works for standalone NVMe's. Under RAID, the M2_1 slot still reverts back to the slowest speed. So if you have say, M2_1 and M2_2 used, the M2_2 is fine and is steady at x4 even before A41 beta, but for M2_1 is still random up to x4 mainly stays in x1.
Have you mentioned it to support about RAID? It’s definitely gone for single drive use.
 
I have closed the ticket for the Tomahawk X870E PCIe M2.1 1.0 x4 speed drop using the beta A41 Bios.

After 5 days of testing and heavy usage and benchmarks, it never occurred again and all reports were 5.0 x4 for my single drive (Crucial T705) and benchmark figures were to be expected for the NVME read/writes.

Good luck to Godlike and Carbon users of the X870E chipset, as I’m sure the fix will apply to those soon.
I wonder if it has somehting to do with how many m.2's you have? Are there other people with single drives in the m2_1 slot that still have the issue?
(for reference I have all 5 populated on my godlike)
 
I wonder if it has somehting to do with how many m.2's you have? Are there other people with single drives in the m2_1 slot that still have the issue?
(for reference I have all 5 populated on my godlike)
Apologies, maybe it was the way I worded it, I meant Single Drive (non RAID) because there are reports of it not being fixed in the beta with RAID setups. I have all M.2 slots populated on the Tomahawk, so the issue didn't matter how many you was using because it was always on the M.2.1 that was problem every time. .
 
Ah okay, thanks.

Then since at least 1 other person does not have this fixed is enough for me not to bother updating my BIOS on the godlike. What a shame.
 
Has anyone else had problems with your monitors not displaying anything until after the OS boots? it randomly started happening to me as i was going back and forth between BIOS versions and testing the m.2 issue. I have to disconnect all monitors from my GPU and use a usb c cable monitor directly into the mobo now to see anything so i can still boot into the BIOS. Trying right now to determine if this is another MSI bios bug and somehow related, or if its just a "me" problem.
 
Has anyone else had problems with your monitors not displaying anything until after the OS boots? it randomly started happening to me as i was going back and forth between BIOS versions and testing the m.2 issue. I have to disconnect all monitors from my GPU and use a usb c cable monitor directly into the mobo now to see anything so i can still boot into the BIOS. Trying right now to determine if this is another MSI bios bug and somehow related, or if its just a "me" problem.
Irrelevant to the topic, but it is probably your shitty 5090. it is a known problem. force pcie 4.0 or lower for the x16 slot
 
Has anyone else had problems with your monitors not displaying anything until after the OS boots? it randomly started happening to me as i was going back and forth between BIOS versions and testing the m.2 issue. I have to disconnect all monitors from my GPU and use a usb c cable monitor directly into the mobo now to see anything so i can still boot into the BIOS. Trying right now to determine if this is another MSI bios bug and somehow related, or if its just a "me" problem.
Nah, never had that on all bios' versions using a 4090. Probably the 5090, as it has been known to black screen.
 
I wonder if it has somehting to do with how many m.2's you have? Are there other people with single drives in the m2_1 slot that still have the issue?
(for reference I have all 5 populated on my godlike)
Its regardless of the number of ssd you have, exactly as Krisk said, i can confirm, as i have only one ssd, mounted in the _1 slot. I dont want to move it to _2 or _3 slots, and im waiting for the official BIOS release. I truly believe that the beta is stable but im not playing with the beta till the official release just because im lazy bastard and is not worth to do the BIOS settings again.
Im checking the BIOS website twenty millions times per day... if this will last a while then will become a habit.... :D
Cheers!
 
Status
Not open for further replies.
Back
Top