Overclock.net › Forums › Intel › Intel CPUs › Skylake Overclocking Guide [With Statistics]
New Posts  All Forums:Forum Nav:

Skylake Overclocking Guide [With Statistics] - Page 202

post #2011 of 11361
Quote:
Originally Posted by mandrix View Post

What does HWINFO call VCCIO on Asus boards? I'm assuming the VTT shown is for the RAM? If not then school me. tongue.gif

VTT is what it used to be called on older boards. I think it is IMC you are looking for, that's the one that changes for me when I adjust VCCIO.
post #2012 of 11361
Quote:
Originally Posted by Deders View Post

VTT is what it used to be called on older boards. I think it is IMC you are looking for, that's the one that changes for me when I adjust VCCIO.
Ah, OK. thanks!
post #2013 of 11361
Quote:
Originally Posted by llantant View Post

Any recommendations on max vccio and sa voltage? I read in the asus over locking guide 1.25v is fine.

Currently on 1.2 set in bios trying to get 3466mhz stable.

Intel does not yet list a max voltage or a min, just typical. There is a note for vccio that says when connecting to a lower speed PCH that it can be undervolted to .85v and the top grade PCH like we have in our good boards use .95v as typical. But ya, no max is listed. Still, that doesnt mean unlimited. I personally dont push past around 1.15v or so, and I dont know many that go over 1.2v unless they are doing LN2 runs or something.

Quote:
Originally Posted by mandrix View Post

What does HWINFO call VCCIO on Asus boards? I'm assuming the VTT shown is for the RAM? If not then school me. tongue.gif

Probably the IMC because vccio is the memory controller and external cache voltage so integrated memory controller would make sense for a label.
Gaming
(17 items)
 
Gaming PC
(20 items)
 
 
CPUMotherboardGraphicsRAM
7700K AS Rock Z170 OC Formula Titan X Pascal 2050MHz 64GB DDR4-3200 14-14-14-34-1T 
Hard DriveHard DriveHard DriveCooling
950 EVO m.2 OS drive 850 EVO 1TB games drive Intel 730 series 500GB games drive Custom water cooling 
OSMonitorKeyboardPower
Win 10 Pro x64 AMH A399U E-Element mechanical, black switches, Vortex b... EVGA G3 1kw 
CaseMouseAudioAudio
Lian-Li PC-V1000L Redragon M901 LH Labs Pulse X Infinity DAC Custom built balanced tube amp with SS diamond ... 
Audio
MrSpeakers Alpha Prime 
  hide details  
Reply
Gaming
(17 items)
 
Gaming PC
(20 items)
 
 
CPUMotherboardGraphicsRAM
7700K AS Rock Z170 OC Formula Titan X Pascal 2050MHz 64GB DDR4-3200 14-14-14-34-1T 
Hard DriveHard DriveHard DriveCooling
950 EVO m.2 OS drive 850 EVO 1TB games drive Intel 730 series 500GB games drive Custom water cooling 
OSMonitorKeyboardPower
Win 10 Pro x64 AMH A399U E-Element mechanical, black switches, Vortex b... EVGA G3 1kw 
CaseMouseAudioAudio
Lian-Li PC-V1000L Redragon M901 LH Labs Pulse X Infinity DAC Custom built balanced tube amp with SS diamond ... 
Audio
MrSpeakers Alpha Prime 
  hide details  
Reply
post #2014 of 11361
Quote:
Originally Posted by EniGma1987 View Post

Intel does not yet list a max voltage or a min, just typical. There is a note for vccio that says when connecting to a lower speed PCH that it can be undervolted to .85v and the top grade PCH like we have in our good boards use .95v as typical. But ya, no max is listed. Still, that doesnt mean unlimited. I personally dont push past around 1.15v or so, and I dont know many that go over 1.2v unless they are doing LN2 runs or something.
Probably the IMC because vccio is the memory controller and external cache voltage so integrated memory controller would make sense for a label.

