Posts by betam4x
1 - 20 of 19441 Posts
Well at least they keep the previous versions available. FWIW these are super cheap G.Skill RGB sticks with Hynix memory. They costed $140 or so for 32GB. Tempted to pick up another kit to see if 4 will work.
I tried that early on, ended up with a voltage of 1.175V.
There is also the GTZRC which is Hynix (just has RGB).
A couple notes here.
First, you should always “Load Optimized Defaults”, save and exit, flash the BIOS, and then ”Load Optimized Defaults” again when flashing a BIOS for any motherboard on any architecture. Yes it is possible to dirty flash, but it can create problems, some hidden. A particularly nasty scenario is a case where functionality for an item is present, but the UI option is removed. I have had this happen on both AMD and Intel systems. The only way to really fix things at that point is to open up the case and short the pins. On some boards I even had to remove the battery.
Second, Ryzen Master will launch with SVM enabled, however it won’t launch with Hyper-V enabled.
I will be testing this BIOS later tonight. However, I am curious as to what the X590 chipset will bring to the table. I can't think of any way they can improve things, unless it is a reason to release a refresh of high end boards that don't suck.
EDIT: Power Reporting Deviation is better, but still not perfect. It is a tad over 94% for me when Prime95 was running. Previous BIOS revisions were as low as 72% depending on load when CPU voltage was on "Auto".
EDIT #2: Idle voltages are down by a couple hundred mV for me.
EDIT #3: Forget what I said in the previous edit, idle voltage is SIGNIFICANTLY down. I went from 970mV to 800-925 mV. My machine now idles at 80 watts (system power as measured from the wall). Also, apparently whatever improvements they made to fix compatibility with my RAM were reverted in this update, I had to drop down to DDR4-3466 for now. Okay, one last thing: My CPU cores drop as low as 0.2V. I assume this is the new sleep feature.
Okay, now I have to get to work.
EDIT: Power Reporting Deviation is better, but still not perfect. It is a tad over 94% for me when Prime95 was running. Previous BIOS revisions were as low as 72% depending on load when CPU voltage was on "Auto".
EDIT #2: Idle voltages are down by a couple hundred mV for me.
EDIT #3: Forget what I said in the previous edit, idle voltage is SIGNIFICANTLY down. I went from 970mV to 800-925 mV. My machine now idles at 80 watts (system power as measured from the wall). Also, apparently whatever improvements they made to fix compatibility with my RAM were reverted in this update, I had to drop down to DDR4-3466 for now. Okay, one last thing: My CPU cores drop as low as 0.2V. I assume this is the new sleep feature.
Okay, now I have to get to work.
Certain software enables Windows virtualization at boot. This is what kills Ryzen Master. Ryzen master does not care about SVM, nor should it.
In order to disable it completely you have to use bcdedit. Merely removing hyper-v doesn’t disable it.
Probably.
On a related note, I just got done dealing with a bootloop situation where the BIOS kept resetting to defaults. It eventually worked itself out after I flipped the switch on the PSU and then pushed the power button to discharge power from the system. Overall this new BIOS is a step in the right direction, but it has some bugs.
Few percentage points? It drops by less than 1% unless you tend to overclock your bclk (like me). That being said, I was busy today and haven't had a chance to look into whether svm can be disabled or not. I may check it before I go to bed in the next couple of minutes, just trying to fire off a few emails.
No, it's just Gigabyte, as usual. I downgraded to F12, and as others may have passively mentioned, I had odd issues I did not have initially. I did a DMI clear and a CMOS reset. The last time I had this type of issue I was running an MSI board. I decided to update back to the latest release to play with the EDC bug. There have been some behavioral changes on my board. I had to drop the EDC back to 1 to get things to work again.
I updated again to this BIOS. A few things I have noticed:
1) SVM is working fine on my board.
2) The EDC bug operates somewhat differently, but it works fine.
3) The bootloop bug sucks, but once you get things going the new BIOS and AGESA work pretty well (though some BIOS options brick the board requiring a CMOS reset).
1) SVM is working fine on my board.
2) The EDC bug operates somewhat differently, but it works fine.
3) The bootloop bug sucks, but once you get things going the new BIOS and AGESA work pretty well (though some BIOS options brick the board requiring a CMOS reset).
The F20a BIOS on the Gigabyte Aorus Elite Wifi has gimped the EDC bug. While it appears to still happen, curiously there are no performance benefits to be had. Instead, a bunch of power gets dumped into the CPU without cause. I am going to roll back to F12 (again).
Disable SATA and limit PCIE to Gen 3 (and possibly USB to gen 1). You shouldn't get any errors. I was running 103 bclk and got no errors. Pushing it to 104, however, caused problems.Ok i lowered my bclk a little and no more event19 whea error so far...
I was so happy F20a allowed me to run 102 bclk, guess not. I mean, i wasnt getting any bsod, passed my suite of stress tests, but the event19 log bugs my ocd.
I have a G.Skill RGB kit with Hynix DJR as well: F4-3600C16-16GTZRC
I found that by using Ryzen DRAM Calculator, selecting Hynix CJR/DJR, and Choosing the A0/B0 PCB revision, I get timings that work.
If it's DDR4 3600 and the memory is Hynix, try the timings I've attached here.
Attachments
Yay they bricked my system with their bugs.
EDIT: To clarify, I have continued to have serious issues with F20A on my elite wifi so I downgraded to F12. Now the system refuses to boot.
The issue I was having with F20a was that Windows would never properly shut down for some odd reason, forcing me to force power off the system. The system detected it as a memory error for some reason, and would reset the bios settings every single time.
EDIT: Back up and running on F12g (Q-Flash Plus saved the day), which is where I'm staying for now. Here are a list of bugs I've encountered, some of which are also present on F12.
1) The BIOS has a tendency to lock up if a bunch of settings are changed at once.
2) The BIOS is way too quick to reset all your settings if there is a boot issue
3) Changing the BCLK makes the system boot up super slow
4) Some people have had issues with SVM force enabling, though it did not for me
5) For me, Windows does not shut down. It switches to a black screen, but the system stays running. It works fine on F12a.
6) Sometimes BIOS settings reset for no apparent reason?!? This is specific to F20, does not happen on F12.
7) Memory compatibility appears to be worse
8) CSM wonkiness on NVIDIA cards
9) Tendency to favor the Windows Boot manager and interfere with booting other operating systems.
10) USB Reset bug
EDIT: To clarify, I have continued to have serious issues with F20A on my elite wifi so I downgraded to F12. Now the system refuses to boot.
The issue I was having with F20a was that Windows would never properly shut down for some odd reason, forcing me to force power off the system. The system detected it as a memory error for some reason, and would reset the bios settings every single time.
EDIT: Back up and running on F12g (Q-Flash Plus saved the day), which is where I'm staying for now. Here are a list of bugs I've encountered, some of which are also present on F12.
1) The BIOS has a tendency to lock up if a bunch of settings are changed at once.
2) The BIOS is way too quick to reset all your settings if there is a boot issue
3) Changing the BCLK makes the system boot up super slow
4) Some people have had issues with SVM force enabling, though it did not for me
5) For me, Windows does not shut down. It switches to a black screen, but the system stays running. It works fine on F12a.
6) Sometimes BIOS settings reset for no apparent reason?!? This is specific to F20, does not happen on F12.
7) Memory compatibility appears to be worse
8) CSM wonkiness on NVIDIA cards
9) Tendency to favor the Windows Boot manager and interfere with booting other operating systems.
10) USB Reset bug
I am at stock. Thanks.
Actually I have been doing a bit of investigating and I may now know why people are having issues.
EDIT: Prior to flashing the BIOS I tried both the built in qflash as well as efiflash with DMI clear, resetting to bios defaults before and after each tome. I also tried shorting the jumper after killing the power and discharging the system via the power button. Curious, I had interesting issues on F20a, and after downgrading to F12g I continued to have issues. Since the use of Q-flash Plus, however, the system has been working fine.
1 - 20 of 19441 Posts
