Originally posted by h3x1e
View Post
Announcement
Collapse
No announcement yet.
GIGABYTE Latest Beta BIOS
Collapse
This is a sticky topic.
X
X
-
stasio Is there any explanation on why using an AGESA 1.2.0.0 BIOS, my 5800x seem to be capped at 5025mhz boost, no matter the settings?
I've talked with a bunch of friends, with different CPUs and they all seem to have a lower capped max boost than with any 1.1.0.0 BIOS (also, they're all on Gigabyte motherboards).
Is it something Gigabyte decided? was it AMD?
Any clue?
I would assume that's how they made 5000 series more 'stable', but it seems such a lazy solution and i really hope it's not meant to stay like this in the final version...
Comment
-
Originally posted by wisebear View Poststasio Is there any explanation on why using an AGESA 1.2.0.0 BIOS, my 5800x seem to be capped at 5025mhz boost, no matter the settings?
I've talked with a bunch of friends, with different CPUs and they all seem to have a lower capped max boost than with any 1.1.0.0 BIOS (also, they're all on Gigabyte motherboards).
Is it something Gigabyte decided? was it AMD?
Any clue?
I would assume that's how they made 5000 series more 'stable', but it seems such a lazy solution and i really hope it's not meant to stay like this in the final version...
Comment
-
To be honest .. i wish to Gigabyte move the whole team doing z390 bios to fix x570 BIOS issues :)
The thing is over a year ago z390 BIOS was sorted in like 3-4 weeks?
To compare :
z390 XMP works flawless - you set XMP and BIOS set all timing AND voltage according to RAM spd - x570 ... timings in XMP are a lottery, the voltage you have set manually
z390 CPU voltages on auto - fine - x570 way to high and every reset changes
the list of examples is long,, but just to give a clue :)
Comment
-
Originally posted by F3RHAT View PostSorry
X570 Aorus Elite / Bios F33a / 2x8GB 3200MHz memory DRAM voltage 1,35
Gives higher voltage than specified to memories ! Bios settings 1,35V
in reality 1,368 !
- Likes 1
Comment
-
Jason_Cruze
I know that, but that's not what i'm asking.
Besides, on 1.1.0.0 i was at 5050mhz with 150 PBO override...
This is something different and seem to be hard capped, regardless of how much you set PBO override at.
In the meanwhile, a friend has confirmed me it's not a specific Gigabyte issue, since he has the same exact behavior on his ASUS MB.
Comment
-
Originally posted by stasio View Post
96 - Assign PCI device resources.
AMD early stage Agesa 1.2.0.0 make some difficulties with SATA mode on M.2 (known bug,but not always).
I only have M2 discs on my x570 Master .... *sigh*
Comment
-
Originally posted by Rock3t View Post
I had exactly the same issue. After i lost connection , i could not go to 192.168.1.1 router menu even through a wifi device. Unplug/plug lan cable restored my router. Reply please if it helps you.
- Likes 1
Comment
-
Originally posted by wisebear View PostJason_Cruze
I know that, but that's not what i'm asking.
Besides, on 1.1.0.0 i was at 5050mhz with 150 PBO override...
This is something different and seem to be hard capped, regardless of how much you set PBO override at.
In the meanwhile, a friend has confirmed me it's not a specific Gigabyte issue, since he has the same exact behavior on his ASUS MB.
I'm still running F30 just fine, my computer is now 2 + months old and i have it overclocked,i get WHEA errors in eventlog but the machine has been running none stop doing hard work for 2 months and not yet once has it shown any sign of instability, so those WHEA errors are most likely driver bugs (in my base) then anything else. They do not affect the computer for me at all. I have decided not to upgrade my bioses or play around anymore, i realize with my build i am quiet lucky to be able to run the spec i am running (16-17-17-31 4x16tb at flck 3900)
Comment
-
Originally posted by AMD718 View Post
I've posted about this extensively on reddit. I had similar issues with my Aorus B550 Master. What's impacting the whole network is an ARP broadcast loop. Happy to report that my RTL8125 has been rock solid for the past few months after making changes referenced in here. Bottom line - Latest RTL8125 driver from Realtek site + disable power management in device settings + disable power settings in driver advanced settings + make sure you are UEFI-booting with no CSM + enable "network stack" / UEFI for Realtek NIC (you don't have to actually have it attempt network boot though). Good luck.
2. Disabled the Intel Intel Wi-Fi 6 AX200 adapter, as I'm not using WiFi
I sold my AX200 few weeks ago. It could be one of the things that caused a problem
- Likes 1
Comment
-
Originally posted by cder2 View Post
Yeah this is the "solution" everyone was waiting for. turns out many of the chips chipped from factory could not perform to their hard set spec so they tuned everything down in order to stabilize the bad batches. the result is anyone who had a stable overclock/build pre AGESA 1.2 is essentially downgrading by updating their bioses.
I'm still running F30 just fine, my computer is now 2 + months old and i have it overclocked,i get WHEA errors in eventlog but the machine has been running none stop doing hard work for 2 months and not yet once has it shown any sign of instability, so those WHEA errors are most likely driver bugs (in my base) then anything else. They do not affect the computer for me at all. I have decided not to upgrade my bioses or play around anymore, i realize with my build i am quiet lucky to be able to run the spec i am running (16-17-17-31 4x16tb at flck 3900)
Having IF at 1966 stable is nice and all, but provides zero tangible improvement compared to my old 1867 on 1.1.0.0 (1ns less latency, pretty much...) while seeing SC performance going down noticeably (MC is pretty much the same) kinda pisses me off.
However, It would be nice to have an official (or in this case, an 'insider') comment on the matter... there's always a (tiny?) chance that it's an unwanted behavior on a beta release...
(believeTM)
Comment
Comment