Discussion in 'Processors and motherboards Intel' started by -Tj-, Jun 7, 2013.
Just noticed, running P95 it actually hits 1.312v, even more impressive
Yep that is adaptive voltage fault.. Don't bother running these stress tests.. Funny it doesnt do it by X264 though.
Btw nice temps with new cooler
Hey TJ, yeah I know about adaptive and prime, I did it on purpose, nothing else I did even made the fans go above 50% haha
Even on P95 they only went to about 60%, it's quite quiet, all I can hear during a normal load is the PSU fan.
Just tried 4.8Ghz @ 1.33,, no go, windows loaded but BSOD right away on x264
It seems like you have hit a wall. I've ran into a few of those with Haswell. I wouldn't push it any further though. I'd drop it back to your last known stable speed and call it a day.
Yeah, guess so.
I know 4.7 was almost stable at 1.25 so might work on that instead.
Why you guys use adaptive? I use manual all time and it work just fine.
Because it heats less in idle and expands cpu lifespan while in idle.
Why use constant fixed voltage all the time, kinda pointless by default no?
I personally dont notice any real difference if it runs @ 800mhz and then ramps up to 4.7ghz by higher load or @ 4.7ghz all the time..
By gaming I switch to high perf. power plan to have max perf. all the time and it works very well this way.. Only one - two clicks and im done
Manual drop vcore at idle, only maintain VID static at max. Temps are same at idle with adaptive or manual here, either the wattage draw from kill-a-watt is 60w at idle on manual or adaptive. The theory about haswell manual voltage idle at full voltage dont looks true for my experience.
I only enable C3 at BIOS which drop vcore for all cores to around 0.750v at idle because i dont like the c6-c7 0.000v at idle.
Yes but you still have max cpuVID all the time, with adaptive it drops to 0.7v as well like coreV.
But with adaptive i dont have control under voltages in high load. I feel better knowing the voltage cpu will use when running some programs.
i have a question please for the 4970 k owners ,
why are you ocing to 4.6 if you turbo speed is 4.4 ghz ?
Because more is always better and I assume most of us are habitual overclockers
IE We bought the K version for a reason
do you guys think a non idle manual vid is that dangerous to the cpu ?
i calculated the oc from 4.5 to 3.9 its 17% power that is a lot to lose
I've been running at 4.4Ghz @1.26v (1.8v CPU Input) for a bit and whilst I haven't had any problems at all whilst in long gaming sessions or general use, yesterday IE11 was doing weird things (I'm used to that though and normally use Chrome) and today, I've been trying to transfer a lot of files from one USB3 drive to another and it's crashed twice. The first time, I was comparing drives with FreeFileSync and I got a BSOD , so I dropped the CPU Multi down from 44 to 43. I restarted the data transfer but after an hour or so, I noticed the activity lights on both drives had stopped flickering and then I found I couldn't even wake the monitor up, so it had obviously crashed again silently.
I've got Intel Extreme Tuning Utility installed now, although I haven't used it so far but I'll drop the Multi down to 38x and see if it still crashes but it seems pretty bad if it can't even manage 43x at 1.26v doesn't it?
Maybe you need a small VCCSA (cpu system agent) voltage bump, ie 0.020v+ offset or 0.040v+.
Also set cpu power current to 110 or 120% instead of auto (in DIGI+ section), keep rest at auto including LLC..
Hi Dove, as TJ says it's now a lot more than just the vCore that needs to be monitored. It could even be that if you raise your VCCSA you might even be able to drop your vCore a little, for example.
Personally I've got every voltage on auto except vCore (1.214v) and vin (1.75v) to be completely stable at 4.6Ghz, but I could just be lucky I guess.
I can boot at 4.8Ghz but I still need to tweak to get it completely stable but I don't see the point to be honest. Seems a lot of hassle for a 200Mhz gain. My OCD prevents me from using an odd multiplier lol
Well I got the same BSOD doing the folder compare with FreeFileSync even at 3.8Ghz, so I guess it's not the overclock that's the problem. The error is "Reference by pointer" and according to BlueScreenView it's caused by ntoskrnl.exe, on two of the three occasions anyway, on the third it was caused by fltmgr.sys but it still referred to ntoskrnl.exe.
It's probably something messed up after I updated my motherboard, even though I used imaging software to reset Windows, so I'll have to try a fresh install sometime. It only seems to be triggered by transferring data between two USB3 drives, although I haven't really tried using one on it's own much yet, so it might happen then as well. I ended up doing the transfer on my other machine (AMD).
Thanks for the tips Tj, I'll give them a go and see if I can push it a bit further. It might even be OK at 4.6Ghz with the current settings, I haven't tried to go beyond 4.4Ghz yet.
SpecChum, I thought that I (or my Dad to be precise) was lucky when I got his 4670k stable at 4.4Ghz with 1.225v (wish I'd kept that one for myself!), so I'd say you're very lucky You do have a 4690k though, so maybe it's because of that. As you say, it gets to the point where you think "Is it worth it to keep on tweaking for an extra 200Mhz?", particularly if it means increasing the voltage and thus temps, so I might settle at my current 4.4Ghz but if I can reduce the voltage that would be nice, although my Scythe Kotetsu is keeping it at reasonable temperatures already.
I think I may have to go 1.215v as it happens. Just got my first 0124 BSOD
First BSOD in 2 months, I did have reboots before but that was gfx card related, not single reboot since I went back to stock on that.
VCCIN is 1.75 so I think that's fine, definately above the 0.4 - 0.5v above vCore that's recommended.
I had some worrying glitches the other night playing ArmA3, where the audio would stick/go into a loop (sounds like it's buzzing) and the video would stutter. In the past, when this happened (on my old AMD system I think but maybe it happened on this Intel system when I was initially tweaking the overclock as well) it invariably resulted in it locking up completely and I had to reboot but thankfully that didn't happen this time. I've played it a few times with my current settings and haven't had this happen before, so I'm not sure why it happened the other night.
Anyway, I've bumped up VCCSA by +0.020v and set CPU Power Current to 110%, so I'll see if it happens at all next time.