Yeah. I'm an advocate for not over overvolting. Hate pumping way more than what I need.
On the plus I've knocked dram voltage up to 1.375v and vccio and sa down to 1.15 so far and it's passed an hour of stressapp test. thumb.gif

I'll keep working it down if poss.
Skylake!
(15 items)
 
 
Old School!
(13 items)
 
CPUMotherboardGraphicsRAM
Intel 6700k 4.7ghz 1.37v (4.6 cache) ASUS Maximus VIII Hero Nvidia GTX 1080 FTW 16gb G Skill TridentZ 3600hz 16/16/16/36 @ 1.35v 
Hard DriveHard DriveHard DriveCooling
SM951 256gb Nvme 2 x Samsung 840 Pro 256gb Raid 0 Western Digital Black 1.5tb HDD Storage Corsair H110 GTX 
OSMonitorKeyboardPower
Windows 10 Yamakasi Catleap Q251 1440p ips Corsair K70 EVGA Supernova 850 G2 
CaseMouseMouse Pad
Corsair Carbide 600Q Roccat Kone Pure Roccat Taito 
CPUMotherboardGraphicsRAM
Ph.II BE 1090T 3.75ghz BE (1.4v) 3000NB (1.325v) Asus M4A88TD-M Evo/USB3 GTX 470 G Skill Eco 1333mhz 5-6-5-18-23 1T 
Hard DriveOptical DriveOSPower
Crucial C300 128gb SSD, 2 x 640gb Storage (Raid) DVD-RW Win 7 Home Premium 800W 
Case
Coolermaster 310 
  hide details  
Reply
Skylake!
(15 items)
 
 
Old School!
(13 items)
 
CPUMotherboardGraphicsRAM
Intel 6700k 4.7ghz 1.37v (4.6 cache) ASUS Maximus VIII Hero Nvidia GTX 1080 FTW 16gb G Skill TridentZ 3600hz 16/16/16/36 @ 1.35v 
Hard DriveHard DriveHard DriveCooling
SM951 256gb Nvme 2 x Samsung 840 Pro 256gb Raid 0 Western Digital Black 1.5tb HDD Storage Corsair H110 GTX 
OSMonitorKeyboardPower
Windows 10 Yamakasi Catleap Q251 1440p ips Corsair K70 EVGA Supernova 850 G2 
CaseMouseMouse Pad
Corsair Carbide 600Q Roccat Kone Pure Roccat Taito 
CPUMotherboardGraphicsRAM
Ph.II BE 1090T 3.75ghz BE (1.4v) 3000NB (1.325v) Asus M4A88TD-M Evo/USB3 GTX 470 G Skill Eco 1333mhz 5-6-5-18-23 1T 
Hard DriveOptical DriveOSPower
Crucial C300 128gb SSD, 2 x 640gb Storage (Raid) DVD-RW Win 7 Home Premium 800W 
Case
Coolermaster 310 
  hide details  
Reply
post #2015 of 11361
Ok guys, bigger plot twist in my developing story of overclocking. After resetting my bios back to optimized default, my 6600k is running realbench as I type this at 4.4ghz on stock voltage, by that I mean it's only at 1.265v with about a .010v variance. Maybe I did something wrong before but how could it not be stable at higher than 4.6 when the voltages are so low already. Will update if stress test fails

Edit: Plot development, my cpu is stable at 4.7ghz at 1.42v. I don't know how, but it is
Edited by mattebad - 9/22/15 at 7:21pm
post #2016 of 11361
Quote:
Originally Posted by mattebad View Post

Also, my screen keeps flashing and tearing and I have no idea why. igpu clock is still at stock and its voltages are set to auto. I don't have a gpu yet as I'm waiting for my 980ti to come in the mail. Could that be the cause of the screen tearing and flashing?

Edit: Set my overclock to Asus' optimized profile at 4.4ghz and everything is fine, I have no idea what could be the cause of the tearing and flashing

