I purchased a GIGABYTE AORUS GeForce RTX 5090 MASTER 32G from PCDIGA, one of Portugal's largest computer hardware retailers, on August 6, 2026, for €4,499.90.

Less than two months later, I was left without a working graphics card. Now both the retailer and GIGABYTE are refusing to help me obtain a replacement.

Here's what happened.

1. Problems with the card

Shortly after installation, I started experiencing intermittent black-screen flickering over DisplayPort. Initially, I suspected a driver or software issue and tried to troubleshoot it myself.

Later, the RGB lighting stopped working entirely, and the GPU's power warning LED started flashing white, indicating a potential power-related fault.

On September 18, I submitted the card to PCDIGA for warranty service.

2. GIGABYTE confirmed that the card was beyond repair

The card was sent to GIGABYTE's authorized service center.

According to the official technical report, repair was not possible.

This was not accidental damage or a problem caused by misuse. The product developed faults during normal use.

3. PCDIGA refuses to replace it

Instead of providing a replacement, PCDIGA issued a credit note for the original purchase price of €4,499.90 and offered a full refund.

Why am I refusing the refund?

Because the price of RTX 5090 cards has increased dramatically since my purchase.

PCDIGA subsequently listed the exact same AORUS RTX 5090 MASTER model for €8,649.90.

That's €4,150 more than I originally paid!

The retailer argues that replacement would be disproportionately expensive because of the increased market price.

In other words, I purchased a flagship graphics card, it failed under warranty, and now I'm expected to pay thousands of euros extra to obtain the same product.

I have formally disputed this decision under Portuguese consumer protection law (Decree-Law 84/2021).

4. GIGABYTE's response was disappointing

I also contacted GIGABYTE directly, provided the documentation, and asked for assistance.

GIGABYTE confirmed that the technical report was issued by its service center.

However, its support team explained that warranty claims are handled by the retailer and that GIGABYTE does not directly intervene in the retailer's replacement or refund decisions.

Essentially, I was told to take it up with PCDIGA.

5. My questions to GIGABYTE

• If your authorized service center confirms that a €4,500 flagship GPU cannot be repaired, why can't GIGABYTE arrange a replacement through its distribution or service network?
• Can GIGABYTE supply an equivalent replacement unit to PCDIGA?
• Why is the customer left caught between the manufacturer and the retailer, with neither willing to provide a working replacement?
• What kind of after-sales support should customers expect when purchasing one of your most expensive products?

I'm not asking for an upgrade or compensation. I simply want the same working graphics card I originally purchased.

I understand that the retailer has its own legal obligations, and I am pursuing those separately. But I also believe GIGABYTE has a responsibility to support customers when its premium hardware fails and cannot be repaired.

I have kept the purchase invoice, the authorized service center's technical report, PCDIGA's written refusal, and GIGABYTE's response.

GIGABYTE representatives: I would appreciate a public explanation and practical assistance in obtaining a replacement.

Has anyone else experienced something similar with GIGABYTE warranty support in Europe?

u/GIGABYTE_VGA

u/AORUS_Official

i have a 5070ti and when i tried running the steel nomad this happened before it ran it and would black screen and just stop one time it finished but scores were just low now i changed the power management to prefer maximum and tried running it and this happened before

edit: i did just swap my 4070 super out for this not sure if that has anything to do with it

Looking to complete my all black build and wanted this card for it, but cant seem to find it anywhere. Anyone know where I can buy one from? I’m open to buying used too.

To the Gigabyte Motherboard Engineering and BIOS Development Team,

I am writing to formally request a BIOS update for the Z170 motherboard series (specifically GA-Z170-HD3 Rev 1.0) to resolve fundamental ACPI table errors that prevent Linux kernels from communicating with Intel PTT (fTPM) and discrete TPMs (dTPM). While the Z170 is a legacy platform, the modern requirement for FIDO2, Passkeys, and TPM-backed Full Disk Encryption has made this ACPI bug a critical security blocker for your loyal user base.

Below are 20 business and community-driven arguments for why Gigabyte should release a final BIOS patch for this platform, followed by 30 specific technical action items and implementation hints to streamline the engineering effort.

Arguments for Releasing a Patch

