If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
Just bought a 5600x paired with a B550 Aorus Pro v2.
USB stuttering & Realtek dc's right off the bat.
Disables C-states\pcie 4.0 -> 3.0 and using an external NIC and for now, I'm good.
When will Gigabyte\AMD\both will announce they address this awful situation?
Get newest driver for realtecc 2.5gbit, may help.
But F13a + not enabling low current idle fixed all problems for me
b550 v1 + 5950x here
I used the latest Realtek LAN driver and it did not help. The consensus (after looking on Reddit and forums) is that older, Microsoft-certified drivers (from Windows Update) are the best for stability.
I am currently testing a configuration with the UEFI Network Stack enabled. So far so good, but it has only been 1 day.
Just flashed my B550 Pro AC to F13a with my ryzen9 3900, I don't overclock or even run PBO so nothing exciting. The USB issue was fixed with the earlier BIOS but I notice the core volts now run lower than before. Previously it would run around 1.4 consistently now the average is around 1.2v
F13a 5900x + Aorus B550 Pro AC still getting random reboots without bsod or anything like that. Just boom, black screen, like I pressed reset button, but i didnt.
May it be faulty CPU, guys?
Any reason behind the curve optimizer doesnt go past -30 on the new AGESA BIOS? on the last 1.0.0.0D I had way more margin, I'm stable with -35 on some of my cores with that one and updating to the new BIOS means I lose significant CPU performance (on benches) for instance CPU-Z at -30 struggles hard to reach 13k.
stasio generaly question, goes our feedback (in-)directly to the development team?
i didn't unterstand why f13a would be released, beacause with f12 solved bugs are back in f13a.
F13a 5900x + Aorus B550 Pro AC still getting random reboots without bsod or anything like that. Just boom, black screen, like I pressed reset button, but i didnt.
May it be faulty CPU, guys?
for me it looks like more like psu. cpu or a beta bios could it be too.
for example my system crash also with f13a and flck 1900 and default power-values. f12 runs absolut stable.
stasio generaly question, goes our feedback (in-)directly to the development team?
i didn't unterstand why f13a would be released, beacause with f12 solved bugs are back in f13a.
just a quick question, could somebody what the benefits are of that said AGESA V2 1.2.0.0? did a little research but did not really quite understand what it really means, thx in advance!
Your feedback doesn't go anywhere. Statsio just has access to beta bioses and uploads here. I doubt GB engineers come here to check for any feedback, if they even know this place exists. All your reports are only useful to other members who want to try new BIOSes. You only warn others to try BIOS, or not to try because of bugs. This is all your words do here.
Your feedback doesn't go anywhere. Statsio just has access to beta bioses and uploads here. I doubt GB engineers come here to check for any feedback, if they even know this place exists. All your reports are only useful to other members who want to try new BIOSes. You only warn others to try BIOS, or not to try because of bugs. This is all your words do here.
At one point, were employees of Gigabyte involved in this forum (i.e., active participation)? From the top page: "GIGABYTE needs no introduction but they are here to provide free technical support for their motherboards, graphics cards and other products!".
Comment