Originally posted by mgfirewater
View Post
Announcement
Collapse
No announcement yet.
GIGABYTE Latest Beta BIOS
Collapse
This is a sticky topic.
X
X
-
Originally posted by lotharmatheos View Post
Officialy posted F15a has different checksum than F15a from Gigabyte support email to Boing.
AGESA 1.2.0.6b, still with VDDG bug :-(
Yeah the official version was created on 16th February, the version from boing is 2 days olderLast edited by mgfirewater; 02-22-2022, 02:27 PM.
Comment
-
Question to updating chipset Drivers for B550:
at amd page, newest chipset driver is 3.10.08.506, 2021-10-21
On GB Page, there is a newer driver 3.10.22.706, 2022-02-18
Comment
-
Originally posted by ChrisLo84 View PostQuestion to updating chipset Drivers for B550:
at amd page, newest chipset driver is 3.10.08.506, 2021-10-21
On GB Page, there is a newer driver 3.10.22.706, 2022-02-18
3.11
Comment
-
Originally posted by mgfirewater View Post
do you have try this uefi?
performace is better, but the first boot of the day makes yesterday and today some trouble.
yesterday i get an uefi info. ftpm detect an new cpu and blocked the boot (cpu is the same). i didn't use bitlocker so i said yes and the windows try to boot. the load cycle freeze. after reboot everthing is fine. my uefi setting (ram oc and some little chnages wasn't reset.
today win10 will also not boot. after reset. win starts the auto reparation and said the system wasn't correct start.
i inform the esupport.
i believe thats is something with the tpm modul. tpm is active.
Edit: Just realized what was drastically different in F36B as opposed to previous Bios versions. That WORTHLESS default status of AMD PSP fTPM is Enabled. I changed that to Disabled and my problems disappeared. I know guys run Win10 with it Enabled BUT I'm guessing it needs to be Enabled when you install Win10 to start with. Me, I NEVER want to see that !@#$ thing Enabled on MY Win10 machine again.....
Last edited by BagoBones; 02-22-2022, 04:50 PM.
Comment
-
Originally posted by jwsg View Post
fTPM is needed by the W11 checker but there's no need to update BIOS to enable it - its a CPU feature always available but GB have just enabled it by default on the recent BIOS
I have seen threads about stutter with fTPM enabled - I havent seen it and dont undertand the connection because it shouldn't have any performance impact but thats what some people are saying theyre getting
Its natural to blame new BIOS for many issues but often its just that settings are different - and sometimes the process of updating has an effect - I think some device firmware was updated when I updated to F15 on my B550i
Comment
-
You shouldn't have honestly;
Always, always (be it Intel or AMD, high or low end), start with Gigabyte's drivers.
Then (as in on top of it, no uninstalls or manual tweaking/removals, everything 'stock') and only then do you install the latest from the official vendor. Or in your case, chipset drivers.
- This applies for Gigabyte boards, been over a decade since i tried anything else. Even if you haven't had any issue 'till now, i'd tell you hand to heart you've just been lucky.. or, just as possible, you have had issues, just not the skillset/experience to be aware of them.
- Should you have a Radeon GPU, be it discrete or integrated, same thing applies. First download the Gigabyte driver suite, reboot if not automatically forced to, then install latest Adrenaline. Again, on top of the Gigabyte one, no uninstalls, no manual changes.
Fan curves are always reset, along with everything else after a BIOS upgrade.
This isn't a Gigabyte thing, it's everywhere.
Since you ask basic questions, a bit more advise if you don't mind.
The process to safely upgrade a BIOS is only one:
- Go to BIOS, select reset to defaults, save, exit. Will reboot on its own.
- If you have manually set extremely tight timings on your RAM, you'd also need a hard reset in this step, ie removing CMOS batery entirely --and-- waiting for say 10mins before reinstalling it.
- After booting, go straight to BIOS again, don't let it load your OS. Inside the BIOS, do your upgrade. It will reboot again when done.
- After booting, go straight to BIOS again, don't let it load your OS.
- Check if new BIOS version shows correctly. Again select defaults (yes, even though you just upgraded and everything is stock), again save, again exit.
- After booting, go straight to BIOS again, don't let it load your OS. Now you can redo your individual settings.
* Why not let it boot your OS too? Because in select scenarios, your current install with your current BIOS settings could potentially cause issues in the OS if suddenly booted from a stock/new BIOS. As is so, so often the case.
** Never, ever upgrade a BIOS without first resetting it to default(s).Last edited by Aenra; 02-22-2022, 05:37 PM.Pride, honour and purity.
- Likes 1
Comment
-
Originally posted by BagoBones View Post
You're absolutely correct about the Boot and Auto Reparation issues. Upgraded from F35b (ran flawlessly) to F36b (What a pain in the ass). Found out the new F36b doesn't play well with Win10. Had to use System Restore to get my 3900x/X570 Aorus Master machine rockin' again.....
Edit: Just realized what was drastically different in F36B as opposed to previous Bios versions. That WORTHLESS default status of AMD PSP fTPM is Enabled. I changed that to Disabled and my problems disappeared. I know guys run Win10 with it Enabled BUT I'm guessing it needs to be Enabled when you install Win10 to start with. Me, I NEVER want to see that !@#$ thing Enabled on MY Win10 machine again.....
addition: esupport told me the bug has to do something with the profile import. the reason is for me incomprehensible, because the value is the value.Last edited by mgfirewater; 02-23-2022, 07:21 AM.
Comment
-
hi, why it is Could not find any Pinnacle Ridge SMU modules while last version it is 43.24.0 (101 KB) Pinnacle Ridge 2x00 CPU [0019FB00-001B8EF0] , is there anything wrong with the bios file?
-
UPDATE: just checked, it is the same for other GIGABYTE AORUS, and even the same for ASUS PRIME B450-PLUS and ASUS Pro WS X570-ACE
B450 AORUS PRO WIFI (rev. 1.x)
B450 AORUS Elite V2 (rev. 1.x)
X470 AORUS GAMING 7 WIFI-50 (rev. 1.1)
B550 AORUS PRO AX (rev. 1.1) rev. 1.0
X570S AORUS PRO AX (rev. 1.1) rev. 1.0
-
B450 AORUS PRO (rev. 1.0)
F63a 10.73 MB 2022/02/17
Checksum : 18F8
Update AMD AGESA V2 1.2.0.6 B
Reappear the option of Max CPU Boost Clock Override for Vermeer
Ryzen SMU Checker 1.2.0.8
U E F I I N F O
File: B450AOPR.63a
Size: 16,384 KB
Chipset Version/FW: 40.01.80 | FW_3306A | 2019.10.30 | (112 KB)
Chipset Version/FW: 60.01.81 | FW_3306B | 2021.04.14 | (112 KB)
AMD RYZEN 1st and 2nd CPU Generation
25.86.0 (118 KB) Summit Ridge 1x00 CPU [00182200-0019FA60]
Could not find any Pinnacle Ridge SMU modules
30.98.0 (130 KB) Raven Ridge 2x00 APU [0027DF00-0029E550]
30.98.0 ( 17 KB) Raven Ridge 2x00 APU [002B1F00-002B6370]
37.67.0 (139 KB) Raven Ridge 2 30x0 APU [00339D00-0035C910]
37.67.0 ( 27 KB) Raven Ridge 2 30x0 APU [0035CA00-00363600]
4.30.85.0 (140 KB) Picasso 3x00 APU [00363600-00386780]
4.30.85.0 ( 27 KB) Picasso 3x00 APU [00386800-0038D5F0]
AMD RYZEN 3rd and 4th CPU Generation
46.72.0 (110 KB) Matisse (MTS) 3xx0 CPU [004FBE00-00517720]
46.72.0 ( 1 KB) Matisse (MTS) 3xx0 CPU [00517800-00517C20]
46.72.0 ( 52 KB) Matisse (MTS) 3xx0 CPU [00517D00-00524D80]
55.91.0 (132 KB) Renoir (RN) 4xx0 APU [00636600-006575B0]
55.91.0 ( 64 KB) Renoir (RN) 4xx0 APU [00676C00-00686C70]
56.69.0 (130 KB) Vermeer (VMR) 5xx0 CPU [00407C00-00428410]
56.69.0 ( 1 KB) Vermeer (VMR) 5xx0 CPU [00448400-00448820]
56.69.0 ( 58 KB) Vermeer (VMR) 5xx0 CPU [00468E00-00477420]
64.60.0 (132 KB) Cezanne (CZN) 5xx0 APU [007B6600-007D7660]
64.60.0 ( 70 KB) Cezanne (CZN) 5xx0 APU [007F6D00-00808490]
Credits to RaINi, Reous and PatrickSchur
U E F I I N F O
File: B450AOPR.F62
Size: 16,384 KB
Chipset Version/FW: 40.01.80 | FW_3306A | 2019.10.30 | (112 KB)
Chipset Version/FW: 60.01.81 | FW_3306B | 2021.04.14 | (112 KB)
AMD RYZEN 1st and 2nd CPU Generation
25.86.0 (118 KB) Summit Ridge 1x00 CPU [00182200-0019FA60]
43.24.0 (101 KB) Pinnacle Ridge 2x00 CPU [0019FB00-001B8EF0]
30.97.0 (130 KB) Raven Ridge 2x00 APU [0027DF00-0029E550]
30.97.0 ( 17 KB) Raven Ridge 2x00 APU [002B1F00-002B6370]
37.65.0 (139 KB) Raven Ridge 2 30x0 APU [00339D00-0035C8A0]
37.65.0 ( 27 KB) Raven Ridge 2 30x0 APU [0035C900-00363500]
4.30.84.0 (140 KB) Picasso 3x00 APU [00363500-00386650]
4.30.84.0 ( 28 KB) Picasso 3x00 APU [00386700-0038D500]
AMD RYZEN 3rd and 4th CPU Generation
46.72.0 (110 KB) Matisse (MTS) 3xx0 CPU [004F5000-00510920]
46.72.0 ( 1 KB) Matisse (MTS) 3xx0 CPU [00510A00-00510E20]
46.72.0 ( 52 KB) Matisse (MTS) 3xx0 CPU [00510F00-0051DF80]
55.89.0 (132 KB) Renoir (RN) 4xx0 APU [00636600-00657570]
55.89.0 ( 64 KB) Renoir (RN) 4xx0 APU [00676C00-00686C30]
56.65.0 (130 KB) Vermeer (VMR) 5xx0 CPU [003FFC00-00420400]
56.65.0 ( 1 KB) Vermeer (VMR) 5xx0 CPU [00440300-00440720]
56.65.0 ( 58 KB) Vermeer (VMR) 5xx0 CPU [00460E00-0046F420]
64.58.0 (132 KB) Cezanne (CZN) 5xx0 APU [007B6600-007D7600]
64.58.0 ( 70 KB) Cezanne (CZN) 5xx0 APU [007F6C00-00808390]
Credits to RaINi, Reous and PatrickSchur
Comment
-
Originally posted by Aenra View Post
You shouldn't have honestly;
Always, always (be it Intel or AMD, high or low end), start with Gigabyte's drivers.
Then (as in on top of it, no uninstalls or manual tweaking/removals, everything 'stock') and only then do you install the latest from the official vendor. Or in your case, chipset drivers.
- This applies for Gigabyte boards, been over a decade since i tried anything else. Even if you haven't had any issue 'till now, i'd tell you hand to heart you've just been lucky.. or, just as possible, you have had issues, just not the skillset/experience to be aware of them.
- Should you have a Radeon GPU, be it discrete or integrated, same thing applies. First download the Gigabyte driver suite, reboot if not automatically forced to, then install latest Adrenaline. Again, on top of the Gigabyte one, no uninstalls, no manual changes.
Fan curves are always reset, along with everything else after a BIOS upgrade.
This isn't a Gigabyte thing, it's everywhere.
Since you ask basic questions, a bit more advise if you don't mind.
The process to safely upgrade a BIOS is only one:
- Go to BIOS, select reset to defaults, save, exit. Will reboot on its own.
- If you have manually set extremely tight timings on your RAM, you'd also need a hard reset in this step, ie removing CMOS batery entirely --and-- waiting for say 10mins before reinstalling it.
- After booting, go straight to BIOS again, don't let it load your OS. Inside the BIOS, do your upgrade. It will reboot again when done.
- After booting, go straight to BIOS again, don't let it load your OS.
- Check if new BIOS version shows correctly. Again select defaults (yes, even though you just upgraded and everything is stock), again save, again exit.
- After booting, go straight to BIOS again, don't let it load your OS. Now you can redo your individual settings.
* Why not let it boot your OS too? Because in select scenarios, your current install with your current BIOS settings could potentially cause issues in the OS if suddenly booted from a stock/new BIOS. As is so, so often the case.
** Never, ever upgrade a BIOS without first resetting it to default(s).
never had any problems with updating the chipset drivers from AMD.
Is it ok to install now the ones from Gigabyte or is this a problem?
Comment
-
I think that some people don't think that resetting CMOS after every flash is necessary, and they're usually the ones having problems with a new bios. Without resetting CMOS all of the previous bios settings aren't fully erased before the new settings are entered for the new bios, and it can cause a lot of weird problems. As well, some people really don't know how to reset CMOS properly, either...;) x570 Aorus Master, 3900X, flashed from F34 to F35, no problems, and then from F35 to F36b yesterday, no problems. Running Win11 build 22557.1000.
Comment
-
Did someone tried to contact the customer support at gigabyte? How has been your experience? I've contacted them and personally I'm quite shocked, the process lasted more than one week I never got more than one answer per day and for the last one I waited 3/4 days. At the end of the story they denied that the vddg bug even exists, they didn't provide a solution and they never said sorry.
- Likes 1
Comment
Comment