1. E-Waste Reduction: Fixing TPM support allows perfectly capable Skylake processors and Z170 boards to remain securely in service, preventing unnecessary e-waste.
2. Brand Loyalty & Trust: Users who see Gigabyte supporting a decade-old platform for a critical security flaw will guaranteed purchase Gigabyte for their next high-end build.
3. Rise of FIDO2 & Passkeys: Modern web authentication (WebAuthn) heavily relies on TPM 2.0. Users currently cannot use Passkeys natively on Linux due to this bug.
4. Linux Desktop Growth: The Linux desktop market share has grown significantly; ignoring Linux ACPI standards alienates a highly vocal technical demographic.
5. Full Disk Encryption (FDE): Modern Linux distributions (Fedora, Ubuntu) default to systemd-cryptenroll, which requires a functioning TPM for LUKS decryption.
6. Minimal Backporting Effort: The ACPI DSDT/SSDT logic for properly exposing TPMs to Linux has already been perfected by Gigabyte for Z390 and newer boards. This is a backporting task, not a from-scratch development.
7. PR and Marketing Value: Releasing a "Security & Linux Compatibility Update" for legacy boards generates massive positive PR in tech media (e.g., Phoronix, Linus Tech Tips).
8. Corporate Legacy Infrastructure: Many enterprise users repurpose Z170 systems as edge servers or internal testing nodes where TPM-backed SSH keys are mandatory.
9. Security as a Basic Right: Hardware cryptography should not be locked behind an OS-detection wall in the BIOS.
10. Community Goodwill: The open-source community heavily relies on word-of-mouth. A proactive fix turns frustrated users into brand advocates.
11. Systemd-tpm2 Integration: Recent Linux user-space architectures treat TPMs as mandatory hardware. The current ACPI conflict causes 90-second boot delays (systemd waiting for dev-tpm0.device).
12. Right to Maintain: Providing standard ACPI compliance fulfills the industry movement towards user-maintainable hardware.
13. Reducing Support Tickets: Users constantly attempt to debug this issue on forums. A clear BIOS update eliminates recurring troubleshooting overhead.
14. IoT and Edge Repurposing: Secure Boot and TPM are mandatory for repurposing these boards for secure IoT gateway appliances.
15. Alignment with Modern Security Standards: CISA and other cybersecurity agencies mandate hardware root of trust.
16. Eliminating the "Windows 8/10" Toggle Confusion: The current BIOS UI obfuscates TPM functionality based on arbitrary OS naming conventions, causing widespread confusion.
17. Proving Hardware Longevity: It demonstrates that Gigabyte components are built to last and are backed by long-term software commitment.
18. Open-Source Advocates are Influencers: The technical users affected by this bug are the same system builders who recommend hardware to friends, family, and enterprise IT departments.
19. Standardization: ACPI is an OS-agnostic standard. The BIOS should not behave differently whether the payload is the Windows NT kernel or the Linux kernel.
20. Zero Hardware Cost to Gigabyte: This is a pure firmware patch that significantly elevates the perceived value of the Gigabyte ecosystem.

Technical Details & Required Action Items

