• Welcome to TechPowerUp Forums, Guest! Please check out our forum guidelines for info related to our community.

Interesting find on the the 3700x . (ur cpu maybe?)

Joined
Jun 30, 2011
Messages
42 (0.01/day)
Hey check out what I found:

Repeat this test on your machine. Fresh start of Windows 10 - Open Cinebench20 and HWinfo. Run the test and watch the clock speeds in HWinfo ........ for me I'd say 2 cores show almost 4.4 ghz and the rest of them more or less show 4.1 - 4.2 range in HWinfo..... / slowing down as it heats up....... fine.

Cool.

Now - Same thing / different test. Restart windows fresh. Pull up HWinfo again but this time, pull up and run "Intel Burn test" ---- set the "Times to Run" from 10 to 5 and *MAKE SURE* you tick the the little box that says "Output Results to results log"

Let it run. HWinfo will show similar speeds = 4.3 4.2 4.1 range for cores............. Now go look at the "results log" --- Mine will clearly say "clock speed." and it varies.......sometimes showing 3.68 , sometimes It gets up to 3.8 ghz.......... but HWinfo shows the 4.3ghz...... so........wtf?

One of the 3 isn't telling the truth. AMD/Hwifno/ or IBT.....or.....I'm not doing something right . But Hwinfo and IBT CLEARLY do not agree on "clock speed." Not even close. You try it......
 

Goro_2030

New Member
Joined
Aug 1, 2020
Messages
8 (0.01/day)
I did what you did, but Intel's Burn Test does not report a "per-run" Clock Speed. The only one clock speed that it reports is the Base Clock Speed at the beginning, like this:

----------------------------
IntelBurnTest v2.54
Created by AgentGOD
----------------------------

Processor: AMD Ryzen 7 3700X 8-Core Processor
Clock Speed: 3.60 GHz
Active Physical Cores: 16
Total System Memory: 32678 MB

Stress Level: High (2048 MB)
Testing started on 8/8/2020 6:47:33 PM
Time (s) Speed (GFlops) Result
[18:48:12] 29.311 90.1553 3.850163e-002
[18:48:49] 28.235 93.5911 3.850163e-002
Testing ended on 8/8/2020 6:48:49 PM
Test Result: Success.
----------------------------
 
Joined
Oct 22, 2014
Messages
13,210 (3.80/day)
Location
Sunshine Coast
System Name Black Box
Processor Intel Xeon E3-1260L v5
Motherboard MSI E3 KRAIT Gaming v5
Cooling Tt tower + 120mm Tt fan
Memory G.Skill 16GB 3600 C18
Video Card(s) Asus GTX 970 Mini
Storage Kingston A2000 512Gb NVME
Display(s) AOC 24" Freesync 1m.s. 75Hz
Case Corsair 450D High Air Flow.
Audio Device(s) No need.
Power Supply FSP Aurum 650W
Mouse Yes
Keyboard Of course
Software W10 Pro 64 bit
(ur cpu maybe?)

I R not. :roll:
 
Joined
Jun 30, 2011
Messages
42 (0.01/day)
I did what you did, but Intel's Burn Test does not report a "per-run" Clock Speed. The only one clock speed that it reports is the Base Clock Speed at the beginning, like this:

That's what I thought too.......... I really did. But repeated tests will show different results in there. I mean, if it was only reading the base clock.......it would be 3.6 every time. Right? But the problem is , repeated testing will show different results. 3.8, 3.7. Once I even think I saw 3.83.......best I could ever get out of it.

Meanwhile, HWinfo is thinking it's cooking along just fine at 4.3 ish.........
 
Joined
Dec 29, 2010
Messages
3,457 (0.71/day)
Processor AMD 5900x
Motherboard Asus x570 Strix-E
Cooling Hardware Labs
Memory G.Skill 4000c17 2x16gb
Video Card(s) RTX 3090
Storage Sabrent
Display(s) Samsung G9
Case Phanteks 719
Audio Device(s) Fiio K5 Pro
Power Supply EVGA 1000 P2
Mouse Logitech G600
Keyboard Corsair K95
That's what I thought too.......... I really did. But repeated tests will show different results in there. I mean, if it was only reading the base clock.......it would be 3.6 every time. Right? But the problem is , repeated testing will show different results. 3.8, 3.7. Once I even think I saw 3.83.......best I could ever get out of it.

Meanwhile, HWinfo is thinking it's cooking along just fine at 4.3 ish.........

Seriously, you're doing it wrong.
 

Goro_2030

New Member
Joined
Aug 1, 2020
Messages
8 (0.01/day)
The intel software may be reading the speed of your CPU at the exact moment you start the benchmark, and it happens to be xxx Mhz?
 
Top