No, CL/Latency doesn't influence compatibility.
No, CL/Latency doesn't influence compatibility.
I'm experiencing the same issue myself. I only remove one side of the rams to avoid detection, but it still gets stuck at a certain code. This time I think the problem is related to the postcode I'm using—it seems it's expecting a signal that isn't present. I managed to push them in slightly more, but the rams didn't fully engage and now I have these confusing photos. I'm really curious about what would happen if I overclock them given the sensitivity of RAM to timing. If I figure it out, I'll definitely enjoy experimenting with it!
The picture isn't that bad, the RAM pins aren't visible which suggests they're probably in contact at least 70-80% of the time