I wonder if that’s it. So when I checked the specs originally it listed the below RAM types as compatible.
RDIMM: up to 64GB
LRDIMM: up to 128GB
RDIMM/LRDIMM-3DS: up to 256GB
NVDIMM-N: up to 32GB
But when I check the QVL on ASRock’s site it only lists 10 different modules and all of them are RDIMMs (mine are LRDIMMs). The other thing I noticed is all RAM listed is between 2666-3200mhz while mine is 2400.
My first batch of RAM - Micron 64gb LRDIMMs, MTA72ASS8G72LZ
Second batch of RAM - Samsung 64gb LRDIMMs, M386A8K40BM1-CRC5Q
First thing I notice this morning is because I was using the 1 good stick from the first batch, and 2 from the second, I was mixing vendors as far as RAM goes, which I’ve always heard is bad. Never had an issue in the past but to rule that out I’ve removed the Micron stick and currently just have the 2 working (memtest confirmed good) Samsung sticks. Try and post, stuck on debug indicator AD. So while the RAM may still be what’s causing me issues, I don’t think it was specifically mixing RAM that was stopping it from posting.
Another note, according to the manual, code AD means “DXE_READY_TO_BOOT”. 50, 53, and 55 are the codes that are RAM related, invalid type, not detected, and not installed respectively. I feel like every time it successfully posts I see those codes appear for a split second and disappear as it cycles through a lot of different numbers, but when it hangs on AD it hasn’t hit them yet. Almost makes me feel like whatever is hanging it up is before it even checks for the RAM.
Last thing, it occurred to me that maybe it was just taking an extra long time to boot? Every time it posts, it goes through the process relatively fast. Just in case I wasn’t being patient enough, I let it sit on AD for about 10 minutes now and no change, so it’s definitely stuck.
I wonder if that’s it. So when I checked the specs originally it listed the below RAM types as compatible.
But when I check the QVL on ASRock’s site it only lists 10 different modules and all of them are RDIMMs (mine are LRDIMMs). The other thing I noticed is all RAM listed is between 2666-3200mhz while mine is 2400.
First thing I notice this morning is because I was using the 1 good stick from the first batch, and 2 from the second, I was mixing vendors as far as RAM goes, which I’ve always heard is bad. Never had an issue in the past but to rule that out I’ve removed the Micron stick and currently just have the 2 working (memtest confirmed good) Samsung sticks. Try and post, stuck on debug indicator AD. So while the RAM may still be what’s causing me issues, I don’t think it was specifically mixing RAM that was stopping it from posting.
Another note, according to the manual, code AD means “DXE_READY_TO_BOOT”. 50, 53, and 55 are the codes that are RAM related, invalid type, not detected, and not installed respectively. I feel like every time it successfully posts I see those codes appear for a split second and disappear as it cycles through a lot of different numbers, but when it hangs on AD it hasn’t hit them yet. Almost makes me feel like whatever is hanging it up is before it even checks for the RAM.
Last thing, it occurred to me that maybe it was just taking an extra long time to boot? Every time it posts, it goes through the process relatively fast. Just in case I wasn’t being patient enough, I let it sit on AD for about 10 minutes now and no change, so it’s definitely stuck.