F5F Stay Refreshed Power Users Overclocking Check the maximum clock! Is it really achievable?

Check the maximum clock! Is it really achievable?

Check the maximum clock! Is it really achievable?

L
louie018
Posting Freak
824
05-05-2016, 09:41 AM
#1
I left my PC overnight to download games from Epic. While I was away, I checked the HWmonitor to see what was happening. When I woke up today, I found all downloads completed. The HWmonitor displayed a maximum clock speed of 6.4Ghz! That’s impossible. My CPU is barely overclocked and nothing was occurring during the download. Here is a screenshot.
L
louie018
05-05-2016, 09:41 AM #1

I left my PC overnight to download games from Epic. While I was away, I checked the HWmonitor to see what was happening. When I woke up today, I found all downloads completed. The HWmonitor displayed a maximum clock speed of 6.4Ghz! That’s impossible. My CPU is barely overclocked and nothing was occurring during the download. Here is a screenshot.

C
CobraBlizard
Member
229
05-10-2016, 07:12 PM
#2
It seems there was a misunderstanding. The maximum temperature is significantly too low, and the current is much higher than expected. It likely was a brief surge or mistake that led to the data changes. If the system reached such high levels across all cores, it would have likely crashed and restarted.
C
CobraBlizard
05-10-2016, 07:12 PM #2

It seems there was a misunderstanding. The maximum temperature is significantly too low, and the current is much higher than expected. It likely was a brief surge or mistake that led to the data changes. If the system reached such high levels across all cores, it would have likely crashed and restarted.

M
mijuel32
Junior Member
6
05-12-2016, 07:49 PM
#3
It seems there was a misunderstanding. The maximum temperature is significantly too low, and the current is much higher than expected. It likely was a brief surge or mistake that led to the data changes. If the system reached such high levels across all cores, it would have likely crashed and restarted.
M
mijuel32
05-12-2016, 07:49 PM #3

It seems there was a misunderstanding. The maximum temperature is significantly too low, and the current is much higher than expected. It likely was a brief surge or mistake that led to the data changes. If the system reached such high levels across all cores, it would have likely crashed and restarted.

X
xMahfiax
Junior Member
1
05-13-2016, 02:24 AM
#4
HWINFO64 provides details about the most recent release, outlining its features and updates.
X
xMahfiax
05-13-2016, 02:24 AM #4

HWINFO64 provides details about the most recent release, outlining its features and updates.

B
Buggyer
Member
62
05-29-2016, 12:48 AM
#5
It's a bug in HWINfO64 where my 5600X sometimes displays 9000MHz, but it shouldn't matter—just wait for the next stable update of hw info64. You have HW Monitor, not HW Info 64, yet both are behaving the same! Another point: showing 250 amps is quite high; perhaps the sensors on the MB are malfunctioning, and the Ryzen 2600 can't handle that much current.
B
Buggyer
05-29-2016, 12:48 AM #5

It's a bug in HWINfO64 where my 5600X sometimes displays 9000MHz, but it shouldn't matter—just wait for the next stable update of hw info64. You have HW Monitor, not HW Info 64, yet both are behaving the same! Another point: showing 250 amps is quite high; perhaps the sensors on the MB are malfunctioning, and the Ryzen 2600 can't handle that much current.

S
66
05-30-2016, 08:19 AM
#6
If you notice unusual behavior, disregard it. This issue arises from measuring clock speed at a very low sampling rate.
S
SenpaiWithEyes
05-30-2016, 08:19 AM #6

If you notice unusual behavior, disregard it. This issue arises from measuring clock speed at a very low sampling rate.