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

ROG Crosshair VI overclocking thread - Page 1014

post #10131 of 17248
I'm more pissed with G.Skill and their crappy RGB RAM. 2 dead kits within 3 weeks...just sent my second set out for RMA today. First kit, somehow the SPD tables got FUBAR'd, second kit killed themselves on stock volts/clocks.
post #10132 of 17248
Quote:
Originally Posted by ProTekkFZS View Post

No, you're right, I don't think this was the absolute best way to go about it either. Just rather wanted to point out that it was AMD's choice and their "reasoning" for it, if you will. Quite a few people in this thread think it's ASUS making that choice. With AMD pulling back on Ryzen Master showing the offset, I'm pretty sure we will see the whole offset crap going away fairly soon™.

Yeah posted about "improved" Ryzen Master just a page or so back. Reddit members lapped it up IMO and as said no top comments said "hey what about the firmware, as our fan profiles are borked".

I have said before in the AM4 mobo thread, Elmor is top bloke, he helped on a query via PM on HWBot. I offered him a token paypal transfer for help, as it had value for me, he refused.

I have contacted experienced OC'ers several times in my exploits. There are only a few that have really given help, some ignored any request for help.

Below the Best of the Best in my eyes wink.gif .

post-flame-small.gifpost-flame-small.gifpost-flame-small.gifpost-flame-small.gif The Stilt, Elmor and Der8auer post-flame-small.gifpost-flame-small.gifpost-flame-small.gifpost-flame-small.gif

Then there is Martin Malik, phenomenal help. I have also tried to strike conversation with other app authors, shamefully lacking in support compared to him.
Edited by gupsterg - 4/19/17 at 12:13pm
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 #10133 of 17248
Quote:
Originally Posted by hotstocks View Post

Well it is the 2X8 G.skill 3600 C16 kit, samsung b-die obviously.
I have boot volt at 1.45, ddr voltage at 1.39v, soc at 1.2v 117BCLK with GEN 3 settings working fine 16-16-16-36 for the 3430 speed
and the 3200 is just stock with all the same voltages but cas 14-14-14-34

You overclocked your CPU as well? Using pstates or directly via multiplicator? I take it you didn't increase the PLL voltage.
main
(10 items)
 
  
Reply
main
(10 items)
 
  
Reply
post #10134 of 17248
Quote:
Originally Posted by ProTekkFZS View Post

I'm more pissed with G.Skill and their crappy RGB RAM. 2 dead kits within 3 weeks...just sent my second set out for RMA today. First kit, somehow the SPD tables got FUBAR'd, second kit killed themselves on stock volts/clocks.

Thats just bad luck damn. My g5 mobo went after 4 days ordered my ch6 about a week later.
    
CPUMotherboardGraphicsRAM
R7 1700X asus crosshair 6 Sapphire R9 390 Nitro CMK16GX4M2B3200C16 
Hard DriveHard DriveCoolingCooling
Kingston HyperX 3K Seagate ST2000DM006 EKWB Supremacy Evo EK-XRES 100 Revo D5 - Acetal 
CoolingCoolingCoolingCooling
Alphacool GPX r9 390 m01 alphacool xt45 240 Alphacool xt45 360 Alphacool D5 PWM 
OSMonitorKeyboardPower
Windows 10 LG 29UM68 Corsair Strafe Corsair RM1000 
CaseMouseMouse Pad
Thermaltake X5 Corsair M65 Pro RGB Razer Goliathus Speed 
  hide details  
Reply
    
CPUMotherboardGraphicsRAM
R7 1700X asus crosshair 6 Sapphire R9 390 Nitro CMK16GX4M2B3200C16 
Hard DriveHard DriveCoolingCooling
Kingston HyperX 3K Seagate ST2000DM006 EKWB Supremacy Evo EK-XRES 100 Revo D5 - Acetal 
CoolingCoolingCoolingCooling
Alphacool GPX r9 390 m01 alphacool xt45 240 Alphacool xt45 360 Alphacool D5 PWM 
OSMonitorKeyboardPower
Windows 10 LG 29UM68 Corsair Strafe Corsair RM1000 
CaseMouseMouse Pad
Thermaltake X5 Corsair M65 Pro RGB Razer Goliathus Speed 
  hide details  
Reply
post #10135 of 17248
Quote:
Originally Posted by BoMbY View Post

Regarding the memory latency, and performance, some things are not easily explainable with Ryzen. I see no performance difference between 1T and 2T Command Rate for example, using 2x16 GB Dual Ranked at 3200-18-16-16-36. Also several tests by now proof you get a better performance using Dual Ranked modules, compared with Single Ranked modules using the exact same settings (because of rank interleaving), also the Data Fabric seems to mask some improvements from lower memory latency settings, which is why the higher memory frequency seems to be more important.

The issue is that right now, the sub-timings are locked. So, as you increase the memory frequency or the config, you're likely retaining the same sub-timings (or could be drastically different). In a true test you'd set the sub-timings to their minimum value for the given clock speed to evaluate the disparity accurately. Personally, I dont care where the performance comes from, but I do want to make sure any statements or claims I make have a semblance of being thorough and show the gains in the proper light.
Edited by Raja@ASUS - 4/19/17 at 12:37pm
post #10136 of 17248
I was excited to return home and load up the new bios after being on vacation for 2 weeks, but that excitement quickly turned to disappointment once I loaded 0079 - 0083. All of these bios revisions have issues posting using the exact same settings I was running with 1001.

1001 was quite stable for me except for when booting after the PSU was unplugged or switched off.

0079+ randomly fails to post when turning on the computer. Actually it fails far more often than it succeeds. The system is also less stable in Windows with any one of these bios. Lowering my ram clock/timings and upping the voltage and vboot doesn't seem to help either unless I drop it below 2933.

I'm not sure what all these revisions contain other that AGESA and what's noted on page 1, so not easy to pinpoint the issue.
post #10137 of 17248
Two of us have found that setting ProcODT to the correct value for the memory config solves a lot of POST issues. One just needs some patience to tune it.
post #10138 of 17248
Quote:
Originally Posted by Raja@ASUS View Post

The issue is that right now, the sub-timings are locked. So, as you increase the memory frequency or the config, you're likely retaining the same sub-timings (or could be drastically different). In a true test you'd set the sub-timings to their minimum value for the given clock speed to evaluate the disparity accurately. Personally, I dont care where the performance comes from, but I do want to make sure any statements or claims I make have a semblance of being thorough and show the gains in the proper light.

When people like to nail you to the wall for "promising" them something, being careful about HOW you say things, not just what you say will be useful. I fully respect that you are being careful. As an old-school Computer Science guy, I sometimes want to get into discussions about architecture. The whole "Fabric speed" being key for overall performance and how RAM speed comes into it discussion being one of those.

Thank you again for your continued presence here, because most of us DO appreciate what you and Elmor do for the community.
post #10139 of 17248
Quote:
Originally Posted by Raja@ASUS View Post

Two of us have found that setting ProcODT to the correct value for the memory config solves a lot of POST issues. One just needs some patience to tune it.
Thanks. Checking the spreadsheet now. What does it default to on 1001? What is auto on 0079? This might help me pinpoint the right figure to use.
post #10140 of 17248
Quote:
Originally Posted by bluej511 View Post

The BIOS already has that done. It does on my ch6 and i haven't changed a thing. I'm on BIOS 1002 and on my 1700x my idle temp is 26°C today, its reported exactly right. No issues.

No it reports the right temperature and then another temperature 20C higher which most software uses. Unless you can tell me the bios setting that makes it report ONLY one correct lower temperature.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread