JT! Wrote:Certainly didn't over heat.
How do you know that? 78C is already pretty hot. And you pushed the voltage and clock rate higher. Your system will crash from overheating well before it triggers thermal shutdown or throttles when overclocking.
JT! Wrote:I'm saying that there doesn't appear to be one right way to do it
CPU overclocking is usually a nearly identical process on almost any platform or chip.
And since you're just looking at haswell overclocking guides that limits variation even more. Most of the guides you'll be looking at pretty much tell you to do the same things the same way. So I don't really agree with that statement. They might slightly vary certain things based on the personal results of their own system or include/leave out certain tidbits of extra info. But the process pretty much remains the same.
1. Raise clock rate a tiny bit.
2. Stress test and check temperatures.
3. If temperatures were high lower clock rate or increase cooling. If system or application was unstable continue to step 4.
4. Raise voltage a tiny bit.
5. Stress test and check temperatures.
6. If temperatures were high you've hit your limit. Revert your settings back to the highest ones you were able to use with a stable system and good temperatures.
7. If system was still unstable repeat from step 4.
8. If system is stable and temperatures good repeat from step 1.
Use .1 GHz for clock rate bumps and 0.025v for voltage bumps.
Some users prefer to work it backwards. In other words they deliberately start way too high and lower it slowly until they find the sweet spot. It doesn't really matter which way you do it but I always preferred my way because I consider it safer. For extreme overclocking use smaller increments and add some other fancy stuff in there that guides mention. I've never really tried to push a cpu to its absolute limit with my cooling since I like to leave myself some headroom when overclocking for 24/7 stability with a long lifespan. Keep in mind that 4.4GHz is a very ambitious overclock for haswell with your cooling. Unless you have a good chip you may not be able to hit it safely. And if that's the case you'll just need to accept that.
78c is hot, but not "I'm gonna shut this down" hot. And I didn't push the voltage AND the clock higher from where I am now, I did one then the other. When I upped the voltage to 2.7, I didn't even get to the stress testing. So the temp was at something like mid 60's tops when it froze up on me.
I'm somewhat happy with 4.3. Had a quick go with Dolphin and to be able to play at 100% is amazing.
JT! Wrote:78c is hot, but not "I'm gonna shut this down" hot.
Ahem:
NaturalViolence Wrote:Your system will crash from overheating well before it triggers thermal shutdown or throttles when overclocking.
78C can and will crash overclocked systems on a number of cpus. I'm not sure about haswell. That's probably about the upper limit for haswell.
JT! Wrote:When I upped the voltage to 2.7
1.27v
2.7v would kill it instantly.
JT! Wrote:So the temp was at something like mid 60's tops when it froze up on me.
Then the voltage wasn't high enough. Some people have needed as much as 1.29v to get it stable at 4.4GHz.
JT! Wrote:I'm somewhat happy with 4.3. Had a quick go with Dolphin and to be able to play at 100% is amazing.
Based on what you've told me so far I would probably settle on 4.3GHz at 1.25v too.
So I'm done OCing at 4.4GHz. But I've been left with a problem. Even though I have the vcore set to 'adaptive' voltage, the voltage doesn't drop under low cpu usage like I've read it's supposed to do. No matter what I try, it stays at the voltage I set it to. I've gone though the bios many times but found nothing.
Any suggestions?
EDIT: Finally figured it out, needed to enable intel c state from 'auto' to 'enabled'. Odd that it didn't work when set to auto.
Interesting enough, when the vcore voltage mode was switched from adaptive to auto, they gave exactly the same results on the voltages. 1.288 max and 0.776/0.784 (I'm assuming the min voltages are close enough together the call them 'the same').
So now when idling i'm at 32c instead of 42c which is nice.
Only issue I have is that I have no program that shows me a real time figure for the frequency the CPU is currency at. Real temp shows 4.4GHz constantly, and everything else shows stock frequency. Any suggestions on what would show me the frequency real time?
CPU-Z will show you a more accurately what your current clock speed, etc is.
@JT!
Dynamic voltage shouldn't do anything unless you either change the clock rate or the c-state since otherwise the voltage requirements don't change. That's completely normal. You basically have a dynamic variable whose value is dependent on a constant. Thus it will remain constant too unless you change the dependency from a constant to a variable. Have you enabled any sort of dynamic clock rate like C'n'Q?
OH it appears RealTemp GT is tracking my frequency in real time, it just doesn't change that much.
NV, the voltage is now dropping when it needs to.