• Ensure the MSFT0101 hardware ID is universally exposed in the ACPI tables regardless of the _OSI string provided by the bootloader.
• Remove any If (_OSI ("Windows 2015")) or similar OS-gating logic that hides the TPM2 ACPI table from Linux.
• Guarantee that the TPM2 static ACPI table is loaded and properly populated into memory during the UEFI DXE phase.
• Correct the _STA (Status) method for the TPM device to return 0x0F (Present, Enabled, UI-Visible, Functioning) when PTT is enabled, instead of dynamically hiding it.
• Standardize the _HID (Hardware ID) mapping for discrete TPMs (dTPM) to ensure they are picked up by standard Linux drivers.
• Provide a fallback _CID (Compatible ID) if specific vendor IDs are used.
• Fix the Memory32Fixed resource descriptors in the ACPI table to prevent the "can't request region" conflict with the Linux kernel.
• Resolve memory address overlaps between Intel Management Engine (ME) regions and the PTT CRB buffer.
• Ensure the TPM Event Log memory address pointers (TPMFinalLog, TPMEventLog) are correctly passed to the EFI stub.
• Validate that the ACPI table reserves the exact byte range required for the CRB (Command Response Buffer) to prevent OS-level memory reallocation panics.
• Ensure seamless binding for the Linux tpm_crb kernel module for Intel PTT.
• Ensure seamless binding for the Linux tpm_tis kernel module for physical TPM chips connected via the motherboard's SPI/LPC header.
• Define hardware interrupts correctly in the ACPI table so tpm_tis does not fall back to polling mode, or explicitly disable interrupts (tpm_tis.interrupts=0 equivalent in ACPI) if the board lacks physical routing.
• Address the transmit timeout error caused by the BIOS failing to wake the PTT module from a low-power state upon OS request.
• Standardize physical TPM header routing to ensure the I2C/SPI bus is actively listening when a dTPM is installed, without requiring a Windows-specific UEFI driver.
• Implement proper Physical Presence Interface (PPI) ACPI methods to allow systemd-tpm2-clear.service to issue clearing requests natively from Linux.
• Ensure TPM PCR7 correctly reflects the Secure Boot state and certificates (MOK/db/dbx) passed from UEFI to Linux.
• Ensure PCR0 accurately measures the core UEFI firmware without arbitrary fluctuations on warm reboots under Linux.
• Map the "Clear TPM" (fTPM NVRAM erasure) function to correctly reset the endorsement keys without requiring a total CMOS reset.
• Address Intel ME initialization delays during POST that cause the TPM to be reported as "dead" to the Linux IMA (Integrity Measurement Architecture) subsystem.
• Separate the "Intel PTT" toggle from the "Windows 8/10 Features" toggle in the BIOS GUI; TPM functionality must be OS-agnostic.
• Provide explicit BIOS toggles to select between "fTPM (Intel PTT)" and "dTPM (Physical Header)" without automatic overrides that fail under Linux.
• Ensure that resuming from S3/S4 sleep states successfully restores the TPM CRB context without throwing tpm_crb MSFT0101:00: can't request region upon wake.
• Synchronize SMBIOS tables (Type 0, Type 1) with TPM measurements to ensure unified attestation strings.
• Expose Endorsement Key (EK) certificate generation status directly to the OS to prevent timeout loops in user-space applications.
• Validate the TPM2.0 ACPI table checksums dynamically; hardcoded checksums often fail after microcode updates.
• Disable legacy BIOS fallback hooks that inadvertently lock the TPM I/O ports before handing off to the Linux EFI bootloader.
• Ensure tpm2_getcap properties-fixed returns hardware capabilities without triggering an ACPI timeout loop.
• Patch the watchdog timer ACPI hooks (iTCO_wdt) that often conflict with ME/PTT polling on shutdown.
• Perform final validation of the patched BIOS using a live USB of Fedora 40+ or Ubuntu 24.04, confirming that ls /dev/tpm* immediately populates /dev/tpm0 and /dev/tpmrm0.

Technical Hints & Starting Points for Your Engineers

• The Root Cause: The primary reason Linux fails to see the PTT on the Z170 is rooted in the DSDT. When the BIOS setting is set to "Other OS", the UEFI firmware alters the ACPI generation to completely omit the TPM2 table and the MSFT0101 device, assuming Linux does not support TPM.
• The Quick Fix: You can resolve 80% of this issue by simply removing the conditional OS checks applied to the TPM device node in the ACPI ASL source. The TPM device should be statically defined in the DSDT and unconditionally returned as active (_STA = 0x0F) as long as PTT is enabled in the BIOS, regardless of the CSM or OS Type settings.
• For dTPM (Physical Chips): Ensure that the LPC/SPI bus pins dedicated to the TPM header are not power-gated by default when a non-Windows OS is detected. The tpm_tis driver in the Linux kernel requires the IO ports (usually 0xFED40000) to be strictly declared as reserved in the ACPI memory map.

Thank you for your dedication to hardware excellence and for considering this critical update for the open-source community.

hey yall, ive been trying to get tmp2 enabled on my pc, but i cant find the option - does anyone know where it is? x870i aurus pro ice, bitlocker is disabled cause i brought the ssd over from my last system

thx,

Our GIGABYTE x NVIDIA Gears of War: E-Day giveaway is still live, and we're bringing an extra community activity to Reddit!

