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

ROG Crosshair VI overclocking thread - Page 762

post #7611 of 16826
Quote:
Originally Posted by Targonis View Post

Is that with Creators Update for Windows 10? Creators Update caused some headaches for me on my laptop due to the Microsoft Ink garbage and it trying to draw on the screen for some odd reason, and causing some pausing in even stupid "casual" games. I forced the removal of OneNote to see if that would help, and have not run into that problem again on my laptop.

Hey, yes it is with the new "Creators Update" but I did not have any problems yesterday or before the BIOS update. Even thought it could be GPU related for a while, no clue... will try removing OneNote.
post #7612 of 16826
Quote:
Originally Posted by dorbot View Post

Well yes I suppose so. The point is that there are no changes to undo. The board spontaneously decides it wont boot to bios anymore. Its been pretty much stock apart from the odd foray into ram speed changes with Dram & Boot voltage, SOC, that's all.
So I clear the bios, flashback and try my luck getting the damn thing to go. I wish there was a way to reliably get back to a factory state. It seems that the only way to get a factory condition is to replace the board which is clearly an absurd situation. Perhaps a tool in windows even because the bios is just so ass backwards its insane.

I may be suggesting above my grade, but I would suggest trying the newly announced (a few pages back) BIOSes. Other possibilities are damaged board, memory, or CPU (I think attitudes toward ignoring ESD damage are too cavalier, even if the manufacturers try to protect the circuits); even testing the PSU outputs for appropriate voltages could be considered.

There are too many suggestions on this thread for voltage and frequency changes to cover here, but you might try one or more related to other examples of difficult booting.
     
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 #7613 of 16826
Quote:
Originally Posted by finalheaven View Post

@gupsterg

Did the new bios change default Vcore values for you? Or are you using the same +offset values to reach the same Vcore values are the prior bioses?

I did not boot into OS on default, only UEFI and monitoring data looked similar as stock 1002, 1001 and 0902. I did not place DMM on Pro Belt points.

OC was set on 0079 as my usual settings for 1002 1001 0902. With CPU under load from f@h I get same reading on DMM via Pro Belt for all points.

0079 f@h 5hrs (SIO CPU Sensor sync'd to tCTL using Elmor's posted app)





1002 f@h 2.5hrs earlier today



Edited by gupsterg - 4/7/17 at 10:48am
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 #7614 of 16826
Quote:
Originally Posted by pantsoftime View Post

I had a similar problem at one point when I moved the board vertically from a horizontal bench. It was the backplate causing pressure on the socket in a way that the board didn't like. After adjusting the cooler mounting screws I was able to get it stable again. There's something funny about the way mechanical stresses work on this board around the socket. It might be somewhat related to the EK supremacy issues as well (hard to say).

I recommend playing with your cooler a little bit to see if the behavior changes. At one point I could get mine to POST better by pressing against the backplate.

Ok thanks, I'll have a play around with that too. it is an AM3 H110i that just uses the original plastic that comes on the board, no backplate or fanciness. But I'd be surprised if it had any effect making it a bit looser or tighter. But perhaps. Maybe it isn't a dodgy bios ecosystem afterall !
One day it will all be good, lol.
smile.gif
post #7615 of 16826
I tried those settings earlier to no avail. I was having to use 0038 before to get anything above 2666 for some reason, so it seems the 2T BIOS is what I'm stuck with for the time being.
post #7616 of 16826
3200 still no go for me at reasonable volts on 0079 frown.gif

Tried up to 1.4v and just F9 reboot.
post #7617 of 16826
Hello Followed this thread for a while and got a lot of hints thumb.gif

Testing out the 0081 BIOS and playing with ProcODT
anyway to share experience so far
was on 1001 with ram at 2933 cl18 http://valid.x86.fr/ap5ls4

0081 only booted at 2666 at first but setting Procodt to 68,6 allowed me to run 2933 again and 80 allows 3200! unable to get under cl18 but its an improvement. http://valid.x86.fr/6e5xmn

But can anyone explain what this setting does? I am a bit worried as i have no idea what it is doing smile.gif

2x16GB dual sided b-die btw
post #7618 of 16826
Quote:
Originally Posted by elmor View Post

We will have official 1102 soon which is identical to 0081. Next iteration of BIOSes will fix P-state 0 + VID getting stuck at P1.

To change SIO CPU temperature sensor to match Tctl, use this software. Let me know if it helps. sio_tempsrc_t1.zip 550k .zip file


0079 with GSKill FlareX 2x8GB at 3500 with refclk + p-states smile.gif



Better safe than sorry.
No added issues AFAIK.
awesome! gonna wait for 1102 since its going to be coming out soon. thanks elmor for the hard work!
post #7619 of 16826
Quote:
Originally Posted by elmor View Post

Warning: Spoiler! (Click to show)
Got some new BIOS so I'll pull the previous ones (obselete). All new BIOSes has the Voltage offset during recovery bug fixed. Would be very nice to get some feedback on which is working best for you guys in terms of DRAM compability.

Test BIOS 0079

