Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread
New Posts  All Forums:Forum Nav:

ROG Crosshair VI overclocking thread - Page 872

post #8711 of 17850
The good news is, games that can fully load a Ryzen 7 are practically non-existant, so if youre into Ryzen 7 more for gaming than for production then LLC levels probably dont need to leave level 1. but when that crazy game arrives... sometime in the year 2250....
post #8712 of 17850
Quote:
Originally Posted by Reikoji View Post

The good news is, games that can fully load a Ryzen 7 are practically non-existant, so if youre into Ryzen 7 more for gaming than for production then LLC levels probably dont need to leave level 1. but when that crazy game arrives... sometime in the year 2250....

Absolutely; for me this is only an issue while benchmarking.
Inferior FTW!
(23 items)
 
  
CPUMotherboardGraphicsRAM
R7 1700@3.9ghz Asus Crosshair VI Hero Founder's GTX 1070 200/800 G.skill TridentZ RGB 3200 C14 
Hard DriveHard DriveCoolingCooling
Samsung 960 Evo Centon 120gb EK-FB Monoblock XSPC RX360 (White) 
CoolingCoolingCoolingCooling
XSPC RX240 (White) EK Vardar F2s (x5) EK-FC1070 GTX1070 (nickel/plexi)  EK GTX1070 FE backplate 
CoolingCoolingCoolingOS
EK Double Bay PWM D5 MX Bitspower 250 Z-Multi Res EK HDC fittings (12mm) Windows 10 
MonitorKeyboardPowerCase
Samsung C32F391 Razer Blackwidow Chroma EVGA Supernova G1 1000w Phanteks Enthoo Primo 
MouseMouse PadAudio
Razer Naga Epic Razer Vespula Sennheiser HD598 
  hide details  
Reply
Inferior FTW!
(23 items)
 
  
CPUMotherboardGraphicsRAM
R7 1700@3.9ghz Asus Crosshair VI Hero Founder's GTX 1070 200/800 G.skill TridentZ RGB 3200 C14 
Hard DriveHard DriveCoolingCooling
Samsung 960 Evo Centon 120gb EK-FB Monoblock XSPC RX360 (White) 
CoolingCoolingCoolingCooling
XSPC RX240 (White) EK Vardar F2s (x5) EK-FC1070 GTX1070 (nickel/plexi)  EK GTX1070 FE backplate 
CoolingCoolingCoolingOS
EK Double Bay PWM D5 MX Bitspower 250 Z-Multi Res EK HDC fittings (12mm) Windows 10 
MonitorKeyboardPowerCase
Samsung C32F391 Razer Blackwidow Chroma EVGA Supernova G1 1000w Phanteks Enthoo Primo 
MouseMouse PadAudio
Razer Naga Epic Razer Vespula Sennheiser HD598 
  hide details  
Reply
post #8713 of 17850
Quote:
Originally Posted by kaseki View Post

LLC provides a change in the loop characteristics to reduce the error at a cost of more overshoot.
.

For the most part (at equivalent currents), peak magnitude and settling times remain similar across the LLC range.
post #8714 of 17850
Quote:
Originally Posted by Reikoji View Post

The good news is, games that can fully load a Ryzen 7 are practically non-existant, so if youre into Ryzen 7 more for gaming than for production then LLC levels probably dont need to leave level 1. but when that crazy game arrives... sometime in the year 2250....

The over-voltage effect doesn't require 100% load to manifest. That means, you still need to be aware that you're applying +50mv more than what you've set in UEFI. Nothing more.

This is what ringing looks like:


Edited by Raja@ASUS - 4/12/17 at 7:47am
post #8715 of 17850
Well I call it stable almost 9 hours of prime.

post #8716 of 17850
Quote:
Originally Posted by Raja@ASUS View Post

For the most part (at equivalent currents), peak magnitude and settling times remain similar across the LLC range.

Thanks. I must have misread somewhere that the overshoots went up with higher settings, or perhaps conflated the higher corrections with higher overshoots. In general, though, if one wants a correction to occur with a shorter delay to some percentage of the final level, then the overshoot should be expected to grow.

I guess from what I've read that the higher LLC settings should be considered only where (in a server application, say) the variation in core current is rarely max to min, or where the baseline voltage being used is low enough that LLC overshoots do not reach the durability degradation level.
     
