Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
Does save states and turbo cause instability in RealBench?
I get a " Driver has stopped responding " at 4.7GHZ in Realbench within 5mins, but AIDA64 Extreme is stable for hours of stress testing
Does save states and turbo cause instability in RealBench?
Do you do any extensive rendering etc?
I can get mine to 4.8 but it doesn't pass real bench, yet every game i've played i cannot for the life of me get it to crash. So as far as i'm concerned it's stable
Doesn't seem to be much love for the i5 4690 around these parts!
Just thought I'd share my new buid results. Running a reasonable 4.4 at 1.15v and 4.0 uncore at 1.185v, default VCCIN and LLC Medium.
Just pushing it this evening to see what it can do when called apon, seem to hit a voltage wall at 5.0, but will do 4.9 with 1.375v, 1.9v VCCIN and High LLC. Haven't pushed uncore any further yet.
The VRIN can be thought of as the entire amount of voltage drawn by the CPU and all of its components.
When your Vcore is really going up, at least 1.30 probably 1.35v or above, you may need to change other settings. For one, keep your Vccin or total CPU voltage to 0.5v above Vcore. You can try 1.9 or 2.0v. 2.2 is uncharted territory, but for my personal overclock, a Vcore of 1.42 required Vccin of 2.15v for stability. Vccin is also known as Vrin. In Asus ROG boards, try tweaking the "eventual input voltage" instead. No benefits have been recorded by tweaking the "initial input voltage" setting.
I recommend changing input voltage in 0.05v increments. Any less you need a zen-like patience to test everything. I recommend max 0.1v increment if you are lazy. Do not do the same with Vcore or other types of voltages obviously. The reason why input voltage becomes a larger factor at higher Vcore is because input voltage is typically automatically managed by the motherboard's own software. But when the Vcore goes high up, the motherboard almost never compensates the input voltage well enough to ensure stability. Depending on how good your motherboard is at making sure the CPU has enough input voltage for the Vcore, you may have to tweak the input voltage before you even hit 1.3v Vcore.
For my case, I was trying to get x46 core multiplier and could not stabilize. Odd, considering x45 was rock solid @ 1.35v. I scaled up voltage from 1.35 to 1.4, 1.42, 1.47, 1.5, 1.512v, without being any more stable as voltage went up. The key was a higher Vcore, AND a higher input voltage. I demonstrated this by testing stability at 1.42v with various input voltage. I tested by running x264 until Bsod 5 times per setting, keeping track of averages. From 1.85 to 1.95 to 2.05 to 2.15, I could see demonstrable improvement in stability, with a higher maximum, minimum, and average time until Bsod. So what is this saying? Often times we are just tempted to test the Vcore and if it doesn't work, just get a higher Vcore, and higher, until we use ridiculous voltage and still crash, where we then put our hands in the air and give up. Just chucking Vcore as high as you can will often not net stability if you do not have high enough input voltage to match that high Vcore.
Also keep in mind that the amount of Vrin you need for a specific Vcore varies from CPU to CPU.
Temps are pretty ok Neil, I've found that if it can pass 5 runs of real bench it runs everything else fine. I've benched mine at 4.8 on 1.31v, but not game stable at that.
Looks like I'm being very conservative with my voltages, I was struggling to get stable at 4.7GHz (BSOD at 59min Realbench Stress Test) at 1.3v
Can they safely go higher without affecting longevity?