Have you found a fix for this yet beyond getting a dGPU or lowering OC? I removed XMP and it appeared to fix it (like you dropped OC it helped you).

Monitoring HWInfo while I run something simple as Cine15 OpenGL shows a limiter is kicking in but I cannot find a fix for it. The odd thing is, I start XTU, drop the multiplier or do something else and the limiter is gone.

http://www.overclock.net/t/1235672/official-hwinfo-32-64-thread/930#post_24437522
Just a 'puter
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 6700K ASUS Maximus VIII Hero iGPU thanks to Nvidia 970 3.5GB Corsair Vengeance LPX CMK8GX4M2B3200C16 
Hard DriveHard DriveCoolingCooling
Samsung 950 PRO 512GB Crucial M4 256GB RX360 V3 Koolance CPU-380I 
CoolingCoolingOSMonitor
Koolance RP-452X2 Reservoir Koolance PMP-450 12V Variable Speed Pump Windows 10 Pro x64 benq XL2411Z 
KeyboardPowerCaseMouse
logitech G510 Seasonic X-760 Corsair 800D Mionix Castor 
AudioAudio
Creative Sound Blaster X-Fi Titanium HD DT 990 Premium 250Ohm 
  hide details  
Reply
Just a 'puter
(18 items)
 
  
CPUMotherboardGraphicsRAM
Intel Core i7 6700K ASUS Maximus VIII Hero iGPU thanks to Nvidia 970 3.5GB Corsair Vengeance LPX CMK8GX4M2B3200C16 
Hard DriveHard DriveCoolingCooling
Samsung 950 PRO 512GB Crucial M4 256GB RX360 V3 Koolance CPU-380I 
CoolingCoolingOSMonitor
Koolance RP-452X2 Reservoir Koolance PMP-450 12V Variable Speed Pump Windows 10 Pro x64 benq XL2411Z 
KeyboardPowerCaseMouse
logitech G510 Seasonic X-760 Corsair 800D Mionix Castor 
AudioAudio
Creative Sound Blaster X-Fi Titanium HD DT 990 Premium 250Ohm 
  hide details  
Reply
post #2017 of 11361
Quote:
Originally Posted by error-id10t View Post

Have you found a fix for this yet beyond getting a dGPU or lowering OC? I removed XMP and it appeared to fix it (like you dropped OC it helped you).

Monitoring HWInfo while I run something simple as Cine15 OpenGL shows a limiter is kicking in but I cannot find a fix for it. The odd thing is, I start XTU, drop the multiplier or do something else and the limiter is gone.

http://www.overclock.net/t/1235672/official-hwinfo-32-64-thread/930#post_24437522

After I updated my igpu it was okay for a bit but then it came back. It's been fine ever since I set my VCCIO to like 1.1 and SA to 1.05. I think I just had them both too high
post #2018 of 11361
Quote:
Originally Posted by EniGma1987 View Post

yes you are right, those big legs are not the capacitors. I had thought they were kinda big, but i didnt see anything else that looked like capacitor legs. Guess they were just covered up by that big bracket.

If you are reading only 1.208, then either you are reading voltage from something other than the vcore (in the VRM area there is vcore, iGPU voltage, and vccsa+vccio) or your bios really is not setting the voltage properly. Normally those points you circled are the vcore, but I suppose it is possible that your board has the circuit traces set up kinda weird and they are something else. Did you try using manual voltage or just offset or adaptive? Id try manual and set it to 1.4v and leave all other voltages at default, and CPU speeds at default. Also turn off SpeedStep and disable all C-States. Then poke around and find the area that is closest to a 1.4v reading. Once you find that you will know where to read the CPU voltage and you can then change things how you want to determine which software program is the most accurate for you.
You never ever read VID with a dmm, since VID is only what the processor itself is requesting for a certain performance level. It is not a real voltage and you cannot set VID, it comes from physical parts in the CPU. You only set vcore, and what gets fed into the processor is vcore. When you mess with voltages yourself then the processor no longer gets its VID.
EDIT: However, some programs dont label stuff right and they label VID in areas where they should really call it vcore. It causes a lot of confusion.
Quote:
Originally Posted by ktmderf View Post

