does this mean that Ryzen should not be overclocked?I was just about to comment that I very much doubt you have rock solid 60 fps with Ryzen 3900x, especially one crippled by a manual overclock of 4.3 all-core, but then you admit you have framerate drops, so...
That's a bit too general of a statement. But if you "overclock" a 3900x to an all-core OC of 4.3, you're pretty much lowering it's performance for the vast majority of tasks (that use a couple of threads at max) while maybe possibly *slightly* improving it's performance for tasks that can actually use all cores. While, at the same time, also locking its voltage (though also possibly lowering average temperatures in the process).does this mean that Ryzen should not be overclocked?
As Martin said for multicore usage:I know this isn't the right forum, but how do you know if a title uses multiple cores or not? And how does Ram affect the performance? Microsoft Flight Simulator 2020 has 32GB in its ideal system requirements and I wonder how 16 would affect the game
The program will be fully automated and has no restrictions
I need to figure this stuff out...Exactly what a duffer like me needs
P.S.
I think lower voltage is absolutely doable because I run my 3900X silicone lottery
ie: 4.2GHz all cores @ 1.2volt and sims easy under 60C ( with Kraken X62 AIO )
Not really. These Ryzens will "run" at ridiculously low voltages. But you will be losing performance and/or it will almost certainly not be actually stable - as in if you run a full AVX2 load, it will crash.Re-dialed in my overlock numbers and er....voltage seems to have dropped a lot. I set 1.275, HWinfo reading 1.075....and still getting 4.35GHz all core?! Must be a glitch/bug surely?
Though setting voltage at 1.275 (so close to the upper limit of safe voltages) and getting 1.075 still seems like one hell of a VDroop, unless there's more to it.
That sounds doubly suspicious, then. VID Effective should be the voltage the MB tries sets for the CPU, while the SVI2 Core voltage should be the actual one. VID voltage for that reason is usually the higher one of the two (because of VDroop), but it's somehow lower of the two for you, and by a lot.
Did you check for possible offsets or something like that? Checked for a HWInfo update?