Overclock.net - An Overclocking Community - Reply to Topic

Thread: ROG Crosshair VI overclocking thread Reply to Thread
Title:
Message:

Register Now

In order to be able to post messages on the Overclock.net - An Overclocking Community forums, you must first register.
Please enter your desired user name, your email address and other required details in the form below.
User Name:
If you do not want to register, fill this field only and the name will be used as user name for your post.
Password
Please enter a password for your user account. Note that passwords are case-sensitive.
Password:
Confirm Password:
Email Address
Please enter a valid email address for yourself.
Email Address:

Log-in


  Additional Options
Miscellaneous Options

  Topic Review (Newest First)
07-20-2019 07:43 PM
Ne01 OnnA AMD AGESA 1.0.0.3ABA Buggy, Company Pulls it from Motherboard Vendors

The latest version of AGESA ComboAM4 microcode that enables 3rd generation Ryzen support on AMD 400-series chipset motherboards has been deemed buggy and pulled from motherboard vendors.
AGESA ComboAM4 1.0.0.3ABA (not to be confused with 1.0.0.3AB that's being widely distributed), was originally released to fix an application crash noticed with "Destiny 2."
The microcode inadvertantly destabilizes PCI-Express on motherboards, with users of ASUS motherboards complaining of stability issues with the latest BIOS updates that include 1.0.0.3ABA.

Peter "Shamino" Tan from ASUS commented that the company was under a tight schedule to push 1.0.0.3ABA out as BIOS updates, and didn't have the time to properly validate it.
"We just got told to pull (was undergoing validation prior) 1003 ABA version," he said, adding the root cause of the problem being "that PCIE speed of BXB-C downgraded from gen4 to gen2,..."
He comments "so its not surprising that bugs emerge since the source has hidden bugs that only gets unraveled with thorough testing.
combine that with trying to get firmwares out in a tight time frame, kinda damn if you do (release firmware quickly) and damn if you dont (dont release firmware quickly) situation."
It's interesting to note that in their BIOS update change-logs, quite a few motherboard vendors omit the full version string of AGESA.
You may encounter ComboAM4 1.0.0.3AB being referred to simply as "AGESA ComboAM4 1.0.0.3."
07-20-2019 07:00 PM
Targonis
Quote: Originally Posted by shilent View Post
I didn't plan on overclocking until later when we have better BIOS's, but there's one thing I'd like to change.

If I run Prime95 blend, it'll run at 4.2+GHz all core 1.325V around 50-60C (varies a lot with Blend).
If I run Prime95 small FFTs it immediately goes to 3.9GHz 1.2V starts around 66C then creeps up to 71C max.
Cinebench R20 runs at 4.0-4.1GHz.

How can I keep it at 4.2GHz 1.325V for Prime95 small FFTs or any heavy loads?

Total power from my Kill-a-watt:
Prime95 blend = 150W
Prime95 small FFTs = 170W
Idle = 75W

Anyone know what's holding it back? Temp, power draw? I tried increasing CPU current capability in the BIOS to 140%, didn't do anything.

Or is this just the way the 3700X is designed? Is it possible to override this while keeping my 4.4GHz single thread boost speeds?
MY own feeling is that this AGESA 1.0.0.2 is definitely rough, but Asus doesn't want to give us 1.0.0.3ab because that would disable PCIe 4.0. I am keeping my 3900X at stock settings, just using DOCP to get my Hynix M-die 2x16GB 3200CL16 RAM to run at the rated speeds.
07-20-2019 06:53 PM
shilent I didn't plan on overclocking until later when we have better BIOS's, but there's one thing I'd like to change.

If I run Prime95 blend, it'll run at 4.2+GHz all core 1.325V around 50-60C (varies a lot with Blend).
If I run Prime95 small FFTs it immediately goes to 3.9GHz 1.2V starts around 66C then creeps up to 71C max.
Cinebench R20 runs at 4.0-4.1GHz.

How can I keep it at 4.2GHz 1.325V for Prime95 small FFTs or any heavy loads?

Total power from my Kill-a-watt:
Prime95 blend = 150W
Prime95 small FFTs = 170W
Idle = 75W

Anyone know what's holding it back? Temp, power draw? I tried increasing CPU current capability in the BIOS to 140%, didn't do anything.

Or is this just the way the 3700X is designed? Is it possible to override this while keeping my 4.4GHz single thread boost speeds?
07-20-2019 05:57 PM
TheRic89 I think it is Geardown mode being Auto or enabled that only lets CL bet set to an even number. Disable that and enable your DOCP setting and it should set it to 15. Geardown is under the DRAM Timings options I believe.
07-20-2019 05:32 PM
TwoBeers
Quote: Originally Posted by KWSW View Post
So for now till Asus sorts out the bios, should I be using offset or manual for my vcore?

Currently running manual 4.0ghz at 1.1v for my 3800X with almost everything else like LLC on auto. Since it's working fine without much issues so far, I dont really dare to touch anything else.
I'd suggest to just use "auto" Vcore and no manual or offset and no LLC. You will get the best performance out of it without worrying about anything.
07-20-2019 05:29 PM
KWSW So for now till Asus sorts out the bios, should I be using offset or manual for my vcore?

Currently running manual 4.0ghz at 1.1v for my 3800X with almost everything else like LLC on auto. Since it's working fine without much issues so far, I dont really dare to touch anything else.
07-20-2019 03:54 PM
PolRoger 4.4GHz all core with 1.4v BIOS and LLC set ~midway...
07-20-2019 02:17 PM
Takla
Quote: Originally Posted by looncraz View Post
My multi-meter showed that voltage offset was working with the 3900X I was testing and my Crosshair VI Hero... though the software showed a HUGE disparity with the actual voltage supplied to the CPU... it was reading WAY too low. About 80mv too low.

I saw spikes as high as 1.6V using stock voltage, which is a very scary thing. All other voltages were spot on, except during boot failures, when DRAM voltage could be 1.2V instead of 1.4V or could even just drop to under 1.0V (like 990mv, very close to 1V)... this, of course, would cause boot failure. It's very easy to reproduce.

Coupled with my bad memory slot(s), I've set up an RMA. Hopefully the replacement board won't have these issues.
I don't think all the voltage issues of ryzen 3000 are hardware related. Just busted software/bios/microcode what ever you wanna call it.

Quote: Originally Posted by infraredbg View Post
Still waiting for 3900X to be available here, but couldn't resist and bought a 3600 to play until I get the 3900X.
New bios 7102 doesn't seem to be different than the previous one. Still C5 when training fails and have to clear CMOS, still same PBO behaviour I can't seem to figure out. Fan profiles don't seem to work correctly either.
I could get 3600C14 working with 2x16GB B-die - DOCP then rest on auto, just GearDown mode to "Enabled" and Command Rate to 1T set manually.
Hey, atleast your CAS latency isn't stuck at 16...
07-20-2019 02:03 PM
infraredbg Still waiting for 3900X to be available here, but couldn't resist and bought a 3600 to play until I get the 3900X.
New bios 7102 doesn't seem to be different than the previous one. Still C5 when training fails and have to clear CMOS, still same PBO behaviour I can't seem to figure out. Fan profiles don't seem to work correctly either.
I could get 3600C14 working with 2x16GB B-die - DOCP then rest on auto, just GearDown mode to "Enabled" and Command Rate to 1T set manually.
07-20-2019 01:42 PM
looncraz
Quote: Originally Posted by Takla View Post
Ok I'm back from testing voltages offset. And yep, as already said, it is the same as setting a "manual" voltage on the crosshair 6 hero of mine. Always annoying to test things with these beta bios since I once again had to clear cmos to revert to defaults to boot which of course deleted my perfectly set up profile. So yeah, if you use the crosshair 6 hero and a ryzen 3000 cpu, use the manual voltage since offset is broken atm.
My multi-meter showed that voltage offset was working with the 3900X I was testing and my Crosshair VI Hero... though the software showed a HUGE disparity with the actual voltage supplied to the CPU... it was reading WAY too low. About 80mv too low.

I saw spikes as high as 1.6V using stock voltage, which is a very scary thing. All other voltages were spot on, except during boot failures, when DRAM voltage could be 1.2V instead of 1.4V or could even just drop to under 1.0V (like 990mv, very close to 1V)... this, of course, would cause boot failure. It's very easy to reproduce.

Coupled with my bad memory slot(s), I've set up an RMA. Hopefully the replacement board won't have these issues.
This thread has more than 10 replies. Click here to review the whole thread.

Posting Rules  
You may post new threads
You may post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off