CPUMotherboardGraphicsRAM
AMD Ryzen 1800X ASUS ROG CROSSHAIR VI HERO X370 Asus ROG STRIX nVidia GeForce GTX1080Ti-O11G G. Skill TridentZ F4-3200C14D-32GTZ 
Hard DriveOptical DriveCoolingOS
Samsung SSD 850 EVO 256GB Asus UltraDrive 8X Noctua NH-D15 SE-AM4  Linux Mint 18.1 MATE 64-bit  
MonitorKeyboardPowerCase
LG 4K TV OLED55B6P Logitech MK235 RF Wireless Keyboard & Mouse PC Power & Cooling Turbo-Cool 860i Nanoxia Project S 
Mouse
See Keyboard 
CPUGraphicsRAMHard Drive
147,456 cores all registers exposed at the console 4096 36-bit words rotary drum 
Optical DriveMonitor
6 magnetic tape drives neon lites for every register; oscilloscope for... 
  hide details  
Reply
     
CPUMotherboardGraphicsRAM
AMD Ryzen 1800X ASUS ROG CROSSHAIR VI HERO X370 Asus ROG STRIX nVidia GeForce GTX1080Ti-O11G G. Skill TridentZ F4-3200C14D-32GTZ 
Hard DriveOptical DriveCoolingOS
Samsung SSD 850 EVO 256GB Asus UltraDrive 8X Noctua NH-D15 SE-AM4  Linux Mint 18.1 MATE 64-bit  
MonitorKeyboardPowerCase
LG 4K TV OLED55B6P Logitech MK235 RF Wireless Keyboard & Mouse PC Power & Cooling Turbo-Cool 860i Nanoxia Project S 
Mouse
See Keyboard 
CPUGraphicsRAMHard Drive
147,456 cores all registers exposed at the console 4096 36-bit words rotary drum 
Optical DriveMonitor
6 magnetic tape drives neon lites for every register; oscilloscope for... 
  hide details  
Reply
post #8717 of 17850
Quote:
Originally Posted by Raja@ASUS View Post

The over-voltage effect doesn't require 100% load to manifest. That means, you still need to be aware that you're applying +50mv more than what you've set in UEFI. Nothing more.

This is what ringing looks like:


But at LLC1 overshoot in even those cases won't occur correct?
post #8718 of 17850
Quote:
Originally Posted by gupsterg View Post

Warning: Spoiler! (Click to show)
I just had this, never before on say unstable settings for tweaks to RAM / BCLK / CPU OC, etc. IIRC SpecChum, Ubardog and a few others have had this on other UEFI versions perhaps or these newer ones?

Usually I never unhook power from PC when shutdown. I did as wanted to move case to do some tiding up on cabling. The moment I fired her up she went through 3x boots redface.gif, which she never usually does.





ProbeIt VCORE point showed ~1.498V redface.gif .

Attached is zip of UEFI screenies showing what I change from defaults.

0079_UEFI_OC_Setup.zip 2878k .zip file

Quote:
Originally Posted by Reikoji View Post

On every bios I've used, whenever i shut off the power supply for an extended and turn it back on it does the 3 boot thing as well, but my settings have never changed as a result. I never thought anything of it.

However it wont do it if you reset CMOS after re-applying power to the PSU, it will just do its normal initial long post loop and then force you into bios as normal.

After that high VCORE boot, I loaded optimized defaults, let system boot and shutdown. Then mains off and used CLRCMOS, next boot up loaded "base profile" ie everything stock but onboard stuff disabled as needed, fan profiles as want, etc. Then loaded my 3.8GHz 3200MHz C14 OC profile, like I have done when I've had a borked boot from say playing with RAM CLK / BCLK / CPU OC. Shutdown PC as usual (left power on on PSU like usual), waited very little while and switched rig on.

It did 1x post up, did some Q-Codes and shutdown and up again, 3x boot loop and borked again.





I don't think I'm having an issue due to cable tiding earlier.

All I did was remove cable from CHA3 for rear exhaust fans, cable tie and reinsert. Then PCI-E cables to GPU were not removed/relocated just cable tied as needed. Q-Connect / Speaker cable removed to test speaker as for a while it has not worked on C6H, reinserting it solved that issue.

All this has created this now redface.gif .

Like I said I have had borked boots / crashes in OS from unstable OC settings and ever since SpecChum / Ubardog mentioned this issue I have been on the look out if it happens to me and it did not, until today redface.gif .

