F5F Stay Refreshed Power Users Overclocking fx8370E overclocking stability assistance (HWmonitor readings)

fx8370E overclocking stability assistance (HWmonitor readings)

fx8370E overclocking stability assistance (HWmonitor readings)

W
wahleno
Member
243
04-07-2016, 06:40 PM
#1
I was adjusting my CPU FX8370e during an overclock session, after purchasing a new quality motherboard and power supply unit. I'm planning to attempt a 4.1 clock speed with the lowest possible voltage due to the high temperatures in my area. So I was experimenting with a 4.095 core clock (19.5 x 210 bus speed, 2310 ht link and nb, RAM at 1680) and setting the BIOS voltage to 1.261(...)
it seems to function well in games, with temperatures staying below 52º after 10 minutes of stress testing in Prime95.
My concern is: while Prime was running, I monitored CPU-Z, core temp, and HWMonitor to check for any issues. Then I noticed that in HWMonitor, the sensors recorded a minimum clock speed of 3800, which might have been too short for CoreTemp to display accurately.
Is this something I should be concerned about? Or is it just a normal detection error?
W
wahleno
04-07-2016, 06:40 PM #1

I was adjusting my CPU FX8370e during an overclock session, after purchasing a new quality motherboard and power supply unit. I'm planning to attempt a 4.1 clock speed with the lowest possible voltage due to the high temperatures in my area. So I was experimenting with a 4.095 core clock (19.5 x 210 bus speed, 2310 ht link and nb, RAM at 1680) and setting the BIOS voltage to 1.261(...)
it seems to function well in games, with temperatures staying below 52º after 10 minutes of stress testing in Prime95.
My concern is: while Prime was running, I monitored CPU-Z, core temp, and HWMonitor to check for any issues. Then I noticed that in HWMonitor, the sensors recorded a minimum clock speed of 3800, which might have been too short for CoreTemp to display accurately.
Is this something I should be concerned about? Or is it just a normal detection error?

M
162
04-18-2016, 12:25 PM
#2
Don't be concerned if it was under prime and there were no errors.
The voltage might have been slightly low, possibly causing a brief clock drop of a few milliseconds.
In typical operation, 60-80% load is normal, so such an issue shouldn't happen often.
M
martiondude123
04-18-2016, 12:25 PM #2

Don't be concerned if it was under prime and there were no errors.
The voltage might have been slightly low, possibly causing a brief clock drop of a few milliseconds.
In typical operation, 60-80% load is normal, so such an issue shouldn't happen often.

Y
yStoorm_
Junior Member
11
04-25-2016, 06:59 PM
#3
Don't be concerned if it's running under prime and there were no errors.
The voltage might have been slightly low, possibly causing a brief clock slowdown of a few milliseconds.
In typical operation, maintaining 60-80% load should prevent such issues from happening again.
Y
yStoorm_
04-25-2016, 06:59 PM #3

Don't be concerned if it's running under prime and there were no errors.
The voltage might have been slightly low, possibly causing a brief clock slowdown of a few milliseconds.
In typical operation, maintaining 60-80% load should prevent such issues from happening again.