Overclock.net - An Overclocking Community

Overclock.net - An Overclocking Community (https://www.overclock.net/forum/)
-   Intel CPUs (https://www.overclock.net/forum/5-intel-cpus/)
-   -   The GIGABYTE Z97X Overclocking Guide (https://www.overclock.net/forum/5-intel-cpus/1490835-gigabyte-z97x-overclocking-guide.html)

Sin0822 05-20-2014 06:25 PM

GIGABYTE Z97X OC Guide
d3an.png
While this guide focuses heavily on the Z97X-SOC and Z97X-SOC Force, the same principles can be applied to any GIGABYTE Z97 motherboard. All the results done by me in this guide are done on a closed loop AIO watercooler with above ambient temperature. There is a separate section from top overclockers such as Dinos22, and those are mostly done on LN2.

Disclaimer: Overclocking can cause damage to your hardware components if done in correctly, this guide is there to help those who wish to do so knowing something might happen, you and only you are responsible if you damage your hardware.

z2zf.png
The figure above shows all the changes of the Z97X-SOC Force compared to the Z87X-OC, the Z97X-SOC is basically the same except it only has 4 phases of IR3553 and it has the same Intel 217v NIC that the Z87X-OC had.

The Intel Z97 platform has many different devices which can be overclocked and are interlinked; to complete a system wide overclock you should tackle each device in the following order(for the sake of organizing this guide, BCLK will be covered last):
  • BCLK(Optional)
  • CPU
  • Memory
  • Uncore

This video will explain GIGABYTE's SOC series OC features and show how to use the UEFI to overclock:GIGABYTE Z97X-SOC and Z97X-SOC Force features:
pzjf.png
OC DIMM Switch: Allows the user to disable individual channels of memory, this is useful for memory diagnostics, especially when it is difficult to remove DIMMs because of the cooling apparatus installed.
OC PCIe Switch: Allows the user to disable individual PCI-E slots, this is useful for PCIe diagnostics, especially when it is difficult to remove PCIe cards because of the cooling apparatus installed.
OC Ignition: Provides power to DIMMs, PCIe and peripheral devices even when system is off. This feature is a GIGABYTE exclusive and provides many hidden benefits to users. First of all you can test not only the PSU to make sure it properly works, but also any voltage modifications on your graphics cards, water cooling systems, case mods and fans. Anything that requires the board or PSU to provide it power can be engaged. It is especially useful during cold bug situations when you need a fan to run 24/7 to keep condensation at bay. It also can be used to provide continuous power to PCIe/PCI based RAM cards that lose memory when they are powered off (so you won?t lose memory).
OC Tag: Allows user to set specific BIOS profile which is engaged when OC Tag is engaged, this is useful because you can save your OC profile for benching to TAG, and use TAG instead of inputting your settings. This makes it easy to remove the settings if you need to troubleshoot and even easier to re-apply them when needed.
OC Turbo: Easy one touch auto-OC feature from GIGABYTE (~4.2ghz OC depending on CPU SKU).
OC BCLK/Multiplier +/- buttons: Real-time overclocking of BCLK and multiplier
OC Gear: Reduces BCLK +/- button steps from 1mhz to ~0.1mhz
OC Trigger Switch: When engaged can reduce system uncore and CPU ratio to 8x on the fly, this is useful for maximum validations for CPU speed. An example of getting to 7 GHz; you boot in at 6.5 GHz, then increase the multiplier by 1x with OC Touch, but your system becomes unstable quickly. Instead of waiting for instability, you can instead engage the trigger switch (CPU now at 8x), increase the multiplier with OC Touch, and then re-engage high multiplier(dis-engage TRG switch), and you will get to your top multiplier, save a validation, and then engage trigger switch again and complete the procedure again.
Dual BIOS Switch: Select between main and backup BIOS, you can flash one with an official build and the other with an OC BIOS.
Single BIOS Mode switch: Disables dual BIOS when enabled to allow faster boot-up and OC recovery, since the main and backup are both checked on boot up, disabling dual BIOS will disable this checking and link between the BIOS ROMs.
GIGABYTE Settings Lock: Will restore previously known good values to CMOS settings, this can be used in lieu of clear CMOS.
DTB: Direct to BIOS button allows users to bypass pressing delete to enter the UEFI setup, it can save time.
GIGABYTE Memory Safe: Will engage fail-safe memory settings in case you think your memory settings are causing issues.

r8n4.png
CBAT Switch: Is a hardcore CMOS reset which will reset the CMOS as if the battery and all power were removed from the motherboard. If you have trouble clearing the CMOS you can hit this button, but beware you will probably have to unplug the 24-pin and plug it back in to be able to start the system, that is how intense the CBAT button is. It?s best to use the clear CMOS button first.
OC Connect: Two internal USB 2.0 ports provide easy access for USB devices for overclockers.
5dko.pngfn49.png
HDD LED: Lets user know when the HDD/SSD is being written too, this can help with benchmarks such as SuperPI where it is beneficial to know when the disk is being written too.
OC Dual BIOS: Dual 128Mbit BIOS ROMs designed so that you are in total control over BIOS mechanisms in case of flash failure or OC failure.

Voltages:
nudh.png
9rdn.png
Note1: Voltages 3,5, and 7 are offsets and can be changed only if the manual voltage control is set to ?normal?
Note2: Voltages for iGPU overclocking aren?t covered in this guide.

Advanced Power Settings:
ypb5.png
CPU VRIN Loadline Calibration (1): This is the LLC for the VIN and has many levels, but Extreme is recommended for most OC scenarios:
gho6.png
CPU VRIN Protection(2): Overvoltage protection for the VRIN, set to highest amount of overvolt, or just leave auto.
DDR VRIN Protection(3): Overvoltage protection for the VRIN, set to highest amount of overvolt, or just leave auto.
CPU VRIN Current Protection(4): This is overcurrent protection for the VRIN, set Extreme (which means least protection and highest current).
DDR Current Protection(5): This is overcurrent protection for the DDR, set Extreme(which means least protection and highest current).
Over temperature protection for CPU VRIN and DDR(6,7): Not currently available right now.
CPU and DDR Switch Rate(8,9): This is the switching frequency of the CPU VRIN and DDR VRMs, this setting has minimal effect on performance or power delivery, that is because you can only change it between 300-400KHz, which is very minimal (to protect from user damage). Lower will produce cooler running VRMs, higher will produce higher performance VRMs, just leave auto.
PWM Phase Control (10): This controls the balance of temperature and current in the VRM, Extreme performance will give you the best performance, and that is what you want when overclocking.

CPU Overclocking:
CPU Frequency = BCLK * BCLK Multiplier *CPU Multiplier

4y0b.png
Performance Upgrade(1): Auto CPU and Memory OC Presets
CPU Base Clock(2): BCLK setting, set manual for more options
Host/PCIe Clock Frequency(3): Actual BCLK
Gear Ratio(4): The BCLK Multiplier
Spread Spectrum Control(5): lower percentage is a lower amount of spread spectrum which is known to cause instability, leave this on auto unless you want lower EMI(worse stability) in that case increase it.
Processor Graphics Clock(6): Controls the clock of the iGPU in the CPU.
CPU Upgrade(7): CPU auto overclock presets
CPU Clock Ratio(8): The CPU multiplier
XMP(9): Will enable or disable memory XMP overclock

Note: If you decide to go with a memory frequency higher than 2933MHz, first find out your target BCLK and attain stability with a low CPU multiplier, then start increasing your CPU multiplier.

Steps for CPU OC:
#1 Calculate what frequency you want (this step matters if you use higher BCLK than 100MHz), then set the following advanced CPU features to disable: C1, C3, C6/C7, EIST. Leave turbo and turbo settings on auto.

#2 Set Multiplier and test for stability, if the system is unstable or refuses to boot, then increase voltages. Try 42x as a starting point, and go up one multiplier from there, a good starting point for the VRIN is 2.0v to 2.2v (higher can provide more stability but higher temperature), a good starting point for VCore is 1.15v-1.25v (higher can provide more stability but higher temperature). Increase Ring Voltage as a last resort when you cannot increase the VCore or VIN anymore because of high temperatures but you need a bit more stability, the Ring Voltage is mainly used to stabilize the uncore, however it can aid CPU overclocking.

#3 Most important voltages for CPU OC (in order): VCore(higher), VIN(higher), Ring Voltage(higher). You should note that the VCore and other voltages will increase automatically with CPU multiplier unless you manually set them or set them to ?normal?. You can also start from your VID as a base voltage (this will be the grayed out voltage near VCore setting around 1v when you load optimized defaults and restart), lower VID possibly means higher clocking CPU.

#4 Determine if you want the CPU frequency to drop and/or if you want the CPU VCore to drop when the system is idle. If you want the voltage to drop then enable C3. If you want the frequency to drop then enable EIST. If you want both to drop then enable both.

3127.png
K OC(1): Unlocks multipliers on some multiplier locked CPUs
CPU PLL Selection/PLL filer level(2,3): selection of the CPU?s internal clock generator and its filter level. (leave Auto, however LC PLL can provide better results for higher BCLK)
Uncore Ratio(4): Uncore multiplier
Turbo Boost Technology(5-12): Intel?s Turbo boost technology, leave most Turbo mode settings on auto, these will max out current and power automatically on auto.
Number of Cores(13): You can disable CPU cores to reduce the heat and increase clocks, the CPU randomly shuts down cores if you select this option.
Hyper Threading(14): Disabling this will reduce CPU temperature but might impact multi-threaded performance, if you are running benchmarks like SuperPI or going for max clocks then disable, otherwise leave enabled.
C1E, C6/C7 and CPU Thermal Monitor(15,17,18): Disable in most cases
C3 and EIST(16,19): C3 state will drop CPU voltage when there is less load, EIST will drop CPU multiplier in the same case, enable or disable both depending on whether you want voltage and/or frequency to drop during idle.

Example of 4.5GHz OC with XMP and drop in CPU voltage and multiplier at idle (If you don?t see a setting below then assume it is ?Auto?):
Frequency:
CPU Clock Ratio: 45x
XMP: Enable
Uncore Ratio: 40x or 43x
C1E: Disable
C6/C7: Disable
CPU Thermal Monitor: Disable
C3: Enable
EIST: Disable
Voltage:
CPU VRIN Loadline Calibration: Extreme
CPU Phase Control: Extreme Performance
VRIN Override: 2.2v
VCore: 1.275v
Ring Voltage: 1.1v

Example for Max CPU Frequency:
Frequency:
CPU Clock Ratio: 45x (Then use OC Touch or GTL to increase to top frequency)
XMP: Disable
Uncore Ratio: 8x
C1E: Disable
C6/C7: Disable
CPU Thermal Monitor: Disable
C3: Disable
EIST: Disable
Voltage:
CPU VRIN Loadline Calibration: Extreme
CPU Phase Control: Extreme Performance
VRIN Override: 2.3v to 3v on LN2
VCore: 1.4v to 2v on LN2
Ring Voltage: 1.1v to 1.5v on LN2

it1q.png

Memory Overclocking:
Memory frequency = BCLK * BCLK Multiplier * DRAM Multiplier

A more advanced memory overclocking section with recommendations from top overclockers with the Z97X-SOC Force is provided later in this guide.

8pcr.png
XMP(1): Enable for XMP profile for your memory, XMP settings are override by any changes done to memory. If you select XMP and then select a multiplier for the memory, then you will lose XMP timings. To properly engage XMP just enable XMP and do not touch any other memory settings, except DRAM voltage (which has no effect like DRAM multiplier setting).
Memory Overclocking Profiles(2): Shown Below.
Memory Multiplier(3): Selects memory speed
Memory Enhancement(4): Chose between performance, stability, and balanced. Leave auto most of the time, this setting doesn?t have a big impact.
Memory Timing Mode(5): Select to change both channels at once or individually, you need to change individually if you change RTLs/IOLs for super advanced memory OC. That means if you choose advanced manual you need to set your timings twice, once for each channel.
Memory Boot Mode(6): Select whether to train memory on boot up, this can be useful because some types of memory like to be trained on every boot, and some do not, so this allows you to choose.
Channel and Rank Interleaving(7,8): Do not bother messing with these.

The following memory OC profiles are available:
ys19.png

Memory OC Steps:
#1 If you want the memory frequency to reach speeds higher than 2933MHz, you will need to figure out your target memory frequency and BCLK. So use the equation Memory frequency = BCLK * BCLK Multiplier * DRAM Multiplier to determine the BCLK you need. It is recommended to use the 1.25x divider with memory first and if really needed use 1.66x.

#2 If using XMP settings only enable XMP, if you want to manually OC the memory to speeds or timings different than XMP, then disable XMP.

#3 Set memory multiplier as well as timings you desire, if you set a timing such as RTl or IOL then you will need to use advanced manual mode and set each channel individually (copy all timings to both channels). Many times the board is pretty good at picking timings, for a 3440MHz clock with ADATA2800C12 memory, all that needs to be set is Cas Latency to 13, the board sets all the other timings accordingly.

#4 If you encounter issues with memory training (advanced memory OC), then you can disable fast boot under memory boot options, which will force the board to retrain the memory every time.

#5 Memory voltages: DDR Voltage, DDR VTT, System Agent(IMC), VCCIO Analog(IMC), VCCIO Digital (IMC). IMC voltages will differ for every IMC and memory IC type. In general you want to leave DDR VTT on auto, however if needed you can set it to whatever you like(around ? DDR Voltage). System Agent and VCCIO Analog and Digital will vary depending on the system. Usually you can raise all 3 together, like to +0.25, and then if you get issues, take one down at a time back to normal value. Be aware the motherboard will auto increase some of these voltages(when the voltage is set to ?Auto?) depending on memory frequency, to stop this you can set it to ?Normal?, however do not do this just because.

Memory OC Tips:
  • Some dividers work better than others depending on the BCLK multiplier and modules and BIOS version. Sometimes 26x and 28x will work better than 26.66x, other times 26.66x might work better. Do try them all, just because 26.66x doesn?t work doesn?t mean 28x won?t work.
  • There is a DRAM Sync option in GTL which allows you to tune the DDR VTT (DDR Termination voltage) separately from the DRAM voltage.
  • Some memory might not like higher voltages, especially some of the IMC voltages like the VCCIOA and or VCCIOD.
  • Memory training is also important, some memory might be able to be trained at higher frequencies and some not, you can control whether or not training takes place through the memory boot option.
    nxyr.png
  • When OCing memory and BCLK very high, the board will train the BCLK first and then the memory, let the board cycle through, it might take a while to get the training right.

All available memory timings:
zw1x.th.png

Quick Memory OC to 3400mhz using the following changes to UEFI settings (If a setting isn?t listed then assume it is Auto):
Frequency:
CPU Clock Ratio: 8x
CPU Base Clock: Manual
Host/PCIe Clock Frequency: 103.5
Gear Ratio: 1.25
XMP: Disable
Uncore Ratio: 8x
C1E: Disable
C6/C7: Disable
CPU Thermal Monitor: Disable
C3: Disable
EIST: Disable
Memory:
Memory Multiplier: 26.66
Memory Timing Mode: Manual
Memory Boot Mode: Disable Fast Boot
Cas Latency: 13
Voltage:
CPU VRIN Loadline Calibration: Extreme
CPU VRIN Protection: Auto or 400mv
DDR VRIN Protection: Auto or 400mv
CPU VRIN Current Protection: Extreme
DDR Current Protection: Extreme
CPU and DDR Switch Rate: Auto
CPU Phase Control: Extreme Performance
VRIN Override: 2.0v
VCore: 1.25v
Ring Voltage: Auto
System Agent: +0.3
CPU IO Analog: +0.15
CPU IO Digital: +0.15
PCH Voltage: Auto
PCH IO Voltage: 1.05v
DRAM Voltage: 1.85v
pw6n.png

Uncore Overclocking:
Uncore Frequency = BCLK * BCLK Multiplier * Uncore multiplier
For extreme overclocking it is best to match Uncore with CPU speed to get the fastest benchmark scores, however in a 24/7 machine the uncore frequency can be 300mhz-500mhz lower than the CPU speed without noticeable impact to performance. The issue with the uncore is that it puts out its heat in the same package as the CPU, so you can negatively impact your CPU OC by increasing the uncore too much, but also negatively impact your performance with uncore being too low.

The uncore trade off:
Increase in Uncore = decreased stability = increased voltages = increased CPU temperature = lower CPU stability = lower CPU speed at certain uncore frequencies.
Steps:
#1 Increase the uncore multiplier to 300-500mhz lower than the CPU multiplier, never set the uncore multiplier higher than the CPU multiplier as you won?t gain any performance.

#2 Increase Ring Voltage to increase the stability of your uncore overclock

#3 If you increased Ring Voltage to increase the stability of your uncore, and you CPU OC is not affected, then increase the uncore multiplier by 1 and repeat.

Base Clock Overclocking:
The BCLK can be overclocked on the Z97 platform to very great extents, the following settings are those not mentioned already and which can effect your BCLK Overclock.
wxpe.png
PCIe Slot Configuration(1): Set gen2 if using discrete GPU while OCing BCLK.
DMI Gen2 Speed(2): Disable will set DMI bus to gen1 which will help with BCLK OC.
3DMark01 Boost(3): Helps boost scores in legacy benchmarks.

BCLK Overclocking on Z97 is totally optional, in fact its main use is for memory overclocking past 2933MHz as the maximum memory divider currently available for Haswell CPUs is 29.33x. While tuning memory is one of the most exciting aspects of the Z97 platform, most users won?t be overclocking their memory over 2933MHz, but for those who BCLK overclocking is very important.
GIGABYTE has improved upon their Z87 BCLK overclocking mechanism (BIOS training), for the SOC by adding in an extra clock buffer for BCLK overclocking.

Steps for max BCLK:
#1 Down clock the CPU, Uncore, and Memory multipliers to 8x

#2 Select divider and then set BCLK to get your target frequency

#3 The most important voltages for BCLK are in the following order: PCH IO(low as possible), PCH Core(higher is better), System Agent(higher is better). Set the PCH IO voltage to 1.05v, this is a 0.45 decrease in this voltage and this will heavily impact your overall BCLK. PCH voltage should be increased to 1.25v or higher and System Agent to +0.3, and the board might do this automatically on most BIOS versions.

#4 Reduce spread spectrum to as low as possible or leave auto, leaving on auto will let the board pick the best setting.

#5 Use iGPU or a GPU in the last 4x slot connected to the PCH which always has a 100mhz PCI-E clock, if neither is possible change to PCI-E gen 2.

#6 Change DMI to Gen 1

Tips for BCLK OC:
#1 The board will train the BCLK on a cold boot no matter the boot settings, it will cycle to 95 about 4-6 times and then go through POST again, this is normal especially on the 1.00x divider. The 1.25x and 1.66x dividers might not require this type of training, it depends on the BIOS version. Do not be afraid.

#2 Try to boot as close to your target BCLK as possible if you plan on OCing BCLK in Windows.

#3 use the last 4x slot on the board or iGPU, do not use the main 16x slots for BCLK OC as your GPU might not take it.

#4 Once you train for example 115mhz BCLK, if you set 116MHz the board will retrain and might fail. However if you increase my 0.5mhz then the board will NOT retrain, and will most likely successfully boot. So train at 115MHz, then reboot and train at 115.5mhz, then 116mhz, then 116.5, 117, 117.5, 118, 118.5 and so on. You will be amazed by how high you can go without retraining on the DMI(BCLK) bus.

#5. You might be able to get higher BCLK on higher dividers as opposed to the 1.00x divider.

BCLK Results using this same template but with different divider and host clocks (If a setting isn?t included then assume it is ?Auto?):
Frequency:
CPU Clock Ratio: 8x
CPU Base Clock: Manual
Host/PCIe Clock Frequency: 100-119(If boot fails, then set lower frequency until it boots, then increase by 0.5mhz each time(until it fails to boot, then boot into Windows at two 0.5mhz steps below that), then use OC Touch or GTL to increase BCLK in fine steps.)
Gear Ratio: (1.00x, 1.25x, or 1.67x)
XMP: Disable
Uncore Ratio: 8x
C1E: Disable
C6/C7: Disable
CPU Thermal Monitor: Disable
C3: Disable
EIST: Disable
Memory:
Memory Multiplier: 8x
Voltage:
CPU VRIN Loadline Calibration: Extreme
CPU VRIN Protection: Auto or 400mv
DDR VRIN Protection: Auto or 400mv
CPU VRIN Current Protection: Extreme
DDR Current Protection: Extreme
CPU and DDR Switch Rate: Auto
CPU Phase Control: Extreme Performance
VRIN Override: 2.0v
VCore: 1.25v
Ring Voltage: Auto
System Agent: +0.3
PCH Voltage: 1.275v
PCH IO Voltage: 1.05v
Miscellaneous:
PCIe Slot Configuration: 2.0 mode
DMI Gen2 Speed(2): Disable

Examples of max overclocks at all multipliers using the above settings.
1.00x divider(118mhz):
sijs.png

1.25x divider(149.88):
908s.png

1.66x divider(199.74):
rpf3.png

Advanced Memory OC Tips from Pro Overclockers:
Dino?s PSC Tips:
  • PSC subzero tRCD 12 or 10 is more stable with current bioses (April 2014).
  • When benching subzero, you have to find the right bclock range in which the memory doesn't fail training on restart.
  • In the AM3 we did 101.5 and 101.7MHz bclock were a lot easier to bench with and loosening to tRCD 12 but will impact 32M performance.
  • If CPU is subzero best to try keep it around -40C (on CPU) for initial training on testing and memory around -90C
  • Note that 1T is broken on some PSC and may require 2T (on bioses tested from April 2014).
  • Also TWCL may require 7
  • One thing that helps when tuning tRCD subzero is loosening up tWRRD_dr and tWRRD_dd or leaving auto
  • Manually tuning RTL and IOL can also help
  • Start training with several profiles from 24.00 first
  • 2600 divider might be better with BCLK of 101 rather than 100, 26.66 can be more stable too.
  • I normally run DIMM VTT at half the value of VDIMM. With Samsung ICs I ran 1.1-1.2vtt to get stability at higher clocks
Some screens:
sqnn.th.pngw1g1.th.png1t86.th.png

Bullant?s PSC Tips:
PSC air training
1.So we start at 2400Mhz first if we start to high it seem rtls and iols are setting bit too tight and wont boot
2.2400Mhz memory boot and train rtls,auto rtls are now 38-38 39-39 then save and reboot go back to bios
3.2600Mhz memory boot and train rtls,auto rtls are now 40-40 41-41 iols 5-5-5-5, I then lock rtls and iols in manually 40-40 41-41 4-4 4-4 save and reboot go back to bios
4.Then reboot still at 2600Mhz with the rtls and iols locked in,I then set 2666Mhz and reboot
5.Back to bios and then can start adding blk if memory will allow it and reboot and go to windows and rtls 40-40 41-41 iols 4-4 4-4
Screenshots:
tvaa.th.pngqtxc.th.png

Software:
GIGABYTE Tweak Launcher:
This is the best piece of software GIGABYTE makes for extreme overclocking; it is built to be light, fast, efficient, and respectable. This software works by changing the input values in real time either through integrated clock generators or through BIOS controlled voltage regulators to provide quick alterations to system parameters while in the Windows environment. GTL is currently available for XP as well as Windows 7 and 8, however in XP BCLK control might be tough since Intel discontinued Intel ME(management Engine) driver support for XP. You can still try to install Intel ME Drivers and find a hack.
lf18.png
GTL Frequency: You can change the BCLK, CPU and Uncore parameters on the fly, (CLR Clk =Uncore Frequency)
GTL Voltage: Typical voltages, however you might notice DRAM Sync option. Usually VDDR_T (DDRVTT or DRAM termination voltage) is ? of the DDR Voltage, however when overclocking it might be necessary to increase or decrease the termination voltage separately from the DRAM voltage. DRAM Sync allows you to choose whether the VDDR_T will increase and decrease with the VDDR or whether it will stay at what you set while you increase or decrease DRAM Voltage. This is a very cool feature to boost memory overclocking capabilities.
GTL Hotkeys: Something new you might also notice is the Hot Key(HK) settings which allow you to choose hotkeys to load certain settings or increase or decrease certain parameters on the fly.
Note: For GTL and/or EasyTune to work with BCLK and Multiplier adjustment in Windows, it is imperative to install the Intel ME Driver(intel Management Engine).
EasyTune:
wmeb.th.png
EasyTune is GIGABYTE?s answer to in-Windows overclocking for those who are too scared to enter the BIOS and do it. You can control everything you need for overclocking, and EasyTune allows you to do something GTL doesn?t; your settings can be retained after reboot which means you don?t have to go into the BIOS to OC or redo your OC every time you reboot into Windows.

System Information Viewer:
8fu1.th.jpg
The GIGABYTE system information viewer is part of GIGABYTE?s new software package, it basically is the fan control and hardware monitoring from EasyTune, moved into its own separate program. This program can be in a mode where you control the fans or in a mode where you can see system stats such as below. The System information Viewer is much better than CPUz for CPU VCore and even Frequency, which is very odd since CPUz is supposed to be the golden standard.

GIGABYTE Memory Tweaker:
kefp.png
A memory timing program which shows users all the timings of their memory modules on both channels, it is easy to use and shows everything on one page.

To Test Stability and Get System info try:
CPUz
Prime95
HWmonitor
RealTemp
LinX w/AVX

BIOS Flashing:
After any BIOS flash it is important to first shut down the system, remove AC power, remove the battery, clear the CMOS and then boot into the BIOS and load optimized defaults.
Method #1 in BIOS Flashing with QFlash: Put the BIOS file only(something like Z97XSOCF.F5) on a flash drive formatted in FAT32 or 16 and enter qflash utility in the BIOS and follow the steps.
Method #2 DOS BIOS Flashing using EFIFlash: Put the contents of the downloaded BIOS file such as this one (you need the BIOS file and the efiflash.exe file) onto a USB stick that is already formatted to be a DOS boot drive. When you see the cursor flash under the drive name once you boot to the USB drive, type(using the F5 BIOS for the Z97X-SOC Force as an example): "efliflash.exe z97xsocf.f5" without the parentheses.
Method #3 Windows Flashing using @BIOS: This method isn't as good as the first two, but you can use the @BIOS program from GIGABYTE to flash your motherboard's BIOS with a few clicks of the button. Just open the program and decide which method(from server, from file, etc...) @BIOS provides that you want to use, and the program will guide you.

You can get all the latest BIOS from this thread which Stasio always updates.

Any questions or concerns can be posted here. This guide will be updated with more tips from the overclockers, and I will make a point to let everyone know when something gets added.

OC Programs from GIGABYTE:
GIGABYTE Tweak Launcher for 9 Series boards
OC Touch Driver for 9 series provides BCLK button capability in Windows(Must also have Intel ME installed)
GIGABYTE Memory Tweaker Program
Z97 XP MEI, basically like an XP package for those guys benching and using XP:
Z97 MEI for XP
Major OC achievements with the Z97X-SOC/Z97X-SOC Force:
GIGABYTE Z97X-SOC Force Breaks All Legacy 3D Records

Sin0822 05-20-2014 08:03 PM

Added:
OC Programs from GIGABYTE:
GIGABYTE Tweak Launcher for 9 Series boards
OC Touch Driver for 9 series provides BCLK button capability in Windows(Must also have Intel ME installed)

MaKe OuT 05-20-2014 08:09 PM

in on this one

Sin0822 05-20-2014 08:18 PM

Nice if you need help let me know smile.gif

Also Z87 users can use this guide, it is more updated than the Z87 one, but the CPu is the same so....
Certain things are in this that aren't in the Z87, but which still apply such as BCLk with lower PCH IO voltage, and some of the tips to get higher speeds. However certain things are different, BCLk training for one is different and more time consuming on Z87.

Sin0822 05-20-2014 08:26 PM

Added:
GIGABYTE Memory Tweaker Program


So this is prob one of the only places you can find this software and OC button driver right now for everyone as well. I was just given permission to post both for everyone.

Germanian 05-20-2014 08:37 PM

Awesome guide thumb.gif. I am on z87x-oc, but I still learned something from your video and the guide.

I didn't know about GTL that tool is amazing. Could a saved me like 10 BIOS restarts the other day trying to find low undervolt biggrin.gif

dinos22 05-20-2014 09:08 PM

Nice one Scuba Steve smile.gif

error-id10t 05-21-2014 12:22 AM

With the VRIN over-ride, is that true now for Z87 also.. seems to have increased a bit...?

stasio 05-21-2014 01:55 AM

Nice review Steve...as usual......
Can you replace pic for EasyTune and System Information Viewer (at the bottom)....it's to small to see.

fateswarm 05-21-2014 02:26 AM

Auto-subscribe obviously. Auto-rep obviously. I tend to a UD5H from what I've seen (though I'm still waiting for all boards information and for Devil's Canyon).

MaKe OuT 05-21-2014 06:11 AM

Quote:
Originally Posted by error-id10t View Post

With the VRIN over-ride, is that true now for Z87 also.. seems to have increased a bit...?
I have the same question after reading the guide. I think we were directed towards 0.5-0.6 V above Vcore on Z87, on Air/AIO. Maybe I could have achieved a higher OC by increasing VRIN...possibly less Vcore needed.

And another question, has anyone discovered the best "hardware monitor" for keeping track of voltages and temps while under load stress testing on these boards?

stasio 05-21-2014 07:39 AM

Latest HWiNFO 2205 Beta (Sensors).
http://www.hwinfo.com/beta/hw64_439_2205.zip

Sin0822 05-21-2014 07:43 AM

Quote:
Originally Posted by Germanian View Post

Awesome guide thumb.gif. I am on z87x-oc, but I still learned something from your video and the guide.

I didn't know about GTL that tool is amazing. Could a saved me like 10 BIOS restarts the other day trying to find low undervolt biggrin.gif
Yea GTl is awesome smile.gif
Quote:
Originally Posted by MaKe OuT View Post

I have the same question after reading the guide. I think we were directed towards 0.5-0.6 V above Vcore on Z87, on Air/AIO. Maybe I could have achieved a higher OC by increasing VRIN...possibly less Vcore needed.

And another question, has anyone discovered the best "hardware monitor" for keeping track of voltages and temps while under load stress testing on these boards?
Yea they are just suggestions, i think intel suggests 0.8v delta, but I find that higher VIN can help sometimes, but also lower can help as well. Lower delta=lower temps, higher could be more stability if you can handle the temp increase.
Quote:
Originally Posted by fateswarm View Post

Auto-subscribe obviously. Auto-rep obviously. I tend to a UD5H from what I've seen (though I'm still waiting for all boards information and for Devil's Canyon).
haha thanks for subscribing smile.gif
Quote:
Originally Posted by stasio View Post

Nice review Steve...as usual......
Can you replace pic for EasyTune and System Information Viewer (at the bottom)....it's to small to see.
They are thumbnails, but OCN imports all the pics and replaces them on its own server. Ill fix it up.
Quote:
Originally Posted by error-id10t View Post

With the VRIN over-ride, is that true now for Z87 also.. seems to have increased a bit...?
I think it has the same maximum as before? 3v? and same max under normal BIOS of 2.8v? Or do you mean by auto? Because its still 1.8v by auto.
Quote:
Originally Posted by dinos22 View Post

Nice one Scuba Steve smile.gif
Thanks Dinos

$ilent 05-21-2014 08:55 AM

Nice guide Sin, I have one question though as a none haswell owner (looking to pick up 4790k & SOC Force)

For the uncore overclocking, is it best to leave ti at stock regardless of what overclock your going, or must it be within like 500mhz of cpu overclock at all times? What signs would you get that the uncore is the issue when stress testing as apposed to obvious cpu instability like bsod 101.

thanks

Sin0822 05-21-2014 09:16 AM

Quote:
Originally Posted by $ilent View Post

Nice guide Sin, I have one question though as a none haswell owner (looking to pick up 4790k & SOC Force)

For the uncore overclocking, is it best to leave ti at stock regardless of what overclock your going, or must it be within like 500mhz of cpu overclock at all times? What signs would you get that the uncore is the issue when stress testing as apposed to obvious cpu instability like bsod 101.

thanks
The uncore is pretty tricky, there isn't any immediate way to know, but if you think the uncore is causing the issue, you can always back it down to 8x or something very low to isolate it as the culprit, then increase it again. At least that way you would know.

$ilent 05-21-2014 09:31 AM

Yeah I follow you, so see if you fare any better it lower, if you do then youve identified the culprit.

What do you make of the SOC Force board sin? Is it only necessary for LN2 or a decent all rounder? I would just pick up a z97x ud3h but people are saying its not that good...would it really hold say a 5ghz overclock back? I mean ultimately I would like to OC as much as possible under a reasonable 24/7 voltage, like 1.4v.

error-id10t 05-21-2014 04:25 PM

On the Vrin, the Z87 advise was to run it ~0.4v difference/delta from vcore. Unless I'm just misreading it, the advise here is to have it running 0.8v difference/delta from vcore? That's what I was just curious on, has that advise changed. So if I went by how I understood it here, running my VID @ 1.41 then I'd have to raise VCCIN to 2.2V...

mandrix 05-22-2014 03:08 AM

Would be nice if we had some way to monitor Vring. (Hint hint Steve cough)
No utilities show it for my UD5H.

Sin0822 05-22-2014 12:11 PM

First off I added: Z97 XP MEI, basically like an XP package for those guys benching and using XP:
Z97 MEI for XP
Quote:
Originally Posted by $ilent View Post

Yeah I follow you, so see if you fare any better it lower, if you do then youve identified the culprit.

What do you make of the SOC Force board sin? Is it only necessary for LN2 or a decent all rounder? I would just pick up a z97x ud3h but people are saying its not that good...would it really hold say a 5ghz overclock back? I mean ultimately I would like to OC as much as possible under a reasonable 24/7 voltage, like 1.4v.
yea, i mean 1.4v is pretty high, i don't know if you can cool 1.4v without delidding, for 24/7, but yea id recommend the Z97X-SOC Force, its a really strong boards. Where are they saying its not OCing well?
I would think it would OC fine, I have a Ud5H here and it overclocks well.

Either way you will get the last drop of overclock with the SOC Force over any of the other boards in the gigabyte lineup, maybe the SOC. Its BIOS and hardware is tuned very precisely to make sure you get every last drop, especially BCLK and memory, CPU is basically standard now that FIVR is integrated, a lot of BIOS makers are putting in tricks to auto increase volts like input and cache, and i saw one recently of high system agent voltages(not from GBT) which were damn high.
Quote:
Originally Posted by error-id10t View Post

On the Vrin, the Z87 advise was to run it ~0.4v difference/delta from vcore. Unless I'm just misreading it, the advise here is to have it running 0.8v difference/delta from vcore? That's what I was just curious on, has that advise changed. So if I went by how I understood it here, running my VID @ 1.41 then I'd have to raise VCCIN to 2.2V...
0.4v from delta and the system booted stable? Default delta is 0.8v, you shouldn't close that gap unless you are trying to beat temperatures, it will hurt stability in many cases. At the beginning I thought it was cool, but you should get much more stability by increasing it to 0.8-1v delta. Since the release Intel has said 0.4v was the recommended Lowest delta, if you use 0.4v you are prob going to hurt stability. To ensure stability in their own default mode, they choose 0.8v delta. I am using now usually 2.1-2.2v for a 1.25v-1.3v vcore.

Quote:
Originally Posted by mandrix View Post

Would be nice if we had some way to monitor Vring. (Hint hint Steve cough)
No utilities show it for my UD5H.
haha vring so important, you don't think Intel's FIVR can set it correctly? smile.gif haha j/k I can ask, but honestly just critically believe what you see, or believe what you see for the difference between what you set and get with the vcore, because i mean its all the same FIVR that does all of it. The design of the power phases in the CPU for the Ring, core, and system agent are the same.

mandrix 05-22-2014 03:16 PM

Sin the reason I like to monitor Vring is because in the past leaving uncore on Auto by mistake caused the Vring to get pretty high. (Z87)
Otherwise I've checked the setpoint with a meter and it's spot on.

stasio 05-22-2014 05:59 PM

"Z97 XP MEI" driver installed on SOC Force.......(Win7 x64);


error-id10t 05-22-2014 11:26 PM

Quote:
Originally Posted by Sin0822 View Post

0.4v from delta and the system booted stable? Default delta is 0.8v, you shouldn't close that gap unless you are trying to beat temperatures, it will hurt stability in many cases. At the beginning I thought it was cool, but you should get much more stability by increasing it to 0.8-1v delta. Since the release Intel has said 0.4v was the recommended Lowest delta, if you use 0.4v you are prob going to hurt stability. To ensure stability in their own default mode, they choose 0.8v delta. I am using now usually 2.1-2.2v for a 1.25v-1.3v vcore.

Ok that's interesting, thanks for that.

Sin0822 05-24-2014 09:07 AM

Quote:
Originally Posted by error-id10t View Post

Ok that's interesting, thanks for that.
no problem

mandrix 05-28-2014 10:11 AM

Not bad. Hope I get a better 4790K though. biggrin.gif

Sin0822 05-28-2014 10:16 AM

Quote:
Originally Posted by mandrix View Post

Not bad. Hope I get a better 4790K though. biggrin.gif
nice haha! Why not try the RAM out now?

mandrix 05-28-2014 10:18 AM

I don't think this RAM will clock that good....and I confess I'm not very good at OC RAM. biggrin.gif

Not sure it will boot with the 2400 settings and X50.

MaKe OuT 05-28-2014 10:41 AM

Quote:
Originally Posted by mandrix View Post

Not bad. Hope I get a better 4790K though. biggrin.gif
Is this stable? What's your VRIN?

mandrix 05-28-2014 11:36 AM

Quote:
Originally Posted by MaKe OuT View Post

Is this stable? What's your VRIN?
I did no extensive testing.
VRIN was 2.3

MaKe OuT 05-29-2014 03:10 PM

Sin, what's the deal with the difference in opinion on voltage delta between core and input?
http://rog.asus.com/244672013/labels/featured/introduction-to-fully-integrated-voltage-regulators-fivr-on-maximus-vi/

ASUS is stating in the "key lessons" section that 0.6V delta and lower is recommended. You state in this thread/guide that 0.8V delta is a good rule of thumb (paraphrasing here) and maybe more is necessary. Thanks. Just trying to learn stuff.biggrin.gif

Cyro999 05-29-2014 10:23 PM

^Seconding that and wondering if there's data to support using "more than neccesary" on vrin? I've generally been telling people to keep it down. Usually ~1.95 or so for a 1.35vcore OC, depends on the board/llc/cpu a little

MaKe OuT 05-30-2014 07:25 AM

Ran x264 overnight set to 20 loops. Woke up to a fail. This was my first evening stability testing on this z97 board. all previous testing done on a z87 board. Same chip. Interestingly, I always bsod when failing stability test on z87. typically code 101. But, on this z97 board there is no bsod. I think it just reboots and has a window that states that Windows has recovered from some failure. Not a big deal, but does anyone know why this is?

So I need to look over my notes on my previous z87 stability search as I thought for sure I found stability at the x44 cpu multi. I frickin failed to be stable on this z97 board with a x43 multi at 1.34 Vcore setting which goes to 1.35 something volts under load. The uncore was locked at x35 multi and 1.203V. The VRIN was set to 2.2 volts and increased the same as Vcore did under load. Temps were good around 72C hottest core. I am just bummed that I cannot easily pass x264 overnight at x43 yet.

Any ideas?

Sin0822 05-30-2014 07:32 AM

Quote:
Originally Posted by MaKe OuT View Post

Ran x264 overnight set to 20 loops. Woke up to a fail. This was my first evening stability testing on this z97 board. all previous testing done on a z87 board. Same chip. Interestingly, I always bsod when failing stability test on z87. typically code 101. But, on this z97 board there is no bsod. I think it just reboots and has a window that states that Windows has recovered from some failure. Not a big deal, but does anyone know why this is?

So I need to look over my notes on my previous z87 stability search as I thought for sure I found stability at the x44 cpu multi. I frickin failed to be stable on this z97 board with a x43 multi at 1.34 Vcore setting which goes to 1.35 something volts under load. The uncore was locked at x35 multi and 1.203V. The VRIN was set to 2.2 volts and increased the same as Vcore did under load. Temps were good around 72C hottest core. I am just bummed that I cannot easily pass x264 overnight at x43 yet.

Any ideas?
just copy the settings over from the Z87, was your Z87 a GBT? if it was just copy them over.

MaKe OuT 05-30-2014 07:36 AM

Quote:
Originally Posted by Sin0822 View Post

just copy the settings over from the Z87, was your Z87 a GBT? if it was just copy them over.
that's the problem. it was an Asus M6 Hero. I am trying to get used to the GB bios still as I am still familiar with Asus only. So far (very limited time on the board) I have failed to match the stability I had on the Hero. I am confident that it is simply that I need to change some settings. I just need to figure out what those are.biggrin.gif

marrawi 05-30-2014 03:00 PM

You are awesome, Sin! Thank you! let's see if I can overcome the 4.6 wall on my 4770K!

marrawi 05-30-2014 08:50 PM

Quote:
Originally Posted by marrawi View Post

You are awesome, Sin! Thank you! let's see if I can overcome the 4.6 wall on my 4770K!

That's a negative, couldn't go beyond 4.6Ghz. Here are the settings I tried:

CPU Clock Ratio: 47x
XMP: Enable and Disabled
Uncore Ratio: Auto and 40x
C1E: Disable
C6/C7: Disable
CPU Thermal Monitor: Disable
C3: Disable
EIST: Disable
Voltage:
CPU VRIN Loadline Calibration: Extreme
CPU Phase Control: Extreme Performance
VRIN Override: 2.0 - 2.2v
VCore: 1.375v - 1.43v
Ring Voltage: 1.115v - 1.2v


Went back to stable 4.6 settings:

CPU Clock Ratio: 46x
XMP: Enable @ 2400Mhz
Uncore Ratio: 40x
C1E: Disable
C6/C7: Disable
CPU Thermal Monitor: Auto
C3: Disable
EIST: Disable
Voltage:
CPU VRIN Loadline Calibration: Extreme
CPU Phase Control: Auto
VRIN Override: 1.9v
VCore: 1.375v
Ring Voltage: 1.115v


Any suggestion is appreciated smile.gif

Cyro999 05-30-2014 09:24 PM

Quote:
Originally Posted by marrawi View Post

That's a negative, couldn't go beyond 4.6Ghz. Here are the settings I tried:

CPU Clock Ratio: 47x
XMP: Enable and Disabled
Uncore Ratio: Auto and 40x
C1E: Disable
C6/C7: Disable
CPU Thermal Monitor: Disable
C3: Disable
EIST: Disable
Voltage:
CPU VRIN Loadline Calibration: Extreme
CPU Phase Control: Extreme Performance
VRIN Override: 2.0 - 2.2v
VCore: 1.375v - 1.43v
Ring Voltage: 1.115v - 1.2v


Went back to stable 4.6 settings:

CPU Clock Ratio: 46x
XMP: Enable @ 2400Mhz
Uncore Ratio: 40x
C1E: Disable
C6/C7: Disable
CPU Thermal Monitor: Auto
C3: Disable
EIST: Disable
Voltage:
CPU VRIN Loadline Calibration: Extreme
CPU Phase Control: Auto
VRIN Override: 1.9v
VCore: 1.375v
Ring Voltage: 1.115v


Any suggestion is appreciated smile.gif

You might just need more vcore. I have to go from like 1.245 bios to 1.375 bios for 4.5 to 4.7. That's adding like 0.06 then 0.07 for 100mhz. If you tried 1.43 in bios already though - that's already [email protected], so i wouldn't suggest going to like 1.47 for 24/7. Probably best staying @46
Quote:
Originally Posted by MaKe OuT View Post

that's the problem. it was an Asus M6 Hero. I am trying to get used to the GB bios still as I am still familiar with Asus only. So far (very limited time on the board) I have failed to match the stability I had on the Hero. I am confident that it is simply that I need to change some settings. I just need to figure out what those are.biggrin.gif

Triple check vcore vs vrin (that you have turbo/extreme llc on vrin, and a good number for it) then add 0.01 vcore

i think some of these haswell boards even vary slightly in the amount of vcore that they give over what you set in the bios - giga seems to be +0.02, but i've seen volts on asus suggesting +0.03 for example (it reads as IA voltage or something in hwinfo)

You might have a bluescreen code recorded that didn't get shown to you, bluescreenview (the program) can show you that. Restart = typically very close to stability

MaKe OuT 05-31-2014 12:37 PM

Yes, the recommended settings at extreme were done per the guide. I have disabled thermal monitor, cstates, eist...for now.
x264 UNstable (bsod 101) at:
cpu: 43
uncore: 35
vcore: 1.34
vrin: 2.20
vring: 1.20

x264 stable at:
cpu: 43
uncore: 35
vcore: 1.36 (only difference vs the above is this parameter)
vrin: 2.20
vring: 1.20

decided to have it fold and see if it crashes. All I am doing on this machine right now is gaming and folding so as long as I am stable there then that is good for me. x264 was good to get me in the ballpark. currently folding and every so many hours I'll drop the voltages to see how low I can get them. Once I find a good number then I'll try to increase the uncore multi.
currently at:
cpu: 43
uncore: 35
vcore: 1.35
vrin: 2.00
vring: 1.20

mandrix 06-01-2014 07:55 AM

Quote:
Originally Posted by Sin0822 View Post

nice haha! Why not try the RAM out now?
OK got the RAM back to 2400. cpu-z still showing low bus speed though, should read just over 100 which would give a full 5 gigglehertz.
Only ran short testing with x264 as this was more to confirm VCCIN of 2.3 was needed.


sabishiihito 06-10-2014 07:56 PM

Testing some BBSE, couldn't tighten the tertiary timings as much as I wanted to (had to set 5s instead of 4s) but only needed 1.8v as a result to pass 32M at 2400 8-10-7 1T.

4770K40x100BCLKSOCFStorm2133C91200MHz8-10-7-24-1TAIDA64BW_zpsa624c1b6.jpg

Sin0822 06-10-2014 08:31 PM

yea the tertiary thing is being worked on

sorry let me look over the thread guys, I have been gone for the past week and just moved smile.gif

fateswarm 06-13-2014 07:02 PM

Should we be monitoring voltage with a multimeter if possible in case there is voltage regulation degradation over the months/years? Is voltage regulation degradation a common phenomenon? It came to mind when I noticed people usually blame degradation only to chips.

Sin0822 06-13-2014 07:07 PM

Quote:
Originally Posted by fateswarm View Post

Should we be monitoring voltage with a multimeter if possible in case there is voltage regulation degradation over the months/years? Is voltage regulation degradation a common phenomenon? It came to mind when I noticed people usually blade degradation only to chips.
No.... lol VRms don't degrade, only thing that might would be the capacitors, but the 10K ones used on these boards from GBT are top notch and you wont notice degradation even over like 5-10+ years of use, even if you do the voltage and current will remain the same since there is an active feedback loop for voltage, current, and temperature that is always maintained at needed values regardless of the state of the components in the VRM. If a VRm gets to the point it cannot do what it needs to do, it will fail entirely, like blow a MOSFET or capacitor. Degradation only is due to chips, but also sometimes the CMOS more importantly ME can corrupt and need to be re-flashed.

fateswarm 06-13-2014 07:39 PM

Hrm. OK. Then I guess it could be an issue on other brands..

Sin0822 06-13-2014 07:49 PM

Nah in general vrms dont degrade they just fail

mandrix 06-14-2014 04:46 PM

Quote:
Originally Posted by Sin0822 View Post

Nah in general vrms dont degrade they just fail
Yeah. I've seen so much bull repeated on the internet about overclocking, and about Gigabyte boards in particular lately it's unreal. Not sure if there's some kind of anti-Gigabyte campaign going on or what.....but I've sure read a lot of crap lately even on OCN by people who apparently want to be taken seriously. rolleyes.gif

(Not talking about you, fateswarm, I know you're just trying to get to the facts.)

fateswarm 06-14-2014 04:57 PM

Quote:
Originally Posted by mandrix View Post

(Not talking about you, fateswarm, I know you're just trying to get to the facts.)

You better not meant I'm on an anti-Gigabyte campaign considering I have one in the mail smile.gif

mandrix 06-14-2014 05:22 PM

Quote:
Originally Posted by fateswarm View Post

You better not meant I'm on an anti-Gigabyte campaign considering I have one in the mail smile.gif
lol, no, of course not. But I've seen some strange posts here and there lately about Gigabyte boards being "faulty" or "bad" and I think it was just rumor mongers.

Sin0822 06-18-2014 10:54 PM

So there has been a lot of talks recently about getting WRs with Z97 motherboards, I just wanted to share the collection that the Z97X-SOC Force and Z97X-SOC Force LN2 have picked up over the last month or two.
4560MHz Memory WR(Z97X-SOC Force LN2, GBT team live at HOT comp.):
http://hwbot.org/submission/2559133_memory_clock_ddr3_sdram_2282.8_mhz
3DMark03 Single Card(Team AU):
http://hwbot.org/submission/2545879_teamau_3dmark03_radeon_r9_290x_253373_marks
3DMark03 Dual Card(Team AU):
http://hwbot.org/submission/2545864_teamau_3dmark03_3x_radeon_r9_290x_301064_marks
Aquamark Single Card(Sofos): http://hwbot.org/submission/2562963_sofos1990_aquamark_geforce_gtx_580_576442_marks
Aquamark Dual Card(Sofos):
http://hwbot.org/submission/2563185_sofos1990_aquamark_2x_geforce_gtx_780_ti_573521_marks
3DMark05 Dual Card(sofos):
http://hwbot.org/submission/2559673_sofos1990_3dmark05_2x_geforce_gtx_780_ti_73132_marks
3DMark05 Single Card(TeamAU):
http://hwbot.org/submission/2545866_teamau_3dmark05_geforce_gtx_780_ti_74192_marks
3DMark06 Single Card(TeamAU):
http://hwbot.org/submission/2545870_teamau_3dmark06_geforce_gtx_780_ti_57085_marks
3DMark2001SE Dual Card(Sofos):
http://hwbot.org/submission/2559779_sofos1990_3dmark2001_se_2x_geforce_gtx_580_177215_marks
3DMark2001SE Single Card(TeamAU):
http://hwbot.org/submission/2545871_teamau_3dmark2001_se_geforce_gtx_780_ti_190478_marks
UNIGINE Heaven Triple Card(TeamAU):
http://hwbot.org/submission/2545877_teamau_unigine_heaven___xtreme_preset_3x_radeon_r9_290x_9192.02_dx11_marks
UNIGINE Heaven Dual Card(TeamAU):
http://hwbot.org/submission/2563093_teamau_unigine_heaven___xtreme_preset_2x_radeon_r9_290x_8616.29_dx11_marks

marrawi 06-18-2014 11:28 PM

Quote:
Originally Posted by Sin0822 View Post

So there has been a lot of talks recently about getting WRs with Z97 motherboards, I just wanted to share the collection that the Z97X-SOC Force and Z97X-SOC Force LN2 have picked up over the last month or two.
4560MHz Memory WR(Z97X-SOC Force LN2, GBT team live at HOT comp.):
http://hwbot.org/submission/2559133_memory_clock_ddr3_sdram_2282.8_mhz
3DMark03 Single Card(Team AU):
http://hwbot.org/submission/2545879_teamau_3dmark03_radeon_r9_290x_253373_marks
3DMark03 Dual Card(Team AU):
http://hwbot.org/submission/2545864_teamau_3dmark03_3x_radeon_r9_290x_301064_marks
Aquamark Single Card(Sofos): http://hwbot.org/submission/2562963_sofos1990_aquamark_geforce_gtx_580_576442_marks
Aquamark Dual Card(Sofos):
http://hwbot.org/submission/2563185_sofos1990_aquamark_2x_geforce_gtx_780_ti_573521_marks
3DMark05 Dual Card(sofos):
http://hwbot.org/submission/2559673_sofos1990_3dmark05_2x_geforce_gtx_780_ti_73132_marks
3DMark05 Single Card(TeamAU):
http://hwbot.org/submission/2545866_teamau_3dmark05_geforce_gtx_780_ti_74192_marks
3DMark06 Single Card(TeamAU):
http://hwbot.org/submission/2545870_teamau_3dmark06_geforce_gtx_780_ti_57085_marks
3DMark2001SE Dual Card(Sofos):op
http://hwbot.org/submission/2559779_sofos1990_3dmark2001_se_2x_geforce_gtx_580_177215_marks
3DMark2001SE Single Card(TeamAU):
http://hwbot.org/submission/2545871_teamau_3dmark2001_se_geforce_gtx_780_ti_190478_marks
UNIGINE Heaven Triple Card(TeamAU):
http://hwbot.org/submission/2545877_teamau_unigine_heaven___xtreme_preset_3x_radeon_r9_290x_9192.02_dx11_marks
UNIGINE Heaven Dual Card(TeamAU):
http://hwbot.org/submission/2563093_teamau_unigine_heaven___xtreme_preset_2x_radeon_r9_290x_8616.29_dx11_marks

Awesomeness, thanks for sharing.

fateswarm 06-28-2014 02:32 AM

You should add on the guide that max cpu overclocking can benefit from 8x memory. I helped me go from 5.0 to 5.1 on air http://valid.x86.fr/1i9g1v

Though I would be more impressed with very low voltages above 4.6g on high performance settings since it would have a real world benefit.

I currently run 4.6gig, 2400 memory, 40x ring for 24/7 on 1.24v/1.74v (1.20-1.22v had issues).

Cyro999 06-28-2014 11:47 AM

Quote:
Originally Posted by fateswarm View Post

You should add on the guide that max cpu overclocking can benefit from 8x memory. I helped me go from 5.0 to 5.1 on air http://valid.x86.fr/1i9g1v

Though I would be more impressed with very low voltages above 4.6g on high performance settings since it would have a real world benefit.

I currently run 4.6gig, 2400 memory, 40x ring for 24/7 on 1.24v/1.74v (1.20-1.22v had issues).

Not using more than 1.24vcore? I thought you liked higher clocks~

fateswarm 06-28-2014 05:38 PM

I like 8GHz and I'd like to keep the cpu stable for at least a year on 24/7 settings. At 4.7 I get a big jump in voltage requirements. I don't want to go above 1.3v for 24/7 settings.

Cyro999 06-28-2014 10:26 PM

Quote:
Originally Posted by fateswarm View Post

I like 8GHz and I'd like to keep the cpu stable for at least a year on 24/7 settings. At 4.7 I get a big jump in voltage requirements. I don't want to go above 1.3v for 24/7 settings.

[email protected], [email protected] is pretty normal for a haswell chip in terms of scaling, i think 1.3v is a little low if you care about clocks (i used 1.32 for a year with some 1.265 and some 1.395 with air no delid, no noticable degradation)

if you're doing something to load your chip @100% for many hours, lower voltage is good but if not, you don't have to be so careful

fateswarm 06-29-2014 04:49 AM

Quote:
Originally Posted by Cyro999 View Post

[email protected] is pretty normal

Speak for yourself. I want the chip to be stable for a year at least. Also, stop judging others' decisions like they are yours.

error-id10t 06-29-2014 05:54 PM

Dude, you're the new one with an actual Desktop chip now instead of just "speculating" and "guessing", as evident in your sig. Most of us have been playing around with Haswell for a long time. If you want to stay at 1.3v go ahead, hell.. if you want to stay with what ASUS do and limit their auto-OC SW to 1.28v then that's fine too. Many people have had Haswell's for a long time now and some of us know how and what they do.

fateswarm 06-29-2014 05:57 PM

"I'm old here" is not an argument. Find actual arguments. Otherwise you sound like those narcissistic people in the Militaries torturing the newbies.

Cyro999 06-29-2014 07:27 PM

Quote:
Originally Posted by fateswarm View Post

Speak for yourself. I want the chip to be stable for a year at least. Also, stop judging others' decisions like they are yours.

I'm not judging, was just dropping some info with some of my opinion mixed in thumb.gif

As for the chip lasting years: You misinterpreted, i meant 4.7 running at 1.4v was pretty normal stability wise, not that it was normal for people to run those overclocks 24/7. The vast majority of chips (something like 86%) charted on OCN are at 45 and 46, and also below 1.4v

fateswarm 06-29-2014 07:44 PM

Well, let me be blunt. The popular culture of the forum has mixed up what extreme overclockers do with what a 24/7 casual overclock should be for safety in the span of at least ~2 years one would want to use the chip. I have an Intel Engineer on video explicitly saying to go up to 10% above default Vcore (which checks out to be around 1.3v in many cases) and we have reports of degradation in a year (or less) from 1.35v onwards.

Cyro999 06-29-2014 09:33 PM

Quote:
Originally Posted by fateswarm View Post

Well, let me be blunt. The popular culture of the forum has mixed up what extreme overclockers do with what a 24/7 casual overclock should be for safety in the span of at least ~2 years one would want to use the chip. I have an Intel Engineer on video explicitly saying to go up to 10% above default Vcore (which checks out to be around 1.3v in many cases) and we have reports of degradation in a year (or less) from 1.35v onwards.

There's hundreds on OCN who are using 1.25-1.35v with no noticeable degradation in the last year, that's all i'm saying - maybe i have you mixed up with somebody else, but i thought you were asking for ~4.8-4.9ghz, which is why i mentioned it and found it odd to be using only 1.24vcore

fateswarm 06-30-2014 03:57 AM

Now you changed the subject. You talked of 1.4v. 1.25v is safe for more than 3 years most likely and 1.35v is probably safe for at least 1-2 years in most cases.

mandrix 06-30-2014 04:47 AM

What I said in the DC owners thread bears repeating here:
If you are running your cache voltage on Auto, either check it under load or (probably better option) set it manually. Why?
After testing a recent BIOS for my Z97-UD5H I left the Vring on Auto, ran a quick stress test while manually checking voltages with my DMM and the Vring was 1.397v.
IMO that's a little high.
Fortunately the newer BIOS are finally scaling the uncore from 8x-40x so that's good.

Sin you wanted to know why not having a sensor for vring was disturbing to me? How about longevity? lol. thumb.gif

fateswarm 06-30-2014 05:03 AM

Quote:
Originally Posted by mandrix View Post

What I said in the DC owners thread bears repeating here:
If you are running your cache voltage on Auto, either check it under load or (probably better option) set it manually. Why?
After testing a recent BIOS for my Z97-UD5H I left the Vring on Auto, ran a quick stress test while manually checking voltages with my DMM and the Vring was 1.397v.
IMO that's a little high.
Fortunately the newer BIOS are finally scaling the uncore from 8x-40x so that's good.

Sin you wanted to know why not having a sensor for vring was disturbing to me? How about longevity? lol. thumb.gif

Definitely. What I wrote in the club:

Quote:
Originally Posted by fateswarm View Post

Ah by the way. The VRing auto-voltage might be also bugged, at least of similar behavior with what VCore had before BIOS updates. I found it above 1.4v in some instances.

It's a bit uncertain how it works because I've also found it lower while on the same BIOS ver. and still on auto and similar multiplier.

It may be affected by other variables.



I meant even on the latest bios.


I'm not certain how it works (or not yet) as it's apparent on the text.

Also I suspect the "quirk" might be that it's treated like OC'ed 4770.

mandrix 06-30-2014 06:02 AM

Quote:
Originally Posted by fateswarm View Post

Definitely. What I wrote in the club:
I'm not certain how it works (or not yet) as it's apparent on the text.

Also I suspect the "quirk" might be that it's treated like OC'ed 4770.
Maybe..mine is 4770K. Gigabyte needs to adjust in the BIOS as I've seen this come and go.

fateswarm 06-30-2014 06:46 AM

Thank the gods for multimeter support to be honest. I don't see that voltage on HWInfo.

Cyro999 06-30-2014 07:19 AM

Quote:
Originally Posted by fateswarm View Post

Now you changed the subject. You talked of 1.4v. 1.25v is safe for more than 3 years most likely and 1.35v is probably safe for at least 1-2 years in most cases.
Quote:
Not using more than 1.24vcore? I thought you liked higher clocks~
Quote:
i think 1.3v is a little low if you care about clocks
Quote:
if you're doing something to load your chip @100% for many hours, lower voltage is good but if not, you don't have to be so careful
Quote:
maybe i have you mixed up with somebody else, but i thought you were asking for ~4.8-4.9ghz, which is why i mentioned it and found it odd to be using only 1.24vcore

I was never demanding that you use 1.4v. Sorry if it seemed that way biggrin.gif

mandrix 06-30-2014 07:56 AM

Quote:
Originally Posted by fateswarm View Post

Thank the gods for multimeter support to be honest. I don't see that voltage on HWInfo.
OK, I was just going to ask you if your board showed Vring. The OC Force board does, not sure what other GB boards do. For sure the UD5H doesn't....which is strange since my Z87 UD5H does.

fateswarm 06-30-2014 08:38 AM

ga-z97x-gaming 7 has voltage read points. Ud5h does too. Next to the power button.




Ah you mean on HWInfo? Dunno. But I don't see it here.

mandrix 06-30-2014 02:59 PM

Quote:
Originally Posted by fateswarm View Post

ga-z97x-gaming 7 has voltage read points. Ud5h does too. Next to the power button.




Ah you mean on HWInfo? Dunno. But I don't see it here.
Software, yes.
I know how to check voltage with my meter. wink.gif

stasio 07-01-2014 04:11 AM

Guys,
check with latest HWMonitor (is a bit offset....in +) or GTL.



mandrix 07-01-2014 03:16 PM

Quote:
Originally Posted by stasio View Post

Guys,
check with latest HWMonitor (is a bit offset....in +) or GTL.

Warning: Spoiler! (Click to show)
Stasio, Vring isn't shown for all Gigabyte Z97 boards....my Z87 does, my Z97 does not. I told you that a while back.....your OC board shows it but most of the rest don't.
GTL just shows the setpoint in the BIOS, not the actual readout. The only way some of us can see Vring is with the meter.....

fateswarm 07-01-2014 03:56 PM

Weird. When I had ring manually on 1.05 (also the default) I couldn't see it on GTL. Now that I've put it on 1.12 I do (though with a weird print of 1.119141 but that's similar on core).

I still don't see it on hwinfo though.

stasio 07-02-2014 12:35 AM

Quote:
Originally Posted by mandrix View Post

Stasio, Vring isn't shown for all Gigabyte Z97 boards....my Z87 does, my Z97 does not. I told you that a while back.....your OC board shows it but most of the rest don't.
GTL just shows the setpoint in the BIOS, not the actual readout. The only way some of us can see Vring is with the meter.....
Yea,I know you tell me earlier.
GTL and EasyTune displaying VRing (and others) measured voltage (not set voltage).
How about HWMonitor?

fateswarm 07-02-2014 05:46 AM

Is it normal for vcore to be +0.02v than manually set?



On the multimeter. Software reports it as set.

mandrix 07-02-2014 06:34 AM

Quote:
Originally Posted by stasio View Post

Yea,I know you tell me earlier.
GTL and EasyTune displaying VRing (and others) measured voltage (not set voltage).
How about HWMonitor?
HWMonitor shows something for Vring, but nothing close to what my meter shows.

stasio 07-03-2014 02:44 AM

Quote:
Originally Posted by mandrix View Post

HWMonitor shows something for Vring, but nothing close to what my meter shows.
So,EasyTune and GTL is only choice.atm...

Cyro999 07-03-2014 03:22 AM

Quote:
Originally Posted by fateswarm View Post

Is it normal for vcore to be +0.02v than manually set?



On the multimeter. Software reports it as set.

Yes, normal and expected. Everyone went over this a year ago biggrin.gif

It doesn't rise in every load AFAIK, just many, that +0.02.

If your software is reporting it as set, you're probably looking at the wrong software. cpu-z versions past 1.64.0 on gigabyte z87 improperly display VID, and not the Vcore sensor. It was never fixed to my knowledge.

If you download Hwinfo ( www.hwinfo.com ) and scroll past the VID sensor down to Vcore, you should see it's very accurate, if it's the same for z97 as it is z87

stasio 07-03-2014 04:05 AM

Quote:
Originally Posted by Cyro999 View Post

Yes, normal and expected. Everyone went over this a year ago biggrin.gif

It doesn't rise in every load AFAIK, just many, that +0.02.

If your software is reporting it as set, you're probably looking at the wrong software. cpu-z versions past 1.64.0 on gigabyte z87 improperly display VID, and not the Vcore sensor. It was never fixed to my knowledge.

If you download Hwinfo ( www.hwinfo.com ) and scroll past the VID sensor down to Vcore, you should see it's very accurate, if it's the same for z97 as it is z87
Yea,
latest HWiNFO and AIDA64 displaying correct Vcore and VID voltage.

mandrix 07-03-2014 05:11 AM

Quote:
Originally Posted by stasio View Post

So,EasyTune and GTL is only choice.atm...
Easytune and GTL show Vring setpoint, but not actual voltage for me.
When I check Vring (&Vcore) with a meter when the pc is not under load, the voltages bounce around a lot and it's hard to get a good read but Vring seems considerably under the manual setpoint. But under load reading with a meter is much easier since the voltages are steadier.
As checked with a meter during load, Vring overshoots the manual setpoint a little bit but not too much.

On Auto setting Vring can scale up fairly high, at least 1.4v. Sin says that's no problem so I won't worry about it doing any damage.

stasio 07-03-2014 05:27 AM

Right ...Vring fluctuate (follows) as Vcore value.
Once you set fixed value,not much increase (maybe less then 10%).

fateswarm 07-03-2014 05:36 AM

Quote:
Originally Posted by Cyro999 View Post

Everyone went over this a year ago biggrin.gif

Sorry I don't know everything Master of the Universe Cyro999.




It appears that on HWInfo, the CPU itself reports it incorrectly as set, and an IT8620E sensor chip reports it close to the multimeter.

It appears that chip kinda connects like a multimeter. They could probably get rid of voltage read points with it on everything.

Hm, the polling rate appears to not be able to go as low.

Cyro999 07-03-2014 06:46 AM

Quote:
Sorry I don't know everything Master of the Universe Cyro999.

I thought you was following Haswell threads, i just say that because it came up on a daily basis for like half a year and ok a weekly basis since then biggrin.gif
Quote:
It appears that on HWInfo, the CPU itself reports it incorrectly as set

Every giga board i've seen so far has a VID sensor which tells you set voltage, and Vcore which tells you that correct reading

fateswarm 07-03-2014 06:54 AM

Apparently, a few boards report ring too.

Picklewheels 07-13-2014 03:12 AM

Hey, first time overclocking, currently testing my 4690k at 4.2 1.15v with OCCT: Linpack. Temps max at 69C, so at least temp wise this looks ok. Is it normal for OCCT:Linpack to ramp up and down during testing, rather than constantly pinning the cpu at 100%? It looks like it is pinning it at 100% but temps drop to ~50C every 30 seconds or so...

Cyro999 07-14-2014 03:53 AM

Quote:
Originally Posted by Picklewheels View Post

Hey, first time overclocking, currently testing my 4690k at 4.2 1.15v with OCCT: Linpack. Temps max at 69C, so at least temp wise this looks ok. Is it normal for OCCT:Linpack to ramp up and down during testing, rather than constantly pinning the cpu at 100%? It looks like it is pinning it at 100% but temps drop to ~50C every 30 seconds or so...

Yea, that's how Linpack works.

The linpack in OCCT and IBT is out of date and doesn't run avx2 instructions for Haswell, so you might wanna run another test. Also double check that you have windows 7 service pack 1 installed, it's important for CPU performance and a lot of people with new builds/installs miss it! thumb.gif

Airrick10 07-18-2014 11:11 AM

Subbed

mandrix 07-19-2014 05:20 AM

Quote:
Originally Posted by Cyro999 View Post

Yea, that's how Linpack works.

The linpack in OCCT and IBT is out of date and doesn't run avx2 instructions for Haswell, so you might wanna run another test. Also double check that you have windows 7 service pack 1 installed, it's important for CPU performance and a lot of people with new builds/installs miss it! thumb.gif
There are updated linpack libraries....not sure how updated IBT is though. Linx 0.6.5 is updated fairly often, I think it's up to 11.1.3 linpack. Anyway you can look over at TT Gigabyte forum.
http://forums.tweaktown.com/gigabyte/30530-latest-overclocking-programs-system-info-benchmarking-stability-tools.html
...or add newer linpack libs.

sabishiihito 07-19-2014 10:52 AM

Testing some BBSE on the SOC Force with my "old" 4770K.


KnownDragon 07-23-2014 08:25 AM

Nice thumb.gif

Airrick10 07-23-2014 11:20 AM

My Gigabyte Z97 Gaming 7 and 4970K are arriving today....really looking forward to using this guide to OC my DC!!! thumb.gif

Sin0822 07-23-2014 09:40 PM

nice

kpo6969 07-23-2014 09:45 PM

Anyone know what changes and or fixes for UD5H F9b beta bios are?
Thank you

Wildcard36qs 07-30-2014 10:01 AM

I have a 4790K and the Z97MX-Gaming 5. Will attempt at overclocking tonight.

marrawi 07-30-2014 10:05 AM

Quote:
Originally Posted by Wildcard36qs View Post

I have a 4790K and the Z97MX-Gaming 5. Will attempt at overclocking tonight.

May the cores be with you thumb.gif

mr sadistics 08-08-2014 12:43 PM

for z97 oc soc ! non force model! is necesary for overlocking plug the the 8pin 12v conector and 4pin 12v conector ?????' because my psu only have 1 8pin 12v thanks and sorry for my bad english

sabishiihito 08-09-2014 02:56 PM

You only need to connect the 8-pin 12v. Using both is for extreme overclocking under LN2.

mr sadistics 08-09-2014 03:39 PM

Quote:
Originally Posted by sabishiihito View Post

You only need to connect the 8-pin 12v. Using both is for extreme overclocking under LN2.

im using boths rigth now! any risk?

sabishiihito 08-09-2014 06:29 PM

No risk at all.

DarthBaggins 08-12-2014 09:01 AM

Might redo my oc having my rig reset while running [email protected] (full load) saying in my logs (in [email protected]) that it reset due to instability even though it can go 48hrs most of the time with no issues then bam reset. I almost think it might be something within my install of Ubuntu, which makes me want to install Mint, also it was stable in w8.1 which is where the OS stability is coming to question.

mrinfinit3 08-13-2014 09:23 PM

thumb.gif
Quote:
Originally Posted by DarthBaggins View Post

Might redo my oc having my rig reset while running [email protected] (full load) saying in my logs (in [email protected]) that it reset due to instability even though it can go 48hrs most of the time with no issues then bam reset. I almost think it might be something within my install of Ubuntu, which makes me want to install Mint, also it was stable in w8.1 which is where the OS stability is coming to question.
hmmmm where do I know you from....
But anyway; I have the same issue on my Gaming GT1.... seems only similarity I'll notice just prior to the crash is a high PCH core temp spike stored on the remote (tempu-link) server. (and only in [email protected])
I'm dieing for a block for her, but seems like no-one is interested in making one... Half debating on buying a busted Z87 OC Force/used aftermarket block and modding that to work for my needs.

**EDIT**
Quote:
hmmmm where do I know you from....
Wait Wait Wait...I think I've got it... old school SLIzone wink.gif



**EDIT r2**
BTW; hello fellow Giga-Z97er's. I just noticed I haven't posted in this thread yet, though have been lurking since the initial post thumb.gif
Here's what I've currently got going on:
5wacap.png
Figured not too bad of a start considering my last personal Intel "desktop" rig was back in the late 90's. Been working for/with AMD since 2006 as a sub-contractor (Enineer -> ), thus why I've never had to switch. But, considering they felt the need to trend away from the "high-performance" desktop market... I felt the need to trend away from them tongue.gif

hotrod717 08-24-2014 09:57 AM

Just picked up a SOC for my little ole' pentium. Have a nice little collection of legacy rams to try and am really excited about the mobo. I've been Asus for the past few builds and like the promise of this board. This is great guide, as always, Sin! +rep.


All times are GMT -7. The time now is 03:53 PM.

Powered by vBulletin® Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.

User Alert System provided by Advanced User Tagging (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.
vBulletin Security provided by vBSecurity (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.

vBulletin Optimisation provided by vB Optimise (Pro) - vBulletin Mods & Addons Copyright © 2020 DragonByte Technologies Ltd.