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

ROG Crosshair VI overclocking thread - Page 921

post #9201 of 17483
Quote:
Originally Posted by elmor View Post

One more day added to the counter smile.gif (For those who keep count it's at +2 right now, you guys are doing better than I thought)

Tricky this one since he not asked for May update biggrin.gif

Btw Bumping my VDDP to 0.96 stabilized my system where no other setting did. Spend whole evenign yesterday and managed to get it down to use Pstate OC and LLC2 so got same load volts as on llc3. Idle higher before pc drops the clock but that does not matter. Now only gotta wait for fix of P02 setting someday hehe
post #9202 of 17483
I'm getting a bunch of the WHEA-Logger ID 19 entries, but I'm not overclocked. The only change I've made was upping the SoC voltage to 1.125 when I was having black screen issues during the first few days after putting the build together.

Is it possible that it's the ram volts being too low as I'm still running this Trident Z at 2133Mhz while I wait for a newer bios? (running 0902 atm)

Thanks
post #9203 of 17483
What is the best multiplier to use on memory with the latest bios, getting my mobo/cpu/ram next week and went with 3600CL16 G.Skill Samsung b-die memory. Should i just run 32x and OC with BCLK?
Main Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 - 3.810GHz - 1.286v Asus Crosshair VI Hero MSI 1080 Ti Gaming X - 1.000mv 2012/6210 G.Skill Trident Z 16GB 3600Mhz CL16 RGB 
Hard DriveHard DriveOSMonitor
850 evo 120GB (for OS + programs) 850 evo 250GB (for Games) Windows 10 LG 27ea73LM-P 
KeyboardPowerCaseMouse
Razer BlackWidow Ultimate 2013 Corsair RM750x Corsair Obsidian 750D Razer DeathAdder 2013 
Mouse PadAudioAudioAudio
Razer Goliathus Razer Kraken Pro Sennheiser HD 598 Sound Blaster Z  
  hide details  
Reply
Main Rig
(16 items)
 
  
CPUMotherboardGraphicsRAM
AMD Ryzen 1700 - 3.810GHz - 1.286v Asus Crosshair VI Hero MSI 1080 Ti Gaming X - 1.000mv 2012/6210 G.Skill Trident Z 16GB 3600Mhz CL16 RGB 
Hard DriveHard DriveOSMonitor
850 evo 120GB (for OS + programs) 850 evo 250GB (for Games) Windows 10 LG 27ea73LM-P 
KeyboardPowerCaseMouse
Razer BlackWidow Ultimate 2013 Corsair RM750x Corsair Obsidian 750D Razer DeathAdder 2013 
Mouse PadAudioAudioAudio
Razer Goliathus Razer Kraken Pro Sennheiser HD 598 Sound Blaster Z  
  hide details  
Reply
post #9204 of 17483
Quote:
Originally Posted by CeltPC View Post

I am using a 4 GHz P-state overclock, no LLC, The issue I am having is that now although I can see the the various core clocks fluctuating, some at minimum, some at 4 GHz, etc, even with minimal demand going on if only one or two cores are above minimum, I see maximum core voltage being used. Light system demand triggers all eight core frequencies to go to 4GHz.

This basically negates one of the prime rationales for using P-states. How can I get P-states to be less "aggressive" in the threshold to kick into full bore, and how do I get less voltage to be used when the system is basically loafing while using a browser, etc.?

Is this the reason for all the P-states, to be able to make transitions to be more gradual?

Is this impossible to do anyway, sense apparently that mean being able to set up P-state VID for each state, which I guess does not function yet?

Right now I have only the 0 P-state set, all others are left to auto.


UPDATE: I went into Task Manager, while leaving HWiNFO64 open, to look at what might be running in the background to push CPU usage and trip the threshold for the high P-state and volts. I saw that Asus Aura (which was not even "open" at the time, was a process eating 5% to 6% of CPU. I killed the process using end task, and bam, volts dropped to minimum with a browser, HWiNFO64, and Kodi all open.



To verify, I intended to open Aura again, but it crashed immediately. Despite uninstalling and cleaning the registry with CCleaner, then manually deleting anything left under aura folders and files, rebooting, re-installing, etc. - it still crashes right away!

So progress on one issue and now a new problem to tackle.. rolleyes.gif
Edited by CeltPC - 4/14/17 at 1:50am
post #9205 of 17483
Quote:
Originally Posted by Blumondae View Post

Of course, there is nothing too exotic though:

- cpu multi 39.5
- cpu voltage 1.375
- LLC 3 (will try to lower it after what I saw on this topic yesterday, but it's not easy since with LLC auto I need more than 1.425v to get it stable)
- 3200 ram multi
- timings 16-18-18-18-38
- Ram voltage and ram boot voltage 1.4v

Anything else on auto/default with bios 0083.

Note that after trying to bump the bclk I had also a problem: even when back to 100 my ram was rebooting at 2133, I had to clear cmos. Also yesterday back from work I noticed that the computer booted twice, it probably had to train ram again. But everything stable while gaming and benching at 3200.

Thanks for sharing this! I was able to successfully boot with your settings. However like before, any load placed on the system and it just black screens instantly. In fact, I just had this page open and it crashed while replying to you frown.gif

Mine would go into a few F9 loops and then boot up again with your exact settings like nothing happened but will crash again eventually. This is progress as before it would simply revert to 2133 when the system locked up. I do have fail_cnt set to 5. Does anybody have any idea why it's not reverting the settings and also have any idea where I can go from here to potentially get this working?

Thanks again!
post #9206 of 17483
Quote:
Originally Posted by CeltPC View Post

Warning: Spoiler! (Click to show)
Good Information and good work, gup, all your effort is appreciated.

No worries smile.gif .

I didn't study the benches last night, just did them and posted. Will do a graph of data, also be interesting to compare MemTweakIt timings between straps. We know from Elmor's guide lower straps have some improved timings, hoping to do a 3.8GHz / 3200MHz profile with lower strap but upped BCLK to see how that improves over 3200MHz strap + 100MHz BCLK.
Quote:
Originally Posted by hotstocks View Post

Warning: Spoiler! (Click to show)
This platform is goofy as hell. I will try and report back over the weekend when I get max stable ram and cpu overclocks, but I started 2 weeks ago with a 1700 on 1002 bios and never changed the bios. I also have 8X2 G.Skill Tridentz 3600 C16 B-die. I just got an 1800x and this is looking bad and weird.

Results:
1700 Memory ran completely fine at 104,108,109,110, 117 BCLKs up to 3430mhz ddr 16-16-16-16-36 perfectly stable. But REFUSED to run at 3200mhz no matter what I tried!
1800x Memory will ONLY run at 3200mhz. ANY BCLK overclocking at all makes memory drop down to like 2126mhz and Cas 15, WTH? I changed NOTHING BUT THE CPU. The cpu is what is dictating what your memory will run at. I can't believe this, but if true I will have to decide between a 3.9ghz 1700 with 3430 memory or a 1800x with 3200 memory but hopefully 4 or 4.1 ghz, will take some testing. This is all incredible odd and I might flash to bios 81 to see if my memory will go any higher than 3200 like it did before.
Or is there something I am missing, like after I swapped the cpus I have to set something in the bios or do something to retrain the memory? Usually all I had to do was his reset 3 or 4 times on a faild 0d and then it would just retrain and go back to the 3430mhz I was running at 100% stable.

P.S. If it matters, the 1700 is Malaysia and the new 1800X is China

Do you have IHS stamp info? cheers smile.gif .
Quote:
Originally Posted by elmor View Post

Warning: Spoiler! (Click to show)
Your DRAM fails to train from cold boot and causes AMD CBS settings to reset, including P-states. BIOS is not aware of failed DRAM training and has all other settings still intact, meaning you get default voltage + your specified offset. Not sure what we can do about that at this point. Future updates might help with the cold boot issue and maybe a reliable way to detect DRAM training failures. It's also possible to have a fixed P-states. An alternative at this point would be an OS application which applies your P-state settings (FID/VID).

+rep for above and CPU socket thermistor location, will add that and the mobo temp sensor location in OP of my thread wink.gif .

Thank you for your time smile.gif , I agree RAM training was most probable cause of borked boot.

1st setup

As an update, last night I CMOSCLR > set up base profile which has no OC/manual voltages > base with manual voltages (except CPU default UEFI) with 3200MHz 14-14-14-14-34 = borked boot again redface.gif .

2nd setup

So did CMOSCLR again, loaded base profile, then applied only manual voltages (except CPU default UEFI), then 3200MHz 14-14-14-14-34, then applied 3.8GHz Pstate 0 / Offset +162mV.

Now I may be barking up wrong tree, but may help someone.

I reckon in 1st instance of setup above, underlined process, due to VBOOT being set with other voltages = powerdown/up to apply sent 3200MHz training iffy. In 2nd setup I did manual voltages on their own so when went for 3200MHz C14 there was no powerdown/up of mobo.
Quote:
Originally Posted by finalheaven View Post

Warning: Spoiler! (Click to show)
@gupsterg

Raise your SOC volts. It fixed my cold boot up issues. I never had trouble rebooting, but cold boots were a problem until I raised my SOC.

Yeah, I reckon I will go 0.968V or 0.975V. I saw when I used 3.8GHz / lower strap + 134MHz BCLK = 3200MHz C14 1T I needed 0.975V SOC to get into OS, not yet stability tested. So 0.975V using 3200MHz strap + 100MHz should have increased "stability" vs 0.962V I use currently.

+rep for share chap smile.gif
Edited by gupsterg - 4/14/17 at 2:04am
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 #9207 of 17483
Quote:
Originally Posted by Merboe View Post

Warning: Spoiler! (Click to show)
0081:


0082:

Both are the same.
In BIOS itself the Hardware monitor CPU temp (right side) starts at 60°C while the left side (monitor tab) starts at 70°C, then they fluctuate both back & forth. Hardware monitor side is slower but catches up eventually between 52 - 62°C.

So it's still there...
Do you know where those two sensors are?

tCTL is 20 sensors within die. Highest value is shown and some rotating goes on which sensor is shown as tCTL. Thread in my sig, section Temp info in OP has info I've collated.
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 #9208 of 17483
I understand what the Sense MI T_offset does (default: 63), but what does the Sense MI Offset do (default: 272)?
post #9209 of 17483
Quote:
Originally Posted by Merboe View Post

and the socket is higher than tctl.
Watching it over a longer period of time, it jumps just the same as the tctl, but it's 5°C higher.
Are you using an old version of HWinfo?
post #9210 of 17483
Using Statuscore's stresstest on different CPU cores:


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