Continuing the discussion from The Lounge:
yeah my chip is stable at 4.5 at like 1.17v or something like that. i'm about to try a bios update because at this point i cant think of anything else. was 4.9 actually benchmark stable?
@Dynamic_Gravity since your cpu seems to perform similar to mine, what do you have your ring set at for a 4.6 overclock? and what kind of voltage?
@SoulFallen I make sure to turn off turbo boost, I don't want it spiking. I don't mess with the bus, I only change the multiplier to 46. Then I set the core voltage to 1.26 V. I can get away with 1.24 V, but if I'm doing a lot of rendering overnight I want stability so I give myself a bit of headroom.
you haven't had to touch the ring at all?
also i'm in the process of murder torture testing i'm sick of the random once a week crash. i'm running OCCT while playing Star Citizen as the combination tends to cause crashes very quickly whereas It won't fail just benchmarks only unstable in games :s
No, usually I just leave everything on auto. Then only things I change are the core voltage and multiplier. Last night I was able to get to 4.9 GHz stable @ 1.43 V.
Right now I'm running 4.5 GHz @ 1.2 V.
My chip won't run 4.6 unless if I set the cache to 40 or 41 higher than that seems slightly less stable but it's hard to tell the crashes are so inconsistent. 39 (auto) crashes pretty quickly.
I've never messed with the cache... maybe if i did i could achieve my 5 GHz goal.
most likely. mine would only boot 5ghz with a 4.7 cache anything above or below would instant crash.
hmmmmm pondering
If there's one thing i've noticed about Haswell is that no two chips are stable at the same cache. these chips are very strange.
From overclock.net
To get a good idea of how good of a cpu you have try a low over clock
like 4.5GHZand see how low of voltage you can get it stable at. 1.2v and
below without delidding for 4.5GHZis usually a decent chip and when you delid the performance
increases.4.5ghz @ 1.2V vcore or lower is prolly a good chip,but the oc
needs to be stable, not a quick run, like for a validation, then it
could do 1.2V vcore or less mostly
yeah i was able to run an h264 benchmark
its a quick one, like 5 minutes at 100 % cpu
btw +1 for the title
nice, not enough for 100% but proves it's one hell of a chip. I just successfully updated the bios I need to reapply my settings and such then we will find out if it helps.
alright man, I'm gonna try to do more after work today.
I bumped up the VCCIN to 1.95 and brought the cache up to 42x with the cache voltage at 1.2. my computer is at least as stable as it was before if not more so I think the VCCIN was what was holding back my cache thus making it seem like increasing it was causing issues.
I over clocked my Raspberry Pi