Overclock.net › Forums › Intel › Intel Motherboards › ASUS X79 OC help
New Posts  All Forums:Forum Nav:

ASUS X79 OC help

post #1 of 13
Thread Starter 
Hi all,

See sig rig for details, but it's a 3930k with 4x8GB of Patriot rated at 1866MHz 10-11-10-30.

I'm running into stability issues on an OC that should really be a cakewalk. Seems no matter what I do I fail AIDA64 stress test just short of hitting the 6 hour mark (at about 5:48).

I can't get stable at 4.5 GHz and stock RAM, or even RAM timings loosened to 12-12-12-36 (or 11-11-11-30).

The crazy thing is that I fail at _exactly_ the same spot in the stress test at 4.7GHz and RAM at 2133MHz (12-12-12-36).

This is with 1.42vcore, 1.65vdimm, 1.1v (or even 1.15v) VCCSA and CPUVTT. Max current load at 130% for CPU, VTT, and RAM.

Any hints? At the gentler OC listed above I also BSOD'd after several hours (not sure how many, I was sleeping) of "natural" high load, roughly 94% CPU usage running 10 parallel workers that were themselves calling multithreaded math library functions.

Any help that gets me stable is worth rep for sure, thanks in advance!
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
post #2 of 13
What is your BSOD codes?

What method are you using to Stress test? Aida64 ? I suggest Prime 95 with AVX (Latest version) and Run a Custom Blend with 90% of memory available.

What is your Load Line Calibration setting?



You have 32GB ram so the test window should look like this:

Edited by KaRLiToS - 2/13/13 at 9:05am
Quad Damage
(24 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4930k @ 4.6Ghz Asus Rampage IV Extreme (Koolance Full WB) 2 x GTX 1080ti FE in SLI (EK WATERBLOCK) Corsair Dominator GT 2133 MHz (16GB) 
Hard DriveHard DriveHard DriveHard Drive
3 TB Seagate OCZ Vertex 4 256GB Crucial M4 128GB ADATA SX900 128GB 
CoolingCoolingCoolingCooling
RIVE Koolance Waterblock (VRM and PCH) Feser X-Changer 360 Feser X-Changer 240 Feser X-Changer 480 
CoolingCoolingCoolingOS
WaterCool MoRA3 Pro with Gentle Typhoon 3 x MCP 655 pumps (With EK top...all serial) 2 x EK FC 1080ti Blocks Windows 7 Ultimate x64 
MonitorMonitorKeyboardPower
Asus ROG Swift PG348Q (3440x1440 @100hz) CrossOver 27Q Led-P Logitech G15 EVGA SuperNova 1600T2 (Titanium) 
CaseMouseMouse PadAudio
Corsair Obsidian Heavily Modded Logitech G700 RocketFish Speed/Control M-audio AV-40 (Logitech G-35) 
  hide details  
Reply
Quad Damage
(24 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4930k @ 4.6Ghz Asus Rampage IV Extreme (Koolance Full WB) 2 x GTX 1080ti FE in SLI (EK WATERBLOCK) Corsair Dominator GT 2133 MHz (16GB) 
Hard DriveHard DriveHard DriveHard Drive
3 TB Seagate OCZ Vertex 4 256GB Crucial M4 128GB ADATA SX900 128GB 
CoolingCoolingCoolingCooling
RIVE Koolance Waterblock (VRM and PCH) Feser X-Changer 360 Feser X-Changer 240 Feser X-Changer 480 
CoolingCoolingCoolingOS
WaterCool MoRA3 Pro with Gentle Typhoon 3 x MCP 655 pumps (With EK top...all serial) 2 x EK FC 1080ti Blocks Windows 7 Ultimate x64 
MonitorMonitorKeyboardPower
Asus ROG Swift PG348Q (3440x1440 @100hz) CrossOver 27Q Led-P Logitech G15 EVGA SuperNova 1600T2 (Titanium) 
CaseMouseMouse PadAudio
Corsair Obsidian Heavily Modded Logitech G700 RocketFish Speed/Control M-audio AV-40 (Logitech G-35) 
  hide details  
Reply
post #3 of 13
Thread Starter 
Quote:
Originally Posted by KaRLiToS View Post

What is your BSOD codes?

What method are you using to Stress test? Aida64 ? I suggest Prime 95 with AVX (Latest version) and Run a Custom Blend with 90% of memory available.

What is your Load Line Calibration setting?



You have 32GB ram so the test window should look like this:

Yes I've been using Aida64. I can switch to prime for the next test, but if I'm failing Aida64 (and BSODing under natural load) I'm unstable either way, no?

I've mostly been working with LLC on Ultra High and a low offset value set (+0.015), but I've also tried Normal and High with higher offsets, all targeting a peak vcore around 1.41. I've also tried manual mode just straight up setting it to 1.4v and keeping LLC on Ultra High, that was what BSOD'd under natural load last night (at 4.5GHz).

I haven't managed to grab BSOD codes, but the Event Viewer logs show these details for the most recent one:
Code:
Log Name:      System
Source:        Microsoft-Windows-Kernel-Power
Date:          2/12/2013 7:29:43 AM
Event ID:      41
Task Category: (63)
Level:         Critical
Keywords:      (2)
User:          SYSTEM
Computer:      Jared-PC
Description:
The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Kernel-Power" Guid="{331C3B3A-2005-44C2-AC5E-77220C37D6B4}" />
    <EventID>41</EventID>
    <Version>2</Version>
    <Level>1</Level>
    <Task>63</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000002</Keywords>
    <TimeCreated SystemTime="2013-02-12T12:29:43.763219800Z" />
    <EventRecordID>16422</EventRecordID>
    <Correlation />
    <Execution ProcessID="4" ThreadID="8" />
    <Channel>System</Channel>
    <Computer>%%%%%%%</Computer>
    <Security UserID="%%%%%%%" />
  </System>
  <EventData>
    <Data Name="BugcheckCode">209</Data>
    <Data Name="BugcheckParameter1">0x70</Data>
    <Data Name="BugcheckParameter2">0x2</Data>
    <Data Name="BugcheckParameter3">0x0</Data>
    <Data Name="BugcheckParameter4">0xfffff880012ed195</Data>
    <Data Name="SleepInProgress">false</Data>
    <Data Name="PowerButtonTimestamp">0</Data>
  </EventData>
</Event>
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
post #4 of 13
Thread Starter 
Did some research, a little .exe called BlueScreenView says they're 0xd1 codes, so I'll try increasing QPI/VTT voltage next....
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
post #5 of 13
BSOD Codes for SandyBridge
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage

Warning: Spoiler! (Click to show)
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r



QPI/VTT over-volting helps with DRAM and BCLK Overclocking. Secondary VTT does not. However, try to maintain at most a 300mv delta between both voltages for stability. 1.40v is fine on these CPUs. 1.35v is sufficient most of the time.


CPU VCCSA Voltage: Two options here. The first is “Manual Mode”, which allows us to set a ‘static’ level of voltage for the System Agent. The second mode is “Offset Mode”, which works on the same principals as Vcore Offset Mode. VCCSA has a direct impact on memory stability, so will need increasing if you are running high density modules and/or overclocking the memory controller. As a general rule VCCSA should not be set higher than CPU Vcore as this will impact system stability. The reason for this is likely due to processor Vcore being used as either a pull-up rail for IO signaling stages, or internal DC coupling.

If overclocking past DDR3-2000, then finding the optimal delta between CPU vcore and VCCSA becomes critical with some memory modules. Hence, we recommend making small changes and monitoring for impact upon stability. It is probably wise not to exceed a voltage delta larger than 0.6V between VDIMM and VCCSA, so if VDIMM is set to 1.65V, then set VCCSA at around 1.05V minimum as a starting point AND also try to keep VCCSA within 0.3V of Vcore if possible.
Edited by KaRLiToS - 2/13/13 at 10:09am
Quad Damage
(24 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4930k @ 4.6Ghz Asus Rampage IV Extreme (Koolance Full WB) 2 x GTX 1080ti FE in SLI (EK WATERBLOCK) Corsair Dominator GT 2133 MHz (16GB) 
Hard DriveHard DriveHard DriveHard Drive
3 TB Seagate OCZ Vertex 4 256GB Crucial M4 128GB ADATA SX900 128GB 
CoolingCoolingCoolingCooling
RIVE Koolance Waterblock (VRM and PCH) Feser X-Changer 360 Feser X-Changer 240 Feser X-Changer 480 
CoolingCoolingCoolingOS
WaterCool MoRA3 Pro with Gentle Typhoon 3 x MCP 655 pumps (With EK top...all serial) 2 x EK FC 1080ti Blocks Windows 7 Ultimate x64 
MonitorMonitorKeyboardPower
Asus ROG Swift PG348Q (3440x1440 @100hz) CrossOver 27Q Led-P Logitech G15 EVGA SuperNova 1600T2 (Titanium) 
CaseMouseMouse PadAudio
Corsair Obsidian Heavily Modded Logitech G700 RocketFish Speed/Control M-audio AV-40 (Logitech G-35) 
  hide details  
Reply
Quad Damage
(24 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4930k @ 4.6Ghz Asus Rampage IV Extreme (Koolance Full WB) 2 x GTX 1080ti FE in SLI (EK WATERBLOCK) Corsair Dominator GT 2133 MHz (16GB) 
Hard DriveHard DriveHard DriveHard Drive
3 TB Seagate OCZ Vertex 4 256GB Crucial M4 128GB ADATA SX900 128GB 
CoolingCoolingCoolingCooling
RIVE Koolance Waterblock (VRM and PCH) Feser X-Changer 360 Feser X-Changer 240 Feser X-Changer 480 
CoolingCoolingCoolingOS
WaterCool MoRA3 Pro with Gentle Typhoon 3 x MCP 655 pumps (With EK top...all serial) 2 x EK FC 1080ti Blocks Windows 7 Ultimate x64 
MonitorMonitorKeyboardPower
Asus ROG Swift PG348Q (3440x1440 @100hz) CrossOver 27Q Led-P Logitech G15 EVGA SuperNova 1600T2 (Titanium) 
CaseMouseMouse PadAudio
Corsair Obsidian Heavily Modded Logitech G700 RocketFish Speed/Control M-audio AV-40 (Logitech G-35) 
  hide details  
Reply
post #6 of 13
Thread Starter 
Quote:
Originally Posted by KaRLiToS View Post

BSOD Codes for SandyBridge
0x124 = add/remove vcore or QPI/VTT voltage (usually Vcore, once it was QPI/VTT)
0x101 = add more vcore
0x50 = RAM timings/Frequency add DDR3 voltage or add QPI/VTT
0x1E = add more vcore
0x3B = add more vcore
0xD1 = add QPI/VTT voltage
“0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances”
0X109 = add DDR3 voltage
0x0A = add QPI/VTT voltage

Warning: Spoiler! (Click to show)
0x101 = increase vcore
0x124 = increase/decrease QPI/VTT first, if not increase/decrease vcore...have to test to see which one it is
on i7 45nm, usually means too little VVT/QPI for the speed of Uncore
on i7 32nm SB, usually means too little vCore
0x0A = unstable RAM/IMC, increase QPI first, if that doesn't work increase vcore
0x1A = Memory management error. It usually means a bad stick of Ram. Test with Memtest or whatever you prefer. Try raising your Ram voltage
0x1E = increase vcore
0x3B = increase vcore
0x3D = increase vcore
0xD1 = QPI/VTT, increase/decrease as necessary, can also be unstable Ram, raise Ram voltage
0x9C = QPI/VTT most likely, but increasing vcore has helped in some instances
0x50 = RAM timings/Frequency or uncore multi unstable, increase RAM voltage or adjust QPI/VTT, or lower uncore if you're higher than 2x
0x109 = Not enough or too Much memory voltage
0x116 = Low IOH (NB) voltage, GPU issue (most common when running multi-GPU/overclocking GPU)
0x7E = Corrupted OS file, possibly from overclocking. Run sfc /scannow and chkdsk /r



QPI/VTT over-volting helps with DRAM and BCLK Overclocking. Secondary VTT does not. However, try to maintain at most a 300mv delta between both voltages for stability. 1.40v is fine on these CPUs. 1.35v is sufficient most of the time.


CPU VCCSA Voltage: Two options here. The first is “Manual Mode”, which allows us to set a ‘static’ level of voltage for the System Agent. The second mode is “Offset Mode”, which works on the same principals as Vcore Offset Mode. VCCSA has a direct impact on memory stability, so will need increasing if you are running high density modules and/or overclocking the memory controller. As a general rule VCCSA should not be set higher than CPU Vcore as this will impact system stability. The reason for this is likely due to processor Vcore being used as either a pull-up rail for IO signaling stages, or internal DC coupling.

If overclocking past DDR3-2000, then finding the optimal delta between CPU vcore and VCCSA becomes critical with some memory modules. Hence, we recommend making small changes and monitoring for impact upon stability. It is probably wise not to exceed a voltage delta larger than 0.6V between VDIMM and VCCSA, so if VDIMM is set to 1.65V, then set VCCSA at around 1.05V minimum as a starting point AND also try to keep VCCSA within 0.3V of Vcore if possible.

So on this board QPI/VTT is the VTTCPU voltage? Or it's VCCSA? Aaaand.... does the VTTDDR matter at all? I haven't seen anyone discuss it so I've been leaving it on auto.
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
post #7 of 13
QPI/VTT = VTTCPU

VCCSA = System Agent Voltage

What voltage is your memory @1866Mhz (Default voltage, 1.65v) ?

VTTDDR Voltage: Leave at Auto unless experiencing instability with memory. As a starting point, set to 50% of DRAM voltage. So if DRAM voltage is 1.65V, then set ~ 0.825V here

I personnally don't touch VTTDDR but "AUTO" equals half of DRAM voltage like explained in the above definition.


Most important informations can be found here.
Rampage IV Extreme UEFI Guide for Overclocking
Edited by KaRLiToS - 2/13/13 at 10:29am
Quad Damage
(24 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4930k @ 4.6Ghz Asus Rampage IV Extreme (Koolance Full WB) 2 x GTX 1080ti FE in SLI (EK WATERBLOCK) Corsair Dominator GT 2133 MHz (16GB) 
Hard DriveHard DriveHard DriveHard Drive
3 TB Seagate OCZ Vertex 4 256GB Crucial M4 128GB ADATA SX900 128GB 
CoolingCoolingCoolingCooling
RIVE Koolance Waterblock (VRM and PCH) Feser X-Changer 360 Feser X-Changer 240 Feser X-Changer 480 
CoolingCoolingCoolingOS
WaterCool MoRA3 Pro with Gentle Typhoon 3 x MCP 655 pumps (With EK top...all serial) 2 x EK FC 1080ti Blocks Windows 7 Ultimate x64 
MonitorMonitorKeyboardPower
Asus ROG Swift PG348Q (3440x1440 @100hz) CrossOver 27Q Led-P Logitech G15 EVGA SuperNova 1600T2 (Titanium) 
CaseMouseMouse PadAudio
Corsair Obsidian Heavily Modded Logitech G700 RocketFish Speed/Control M-audio AV-40 (Logitech G-35) 
  hide details  
Reply
Quad Damage
(24 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4930k @ 4.6Ghz Asus Rampage IV Extreme (Koolance Full WB) 2 x GTX 1080ti FE in SLI (EK WATERBLOCK) Corsair Dominator GT 2133 MHz (16GB) 
Hard DriveHard DriveHard DriveHard Drive
3 TB Seagate OCZ Vertex 4 256GB Crucial M4 128GB ADATA SX900 128GB 
CoolingCoolingCoolingCooling
RIVE Koolance Waterblock (VRM and PCH) Feser X-Changer 360 Feser X-Changer 240 Feser X-Changer 480 
CoolingCoolingCoolingOS
WaterCool MoRA3 Pro with Gentle Typhoon 3 x MCP 655 pumps (With EK top...all serial) 2 x EK FC 1080ti Blocks Windows 7 Ultimate x64 
MonitorMonitorKeyboardPower
Asus ROG Swift PG348Q (3440x1440 @100hz) CrossOver 27Q Led-P Logitech G15 EVGA SuperNova 1600T2 (Titanium) 
CaseMouseMouse PadAudio
Corsair Obsidian Heavily Modded Logitech G700 RocketFish Speed/Control M-audio AV-40 (Logitech G-35) 
  hide details  
Reply
post #8 of 13
Thread Starter 
Quote:
Originally Posted by KaRLiToS View Post

QPI/VTT = VTTCPU

VCCSA = System Agent Voltage

What voltage is your memory @1866Mhz (Default voltage, 1.65v) ?

VTTDDR Voltage: Leave at Auto unless experiencing instability with memory. As a starting point, set to 50% of DRAM voltage. So if DRAM voltage is 1.65V, then set ~ 0.825V here

I personnally don't touch VTTDDR but "AUTO" equals half of DRAM voltage like explained in the above definition.


Most important informations can be found here.
Rampage IV Extreme UEFI Guide for Overclocking

Stock for my RAM is 1.5v, but I've been running it at 1.65v. I'll try taking VTTCPU and VCCSA to 1.2v (I'm told they're supposed to be kept basically in sync with each other?), if that doesn't work I'll try boosting the VTTDDR a bit.
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
post #9 of 13
Quote:
Originally Posted by TriBeCa View Post

Stock for my RAM is 1.5v, but I've been running it at 1.65v. I'll try taking VTTCPU and VCCSA to 1.2v (I'm told they're supposed to be kept basically in sync with each other?), if that doesn't work I'll try boosting the VTTDDR a bit.

First, you have 32GB memory @ 1866mhz. Don,t go for higher, it will get you nowhere unless you plan to do benchmarks. You will never notice any difference between 1866 or 2133Mhz in every day program/games.

I would run it at 1866Mhz with 1.55v. Since you have 8GB modules. Leave VTTDDR at Auto.
VTT at 1.20v and VCCSa at 1.15v. And play with those voltage.


Also, you should read the guide I posted twice, take an hour or two and learn it by heart, it will greatly helps you.
Quad Damage
(24 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4930k @ 4.6Ghz Asus Rampage IV Extreme (Koolance Full WB) 2 x GTX 1080ti FE in SLI (EK WATERBLOCK) Corsair Dominator GT 2133 MHz (16GB) 
Hard DriveHard DriveHard DriveHard Drive
3 TB Seagate OCZ Vertex 4 256GB Crucial M4 128GB ADATA SX900 128GB 
CoolingCoolingCoolingCooling
RIVE Koolance Waterblock (VRM and PCH) Feser X-Changer 360 Feser X-Changer 240 Feser X-Changer 480 
CoolingCoolingCoolingOS
WaterCool MoRA3 Pro with Gentle Typhoon 3 x MCP 655 pumps (With EK top...all serial) 2 x EK FC 1080ti Blocks Windows 7 Ultimate x64 
MonitorMonitorKeyboardPower
Asus ROG Swift PG348Q (3440x1440 @100hz) CrossOver 27Q Led-P Logitech G15 EVGA SuperNova 1600T2 (Titanium) 
CaseMouseMouse PadAudio
Corsair Obsidian Heavily Modded Logitech G700 RocketFish Speed/Control M-audio AV-40 (Logitech G-35) 
  hide details  
Reply
Quad Damage
(24 items)
 
  
CPUMotherboardGraphicsRAM
Intel i7 4930k @ 4.6Ghz Asus Rampage IV Extreme (Koolance Full WB) 2 x GTX 1080ti FE in SLI (EK WATERBLOCK) Corsair Dominator GT 2133 MHz (16GB) 
Hard DriveHard DriveHard DriveHard Drive
3 TB Seagate OCZ Vertex 4 256GB Crucial M4 128GB ADATA SX900 128GB 
CoolingCoolingCoolingCooling
RIVE Koolance Waterblock (VRM and PCH) Feser X-Changer 360 Feser X-Changer 240 Feser X-Changer 480 
CoolingCoolingCoolingOS
WaterCool MoRA3 Pro with Gentle Typhoon 3 x MCP 655 pumps (With EK top...all serial) 2 x EK FC 1080ti Blocks Windows 7 Ultimate x64 
MonitorMonitorKeyboardPower
Asus ROG Swift PG348Q (3440x1440 @100hz) CrossOver 27Q Led-P Logitech G15 EVGA SuperNova 1600T2 (Titanium) 
CaseMouseMouse PadAudio
Corsair Obsidian Heavily Modded Logitech G700 RocketFish Speed/Control M-audio AV-40 (Logitech G-35) 
  hide details  
Reply
post #10 of 13
Thread Starter 
Quote:
Originally Posted by KaRLiToS View Post

First, you have 32GB memory @ 1866mhz. Don,t go for higher, it will get you nowhere unless you plan to do benchmarks. You will never notice any difference between 1866 or 2133Mhz in every day program/games.

I would run it at 1866Mhz with 1.55v. Since you have 8GB modules. Leave VTTDDR at Auto.
VTT at 1.20v and VCCSa at 1.15v. And play with those voltage.


Also, you should read the guide I posted twice, take an hour or two and learn it by heart, it will greatly helps you.

Thanks, I'll give that a try at my next chance to stress test (should be overnight tonight). However once I get stable at 1866 I will be trying to push to 2133 if the system can handle it without excessive voltages. This is not a gaming rig, but rather a workstation. It does things like matrix inversions and products on matrices with thousands (sometimes hundreds of thousands or even millions) of elements, not just once but tens of thousands of time, and often I'm more or less sitting on my thumbs waiting for it to finish. So RAM latency can indeed matter a lot....
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
Work Rig
(11 items)
 
  
CPUMotherboardGraphicsRAM
3930k ASUS Sabertooth X79 TUF EVGA GeForce GTX 660 Patriot Viper 3 Intel Extreme Masters 1866MHz 
Hard DriveHard DriveHard DriveCooling
OCZ 240G Vertex 3 SSD Seagate SV35 Series 3TB Seagate SV35 Series 3TB Corsair H100i 
OSPowerCase
Windows 7 Enterprise x64 Corsair 860W 80+ Platinum Cooler Mster Cosmos II Ultra 
  hide details  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel Motherboards
Overclock.net › Forums › Intel › Intel Motherboards › ASUS X79 OC help