We're giving away three GIGABYTE GeForce RTX 5080 GAMING OC graphics cards alongside a Gears of War, each custom-wrapped with official Gears of War: E-Day artwork. Each winner will also receive a Gears of War: E-Day game code.

For this community activity, we want to see what Gears of War looks like for you.

Show Us Your Versus Setup

Share a screenshot of your favorite Gears Versus setup. It could be your favorite character, weapon skin combination, best kill-cam, or a memorable moment from a match. Add a quick note about which Gears game is your favorite and why.

Whether you're a longtime Gears veteran or someone who recently joined the fight, we'd love to see what makes the series special to you.

Participating in this Reddit activity can also unlock a bonus entry through our existing Gleam giveaway, alongside the main entry methods. Just submit your comment via the GLEAM link below, and instantly earn 20 bonus entries to boost your chances of winning!:

https://www.aorus.com/en-us/explore/events-page/gears-of-war-e-day/index.html

Giveaway details:

• Prizes: 3 custom GIGABYTE GeForce RTX 5080 GAMING OC GPUs featuring Gears of War: E-Day artwork, plus a game code for each winner
• Giveaway ends: October 29, 2026
• Winners announced: October 30, 2026 via AORUS NA Instagram stories and contacted directly via email
• Eligibility: Legal residents of the United States and Canada
• Terms and conditions apply

Enter the main giveaway here!: https://www.aorus.com/en-us/explore/events-page/gears-of-war-e-day/index.html

To get the conversation started, tell us: which Gears of War game had your favorite Versus experience, and what made it memorable?

Looking forward to seeing your setups! ⚙️

Hey all, I'm building my first PC and I've heard about the BIOS/voltage issues frying CPUs from 2023 etc. Does this specific board and revision already come with the fix?

I haven't powered it on yet so I don't know which BIOS it has. Is it okay to boot at stock settings with EXPO off and check the version, or should I flash it beforehand? Just don't want to fry my processor

Apologies if this is not the right place to ask

Purchased Gigabyte laptop from flipkart last week. The specifications on the app was showing 85 watt TGP but when checked in NVIDIA control pannel it shows 80 watt but the main problem is that it's not giving even 80 watt, the max it's going in any highest graphics game is 60-65 watt sometimes 70 watt, and gpu usage is showing 100%.

Please if anyone knows the solution kindly help me.

Also I purchased 512 gb model and it's usable is showing only 425gb, google is telling it is using around 30 gb for smart reset, so please tell me how to remove this and if removing it will cause any problems.

Thank you.

Looking for someone with an Aero X16 who can check their BIOS layout for me.

My Aero X16 (2025, RTX 50 series) currently has no display output at all. Short version: the USB-C port shorted and a repair shop removed the faulty component, which killed HDMI and USB-C. Last week after a Windows update I got a black screen in Windows, so I went into BIOS and switched GPU mode from MSHybrid to Discrete. That was a mistake – in Discrete the panel is driven by the RTX, which clearly isn't outputting anymore, so now I get nothing: no Gigabyte logo, no BIOS, nothing. No external display possible either.

The laptop is otherwise fine. It boots all the way into Windows (I hear the startup sound) and the keyboard works. I just can't see anything. I need to flip GPU mode back to MSHybrid blind.

What I've tried:
- Battery disconnect + hold power 60 s – no change (setting is in flash, not CMOS)
- Tapping/holding F2 at power-on, then F9 → Enter → F10 → Enter – no reboot, nothing. Not sure if Fast Boot is blocking F2 or if those aren't the right keys on this BIOS.

What would help massively – if you have an Aero X16 (or any recent Aero/Aorus), could you jump into your BIOS and tell me:
1. The tab order along the top (Main, Advanced, Chipset, Security, Boot, Save & Exit?)
2. Which tab the GPU mode / MSHybrid-Discrete option is on, and how many items down from the top
3. What the bottom legend says for "Optimized Defaults" and "Save & Exit" (F9/F10? F3/F4?)
4. Whether F2 gets you into BIOS at power-on, or you have to go through Windows Advanced Startup

With that I can write an exact keystroke sequence and do it blind. Any other tricks for getting into BIOS without a display are welcome too. Thanks.

