So I finally had time for myself to carry out my first tests (finally a vacation, I haven't had one since last September, thank you for the Christmas vacation).
On the other hand, I performed these tests on the Beta "L1.79" BIOS and not with the latest "L1.80A" despite the fact that I had downloaded it almost when it was published, and since then I had completely forget so I would do other tests in the days to come.
So, for the overclocking results of this Corsair Vengeance SO-DIMM 32GB(2x16) 3000MHz CL16 @1.2v kit, they are really good because at the moment I managed to overclock them starting from the settings of the other overclocker which has the same kit of which I had published one of its screenshots earlier in this thread, i.e.
[email protected] CL16-16-16-16-32-48-1T-etc. and I therefore managed to climb in a stable way (verified with TestMem5 and other stress tools) up to 3933MHz and this with exactly the same latencies as those visible on the screenshot in question, which is really impressive but it's after that things go wrong.
So I wanted to continue on this good momentum which took me a lot of hours to check the perfect stability, and it's when I want to go to 4000MHz or more, that there "blackscreen" and impossible to start , and which forces me to "Clear CMOS" manually by shunting the 2 dedicated pins (luckily I installed a quick and easy-to-access switch for this), and so the first time this problem happened I thought say that it was the latencies that were very tight, so I relaxed them to 18-18-18-18-36-54-... as well as the other secondary timings and the different tRFC values too, results: nothing to do "blackscreen" no boot and force ClearCMOS again, so I relaxed even more by completely resetting the XMP default values of the secondary timings and even trying to leave most of the timings settings on "AUTO" so that the system itself chooses the settings to increase the chances of starting, but nothing 'there it stubbornly refuses to start (blackscreen) as soon as I set to 4000MHz (2000MHz in the bios of course) or more.
And so for the moment I have not tested further and so I will try other things to adjust tomorrow to try to unblock the situation, for example I have not yet tried to increase the value of the VSOC voltage and others VDDx voltages which could be related, after that it's weird anyway because I have the impression of having a kind of invisible wall from 4000MHz, whereas with my other kit Corsair Vengeance SO-DIMM 16GB (2x8) 4000MHz CL19 @1.35v at Stock, I had no problems at 4000MHz and I could even push up to 4333MHz and it still started but it was unstable though. Afterwards I say to myself: maybe it is the memory controller of my Ryzen 7 5700G which is much more stressed by the overclocking of RAM modules having 8 chips per rank instead of 4 chips per rank that there is on the Corsair 16GB 4000MHz kit in 2x8GB?
If you ever have any ideas or advice to give me, I'm all ears ;-) of course.
But unfortunately tired of this succession of failures, so I stopped to resume tomorrow as I said rather but I still forgot to make a copy of the overclock and stability validation screenshots and I unplugged everything and put away the x300 to reconnect and go back to my main config, but I promise the screenshots will be there from my next post and without fail ;-)
Well after a STABLE 3933MHz in CL16-16-16-16-32-48-1T and other secondary timings (as on the other guy's screenshot), it's still not too bad for a first 32GB SO-DIMM kit overclocking session, I just hope to be able to go up to 4000MHz and a little more (4266MHz would be really great already!)
To be continued... ;-)
