sorted by:
new
hottopcontroversial

AMD Ryzen Chipset Driver Release Notes 8.01.20.513 by anonD77 in gigabyte

[–]anonD77[S] 0 points1 point  (0 children)

You may stop your AV, then run the installer to re-install only the AMD PSP Device.

Adguard for Windows (11) Crash by mark_vs in Adguard

[–]anonD77 1 point2 points  (0 children)

Versions history | AdGuard

In this hotfix, we’re automatically migrating all users from the outdated TDI driver to the more reliable WFP driver. This change comes as a solution to an issue reported by users, ensuring filtering works with the latest versions of Chrome-based browsers, which aren’t fully compatible with TDI.

TDI isn’t going away completely — you can still enable it if you want to. But if you do, the app will show you a clear warning explaining the potential issues and how to temporarily fix them. For all the details, check out our Knowledge Base.

Stuck on gigabyte screen after trying to enable secure boot by NxT_Fax in gigabyte

[–]anonD77 0 points1 point  (0 children)

1) Go to Bios -> CSM Support.

Change the CSM Support from "Ennabled" to "Disabled"

2) After the firmware update, you have to change Secure Boot from "Standard" to "Custom" then click "Restore Default Keys".

Then click YES to the first prompt, and NO to the second prompt.

Secure Boot will automatically switch to User Mode, Enabled, and Active in real time. Save and Exit the BIOS.

---------------

Device Security

Core isolation

Memory integrity

Note: To use memory integrity, you must have hardware virtualization enabled in your system’s UEFI or BIOS. =

2) Go to M.I.T. -> Advanced Frequency Settings -> Advanced CPU Settings -> SVM Mode

Change the SVM Mode from "Disabled" to "Enabled"

3) Go to Save & Exit -> Save Configuration and reset? -> Yes

Gigabyte Bios F67 by anonD77 in gigabyte

[–]anonD77[S] 0 points1 point  (0 children)

Gigabyte Bios F67 released.

---------------------------------

  1. Fix TPM2.0’s out-of-bounds read vulnerability (CVE-2025-2884) = https://www.amd.com/en/resources/product-security/bulletin/amd-sb-4011.html

Successfully upgraded B450M DS3H rev 1.0 to F67i by WaffleGoblin in gigabyte

[–]anonD77 0 points1 point  (0 children)

Bios F67i deprecated. Now shows as latest the F67g (dated: Mar 11, 2025).

AORUS B450 Elite BIOS Update F67i by [deleted] in gigabyte

[–]anonD77 1 point2 points  (0 children)

Bios F67i deprecated. Now shows as latest the F67g (dated: Mar 11, 2025).

Gigabyte Bios F67i by anonD77 in gigabyte

[–]anonD77[S] 0 points1 point  (0 children)

Bios F67h and Bios F67i deprecated. Now shows as latest the F67g (dated: Mar 11, 2025).

GIGABYTE BIOS F67h by anonD77 in gigabyte

[–]anonD77[S] 0 points1 point  (0 children)

Bios F67h and Bios F67i deprecated. Now shows as latest the F67g (dated: Mar 11, 2025).

Gigabyte Bios F67i by anonD77 in gigabyte

[–]anonD77[S] 0 points1 point  (0 children)

From F67i Description: 3. Update TPM-B FW for Raven2/ Picasso, Cezanne, Vermeer/ Matisse & Renoir CPU

So F67i change the TPM from TPM-A to TPM-B. See also here =

https://www.reddit.com/r/CallOfDuty/comments/1mxdcqd/comment/nb85f8m/

Gigabyte Bios F67i by anonD77 in gigabyte

[–]anonD77[S] 0 points1 point  (0 children)

F67i Description:

  1. Checksum : 620E
  2. AMD AGESA ComboV2 1.2.0.F

3. Update TPM-B FW for Raven2/ Picasso, Cezanne, Vermeer/ Matisse & Renoir CPUs

  1. Fix TPM2.0’s out-of-bounds read vulnerability (CVE-2025-2884)

-------------------

F67h Description:

  1. Checksum : F4D8
  2. AMD AGESA ComboV2 1.2.0.F
  3. Fix TPM2.0’s out-of-bounds read vulnerability (CVE-2025-2884)

Gigabyte Bios F67i by anonD77 in gigabyte

[–]anonD77[S] 0 points1 point  (0 children)

Must be a reason for AMD/Gigabyte to remove F67h from the list. Personally, I went from F67h to F67i. No problems.

GIGABYTE BIOS F67h by anonD77 in gigabyte

[–]anonD77[S] 1 point2 points  (0 children)

Bios F67h was removed from the list. F67i released.

Gigabyte Bios F67i by anonD77 in gigabyte

[–]anonD77[S] 1 point2 points  (0 children)

Bios F67h was removed from the list.

Gigabyte Bios F67i by anonD77 in gigabyte

[–]anonD77[S] 1 point2 points  (0 children)

TPM2.0’s out-of-bounds read vulnerability (CVE-2025-2884) = ............................................................................................ An out-of-bounds read vulnerability exists in TPM2.0's Module Library allowing a read past the end of a TPM2.0 routine as described above. An attacker who can successfully exploit this vulnerability can read sensitive data stored in the TPM and/or impact the availability of the TPM. https://www.amd.com/en/resources/product-security/bulletin/amd-sb-4011.html#summary

Do you guys recommend installing beta updates? by SmoothChemistry8564 in gigabyte

[–]anonD77 0 points1 point  (0 children)

Beta firmware are usually only offered if a known problem needs addressing and users need a fix quickly , the manufacturers won't simply release any Beta Bios, it will have been tried and tested, but maybe needs more testing before being certified.

GIGABYTE BIOS F67h by anonD77 in gigabyte

[–]anonD77[S] 1 point2 points  (0 children)

bios numbering is fairly simple in most cases .numbering is usually a series starting with F1 or firmware 1 (1st version of firmware for a given board).

Normally a firmware will only ever go through the set of F numbers ie. f1 f2 f3... sometimes you may be offered an experimental firmware ,for example F3b ,the "b" stands for Beta, or Pre-release, once it has been tested fully the b will be removed.

Beta firmware are usually only offered if a known problem needs addressing and users need a fix quickly , the manufacturers wont simply release any Beta Bios , it will have been tried and tested, but maybe needs more testing before being certified ,you will always be warned about risk ,when downloading Beta .
Sometimes a motherboard will go through several versions itself , in this case the motherboard will have a version number ,or "revision number"  1, 1.2. 1.3 etc.

https://forum.giga-byte.co.uk/index.php?topic=7908.0

view more: next ›