Does the Ryzen 7 2700X reach its full 3.7GHz boost under all-core workloads?
Does the Ryzen 7 2700X reach its full 3.7GHz boost under all-core workloads?
I recently assembled a system using: Gigabyte B450M DS3H, Ryzen 7 2700X with stock Wraith prism cooler, two 8GB Corsair Vengeance LPX 3000 C15 RAM modules, and a Corsair VS650W power supply. On light tasks the CPU runs smoothly at around 4.3GHz. However, under multi-threaded workloads like Blender rendering, it drops to about 3.7GHz and temperatures stay well below 70°C. The BIOS auto-tunes precision temperature, but I’m unsure what’s missing. I have extra power and some headroom. Any suggestions?
Using this motherboard and cooler (based on past knowledge), to extract more performance you must enter manual overclocking settings.
You're welcome on your questions about the cooler and thermal limits. Let me clarify: with those temperatures, the pbo should indeed have ample space for additional overhead capacity, allowing clocks to run beyond that point. There might be a softcap around 60°C, but managing beyond 3.8 remains challenging without risking instability.
Sure, the newest build (around version F50) works well. For reference, Cinebench R15 shows a max multithread score near 1600, which seems modest for a stock of 2700x. It might just depend on the hardware's performance rather than luck with the chips.
Windows operates in a performance mode already, not just Ryzen optimization anymore. Single-core boosts can hit that speed, and even with 2 or 3 cores working together, they freeze at around 3700MHz when heavy tasks are applied. I’m curious about what might be limiting the processor’s ability to utilize its full capacity—this is quite frustrating. Updated March 9, 2020 by dat_Koriel. Note: I meant it was on a balanced configuration; I’d heard it could be the best. Planning to test performance now.
It could just be a straightforward CMOS setup. Avoid resetting default BIOS settings, aiming for a genuine clear CMOS. I’m aware the 3.7GHz is the top non-turbo speed for that processor, and why it falls to that on startup is interesting. Keep experimenting with it. Something really simple must be the case.