So I ended up testing the points on the motherboard that were suggested and I got some really interesting values. First off in the picture that I provided I believe my cpu mounting bracket is blocking the two legs of the actual capacitors closer to the cpu. When I tested the suggested points I would get no reading on my digital multimeter. Which I thought was really strange so I did more research and found good close up pictures of both the front and back of the motherboard with no bracket. I think the two legs that were pointed out are actually from the mosfets? I could be completely wrong with what those are called. Anyways I ended up testing at these two points that I have circled.


When I tested those two points I would get a constant 1.208v no matter what voltage I set in the bios for vcore. The only way I could get that voltage to fluctuate was to set everything to default settings and it would then give me a lower reading. I don't get why the voltage reading does not increase even though I am upping it in the bios? Are the two legs I have pointed out incorrect? I know the cpu has to be getting more voltage when I up it in the bios because it will start to run hotter.. so maybe I am reading it at the wrong point.

Thanks

Those two points should be VCore, but just test all of the capacitors in the row. That is the Z170 FTW, right? Are you applying load and measuring after measuring at idle?

The big legs are inductors, you shouldn't measure there. Measure at each point of the capacitor which are the much smaller legs that are closer together. From thermal images i took it is the vertical row which has the VCore phases, but it might be that some of the capacitors that are vertical might be for the iGPU output or VCCSA (VCCSA is a slight bump to stock VCCSA voltage). I was able to OC fine on that board and I did manual readings to make sure I was getting votlage, but that was on an earlier BIOS, so maybe it's messed up. Make sure you use vdroop control. If the manufacturer went and messed with the AC/DC LLC settings internal to the CPU I have seen odd things happen. You can try manually setting a very low value like 0-250, otherwise higher values just engaged SVID from what I was seeing on a few boards which have no external LLC and only internal.
Edited by Sin0822 - 9/22/15 at 8:36pm
X99 Main Rig
(10 items)
 
  
CPUMotherboardGraphicsRAM
Intel 5960X Extreme Edition @ 4.5GHz Always Changing VisonTek R9 290 G.Skill Ripjaws 4 16GB (4x4GB) DDR4 @ 3200MHz 
Hard DriveHard DriveHard DriveCooling
Samsung 128GB M.2 PCI-E 4x SSD Apotop 256GB SSD 1.82TB NAS Noctua NH-D15 with both fans 
OSPower
Win7 Pro Enermax 1000W 
  hide details  
Reply
X99 Main Rig
(10 items)
 
  
CPUMotherboardGraphicsRAM
Intel 5960X Extreme Edition @ 4.5GHz Always Changing VisonTek R9 290 G.Skill Ripjaws 4 16GB (4x4GB) DDR4 @ 3200MHz 
Hard DriveHard DriveHard DriveCooling
Samsung 128GB M.2 PCI-E 4x SSD Apotop 256GB SSD 1.82TB NAS Noctua NH-D15 with both fans 
OSPower
Win7 Pro Enermax 1000W 
  hide details  
Reply
post #2019 of 11361
Quote:
Originally Posted by EniGma1987 View Post

yes you are right, those big legs are not the capacitors. I had thought they were kinda big, but i didnt see anything else that looked like capacitor legs. Guess they were just covered up by that big bracket.

If you are reading only 1.208, then either you are reading voltage from something other than the vcore (in the VRM area there is vcore, iGPU voltage, and vccsa+vccio) or your bios really is not setting the voltage properly. Normally those points you circled are the vcore, but I suppose it is possible that your board has the circuit traces set up kinda weird and they are something else. Did you try using manual voltage or just offset or adaptive? Id try manual and set it to 1.4v and leave all other voltages at default, and CPU speeds at default. Also turn off SpeedStep and disable all C-States. Then poke around and find the area that is closest to a 1.4v reading. Once you find that you will know where to read the CPU voltage and you can then change things how you want to determine which software program is the most accurate for you..

