Overclocking the X99E-ITX/ac |
Post Reply |
Author | ||
Jon
Newbie Joined: 26 Apr 2015 Location: USA Status: Offline Points: 62 |
Post Options
Thanks(0)
Posted: 28 May 2015 at 3:08am |
|
I have done a bit of simple overclocking with the X99E-ITX/ac but haven't gotten into it a lot yet. I just wanted to make a thread for anyone else overclocking to share their experiences.
I have the i7-5820K processor with a Seidon 120V all-in-one cooler. I was able to use the preset configuration to take it to 3.8GHz and 4.0GHz pretty easily. Beyond that, I have gotten up to 4.5GHz by increasing the multiplier to 45 and core voltage to 1.26V. I have tried a little to get to 4.6 by upping the multiplier and core voltage up to 1.30 but haven't been successful there (yet). So...has anyone else tried overclocking with this motherboard? Results?
|
||
ASRock X99E-ITX/ac | Intel i7-5820K | ASUS GTX 970 mini | Samsung 850 EVO 250GB | Crucial Ballistix (2x8GB) | Corsair CX600M | CoolerMaster Seidon 120V | CoolerMaster Elite 110 | Windows 10 64-bit
|
||
bog_xdan
Newbie Joined: 15 May 2015 Location: ROMANIA Status: Offline Points: 74 |
Post Options
Thanks(0)
|
|
Probably you need more voltage vcore 1.35v? . But the cooling might not be enough. I didn't not have this platform.
|
||
Live free or die hard
|
||
Jon
Newbie Joined: 26 Apr 2015 Location: USA Status: Offline Points: 62 |
Post Options
Thanks(0)
|
|
I think I have some headroom when it comes to cooling, the hottest I have seen so far is 75C. I have been a little hesitant because I haven't been able to find much discussion of "safe" core voltage for Haswell-E CPUs, specifically the 5820K. I think the Intel I have seen 1.30V or maybe 1.32V as the quoted limit from Intel but I'm curious how far beyond that one can go without running into trouble.
|
||
ASRock X99E-ITX/ac | Intel i7-5820K | ASUS GTX 970 mini | Samsung 850 EVO 250GB | Crucial Ballistix (2x8GB) | Corsair CX600M | CoolerMaster Seidon 120V | CoolerMaster Elite 110 | Windows 10 64-bit
|
||
glnn_23
Newbie Joined: 19 Jun 2015 Location: Australia Status: Offline Points: 3 |
Post Options
Thanks(0)
|
|
|
||
Caselabs S5, E5-1680v3, Asrock X99E-ITX/ac, TitanX with EK block, EK Supremacy Evo, HWLabs
|
||
parsec
Moderator Group Joined: 04 May 2015 Location: USA Status: Offline Points: 4996 |
Post Options
Thanks(0)
|
|
Interesting about the C States seemingly disabled when the Cache ratio is manually (increased?) set. That would seem to be an automatic behind the scenes change done by the UEFI/BIOS code. I assume you have C States set to Enabled rather than Auto.
I've seen things like that happen with other settings, such as automatically changing the CPU cooler fan speed to Full On when the CPU ratio was increased. That was on a Z97 board, not your board. That change could be overridden by resetting the CPU Fan speed setting and would not change again. I imagine you checked the C State option settings when you noticed C States were not active. Something else just struck me, how did you know that C States seemed to be disabled? Was that by monitoring the VCore in a monitoring utility? Meaning the VCore did not decrease at idle when C States should be active? If that is the situation, the monitoring program you are using is displaying VIDs and not the true VCore. That is common with Haswell processors, are you aware of this? Most hardware monitoring programs cannot display the VCore of Haswell processors, since the VCore voltage is created by the internal Haswell VRMs. HWiNFO64 can display the VCore of Haswell processors on many different boards. I don't have personal experience with X99 boards so don't know if it will show your boards VCore. Haswell over clockers generally feel that over clocking the Cache speed provides little to no performance increase. You may know some or all of this, just sayin' |
||
glnn_23
Newbie Joined: 19 Jun 2015 Location: Australia Status: Offline Points: 3 |
Post Options
Thanks(0)
|
|
Temps immediately became higher. Idle temps went from under 20C to over 30C. Went into bios to see what was different and there it was.
So every time cache is changed CStates change.
|
||
Caselabs S5, E5-1680v3, Asrock X99E-ITX/ac, TitanX with EK block, EK Supremacy Evo, HWLabs
|
||
Post Reply | |
Tweet
|
Forum Jump | Forum Permissions You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum |