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

ROG Crosshair VI overclocking thread - Page 963

post #9621 of 17534
Quote:
Originally Posted by malitze View Post

Well ideally you would want to renew the paste each time you remove the cooler for ideal operation. But for "debugging" purposes I'd say it's fine.

Ok so I redid the thermal paste and reseated the CPU now I'm stuck on boot LED Code 0d which according to the Guide is "F9(→0d)
DRAM Training failed. Note that 0d is also displayed during final POST before boot"

Yes even after a manual reboot
Edited by Karpata - 4/16/17 at 9:39am
post #9622 of 17534
Quote:
Originally Posted by nycgtr View Post

Just wanna report that with the Ryzen balanced profile and 0082. If my display goes to sleep I get code 08. Doesn't happen on 1002 or if I swap to high performance.

Thats a bit weird, maybe pcie power management needs to be changed? Link state power management, i always turn that to off so give it a shot might be conflicting, a bit odd that your pc going to sleep causes an 8 code and crash.
Quote:
Originally Posted by gupsterg View Post

@benus74

I have just finished full Win 10 Pro clean install on 3.8/3200 OC, I will share what goes on regarding PowerPlan/downclocking wink.gif . Perhaps another will share as well wink.gif .

@all

Code 8 is like a universal Q-Code for instability / borked rig. Linked this post before from Elmor on HWBot.

Yesterday I did some 4.0GHz subs to HWBot, rig fine all day, revert to 3.8/3200 profile as usual fine for rest of evening. 3x today PC just went q-code 8 whilst downloading Win 10 Creators edition ISO frown.gif .

I reflashed UEFI and all seems fine now, I believe sometimes something is retained in UEFI from "tinkering", so if known good settings go Q-Code 8 it maybe best to just reflash and start with clean slate.

Not saying my answer or experience is right, just sharing in case it help someone.

@bluej511

Sweet thumb.gif , nice to read you've got 3200MHz for sure smile.gif .

Yea its beautiful. Soc made all the difference, i need to up it a bit more and about to try it now since it needs one reset loop to boot so ill give just a hair more soc and see what happens.
    
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 #9623 of 17534
I've just experienced my first fright with my little poor ryzen eek.gif

I was back to my 3.9Ghz using PState 0 at +0.19875v, and then decided it was time to play with memory... so I went back to BIOS I go for the DOCP profile 5: 3200Mhz.
I set memory voltage to 1.35v as specified by my kit, and save and reset...

I was really thinking, c'mon this a new bios 0083 and my good ryzen is going to be good guy today wink.gif

But that's not how it wanted to play it.

The next boot failed 3 time in a row, and on the 3rd time went into the bios.
Then I've seen Core Voltage at 1.55V, and I've quickly plugged DMM to see it was going up to 1.573V !!!
I've checked the CPU Core voltage settings, and I could see it on auto but with CPU Core Voltage Offset of 0.2000v.

I've changed it back to 0.19875v (what I've configured previously), and then save and exit (keeping the DMM plugged to make sure it wouldn't go crazy with volts?).

System rebooted and went with a 54 error code with volts at 1.18v on DMM

I've rebooted the system again (keep power button pressed for 10sec, and then turn on again) and system started and shown message: "Overclocking failed".

I went back into BIOS and all settings look like default, so I though that ok, I can just reboot.

So I've rebooted keeping DMM on, and then seen the VCore going at 1.547v again eek.gif

Shutdown computer -> pressed clear CMOS -> restarted -> all back to normal, and now I'll play with memory only, going one step at a time wink.gif

Lesson learned, always keep DMM plugged in after changing BIOS settings thumb.gif
Ryzen ROG'ks
(15 items)
 
  
CPUMotherboardGraphicsGraphics
AMD Ryzen 1700 Asus ROG Crosshair VI Hero AMD Vega MSI GeForce GTX 1060 GAMING X 6G 
RAMHard DriveCoolingOS
G.Skill F4-3600C16Q-32GTZR samsung 960 PRO 1TB Noctua NH-D15 SE-AM4 Ubuntu 17.04 
OSMonitorKeyboardPower
Windows 10 LG 38UC99 WF Corsair K95 Platinium RGB Silver Switch EVGA T2 850W 
CaseMouseMouse Pad
ENTHOO EVOLV ATX GLASS (Galaxy Silver) Razer Mamba Razer Firefly 
  hide details  
Reply
Ryzen ROG'ks
(15 items)
 
  
CPUMotherboardGraphicsGraphics
AMD Ryzen 1700 Asus ROG Crosshair VI Hero AMD Vega MSI GeForce GTX 1060 GAMING X 6G 
RAMHard DriveCoolingOS
G.Skill F4-3600C16Q-32GTZR samsung 960 PRO 1TB Noctua NH-D15 SE-AM4 Ubuntu 17.04 
OSMonitorKeyboardPower
Windows 10 LG 38UC99 WF Corsair K95 Platinium RGB Silver Switch EVGA T2 850W 
CaseMouseMouse Pad
ENTHOO EVOLV ATX GLASS (Galaxy Silver) Razer Mamba Razer Firefly 
  hide details  
Reply
post #9624 of 17534
Quote:
Originally Posted by gupsterg View Post

@benus74

I have just finished full Win 10 Pro clean install on 3.8/3200 OC, I will share what goes on regarding PowerPlan/downclocking wink.gif . Perhaps another will share as well wink.gif .

Thanks @gupsterg, I'll be happy to know your findings.
Ryzen ROG'ks
(15 items)
 
  
CPUMotherboardGraphicsGraphics
AMD Ryzen 1700 Asus ROG Crosshair VI Hero AMD Vega MSI GeForce GTX 1060 GAMING X 6G 
RAMHard DriveCoolingOS
G.Skill F4-3600C16Q-32GTZR samsung 960 PRO 1TB Noctua NH-D15 SE-AM4 Ubuntu 17.04 
OSMonitorKeyboardPower
Windows 10 LG 38UC99 WF Corsair K95 Platinium RGB Silver Switch EVGA T2 850W 
CaseMouseMouse Pad
ENTHOO EVOLV ATX GLASS (Galaxy Silver) Razer Mamba Razer Firefly 
  hide details  
Reply
Ryzen ROG'ks
(15 items)
 
  
CPUMotherboardGraphicsGraphics
AMD Ryzen 1700 Asus ROG Crosshair VI Hero AMD Vega MSI GeForce GTX 1060 GAMING X 6G 
RAMHard DriveCoolingOS
G.Skill F4-3600C16Q-32GTZR samsung 960 PRO 1TB Noctua NH-D15 SE-AM4 Ubuntu 17.04 
OSMonitorKeyboardPower
Windows 10 LG 38UC99 WF Corsair K95 Platinium RGB Silver Switch EVGA T2 850W 
CaseMouseMouse Pad
ENTHOO EVOLV ATX GLASS (Galaxy Silver) Razer Mamba Razer Firefly 
  hide details  
Reply
post #9625 of 17534
Quote:
Originally Posted by bluej511 View Post

Thats a bit weird, maybe pcie power management needs to be changed? Link state power management, i always turn that to off so give it a shot might be conflicting, a bit odd that your pc going to sleep causes an 8 code and crash.
Yea its beautiful. Soc made all the difference, i need to up it a bit more and about to try it now since it needs one reset loop to boot so ill give just a hair more soc and see what happens.

Yea it's weird and tbh with a better bios down the pipe in may, I really don't even want to investigate lol.
post #9626 of 17534
Quote:
Originally Posted by Benus74 View Post

I've just experienced my first fright with my little poor ryzen eek.gif

I was back to my 3.9Ghz using PState 0 at +0.19875v, and then decided it was time to play with memory... so I went back to BIOS I go for the DOCP profile 5: 3200Mhz.
I set memory voltage to 1.35v as specified by my kit, and save and reset...

I was really thinking, c'mon this a new bios 0083 and my good ryzen is going to be good guy today wink.gif

But that's not how it wanted to play it.

The next boot failed 3 time in a row, and on the 3rd time went into the bios.
Then I've seen Core Voltage at 1.55V, and I've quickly plugged DMM to see it was going up to 1.573V !!!
I've checked the CPU Core voltage settings, and I could see it on auto but with CPU Core Voltage Offset of 0.2000v.

I've changed it back to 0.19875v (what I've configured previously), and then save and exit (keeping the DMM plugged to make sure it wouldn't go crazy with volts?).

System rebooted and went with a 54 error code with volts at 1.18v on DMM

I've rebooted the system again (keep power button pressed for 10sec, and then turn on again) and system started and shown message: "Overclocking failed".

I went back into BIOS and all settings look like default, so I though that ok, I can just reboot.

So I've rebooted keeping DMM on, and then seen the VCore going at 1.547v again eek.gif

Shutdown computer -> pressed clear CMOS -> restarted -> all back to normal, and now I'll play with memory only, going one step at a time wink.gif

Lesson learned, always keep DMM plugged in after changing BIOS settings thumb.gif

Heres my trick, i change small settings to what i KNOW will boot and have no issues (boot setup, LED config, small changes etc) then save it to profile 1 and name it test. Go back and make more small changes then save again. Once i got a decent amount of stuff done, ill clear cmos and load up the profile. Then ill change offset and mess with memory then save a couple profiles then load it up.

Clearing CMOS is a life saver lol.
    
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 #9627 of 17534
@benus74

Known issue frown.gif .

When RAM training fails and AMD CBS resets with Extreme Tweaker having offset value you end up at crazy voltage frown.gif .

I've had it 3x, SpecChum, Ubardog and others had it more times than me and earlier occurrences in ownership than me.

This is how I know it will happen for sure, power PC > mobo boot > weird chirp straight away from speaker > mobo power down > 3x boot loop > enter UEFI = ~1.5V frown.gif .

Normal boot is power PC > Q-codes happen 1x > clean beep from speaker > enter UEFI all is well.

If it has "borked boot" I switch power off on PSU at bold/undelined stage, press CMOSCLR on rear IO and then restart rig. Then use my saved profiles to get back. I have a base profile with no OC but say fans, onboard devices, etc. Then load next profile base + manual voltages on extreme tweaker except CPU = [auto], then after reboot I load base+voltages+3200MHz, then after reboot 3.8/3200MHz profile.
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 #9628 of 17534
Quote:
Originally Posted by malitze View Post

Code 8 is "CPU not operational", so the problem is CPU related.

I also get code 8's if the memory is unstable.... Fyi
post #9629 of 17534
Quote:
Originally Posted by bluej511 View Post

Heres my trick, i change small settings to what i KNOW will boot and have no issues (boot setup, LED config, small changes etc) then save it to profile 1 and name it test. Go back and make more small changes then save again. Once i got a decent amount of stuff done, ill clear cmos and load up the profile. Then ill change offset and mess with memory then save a couple profiles then load it up.

Clearing CMOS is a life saver lol.

Thanks for the good advice, I'll do it now in fact, this way it'll detect my fan etc.

+rep for the trick wink.gif
Ryzen ROG'ks
(15 items)
 
  
CPUMotherboardGraphicsGraphics
AMD Ryzen 1700 Asus ROG Crosshair VI Hero AMD Vega MSI GeForce GTX 1060 GAMING X 6G 
RAMHard DriveCoolingOS
G.Skill F4-3600C16Q-32GTZR samsung 960 PRO 1TB Noctua NH-D15 SE-AM4 Ubuntu 17.04 
OSMonitorKeyboardPower
Windows 10 LG 38UC99 WF Corsair K95 Platinium RGB Silver Switch EVGA T2 850W 
CaseMouseMouse Pad
ENTHOO EVOLV ATX GLASS (Galaxy Silver) Razer Mamba Razer Firefly 
  hide details  
Reply
Ryzen ROG'ks
(15 items)
 
  
CPUMotherboardGraphicsGraphics
AMD Ryzen 1700 Asus ROG Crosshair VI Hero AMD Vega MSI GeForce GTX 1060 GAMING X 6G 
RAMHard DriveCoolingOS
G.Skill F4-3600C16Q-32GTZR samsung 960 PRO 1TB Noctua NH-D15 SE-AM4 Ubuntu 17.04 
OSMonitorKeyboardPower
Windows 10 LG 38UC99 WF Corsair K95 Platinium RGB Silver Switch EVGA T2 850W 
CaseMouseMouse Pad
ENTHOO EVOLV ATX GLASS (Galaxy Silver) Razer Mamba Razer Firefly 
  hide details  
Reply
post #9630 of 17534
Quote:
Originally Posted by Gadfly View Post

I also get code 8's if the memory is unstable.... Fyi

Yeah well it's where the problem manifests in the end smile.gif
Quote:
Originally Posted by Karpata View Post

Ok so I redid the thermal paste and reseated the CPU now I'm stuck on boot LED Code 0d which according to the Guide is "F9(→0d)
DRAM Training failed. Note that 0d is also displayed during final POST before boot"

Yes even after a manual reboot

Have you already made any memory related changes in BIOS? Have you tried reflashing? Maybe to one of the latest versions here like 0081? What memory configuration are you using?
main
(10 items)
 
  
Reply
main
(10 items)
 
  
Reply
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread