Corsair H60i - weird temperature spikes

So I've had a 3570K for quite a while, and not really bothered overclocking it because game performance was just fine. But finally, years down the line, this thing is showing its age in some games. So I decided to try the "one-click overclock" method provided by my motherboard (Asus P8Z77V-LK.) That increased my BCLK to 102 MHz, multiplier to 41 and RAM speed to 1359MHz (24GB DDR3-1333) for a total speed of 4181 MHz.

To make sure everything was stable I started Prime95 and started monitoring temperatures, first with Speedfan then with HWMONITOR. That's when I noticed some really wacky behavior. The hottest core will rise to 92C over the course of about 8 - 10 minutes of Prime95, then suddenly drop to 78C. This pattern has repeated about 4 times now. Anyone else seen this sort of behavior from a Corsair H60i before?

The CPU is *not* speed throttling, verified with CPU-Z. The CPU fan speed readings I'm getting via PWM show consistently between 4455 and 4500 RPM, though I'm not sure I should believe them. What's going on here?
8 answers Last reply
More about corsair h60i weird temperature spikes
  1. I5 3570k with h55 on Asus p8z77-v LE at 4.3GHz 1.08v. P95 26.6 after 1 hr test, small fft temp never goes above 70°C.

    The problem is the OC. Not every 3570k made has identical properties, they are made from different batches of silicon. So stability at stock clocks across all the different cpus is only guaranteed by setting a high vcore voltage. Then you add a software OC which not only bumps up the BCLK but raises vcore, adds to the multiplier, potentially adds to current limits etc. Sure, it's stable, but at a price. Drop the OC and things will return to normal. Then simply raise the multiplier. That's it. You can easily do a 4.2GHz OC by nothing more than multiplier, the stock vcore is set that high.

    You have an intel cpu, best monitor is realtemp (works with p95). Also use p95 v26.6 nothing newer. New versions use high avx among other instructions which will bump temps for no good reason.
  2. OK, lowering the voltage definitely helped. The auto overclock had set it to 1.68 volts. I manually changed it from auto to +0.005V, so it's now running at 1.12v. Temps are much lower, but still showing the crazy peaks and valleys. Now temps start at around 68C, go up to 83C, then suddenly drop back down to 68-70C. Also tried setting the pump and radiator fan in the BIOS to max speed, but I'm not sure if I succeeded or not.
  3. With the h60, no, they'll run as is. The cpu header on these boards is pwm only. Any 3 pin put on that header (corsair instructions say this is the pump) will run a permanent 12v no matter what % you set. At 4000+ rpm, the fan is already maxed.
  4. I may have figured out the weird temperature fluctuations. If I use Small FFTs, the temps are pretty consistently 79C - 81C. OTOH, if I use the "Blend" workload, temps will fluctuate much more, from about 67C - 83C. So it seems to be the workload, not my cooling or config.

    I'm still seeing temperatures much higher than Karadjgne. It seems I can only use offsets in the BIOS, so I've set it to +0.005V. My voltage as reported by HWMONITOR stays around 1.211v, but CPU-Z reports 1.104v. Pretty big difference - which should I believe?
  5. 1.2 for stock voltages is still high. Unless you are trying to jump straight to 4.4,you won't need to add any voltage above stock. You can change the offset mode, to a negative. While cpus vary, it's not usually by much at close to stock speeds. Use a manual OC with a negative multiplier, and use Asus RealBench for stability testing. P95 is best for temps max. You can run a few Asus tests, if it's fine, no errors, then lower the offset more and keep doing that until you get an error, then bump it back up 1 notch. This'll get your base stable speeds. If you decide to raise the speed, try it at the same voltage, if error, bump up 1 notch. Keep doing this upto @4.3GHz. After that, OC generally requires more varied settings like a 25% bump in LLC etc. Make sure any and all eco settings are disabled. You can keep turbo and speedstep, even getting your max OC set, raising the turbo setting to match, then lower the OC a couple multipliers. Then do a p95 test using small fft as that uses a 100% continuous load, unlike blend which bounces loads and ram.
    Both are accurate. Cpu-z is reading the actual cpu voltage (VID). Hwmonitor is reading vcore which is the voltage going into the VRM's to the cpu. Generally, cpu-z ratings are what is acknowledged as voltage but the term vcore is thrown about quite a bit.

    Here's mine.
    AiTweaker : xmp, 100.0, enabled, manual, enabled, 43, enabled, auto, disabled, offset mode, -, auto, auto, auto, auto, auto, disabled.
    Cpu Ratio: all auto, enabled.
    Digi: auto, auto, disabled, optimized, 100%, 125, auto, 100% auto, optimized.

    You should have the same bios as me. Most of these are factory default settings. My cpu voltage at bios bounces from 1.088-1.096.
  6. Thought I'd post an update to this. My BIOS *is* different from yours. For example, I don't have as many VRM options as you do. Anyway, the max stable overclock I seem able to hit is 4.1GHz @ 1.15v. I got it up to 4.2GHz and Prime95 showed no errors, but Youtube videos kept crashing at that speed. Backed off to 4.1, and everything seems stable now. Temps didn't improve as much as I hoped by dropping the voltage to 1.15 - still peaking at around 85C with the small FFT workload.

    There is also a discrepancy in the voltage I set in the BIOS and what CPU-Z and HWINFO64 are reporting. In the BIOS, I set it to stock voltage, 1.08v. But I'm showing higher numbers in both utilities. Any thoughts?
  7. What you set in bios is the baseline voltage for base clock speeds. LLC, offset, turbo etc can and will raise that slightly if needed,
  8. Somehow I got it down to 1.16v. Running at 4.1Ghz now, but temps are still pretty high - ~90C under load. Consider the voltage and the AIO water cooler, isn't that pretty high? I've got about 10C - 15C of overhead to TJMax, but I still worry about cooking my CPU.
Ask a new question

Read More