Originally Posted by Gadfly
How do I uninstall AI Suite? I just get an error telling me that reboot is required, even immediately after a reboot.
Good question, I have no answers. Not tied into the software team.
Originally Posted by SpecChum @elmor
Appreciate it's low priority, but any updates on the new Aura app that will address the lights going completely out on some boards?
My RMA was accepted, in fact my other C6H is here now, but I don't want to swap it over if I don't have to.
How confident are we it's not a hardware issue that would require an RMA anyway?
All I did is update to 1002 and the lights haven't worked since...
We have no leads on this, also this RGB and fan control stuff is really outside my scope. Nothing makes it come back? Clear CMOS? Pull the battery for 30s? Reinstall Aura application? Running calibration etc?
Originally Posted by Mrimstad
I see more People mention fan header issues. And the more i think about it, the more i belive my problem with the aio header to be a aisuit issue rather than bios. I have had No misshapps after removing the software. If it is software related, maybe shoot them guys a heads upp?
Also, educated guess. Do you think we Will ever see support for 3000+MHz dual rank 32GB kits? Guess im blessed with hynix atm..
All I can do is tell them stuff isn't working. Hopefully the May update can get your sticks to 3200 (as long as the sticks are rated for it).
Originally Posted by Dethon
I have just tried the c6h_p0vidfix program and it does not fully work for me. Whenever I execute it, clock goes up to 4GHz (my P0 config), but that's only until an idle period makes it drop to another Pstate. After that it doesn't raise to P0 unless I execute the program again, with the same results.
Something I am doing wrong or have misunderstood?
Seems like a different issue. Which settings exactly? OS?
Originally Posted by y0bailey
What is the "safe" range for ProcODT settings? There isn't any real documentation on it, so I'm hesitant to tweak it without understanding. I've read people putting it in the 80's, but I don't know if that is safe and what that is actually doing?
Any value is safe. ODT = On-die Termination. If you check a few pages back there are a couple of posts detailing what it does.
Originally Posted by icebalm
Yes, from CMOS defaults go into Boot -> CSM. Change ANY of the settings, for example I disable the CSM entirely because I want UEFI only. Then save and reset.
Go back into BIOS and go to Advanced, then go into any of the options, for example go into CPU Options and change SVM Mode, you'll notice it changes for all options on that screen, and more, it changes for all options on all screens in Advanced!
Doesn't do that here, try reflashing the BIOS.
Originally Posted by Zamoldac
Suddenly my board doesn't shutdown properly, it restarts instead. I think i saw this issue here before, can't remember what was the fix
. This is after 2+ weeks of ok operation.
I'm on bios 1002.
Pull the CMOS battery for 30 seconds without standby power.
Originally Posted by 1TM1
0604 reportedly with AGESA update is out for Prime X370-Pro on Asus server (change link manually from 0515 to 0604).
Any ETA for the C6H "unattainable" in Raja's words release (not a test version)? And will 1102 have the microcode or wait till 0079 gets tested?
My best guess would be it goes up on the website this week. Probably we'll be limited to test BIOSes here in the future (internal politics).
Originally Posted by jugs
, can you please clarify this a bit? What does the DRAM ratio have to do with subtimings? Does each ratio set it's own subtimings? What are they?
They're set according to whatever AMD deems appropriate. We will get more control in the May update. For example at the moment:
1866 = tWCL 9
2133 = tWCL 10
2400 = tWCL 11
Originally Posted by LuckyImperial
The amount of RAM mis-information is starting to get a little disheartening.
Nobody has provided the consumers a half decent answer as to why RAM speeds are getting hamstringed so much. The most we have gotten is "AGESA code isn't great." That's it.
What mis-information? The May update will bring lots of additional DRAM options.
Originally Posted by TwoBeers
Hi elmor, want to give you and the guys here my findings.
Some of them I wrote before, but this thread is growing so fast.
My System right now:
- Ryzen 7 1700 @3.8GHz@1.28V(0.12V offset) + Wraith Spire LED (idle on 1.5GHz@0.567V)
- 16GB F4-3200C14D-16GVK 3200@2933 CL14
First, RAM, I have F4-3200C14D-16GVK, which are QVL@3200, but for me they only work at 2933.
I tried 081 and 083 with these settings:
- DOCP 3200 / CL16 / ODT auto / DRAM boot V 1.45V / DRAM V 1.45 -> booted but had 1.48V (that's too high for me)
- ODT 80 or 96 didn't matter, only 1.45V (1.48V) were important
- everything under 1.45V went into safeboot (2133)
- why is my QVL RAM not working?
So, that's the only ASUS issue I have right now.
Just for giggles, some AGESA issue:
- changing p2 FID below 70 (1.4GHz) goes to a QCode "0C", after this no "Clear CMOS" nor "power cycle" works, only reflash via USB flashback! (annoying)
- at BIOS 1001 (with AGESA 1.00x) I could go as low as 1.2GHz
Next, OC findings:
- my max RAM speed is at 3175 with a BCLK of 108.2MHz (with CL14 and 1.35V DRAM V)
- idle powerdraw rises by 10W on this (no Voltage was changed, p0 FID decreased to 8C (3.79GHz))
Before I forget it, thanks a lot for your support here. I learned so much and I'm still excited about this new platform, keep us posted. Kop khun krap
SOC Voltage? The CPU IMC still plays a part.
Originally Posted by 1TM1
Do released versions 0902, 1002 and test versions 0079, 0081, 0083 have menus on core pstates and memory interleaving?