Thanks for the reply. I ended up checking directly under the socket and I found a voltage that has to be the vcore. In my bios I have it set manually at 1.295v. The EVGA E-LEET program was reading 1.3066v at idle and 1.344v under full load. I found a spot under the socket that read 1.317v at idle and 1.348v under full load. So I'm assuming that's it. It's nice to know now that the E-LEET program is close to accurate but still frustrating that my board raises voltage like this.
Quote:
Originally Posted by Sin0822 View Post


Those two points should be VCore, but just test all of the capacitors in the row. That is the Z170 FTW, right? Are you applying load and measuring after measuring at idle?

The big legs are inductors, you shouldn't measure there. Measure at each point of the capacitor which are the much smaller legs that are closer together. From thermal images i took it is the vertical row which has the VCore phases, but it might be that some of the capacitors that are vertical might be for the iGPU output or VCCSA (VCCSA is a slight bump to stock VCCSA voltage). I was able to OC fine on that board and I did manual readings to make sure I was getting votlage, but that was on an earlier BIOS, so maybe it's messed up. Make sure you use vdroop control. If the manufacturer went and messed with the AC/DC LLC settings internal to the CPU I have seen odd things happen. You can try manually setting a very low value like 0-250, otherwise higher values just engaged SVID from what I was seeing on a few boards which have no external LLC and only internal.

Thanks for all the info! Unfortunately my CPU mounting bracket on the backside covers the legs of all of those capacitors up. I was able to take a small notch out of the plastic and measure one of the capacitors but that was where I was getting the constant 1.208v no matter what I set in the bios. I ended up finding the vcore directly under the socket. I haven't actually had any problems overclocking with board it has actually been great. I am stable at 4.8 ghz with a vcore of 1.295v in the bios. The thing that I was curious about and somewhat bothered me is my voltage always rises under load. It will go from 1.308v at idle and up to 1.344v under load. Under the socket I was getting 1.317v at idle and 1.348v at load and if I changed the vcore value in the bios the value would change on the multi-meter where I was testing. So I'm guessing the one capacitor that I decided to uncover just wasn't for vcore? In the bios the only options I have for vdroop is enabled, disabled, and auto. I don't have anyway of setting a value for vdroop or LLC. What value are you talking about manually setting when you mention a low value of 0-250? Thanks for all the help
Edited by ktmderf - 9/22/15 at 8:59pm
post #2020 of 11361
Ok, here we go. Can anyone tell me why my igpu is deciding to try and run at a clock speed of almost 3.5ghz. Yes you heard that correct and no it isn't a sensor fault, it is literally trying to run at that speed during games or cinebench which might lead me to believe why I was getting tearing and flashing before. The only settings I've changed in my Bios are my multiplier, voltage offset to +.150, current capacity 140%, LLC level 3, max gpu ratio 23 (1150mhz), RAM 2500mhz, DRAM Voltage 1.25, SA 1.05, VCCIO 1.1, vrm spread spectrum disabled, and power phase timing to optimized.
I literally have no idea what could cause this when its set to run at 1150mhz in the bios but runs at 3.5ghz in the os and benchmarks. How is this even possible?

Edit: So appearantly my igpu has decided to upgrade itself to a Broadwell Gpu....It also thinks I'm using DDR3...And thinks it has double the shaders....So yeah....

http://gpuz.techpowerup.com/15/09/23/86v.png

I don't even know...

Anybody from Intel wanna chime in on this?
Edited by mattebad - 9/22/15 at 9:36pm
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: Intel CPUs
Overclock.net › Forums › Intel › Intel CPUs › Skylake Overclocking Guide [With Statistics]