Aorus X570 Master

[jesdals]

USB issues - haveing issues during the last week (with both F33j and F33 bios). Getting lag with all the red USB ports and all the black 2.0 ports. Have been without until now but during the last week I have had several experiences of mouse hanging during gameing - newer a plesent experience :-(

 

[Chomiq]

F34 for ELITE, released 3 days ago.

• Checksum: 4B7E

Update AMD AGESA ComboV2 1.2.0.2

Nothing new listed for Master since F33.

 

[Divide Overflow]

More or less same boost behavior as F33j will do some stability testing

You still having USB issues? I haven't noticed any issue with mine, although F33 gives me 250 Mhz less peak boost than F32 on the same curve undervolt settings.

 

[jesdals]

Well I did some changes in bios without effect - but changed my G9x for my spare and it seems to make the difference - have ordered som new mice and will test if the settings does have an effect (e.g. turning of c-states and som settings in the USB menu)

 

[Sadicus]

I have now issue with the ethernet. At start up doesn't detect the cable. I need to put off and put in for fix it....

 

[TheLostSwede]

Looks like F33 brought with it a nice new addition on the Tweaker screen.
No need to go and dig around in the AMD settings any more.

 

[jesdals]

Just uploading this for reference before some bios testing

 

[Guwapo77]

I wish I knew of this page well before F33 came out, thankfully everything is working as intended now. I won't change a thing unless there is a future BIOS that grants me at least 10% performance boost.

 

[jesdals]

New F34 - seems like its just support for Ryzen 5000g cpus

 

[Divide Overflow]

Is that all AGESA ComboV2 1.2.0.3 B changes?

 

[Chomiq]

New F34 - seems like its just support for Ryzen 5000g cpus

F35 on Elite too, same changes.

Edit.
Looks like some folks are reporting that the usb issues they had are gone.
https://www.reddit.com/r/gigabyte/comments/ojy67e

 

[jesdals]

Usually I create a lot of screendumbs wit F12 before upgradeing bios and then send them to my self on a mail - great pain but nice to have them when punching in Memory settings - just realized today that I just could make a Bios Version folder in my One drive and copy the directly as the BMP files they come as to my one drive makeing it much easier

Oh well

But will test F34 for stability with my F33 settings first and then - try raising my Infinity settings from 1900MHz again

Boost behavior during danish summer seems to be the same:

 

[jesdals]

F34 test and stability status - its stable

Been testing settings and going to show my settings below

Still not able to go above 1900MHz Infinity settings witout WHEA´s - been trying BLCK adjust that gives a bit better boost

Not much speciel in the CPU menu - AMD Cool and quiet = on seems to give better PBO performance

Have enabled Powerdown but should not be a problem to dissable

I am using 2 kits of these Patriot memory

Been trying different settings - do recommend changes if any

These settings is stable at 1933/1967MHz as well - but no with 1:1

Under CPU/VRM settings is most basic

Not found much change altering these settings

Under Platform powers

Nothing fancy

Under IO ports Im setting the Above 4G decoding and Re-Size Bar support to match my 6900XT

Under micellaneous settings gen 4 Pcie - but might as well run auto

I am not using the AMD CBS menu options

Settings to Infinity, Mem and PBO by the AMD overclocking menu

Currently running these settings on my cores

All core settings is a good starting point - but do see this https://www.techpowerup.com/forums/threads/amd-curve-optimizer-any-guides-experience.275640/

1900MHz is my max Infinity stable

Mem at 1900MHz
I am using smart fan to control all my fans

A nice average boost

 

[jesdals]

Changed the Curve settings. Negative 30 is apparently the lowest value that can be applied - any thing under negative 24 on core 0 (the first) seems to make the system potiential unstable durring idle periods

PBO settings is still the same

Not much change in CPU-z score

5225MHz is almost as good as my winther test

 

[Horrocko]

Unfortunately, while my system is still perfectly stable overall, none of the recent BIOS/Chipset updates have helped with my USB issues (black USB2 ports being unresponsive). The behavior has changed slightly: if I now plug my mouse into into one of the USB2 ports, the device is recognized by Windows, but the cursor won't move until I plug the mouse back into one of the USB3 ports. Previously (on F31/32), it would sometimes work fully and sometimes not at all, now it's a consistent (but useless) in-between. This applies to all input devices (keyboard, mouse, switches) that I tried on USB2. Bizarrely, storage devices such as thumb drives DO work, though.

I was wondering if any of you guys could point me to a potential alternative solution; otherwise I will have to start looking into PCIe USB adapters to get my ports back, which would be a shame as I bought this board because of the built-in connectivity options.

 

[MxPhenom 216]

Unfortunately, while my system is still perfectly stable overall, none of the recent BIOS/Chipset updates have helped with my USB issues (black USB2 ports being unresponsive). The behavior has changed slightly: if I now plug my mouse into into one of the USB2 ports, the device is recognized by Windows, but the cursor won't move until I plug the mouse back into one of the USB3 ports. Previously (on F31/32), it would sometimes work fully and sometimes not at all, now it's a consistent (but useless) in-between. This applies to all input devices (keyboard, mouse, switches) that I tried on USB2. Bizarrely, storage devices such as thumb drives DO work, though.

I was wondering if any of you guys could point me to a potential alternative solution; otherwise I will have to start looking into PCIe USB adapters to get my ports back, which would be a shame as I bought this board because of the built-in connectivity options.

Im not quite sure what you could do. The USB issues still seem to be a mystery, even for AMD engineers at this point.

Though I have a theory. Go into your device manager and under System devices see if you can find something like 'PCI bus' and if you do open it and check the driver version.; If its 20.50.0.0, try and see if you can roll it back to use the Microsoft driver instead. If you are able too, itll change to 'PCI Express Root Complex' This seems to be a driver only pushed through Windows update for Gigabyte boards and I have a feeling there is something wrong with it and is related to USB issues as theres talk now that USB issues are related to amount of PCIe stuff you are using, etc.

Window's installed it on my system, and it caused a d3 q-code, which is basically a driver software conflict I think. Once I removed it, the q-code cleaned up.

 

[jesdals]

Unfortunately, while my system is still perfectly stable overall, none of the recent BIOS/Chipset updates have helped with my USB issues (black USB2 ports being unresponsive). The behavior has changed slightly: if I now plug my mouse into into one of the USB2 ports, the device is recognized by Windows, but the cursor won't move until I plug the mouse back into one of the USB3 ports. Previously (on F31/32), it would sometimes work fully and sometimes not at all, now it's a consistent (but useless) in-between. This applies to all input devices (keyboard, mouse, switches) that I tried on USB2. Bizarrely, storage devices such as thumb drives DO work, though.

I was wondering if any of you guys could point me to a potential alternative solution; otherwise I will have to start looking into PCIe USB adapters to get my ports back, which would be a shame as I bought this board because of the built-in connectivity options.

You can try to disbale the C-state setting under CPU settings in the tweaker menu

I am using these USB settings

 

[Horrocko]

Im not quite sure what you could do. The USB issues still seem to be a mystery, even for AMD engineers at this point.

Though I have a theory. Go into your device manager and under System devices see if you can find something like 'PCI bus' and if you do open it and check the driver version.; If its 20.50.0.0, try and see if you can roll it back to use the Microsoft driver instead. If you are able too, itll change to 'PCI Express Root Complex' This seems to be a driver only pushed through Windows update for Gigabyte boards and I have a feeling there is something wrong with it and is related to USB issues as theres talk now that USB issues are related to amount of PCIe stuff you are using, etc.

Window's installed it on my system, and it caused a d3 q-code, which is basically a driver software conflict I think. Once I removed it, the q-code cleaned up.

You might be on to something here... as soon as I removed the AMD driver and only left in the base Windows PCI driver, my USB switch immediately started working.

However... on the next restart, my system bluescreened itself to hell and back (I think the error code was Boot Device Not Accessible; I am running an NVME drive as primary boot device). Crashed so hard, even the BIOS automatically reverted to the backup version. It wasn't a big problem in the end; I always expect these kinds of things when messing with drivers and have a secondary clean system drive installed for situations like this. But I had apparently made something inside that box extremely unhappy.

After running a Windows repair on the primary drive to get it back to work, the USB switch is still working now, which is ... surprising. The repair installed the same Pci Bus/20.50.0.0 driver but it doesn't seem to mess with USB devices, for now at least. I'll keep monitoring the situation and update here whether the fix turns out to be permanent (or not).

@jesdals Thanks for your input as well, much appreciated; I had tried those settings based on AMD Support info before but they did not make a difference. Will try them again, though, in case the current fix doesn't hold up over time.

 

[MxPhenom 216]

You might be on to something here... as soon as I removed the AMD driver and only left in the base Windows PCI driver, my USB switch immediately started working.

However... on the next restart, my system bluescreened itself to hell and back (I think the error code was Boot Device Not Accessible; I am running an NVME drive as primary boot device). Crashed so hard, even the BIOS automatically reverted to the backup version. It wasn't a big problem in the end; I always expect these kinds of things when messing with drivers and have a secondary clean system drive installed for situations like this. But I had apparently made something inside that box extremely unhappy.

After running a Windows repair on the primary drive to get it back to work, the USB switch is still working now, which is ... surprising. The repair installed the same Pci Bus/20.50.0.0 driver but it doesn't seem to mess with USB devices, for now at least. I'll keep monitoring the situation and update here whether the fix turns out to be permanent (or not).

@jesdals Thanks for your input as well, much appreciated; I had tried those settings based on AMD Support info before but they did not make a difference. Will try them again, though, in case the current fix doesn't hold up over time.

I didn't have that issue, so that's interesting feedback on your side.

I have a Gen4 nvme as my primary drive too.

EDIT: It might be something worth reporting to Gigabyte/AMD. Not sure if this driver effects other vendors. But Microsoft also needs to pull it from Windows update. Since it seems to install even if you disable the ability for windows to install drivers on its own.

 

[jesdals]

New F35b bios out - will test next week - but say it has better memory compability

 

[Chomiq]

New F35b bios out - will test next week - but say it has better memory compability

Same for Elite except it's F36c.

 

[jesdals]

New F35d bios,

1. Checksum : C44A
2. Update AGESA ComboV2 1.2.0.4 A
3. Windows 11 support

Will test next week

 

[Chomiq]

New F35d bios,

1. Checksum : C44A
2. Update AGESA ComboV2 1.2.0.4 A
3. Windows 11 support

Will test next week

F36d for Eliete

1. Checksum: FEA1
2. Update AGESA ComboV2 1.2.0.4 A
3. Change default status of AMD PSP fTPM to Enabled for addressing basic Windows 11 requirements (https://support.microsoft.com/windows/1fd5a332-360d-4f46-a1e7-ae6b0c90645c)

 

[jesdals]

While still testing F35d a new F35e just came out.

1. Checksum : FCEE
2. Update AGESA ComboV2 1.2.0.4 A
3. Change default status of AMD PSP fTPM to Enabled for addressing basic Windows 11 requirements (https://support.microsoft.com/windows/1fd5a332-360d-4f46-a1e7-ae6b0c90645c)

 

[jesdals]

Been tinkering with F35e - that seems identical with F35d - haveing some minor issues going from games to desktop - that can prompt wheas - settings as previously above - though curve settings at negative 15 set individual on all cores - if whea error can be solved I will give tuning the a go as well.

F35d / F35e give access to windows 11 update - but I am going to wait

With curve settings at negative 15 the boost is a bit lower than earlier bios versions with lower curve settings.

New AMD chipset driver out.

Fun fact enabling AMD cool and quit under the advanced CPU menu gives almost 30 point in the CPU-z benchmark