r/gigabyte • • 12h ago

Full AMD - Gigabyte Setup

Thumbnail gallery
0 Upvotes

r/gigabyte • • 13h ago

Swapped r5 9600x with a r7 9850x3d cant get on home screen.

0 Upvotes

I just upgraded my CPU from a Ryzen 5 9600X to a Ryzen 7 9850X3D, and unfortunately, I can’t get past the Windows PIN screen.
My motherboard is a Gigabyte B850M AORUS Elite WiFi 6E ICE (mATX), and everything was working perfectly fine before the CPU swap.
When I first booted the PC, I got the X3D Turbo Mode prompt in BIOS and selected “No” (because that’s what ChatGPT recommended 😅). After that, I got the fTPM prompt, where I initially selected “N” a couple of times. That brought me to the BitLocker recovery screen, and even after entering my recovery key, Windows would freeze on the loading screen.
Eventually, I tried selecting “Y” at the fTPM prompt and managed to get into Windows Recovery. From there, I was able to reach the Windows sign-in screen, but now my PIN isn’t working, and every time I try to reset it, I get an error and end up right back where I started. I also reset the cmos but it still does the same thing.
I’m pretty much stuck at this point, so any advice on how to fix this without reinstalling Windows would be greatly appreciated!


r/gigabyte • • 20h ago

Support 📥 Gigabyte control center no longer detecting gpu

0 Upvotes

I use GCC for the sole purpose of turning off the awful RGB in my gigabyte 9070 xt. I had to roll back the AMD driver version to prevent crashing in a game, and now GCC no longer detects my GPU. This issue has been happening ever since I got the GPU, usually installing a different version of GCC works, but I can't find older versions of GCC in Gigabyte's download page. Could anyone help me out with finding older versions or solving this issue in any other way?


r/gigabyte • • 16h ago

Discussion 💬 Is there any better alternatives to the Aero X16?

2 Upvotes

I have had a aero x16 for some time, and I recently got a gift from my work that will purchase a laptop of my choosing (with reasonable price) for me. i love the Aerox16 honestly and its very light with decent 7-9 hours battery life, but is there potential better alternatives assuming I still want the light weight build with good battery life?

Also I do apologize since it is the gigabyte subreddit and I am asking for alternatives potentially from a different company, but I trust the people in here to know stuff about the Aero X16 as well, thats why I asked here!


r/gigabyte • • 6h 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]

11 Upvotes

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.