- Jan 22, 2014
- 69
- 2
- 18,565
Alright, so here's the deal. I've been using SpeedFan to monitor my temps for a while now, and it's been -fairly- reliable once I sorted out which one was near enough to the CPU socket's actual temp. I had the CPU clocked through the BIOS to 4.0Ghz at a standard-ish voltage of 1.27(reported by CPU-Z). Running Overwatch, the SpeedFan temp would cap at -about- 60-62C. I installed AMD OverDrive because I was informed that it's better at monitoring temps. Now, with both SpeedFan and OverDrive running to monitor temps, I run OverDrive and then play a match of Overwatch, the CPU Core temps go from 50C to -1C almost immediately, and TMPIN1 went from 30C to 36C and has not yet come down from that. The cores, after exiting Overwatch, returned to around 50C. The temp in SpeedFan hit 69C, which it never does. The same results occurred when I ran a Prime95 small FFT. Concerned, I clocked my CPU back to 3.5Ghz and in both Overwatch and Prime95, my CPU temps reached -1 in OverDrive and hit 70C in SpeedFan.
Below is a list of specs:
Board: ASUS MSa97 LE R2.0
CPU: AMD FX-6300 (Bios Multiplier set to 20x, 4.0GHz)
RAM: 16GB G.Skill DDR3-1600
GPU: AMD Radeon R9 380 2GB
My question is whether or not I should be concerned about these readings? Considering the temps increased by 10C after installing OverDrive, and under full load rapidly spike above that max temp, even after reducing the clock speed by 500MHz, when when literally hours before making this post I did not have that problem.
Below is a list of specs:
Board: ASUS MSa97 LE R2.0
CPU: AMD FX-6300 (Bios Multiplier set to 20x, 4.0GHz)
RAM: 16GB G.Skill DDR3-1600
GPU: AMD Radeon R9 380 2GB
My question is whether or not I should be concerned about these readings? Considering the temps increased by 10C after installing OverDrive, and under full load rapidly spike above that max temp, even after reducing the clock speed by 500MHz, when when literally hours before making this post I did not have that problem.
Facebook
Twitter
Instagram