My x299 board refused to boot from a 2TB WD SSD drive with a single memory chip (forgot which color it was)... No issues with Crucial, Samsung nor Intel.
It sounds like your issue was a SSD firmware bug that would have been a problem on any CPU+motherboard platform. It also sounds like your software had really unusual and probably stupid defaults.
That's very interesting, that just made me realize my x299 ITX board has the exact same issue with CSM while trying to boot into OS/X (so also BSD-ish, but hackintosh).
So a good chance of hanging on boot, unless I disable CSM and a power loss event will clear this CSM setting.
For every good experience like that, there is an equal and opposite bad one.
I have an X399 Taichi for my TR2. I'm using 2 older U.2 NVMe drives that have a legacy boot option rom that causes the board to hang 9/10 times at POST. The only option is to disable CSM, so it will only try to use the UEFI option rom. This works fine, EXCEPT that the CSM disable is lost every time the board looses power. Eg, that configuration setting is not properly saved to non-volatile storage.
When I reported this to ASrock (via email), I was told in very broken english to "re install windows". This is great advice, considering I'm running FreeBSD, not to mention that the entire issue happens at POST. Sigh.
Depending on board support you might get actual error correction or not.
If it doesn't boot, it's very likely that you actually bought registered memory, which is normal in servers, but _not_ supported at all by Ryzen processors, no matter the mainboard.
I've booted Windows 10 from it on an ASRock E3V5 Gaming/OC motherboard, and haven't found anything in its behavior that seems to be non-standard (except that my first one died, but that doesn't seem to have been related to my test of it as a boot drive). Intel hasn't mentioned it being unusual that I was able to boot from it.
What kind of system configurations have you found to cause problems? I wouldn't be surprised to see the NVMe remapping feature of Intel's chipsets get in the way, but that can be disabled on virtually all systems that have the feature.
Out of curiosity, what speed were you trying to boot at? I had an issue getting 4 sticks to run at 3600 MHz 1:1. I got it running at 3200 but this wasnt because of finicky ram it was because memory controller couldn't handle 4 sticks at that high a speed. In hindsight this was even hardcoded into the bios as it tried to set FCLK at 1600 with 4 sticks when the XMP profile was loaded (3600), with only 2 sticks it auto loaded 1800 FCLK.
Failure to boot, random freezes in Windows and Linux.
That said, I got it sorted out. It turned out to be an incompatibility with both the NVMe disk I was using as well as an incompatibility with the memory I had purchased.
Getting the exact parts listed in your motherboard manufacturer's compatibility list appears to be pretty important for Ryzen currently. It's been rock solid since I swapped out those components.
It seems like problems occur from different firmware from the various motherboard manufacturers. I have a motherboard with a Ryzen 7950x and it would randomly not boot. I'd have to remove the battery from the system, let it fully reset, and then it would work again. Finally an update to the firmware fixed that bug.
I've had this issue as well, but that was over a decade ago, when using a smaller brand (ECS) mainboard for an Athlon XP. Eventually it was discovered that the mainboard didn't support Corsair memory, and the shop traded me some Kingston modules.
I have built many systems for myself, friends and family since, and never encountered this issue again.
First-gen products often have issues like this. My old X370 board (zen1 era) turns off and on again twice before actually booting; a similar zen3 system doesn't need that and boots faster in general.
reply