F5F Stay Refreshed Hardware Desktop Very poor Cinebench R20 results on a Ryzen 7 2700X

Very poor Cinebench R20 results on a Ryzen 7 2700X

Very poor Cinebench R20 results on a Ryzen 7 2700X

T
TaZog
Junior Member
35
05-10-2019, 04:26 AM
#1
I have a Ryzen 7 2700X installed on a X470 Aorus Gaming 7 with 2×8 GB of 3600 MHz Corsair Vengeance Pro RAM at 3200 MHz. Recently I was tweaking the memory settings and chose to run Cinebench R20. After several tests, I noticed my performance was significantly weaker than a newer i7 7700K and much lower than an older Ryzen 7 1700X. Interestingly, my Cinebench R15 scores are comparable to what the Ryzen 7 2700X should achieve. The issue continues even on single-core tasks. What options do I have?
T
TaZog
05-10-2019, 04:26 AM #1

I have a Ryzen 7 2700X installed on a X470 Aorus Gaming 7 with 2×8 GB of 3600 MHz Corsair Vengeance Pro RAM at 3200 MHz. Recently I was tweaking the memory settings and chose to run Cinebench R20. After several tests, I noticed my performance was significantly weaker than a newer i7 7700K and much lower than an older Ryzen 7 1700X. Interestingly, my Cinebench R15 scores are comparable to what the Ryzen 7 2700X should achieve. The issue continues even on single-core tasks. What options do I have?

P
Pliskin_Snake
Junior Member
38
05-15-2019, 10:46 AM
#2
You could be experiencing an inconsistent performance boost.
P
Pliskin_Snake
05-15-2019, 10:46 AM #2

You could be experiencing an inconsistent performance boost.

E
Epsylon16
Member
209
05-16-2019, 03:18 PM
#3
What temperature readings are available while using the Cinebench test?
E
Epsylon16
05-16-2019, 03:18 PM #3

What temperature readings are available while using the Cinebench test?

F
FLB1976
Member
235
05-16-2019, 05:54 PM
#4
Your CPU is running at 3.7GHz, which is normal. It might be due to an unstable OS or RAM causing performance issues.
F
FLB1976
05-16-2019, 05:54 PM #4

Your CPU is running at 3.7GHz, which is normal. It might be due to an unstable OS or RAM causing performance issues.

S
SportsBoy12
Member
59
05-22-2019, 05:10 AM
#5
Reset CMOS, undo overclock, then verify.
S
SportsBoy12
05-22-2019, 05:10 AM #5

Reset CMOS, undo overclock, then verify.