Test BIOS with new AGESA 1004a, with a couple of bugfixes. Up to 5% performance increases in specific applications. Also has P-state overclocking working with BCLK increase. If you want to keep C-states, make sure to set Advanced\AMD CBS\Zen Common Options\Global C-state Control = Enabled. There are two new settings under AMD CBS\UMC Common Options\DDR4 Common Options\ you might want to take a look at, Fail_CNT and ProcODT. Fail_CNT decides how many times to retry when DRAM training fails (F9 -> 0d), default is now 1. ProcODT can help improve your DRAM overclocking. There's a setting available also on previous BIOSes under AMD CBS\UMC Common Options\DRAM Memory Mapping named BankGroupSwap. If you have 2x Single-Rank modules you can try setting this to Disabled and you might see some performance boost in certain applications.

Test BIOS 0081

Same as 0079 but has ProcODT default = 53.3 ohm

Test BIOS 0082

Same as 0081 but with a DRAM compability patch for the below part numbers

CMK16GX4M4A2133C13
AHU08GGB13CGT7G
PV416G240C5QK
F4-2400C15Q-32GRR
TCD44G2400C14BK
F4-2666C16Q2-64GRB
AVD4UZ126661504G
BLT8G4D26AFTA.16FAD
IMA41GU6MFR8N-C F0
MD16GK4D4266615AXR
HX430C15PB2K4/16
HX430C15PBK4/32
AX4U3333W4G16-QGZ
GAM4DBLBM2133D15IE041C
TC48G24S817
SP004GBLFU213N02
78.C1GM3.AF10B
F4-3200C16D-8GVKB

MTA4ATF51264AZ-2G6B1
MTA8ATF1G64AZ-2G3B1
MTA16ATF2G64AZ-2G6B1
HMA41GU7AFR8N-TF T0
HMA451U7AFR8N-TF T0
HMA41GU6AFR8N-UH N0
M378A2K43BB1-CTD
M378A1K43BB1-CRC
M378A1G43EB1-CRC

Test BIOS 0083

Same as 0081 but with "2T" DRAM Mode when using above 2666 DRAM Ratio.

feedback, comparing 1002 with 0083, since I wanted to go for max ram oc:
- pstate oc with non stock ref clock works good, managed to get 123.2 MHz x 32.5 just like 100 MHz x 40.0 with 1.4V (all with llc auto)
- pstate 0 multiplier cant go below 32 with fid 80, so for example 4 GHz with 135 MHz refclock is not possible atm
- offset voltage with pstate oc also worked as expected, now running + 0.325V for 1.4V under load
- ram oc is now stable @ 3600MHz 14-14-14-34 1.5V, where with the old microcode it would only pass memory training every third time and then not really be stable (so I had to run 3200 14-34 with 1002)
- ram training completes with 14-14-14-34 timings and 1.5V at speeds up to 3775MHz

- !!! ram oc over 3650 MHz is not stable at all in windows and causes all kinds of memory errors! I'm getting blue screens with "memory_management", "page_fault_on_nonpage_memory", registry corruption, windows lock screen image changing colors, all kinds of the weirdest data corruption.
what I tried to mitigate this behavior:
- increase ram voltage up to 1.7V
- increase soc voltage up to 1.2V
- increase core voltage up to 1.5V
- set boot voltage up to 1.7V
- disable bankgroupswap
- setting 3700MHz with various memory multipliers and refclocks
- losen ram timings up to 20-20-20-40
- all combinations of the above
nothing worked


tldr 3650 MHz ram clock atm marks the tipping point from awesome performance to total madness and data corruption in windows.


If you have important data on your system, do not use these "testing" bioses and stay on the official version. Dont be mad, if your Windows install just craps the bed.

oh and here is a screenshot of my 24/7 with non-stock ref clock pstate oc, offset vcore and 3600MHz ram (no performance bias): Warning: Spoiler! (Click to show)

Edited by skullbringer - 4/7/17 at 11:04am
post #7620 of 16826
Quote:
Originally Posted by elmor View Post

We will have official 1102 soon which is identical to 0081. Next iteration of BIOSes will fix P-state 0 + VID getting stuck at P1.

To change SIO CPU temperature sensor to match Tctl, use this software. Let me know if it helps. sio_tempsrc_t1.zip 550k .zip file


0079 with GSKill FlareX 2x8GB at 3500 with refclk + p-states smile.gif



Better safe than sorry.
No added issues AFAIK.

Would it be possible for a similar little program to make it match CPU (Tdie) instead?

I'm still not certain which is the more correct reading. Utilizing Pstates with Bclk increases to achieve my initial OC setting finally has CPU(Tdie) reading too low to be correct, and Q-code is 24. But as soon as I make any adjustments to windows Q-code changes to 0C and CPU (Tdie) becomes a believable value again. The temperature difference between the two in idle is around 8c.
New Posts  All Forums:Forum Nav:
  Return Home
  Back to Forum: AMD Motherboards
Overclock.net › Forums › AMD › AMD Motherboards › ROG Crosshair VI overclocking thread