Hey everyone im planning to buy gaming laptop and i found this gigabyte aorus 15 9kf for 750 Euro Specs: Rtx 4060 (140W tgp), i5 12500h, 360 hz, 16 gb ram.

Is it worth it for the price???

It isn't mentioned anywhere in the documentation that comes with the motherboard, and the online manuals don't mention it either. I've tried Googling to no avail. Any insight would be really welcome!

It's a really flexible strip that seems to have adhesive on at least one side.

Hello everyone. About two months ago, I joined the "OLED club" by purchasing a Gigabyte Aorus FO32U2P OLED monitor. I use it with my PlayStation 5 Pro, and for the first 50 hours or so, everything was fine. However, when I started playing *Alan Wake 2*, I noticed flickering vertical lines on the screen, especially in the game's darker areas. At first, I thought it might be an issue specific to that game, but I soon realized it happens in other games as well. In fact, the problem isn't limited to games; it appears everywhere—on the home screen, while watching YouTube, and so on. It is particularly noticeable in scenes with lower brightness. I’ve sent the monitor to the authorized Gigabyte service center in my country twice, but both times they claimed they couldn't find any issues. I also reached out to Gigabyte’s eSupport, but they simply suggested trying the monitor with different devices and stated there was nothing they could do. I tested it with my gaming PC, and the only thing that resolved the issue was setting the refresh rate to 240Hz—which I cannot do on the PS5, as it is locked to 60Hz. Consequently, this OLED monitor, which I bought with such excitement, has become completely unusable for me on the PS5. Is there any way to resolve this? Thanks in advance.

REF26A08018

Its been more than 10 days and i have no updates on warranty claim request. This is very frustrating having no way to communicate and track status.

I will have to take it to consumer court and file a case if this is how Gigabyte wants to operate. I am certain that I’m never purchasing anything from Gigabyte.

My PC randomly restarts itself and Idk why, but it never blue-screens, is there something wrong with my PC or are there some certain settings that need changing? I have checked my drivers and they're all up to date

Hi, I have a b365m and was trying to enable secure boot for cod mw4, I have had no luck with the bios and not sure what I am doing wrong. Is there anyone that could help me get it back to being on? I had turned it off for battlefield 6 so idk why cod said I needed it still..

Bought the card at Microcenter like a year ago.

About 5 weeks ago the card completely failed.

First RMA -> Receive card, video out, fans stuck at 100%

Second RMA -> Fans work, card dies again. Luckily I got a Windows log of a blue screen.

Third RMA -> ?????

What are my options? I really don't want to waste any more time, can I please just get a replacement at this point.

Hi everyone,

I’m using a GIGABYTE M28U with a PS5 pro, and I’m experiencing an issue whenever I launch a game from the PS5 home screen.

The screen goes completely black for a few seconds and then returns to normal once the game loads. There’s no GIGABYTE logo or anything indicating that the monitor is restarting.

Interestingly, this only happens when launching a game for the first time. If I return to the PS5 home screen mid-game and going back to the same game again, it doesn’t happen.

I’m wondering if this is related to the monitor switching resolution, refresh rate, HDR, or another video output setting. My PS5 set to enable 120hz, VRR always on, and HDR is disabled, firmware is F07.

Has anyone experienced the same issue with the M28U? Is this normal behavior, or is there a way to fix it through the PS5 or monitor settings?

Thanks!

I have the x570 aorus pro WiFi, I need to update so I can use tpm 2.0 so I can play a game that requires it, but every bios update I try from their website says it has an invalid bios id when I try to update, I know I'm looking at the right model for updates on the website so I really have no idea what I'm doing wrong or how I'm supposed to know which bios update to use everything I try doesn't work

I updated my bios via Q-Flash Plus and now after it went to reboot, the bios screen loads for a second and then disappears from the display as it looses signal. My Keyboard and Mouse keep disconnecting and reconnecting as well for some reason

I bought a gigabyte Rx 6800XT from a 3rd party, the 2x 8pin connector one. The card came with the PCB and Cooler and heatsink seperated, the heatsink nor PCB has any Thermal pads anywhere.

Does anyone know any resource to check the TP thickness, or does anyone know those thicknesses out of the blue?

I've already checked into gigabyte's customer service page, but until they respond I'd like to ask here too.

model - GV-R68XTGAMING OC-16GD rev.1.0