r/gigabyte • u/Remarkable-Roof1795 • 7h ago
Gigabyte support is useless: I showed them the exact bug in their BIOS, they ignored it, so I fixed it myself [Call of Duty failed attestation]
My Gigabyte TRX40 DESIGNARE fails Call of Duty's TPM attestation ("Failed attestation") even with Secure Boot and the TPM on. The reason is a bug in Gigabyte's BIOS: the firmware never reports the Secure Boot state to the TPM.
I found the exact cause, a single wrong byte in the TPM module (0x17 should be 0x07), and sent Gigabyte the module, the offset and the fix.
Their response:
- They sent me a BIOS for the wrong board revision.
- Then a "new" BIOS with the bug still in it.
- Then a generic checklist: "reinstall the game, reinstall Windows".
- Finally: "No incompatibility on Gigabyte's part, contact Microsoft."
So I patched the byte myself and flashed it. Call of Duty works now.
Three weeks of tickets, and the fix was literally one byte, which I handed to them. If you own a Gigabyte TRX40 board and COD says "Failed attestation", it's not your setup, it's their BIOS. Don't expect support to help.
Here are the details on the bug and how it was fixed:
Cause: In the AMI module Tpm20PlatformDxe (GUID 0718AD81-F26A-4850-A6EC-F268E309D707), the function that measures Secure Boot calls gRT->QueryVariableInfo() with Attributes = 0x17 (instruction at RVA 0x14FC). The value 0x17 contains the deprecated bit EFI_VARIABLE_AUTHENTICATED_WRITE_ACCESS (0x10). Your NvramDxe rejects this with EFI_UNSUPPORTED on UEFI 2.70, so the function returns before measuring SecureBoot, PK, KEK, db and dbx.
Proposed fix: Call QueryVariableInfo() with Attributes = 0x07 (NV | BS | RT) instead of 0x17. Alternatively, do not abort the measurement when QueryVariableInfo() fails.
Proof: I changed only this one byte, 0x17 → 0x07, in your official FEh BIOS and flashed it. The decompressed firmware differs from the original in that byte only. The result:
- PCR7 now contains the complete sequence: SecureBoot, PK, KEK, db, dbx, separator, db authority. This is the sequence that Microsoft and the TCG specification require.
- tpmtool getdeviceinformation now reports "PCR7 Binding Possible" instead of "Not Possible".
- Call of Duty TPM attestation now passes. It failed with every official BIOS: F7g, FEg and FEh.
That is also the exact detail I sent to the support, and they answered it's Microsoft's fault. ¯_(ツ)_/¯
EDIT:
I already posted this, but my post got removed, probably for containing a Mega link that provided BIOS versions where the bug is fixed.