Loading defaults now, removing power / battery, then reflashing UEFI.
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
XPS - R7 1700
(14 items)
 
XPS - i5 4690K
(12 items)
 
XPS - Q6600
(8 items)
 
CPUMotherboardGraphicsRAM
Ryzen 7 1700 Asus Crosshair VI Hero Sapphire Fury X@1145/545 G.Skill Trident Z 2x 8GB 3200MHz C14 
Hard DriveCoolingCoolingCooling
Samsung Evo 840 ThermalRight Archon IB-E X2 + 2x TY143 ThermalRight TY-143 2x front case intake Arctic Cooling F12 + 2x F9 as rear case exhaust 
OSMonitorKeyboardPower
Win 7 Pro x64 / Win 10 Pro x64 Asus MG279Q Cherry MX-Board 3.0 Cooler Master V850 
CaseMouse
SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
i5 4690K@4.9GHz 1.255V Asus Maximus VII Ranger Sapphire Fury X@1145/545 HyperX Savage 2x8GB 2400MHz C11 
Hard DriveCoolingOSMonitor
Samsung Evo 840 TR Archon SB-E X2 Win 7 Pro x64 / Win 10 x64 Asus MG279Q 
KeyboardPowerCaseMouse
Cherry MX-Board 3.0 Cooler Master V850 SilverStone TJ06 Logitech G700S 
CPUMotherboardGraphicsRAM
Intel Q6600 G0 Asus P5K Premium Black Pearl Sapphire Toxic HD5850 Corsair Dominator 4GB 
Hard DriveCoolingOSPower
Crucial MX 100 256GB TR TRUE Rev.A Win 7 Pro x64 Cooler Master V650 
  hide details  
Reply
post #8719 of 17850
@Reikoji

Did you see my prior response to your post?
Ryzen - Elmor
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 @ 3.8Ghz ASUS ROG CROSSHAIR VI HERO GeForce GTX 1070 32GB DDR4-3200 14-14-14-34 
Hard DriveHard DriveHard DriveHard Drive
Samsung 960 EVO 1TB Samsung 830 SSD 256GB Hitachi 2TB HGST 4TB  
CoolingOSMonitorPower
Noctua NH-D15S Windows 10 Pro Acer Predator XB271HU SeaSonic PRIME Titanium 750W 
Case
Fractal Design Define R5 
  hide details  
Reply
Ryzen - Elmor
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 @ 3.8Ghz ASUS ROG CROSSHAIR VI HERO GeForce GTX 1070 32GB DDR4-3200 14-14-14-34 
Hard DriveHard DriveHard DriveHard Drive
Samsung 960 EVO 1TB Samsung 830 SSD 256GB Hitachi 2TB HGST 4TB  
CoolingOSMonitorPower
Noctua NH-D15S Windows 10 Pro Acer Predator XB271HU SeaSonic PRIME Titanium 750W 
Case
Fractal Design Define R5 
  hide details  
Reply
post #8720 of 17850
Quote:
Originally Posted by gupsterg View Post

After that high VCORE boot, I loaded optimized defaults, let system boot and shutdown. Then mains off and used CLRCMOS, next boot up loaded "base profile" ie everything stock but onboard stuff disabled as needed, fan profiles as want, etc. Then loaded my 3.8GHz 3200MHz C14 OC profile, like I have done when I've had a borked boot from say playing with RAM CLK / BCLK / CPU OC. Shutdown PC as usual (left power on on PSU like usual), waited very little while and switched rig on.

It did 1x post up, did some Q-Codes and shutdown and up again, 3x boot loop and borked again.





I don't think I'm having an issue due to cable tiding earlier.

All I did was remove cable from CHA3 for rear exhaust fans, cable tie and reinsert. Then PCI-E cables to GPU were not removed/relocated just cable tied as needed. Q-Connect / Speaker cable removed to test speaker as for a while it has not worked on C6H, reinserting it solved that issue.

All this has created this now redface.gif .

Like I said I have had borked boots / crashes in OS from unstable OC settings and ever since SpecChum / Ubardog mentioned this issue I have been on the look out if it happens to me and it did not, until today redface.gif .

Loading defaults now, removing power / battery, then reflashing UEFI.

About that profile. Did you save it in an earlier bios?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread