MAG X670E TOMAHAWK WIFI M.2_1 Slot not detecting WD SN850 and SN850x with certain BIOS versions.

darkgobis

New member
Joined
Jul 26, 2024
Messages
26
...

Sorry if I sound salty but this issue is what, a year and a half old, and only seems to be with MSI motherboards. I'm left with a board that can't support 9000 series CPUs, slowish boot times, and no future security or performance patches. Unless I spend a few hundred to replace my SSDs and gamble they don't stop working with another BIOS update. In my 20 years of building my own PCs I've never had an issue this bad for this long before.

Same here... I would rather spend money on a new motherboard of a different brand though. I have ZERO confidence in MSIs BIOS coders ever fixing this.

This level of problem going unsolved for so long should just not happen, and the SSDs are still on MSIs own compatibility list!
 
Strange problems you have, I have the SN850 and have had X670-P WIFI since it was released. That board shouldn't be too different from the Tomahawk and I haven't had a single SSD issue. I use three M.2 two 4.0 and one 3.0, two normal SSD and two HDD. I've used almost all the bioses and now on the latest beta K3.
 
Strange problems you have, I have the SN850 and have had X670-P WIFI since it was released. That board shouldn't be too different from the Tomahawk and I haven't had a single SSD issue. I use three M.2 two 4.0 and one 3.0, two normal SSD and two HDD. I've used almost all the bioses and now on the latest beta K3.
It only impacts X670E boards, which are quite different to other 600 series boards as they have dual 670 chips on the boards for starters. So yes, the boards are significantly different, despite the numbering scheme not indicating as such, and despite both supporting PCIE 5.0 on the M2_1 slot.

Reports are very widespread by users about this with these drives, which operate fine on older BIOS and in other boards. So it is a problem, it's just not one MSI have reproduced for some reason. Not sure if there's enough pressure on them to bother tbh, given how long this has been an issue.
 
Last edited:
It only impacts X670E boards, which are quite different to other 600 series boards as they have dual 670 chips on the boards for starters. So yes, the boards are significantly different, despite the numbering scheme not indicating as such, and despite both supporting PCIE 5.0 on the M2_1 slot.

Reports are very widespread by users about this with these drives, which operate fine on older BIOS and in other boards. So it is a problem, it's just not one MSI have reproduced for some reason. Not sure if there's enough pressure on them to bother tbh, given how long this has been an issue.

Good I only have X670 then, however X670 also has dual 670 chips like X670E, the boards may be more alike than you would expect. The removal of the second chip is with X870 and B850/B650. The difference between X670 and X670E is the graphics slot, X670 only has PCIE 4.0 for graphics(but very good I/O thanks to that) .

X670.png
 

Could this be the issue with newer BIOS versions?
 
By the way, this entire issue is not just a years old issue
It seems to go back all the way to 2021. It's like someone never learns...
 
Last edited:
Yeah, that's me discussing the matter on reddit user u/ChosenOfTheMoon_GR, and if it's that "simple"of a fix, and it's know, shame to MSI really.
 
Perhaps there is some delay bug during POST causing the SUSCLK signal to not Switch On on time resulting in WD SN850X to be not detected by Bios. This Bios bug could be only occurring on Gen5 Nvme slot in which any Gen4 Nvme SSD that requires SUSCLK signal is inserted.
 
Perhaps there is some delay bug during POST causing the SUSCLK signal to not Switch On on time resulting in WD SN850X to be not detected by Bios. This Bios bug could be only occurring on Gen5 Nvme slot in which any Gen4 Nvme SSD that requires SUSCLK signal is inserted.
Prior to v14 and v152 beta, the board has no issue detecting the drive so whatever MSI missed, it's around the fact that the BIOS has clearly an issue about this, whatever it is, which they are ignoring to take a look at, allegedly they informed people that they tested with the parts in question and BIOS version alone and concluded that there's no issue somehow yet we the users have even at stock BIOS settings.
I am still with v19 and i can only boot my OS driver (which i can only put in the M.2_1 slot) from a warm boot (meaning, on every boot, it goes into BIOS then i have to press control + alt + delete in order to get the drive to be recognized, after that it reboots and detects the drive as if nothing happened, speeds are the expected ones, and i have tried every single thing you can think of, resiting both the drive and the CPU to ensure PCI lane pins are not an issue, previous aforementioned BIOS works perfectly, the drive works perfectly in all slots in another MSI x570x Tomahawk WiFi with the latest BIOS for it and 3 USB NVME enclosures with 2 of them having an ASMEDIA chipset and one Realtek, WD themselves checked the drive and told me it has no issues, no smart errors, the drive works perfectly normal once detected, the drive itself works and gets detected perfectly on other slots which i can't put it because i already have them populated anyway and even if i take them out, the result is the same, all options for GEN 1,2,3,4,5 tested from the BIOS with v19 and all the newest and the issue remains, and the issue is just with these two drives sn850 and sn850x i've also tried 4 other NVME drives of different manufacturers in the M.2_1 slot with the newest BIOS versions and they have no issue getting the detected from either cold or warm boot, so any person with sanity could only conclude that the issue stems from the BIOS itself.)

I want to be able to upgrade my god damn BIOS, since when is that too much of a requirement to ask.
 
Certain SanDisk M.2 NVMe drives (980 Pro and/or 990 Pro) are also affected.
WD is using SanDisk controllers for their NVMe drives:
1735664578416.png


So there's a chance that both, the mainboard and the drive, are to blame for not fully complying with the M.2 specification.
 
Certain SanDisk M.2 NVMe drives (980 Pro and/or 990 Pro) are also affected.
WD is using SanDisk controllers for their NVMe drives:
View attachment 197230

So there's a chance that both, the mainboard and the drive, are to blame for not fully complying with the M.2 specification.
If the motherboard was at fault, the WD wouldn't work flawlessly before BIOS version v152 beta and v14, it makes no sense.
 
WD SN850X Nvme kept being not detected and loading to 7E12v1G2 Beta Bios even after rebooting multiple times. Shutdown PC and switch off wall power button and hold PC power button for 20 or 30 seconds to remove residual electricity from PC. WD SN850X Nvme detected and booted to Windows after it. Probably a fix if WD SN850X Nvme keeps being not detected and booting to Bios, until it happens again.
 
Turns out it seems there is another bug in Bios where if you save and exit after making changes and you have WD SN850X, it will keep going to Bios until you shutdown PC and power back on. Bios version is the stable 7E12v1G.
 
Back
Top