Frequency variation is observed.
Frequency variation is observed.
Hello. I updated my memory settings to Kingston FURY Renegade RGB 32GB (2x16GB) DDR4 3600MHz KF436C16RB1AK2/32. In the BIOS I adjusted the XMP profile to level 1 and set the MHz and CL values to 3600 and 16. Regarding your questions, it's normal for the core frequency to fluctuate slightly—around 3700, then dropping to 3600 or lower. If you're unsure about the changes, feel free to ask. Concerning tRCD and tRP, reducing them can help stabilize performance, though it depends on your specific needs. It’s definitely possible if you want.
Initially I need to clarify that the Uncore refers to the CPU clock speed, not a memory-related measurement. Don’t inquire why CPUID displays it under the memory section—I’m not sure, but it is. Second, the Uncore, also known as the ring and cache clock, can shift somewhat during stock configurations, much like the core clock does based on system load. You can prevent it from adjusting by turning off the Ring down setting in the BIOS (though I don’t recall the exact name they use) or by manually setting a higher ring overclock instead, which should maintain its maximum setting. The ring links the cores together and the memory controller, similar to the infinite fabric found in Ryzen processors, meaning certain tasks like gaming gain from elevated ring frequencies. This process is somewhat complex. Yes, lowering it can be beneficial because tRCD is the most critical primary memory timing parameter, and on LGA 1200 platforms tRCD and tRP are stored together in a single register; thus, adjusting one requires changing both. The challenge lies in the fact that unless you have a Samsung 8Gb B die, significantly reducing its speed from 20 to a more reasonable level isn’t feasible, since it’s uncommon to find a memory IC that can drop below 19 at 3600MT/s while maintaining acceptable voltages. If you plan to tweak memory settings, consider subtimings instead—they usually offer the greatest flexibility and remaining performance potential before hitting those limits. Be cautious, though: memory overclocking can lead down a complex path, so think carefully before proceeding.