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

ROG Crosshair VI overclocking thread - Page 1186

post #11851 of 17696
Quote:
Originally Posted by CeltPC View Post


Can you explain what you mean by tuning an XMP profile for a Ryzen system, and why you would want to do that? Your comment intrigued me.


​I think he means the SPD table has an empty column where you can save your own custom timings, frequency and voltage. So instead of putting them in manually in the bios they can be programmed into this spare profile slot. I had a quick look about what he was on about but there were too many numbers and options I know nothing about. I'm sure its easy if you read up a bit on how it all works and what data you actually need to enter, how to enter it. I think you can take your 3200MHZ ram and stick a profile that works at 3600MHZ with 1.39v or whatever for your system for example.. That overclock might be optimistic but just an example.

 

So after the May update I may have my 3600Mhz RAM running natively on strap (ever hopeful!) but if I can run them at 3800 or 4000 with manual timings and voltage etc I could then save those directly to the spare (extreme) XMP profile on the DRAM module. This tweaked for your build set of timings would then be selectable in bios so you dont have to re-enter manually. I could do it now for 1.35v  14,14,14,14,34 @3200 but there, are like I say, many other timing data I know nothing about.


Edited by dorbot - 4/26/17 at 11:29pm
post #11852 of 17696
Quote:
Originally Posted by Reikoji View Post

And as @Mumak said, there is likely no fix to it. If they cant fix the software to not corrupt the SPD data it for stupid reason needs to access to control the lights, then its lights out on the idea.
The only way to corrupt SPD data is to use any real-time temperature monitoring software that reads temperatures from SMBus-sensors or to read SPD with cpu-z like programs when the G.SKILL RGB Control application is running on the background. Guys from G.SKILL R&D group have implemented an extremely dangerous idea to control LED via SPD writes. User-type software must not make any changes to SPD. For example, Crucial folks developed a similar scheme to control LED on their Ballistix Tactical Tracer series, but they used SPD Read commands. That's why Crucial scheme is save.
Home PC
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X2 550 BE @3600MHz/1.325V Biostar TA780G M2+ RS780/SB700 Gigabyte ATI Radeon HD6850 GV-R685D5-1GD Kingmax KLED438F-B8MN6 PC2-8500 2x1024MB D9LPK 
Hard DriveOptical DriveOSMonitor
WD10EALS(1TB), WD3200AAJS(320GB), WD2000JS(200GB) Optiarc DVD-RW AD-5200S Windows 7 Professional 32-bit LG Flatron L1753RT 2ms. 
PowerCase
Sagitta RAIDMAX 500W Sagitta RAIDMAX 
  hide details  
Reply
Home PC
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X2 550 BE @3600MHz/1.325V Biostar TA780G M2+ RS780/SB700 Gigabyte ATI Radeon HD6850 GV-R685D5-1GD Kingmax KLED438F-B8MN6 PC2-8500 2x1024MB D9LPK 
Hard DriveOptical DriveOSMonitor
WD10EALS(1TB), WD3200AAJS(320GB), WD2000JS(200GB) Optiarc DVD-RW AD-5200S Windows 7 Professional 32-bit LG Flatron L1753RT 2ms. 
PowerCase
Sagitta RAIDMAX 500W Sagitta RAIDMAX 
  hide details  
Reply
post #11853 of 17696

Here is a comparison between the database SPD data on the left and the data I copied off the 1 remaining working stick I had on the right.

Are all the red boxes in the right hand hex dump corrupted? I wonder how red the duff stick must have been.

There seem to be an awful lot of extra "FF" in the right hand dump. 


Edited by dorbot - 4/27/17 at 12:02am
post #11854 of 17696
Quote:
Originally Posted by hotstocks View Post

Screw it. IBT maximum still shutting it down. I guess I'll wait till next bios that fixes and reports the real cpu temp before further overclocking. This 3 different temperatures is just plain silly.
Do you get a Code 8 error, or do you get a real shutdown?

When you run software like ITB there are dynamic offsets applied when load starts, these usually are +10 or +20 C shooting up straight and then either the real temp catches up or the offset temp gradually lowers a bit.

With Sense Skew disabled my 1800X does a thermal shutdown at Tctl 115 C. It does soft throttling (down to x30) at Tctl 95 C including offsets and hard throttling at Tctl 95 C (x5.5) once the real temp catches up. Once it reaches hard throttling temps Tctl climbs over 95 C (there can be spikes over 95 C before that, but usually they decrease back to 95 C).

CH6 temp is only useful for fan-control. It's either Tctl + 5 C or Socket + 30 C, whatever is lower at a given moment.

Speaking of socket temps: when the socket sensor crawls towards 80 C then you are short of a thermal shutdown. That is, unless you are using Sense Skew which not only will prohibit hard throttling to happen, but will also cause a Code 8 crash before thermal shutdown happens (due to overheating).
post #11855 of 17696
Reporting back after more testing on BIOS 0083.

Hardware:
  • Ryzen R7 1700
  • 2*8GB G.Skill Trident Z RGB F4-3200C16D-GTZR (Hynix Ram)

Overclocking:
  • R7 1700 @ 3.95 GHz with 1.425 V LLC auto (drop to 1.375 under load) or 1.375 LLC 3.
  • Hynix ram @ 3200 (3200 strap), with its rated timings (16-18-18-18-38-2T). 1.4V required (1.35V boots but not stable in windows).
  • ProcODT 60 ohm (helps with boot, doesn't affect stability in windows since it was also stable with 53.3 ohm).

Problems:
  1. Cold boot issues when power cord unplugged or ErP enbabled (due to problem [2]).
  2. Aura leds are always on even when option to enable for S3, S4 and S5 is set to "off"
  3. Because of [2] I have to enable ErP to disable the leds when computer is off, which creates [1]

Cold boot issue details:
First let me state that this doesn't occur when ErP is disabled or if I don't switch off the power supply (everything boots quickly as expected at 3200 with the Hynix ram, even in the morning when the computer is "cold"). Because of the PCH and IO leds not turning off (even if specified in BIOS), I have to enable ErP and this is where troubles start: when booting, the PC ALWAYS goes through ram training no matter the value of ProcODT. However with ProcODT set to 60 ohm it (until now) always trains successfully, whereas with other values it can fail training and I have to re-enter the bios to then boot at 3200.

Hope that helps.
Cheers
Edited by Blumondae - 4/27/17 at 12:14am
post #11856 of 17696
Quote:
Originally Posted by Voodoo Jungle View Post

The only way to corrupt SPD data is to use any real-time temperature monitoring software that reads temperatures from SMBus-sensors or to read SPD with cpu-z like programs when the G.SKILL RGB Control application is running on the background. Guys from G.SKILL R&D group have implemented an extremely dangerous idea to control LED via SPD writes. User-type software must not make any changes to SPD. For example, Crucial folks developed a similar scheme to control LED on their Ballistix Tactical Tracer series, but they used SPD Read commands. That's why Crucial scheme is save.

I don't have Trident Z RGB. Things like that don't appeal to me.

But I am grateful people like Mumak and yourself are about to provide information / SW for "us" to be better in the know. In the past I have donated to Mumak via his site as way of thanks for support, his freeware app is invaluable to me. If I had Trident Z RGB RAM I would have no qualms on purchasing your SW to save myself from hassle of RMA.

But it is also saving G.Skill from providing end user support on the matter, which in essence they should feel the "bite". It's a shame they can't even state what is the issue if someone asks them, case and point this video. Even after mentioning @GSKILL SUPPORT in this linked post there has been no response so far. Considering the cost of these kits real poor showing IMO.
Edited by gupsterg - 4/27/17 at 12:17am
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 #11857 of 17696
Quote:
Originally Posted by Timur Born View Post

Do you get a Code 8 error, or do you get a real shutdown?

When you run software like ITB there are dynamic offsets applied when load starts, these usually are +10 or +20 C shooting up straight and then either the real temp catches up or the offset temp gradually lowers a bit.

With Sense Skew disabled my 1800X does a thermal shutdown at Tctl 115 C. It does soft throttling (down to x30) at Tctl 95 C including offsets and hard throttling at Tctl 95 C (x5.5) once the real temp catches up. Once it reaches hard throttling temps Tctl climbs over 95 C (there can be spikes over 95 C before that, but usually they decrease back to 95 C).

CH6 temp is only useful for fan-control. It's either Tctl + 5 C or Socket + 30 C, whatever is lower at a given moment.

Speaking of socket temps: when the socket sensor crawls towards 80 C then you are short of a thermal shutdown. That is, unless you are using Sense Skew which not only will prohibit hard throttling to happen, but will also cause a Code 8 crash before thermal shutdown happens (due to overheating).

And pretty sure thats how it should be. AMD has said that it will start throttling at 95°C, and the fact that you're seeing it at just that proves the point.
    
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 #11858 of 17696
Quote:
Originally Posted by CeltPC View Post

Can you explain what you mean by tuning an XMP profile for a Ryzen system, and why you would want to do that? Your comment intrigued me.
If you have a personal license for Thaiphoon Burner software you can obtain a free copy of the Business Professional version which allows you to apply changes to XMP profiles made with XMP Enhancer.



It's a very easy to use editor. You can create your own XMP profiles or tune them for your Ryzen system.
Home PC
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X2 550 BE @3600MHz/1.325V Biostar TA780G M2+ RS780/SB700 Gigabyte ATI Radeon HD6850 GV-R685D5-1GD Kingmax KLED438F-B8MN6 PC2-8500 2x1024MB D9LPK 
Hard DriveOptical DriveOSMonitor
WD10EALS(1TB), WD3200AAJS(320GB), WD2000JS(200GB) Optiarc DVD-RW AD-5200S Windows 7 Professional 32-bit LG Flatron L1753RT 2ms. 
PowerCase
Sagitta RAIDMAX 500W Sagitta RAIDMAX 
  hide details  
Reply
Home PC
(13 items)
 
  
CPUMotherboardGraphicsRAM
AMD Phenom II X2 550 BE @3600MHz/1.325V Biostar TA780G M2+ RS780/SB700 Gigabyte ATI Radeon HD6850 GV-R685D5-1GD Kingmax KLED438F-B8MN6 PC2-8500 2x1024MB D9LPK 
Hard DriveOptical DriveOSMonitor
WD10EALS(1TB), WD3200AAJS(320GB), WD2000JS(200GB) Optiarc DVD-RW AD-5200S Windows 7 Professional 32-bit LG Flatron L1753RT 2ms. 
PowerCase
Sagitta RAIDMAX 500W Sagitta RAIDMAX 
  hide details  
Reply
post #11859 of 17696
Quote:
Originally Posted by Reikoji View Post

Also @Timur Born discovered in his IBT stressing that his VDDP voltage for his CPU and Dram overclock to remain stable together had to be set a tad bit higher, still below 1v however.
For my 4.0 GHz + 3300-CL14 overclock I am currently using:

Vcore: Offset +0.075 V, P0 VID 20 (1.35 V)
VddSOC: 0.96 (jumps to 0.96something or maybe 0.97, I cannot look into BIOS atm)
VddDDP: 0.96
PLL: Auto (1.8 V)
DRAM: 1.36 V

The OC runs stable using SOC and DDP 0.95/0.945 V and DRAM 1.35 V, but I ran into troubles with keeping P-state OC settings over a reboot, so I am currently testing which voltage is responsible for that. With the above settings I can even cold boot (power off via PSU).
Edited by Timur Born - 4/27/17 at 12:18am
post #11860 of 17696
I have the supremacy evo cpu block. Read that the Supremacy rubber gasket causes trouble. What should i do? Don't use gaskets?
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread