​Hi everyone,

​I wanted to share a frustrating situation regarding the Gigabyte Radeon RX 7900 XTX Gaming OC (24GB) and get some feedback from the community, as well as bring awareness to how Gigabyte is handling support for their flagship Navi 31 GPUs.

​1. The Problem: Driver TDRs & Firmware Desync

​Driver 25.9.1 (Older branch): Flawless stability. Zero crashes, perfect frame pacing, rock-solid in low-latency competitive titles like Warzone.

​Driver 26.x.x (Newer branches, including 26.6.2 / 26.8.1): Constant driver timeouts (TDRs), black screens, and game crashes under heavy low-latency workloads.

​This points directly to a conflict between the aggressive power states / PCIe bus scheduling introduced in recent AMD Adrenalin drivers and the factory VBIOS microcode.

​2. AMD-SN-6023 Advisory & Partner Response

​AMD issued the AMD-SN-6023 notice regarding firmware/security mitigations for the RX 7000 series.

​While partners like Sapphire quickly rolled out updated VBIOS binaries for their 7900 XTX lineup (which community members on Reddit confirmed completely fixed the 26.x.x driver crashes and TDRs across the board), Gigabyte has only updated lower-tier cards (RX 7600, 7700, 7800) on their support page, completely neglecting their top-tier $1,000+ flagship model.

​3. Gigabyte eSupport Response: The "Out of Warranty" Cop-Out

​I submitted a detailed technical ticket to Gigabyte eSupport explaining the TDRs, referencing the AMD-SN-6023 advisory, and asking if an engineering/beta VBIOS was available to align the power delivery handshake with modern drivers.

​Their response was an automated template that:

​Told me to download outdated graphics drivers directly from Gigabyte's product page.

​Stated that because the card is "out of warranty," they cannot help and I should contact a paid local repair shop.

​A VBIOS/firmware update to match an official chipmaker advisory and fix driver compatibility is a software/firmware maintenance issue, not a physical RMA hardware defect. Expecting customers to stay on ancient GPU drivers forever just because the hardware warranty expired is absurd for an enthusiast-grade flagship card.

​4. Questions for the Community:

​Has anyone with a Gigabyte RX 7900 XTX managed to get a newer/beta VBIOS from support by escalating further?

​Are other board partners (ASRock, PowerColor, ASUS) releasing VBIOS updates for 7900 XTX cards, or is Gigabyte the only one dragging its feet on their flagship?

​I have requested a formal Tier-2/Engineering escalation on my ticket. I'll update this post if Gigabyte decides to take technical responsibility.

I’m trying to convince myself to cop a infinity 5070 ti at $1200 but I’ve never bought a gpu above $500, I do love the aesthetic of the infinity and I’m wondering how much different prices would be without the ramnarock.

For example, the msrp of a 5070 ti is $750, if ram prices were normal I would guess the infinity 5070 ti would be +$200. Of course the current price of 5080 at $1800 and 5070 at $950 is too crazy, I feel the 5070 ti is the one that suffers the least from the ram apocalypse.

I currently have a Aorus 3080 xtreme, the jump to a 5070 ti would be nice

Hola como estan? Hace poco tuve un problema el cual no le encuentro solucion hasta el momento. Mi pc funcionaba totalmente bien y al dia siguiente cuando fui a encenderla. No daba imagen ni funcionaba los perifericos.

Probe de casi todo:

RAMs (las cuales estan bien aparentemente).

fuente de poder (la cambie tambien pensando que era eso de una 650w a una de 700w "80 bronce plus las 2 fuentes").

cambiando el procesador y grafica a unas mas antiguas.

receteando la BIOS de manera manual con los pines CMOS.

Dejando la pila descansar un dia mas el receteo de la BIOS nuevamente

Limpiando las ranuras de todo tipo y en general.

Apagando y prendiendo la fuente repetidas veces.

Intentar prenderlo sin cables de reinicio, apagado y LEDs, entre otros.

Los monitores no se si pueden influir pero probe entre uno y otro...

Y las memorias pueden influir?? Lo que recuerdo es que donde tenia el windows, esa memoria mucho espacio ya no tenia.

Pero nada de esto anda. La placa madre / mother. Hace una secuencia de luces pasando por DRAM, VGA y CPU.

Estuve pensando si "murio" mi mother de algun sentido. O se "desconfiguro" la BIOS de alguna menera. Antes de comprar otra me gustaria saber si alguien me podria ayudar con algun dato. Lei muchos problemas similares aca en reddit pero no encuentro la solucion.

Mother: aorus b450 elite (no V2)

Grafica: rx 6700 xt challenger

Procesador: ryzen 5 5600g (los graficos integrados los usaba antes solo hasta que pude tener la grafica, y de tanto tiempo usarlo no hubo problema. Y los monitores estan conectados obvio a la grafica)

Fuente actual: 700w 80 bronze plus

Desde ya muchas gracias por el tiempo en leer y ayudar con lo que sea!

Hi, I’m having a strange XMP/memory training issue with my AM5 system and wanted to see if anyone with the same motherboard has experienced this.

Specs:

Gigabyte B850 AORUS ELITE WIFI7 ICE

Ryzen 5 7600X

Kingston Fury Beast DDR5-5600 CL40, 2×16 GB

BIOS F12d (09/23/2026)

The problem only happens when XMP is enabled.

With XMP Profile 1 at 5600 MT/s, the PC works normally after a shutdown/cold boot. Windows is stable and I haven’t noticed any crashes or other RAM-related problems.

However, if I select Restart from Windows, the PC gets stuck during POST with the red DRAM debug LED and does not boot.

I tested with XMP disabled, and Restart works normally every time. So I’m fairly confident XMP/DDR5 memory training is triggering the issue.

If anyone has fixed this on this exact board, especially while still being able to run XMP at 5600, I’d appreciate knowing which BIOS version/settings worked for you.

Thanks!

I have an AORUS 15 BKF with BIOS version FB14. Does anyone know how to access the hidden/advanced BIOS settings?

I have an AORUS 15 BKF with BIOS version FB14.

Does anyone know how to access the hidden/advanced BIOS settings? I’ve tried several methods and key combinations I found online, including the NVMe menu tricks, but nothing worked.

I really need access to the advanced BIOS settings. Has anyone managed to unlock them on FB14?

If you have picked up the Gigabyte AORUS RTX 5060 Ti AI Box (16GB GDDR7, Blackwell GB206 architecture) and tried plugging it into a Linux host or a tightly managed Windows machine via Thunderbolt, you have likely encountered hard freezes, failed device enumerations, or PCIe bus drops.

Out of the box, this eGPU is exceptionally sensitive to Thunderbolt handshakes, power state transitions, and IOMMU direct memory access (DMA) mappings. Here is the full technical breakdown of the hardware quirks, bugs, and configuration fixes required to make it 100% rock-solid.

Hardware Setup and Motherboard Quirks

• Tested Hosts: Intel NUC11TNHI7 (Tiger Canyon, Core i7-1165G7) and an HP EliteBook laptop.
• Port Selection (Crucial on NUC11 / Tiger Canyon): The NUC11 has two Type-C ports on the rear, but they are not identical. The port directly adjacent to the DC barrel power input is the primary Thunderbolt 4 port wired directly to the CPU root complex. The secondary port operates as Thunderbolt 3. Always connect the eGPU to the primary port beside the power input using a certified 40 Gbps short cable.
• The Cold Boot Handoff Protocol: Do not expect this device to survive dynamic hotplugging or warm operating system reboots. To ensure the host UEFI builds the ACPI DMAR (DMA Remapping) tables and statically allocates the 64-bit BAR windows above 4GB, you must follow a strict cold boot sequence:
  1. Plug in all cables with the host machine powered off.
  2. Switch the AORUS AI Box power on first.
  3. Power on the host computer.

Part 1: Windows 11 Workarounds (High-Security Environments)

If you are running Windows 11 in a high-security enterprise environment with Kernel DMA Protection and Memory Integrity (HVCI) enforced, the eGPU often fails with error codes or gets blocked from memory allocation.

1. BIOS Virtualisation and Memory Prerequisites:
   • Intel VT-d: Enabled (required for hardware memory sandboxing).
   • Kernel DMA Protection: Enabled.
   • Above 4G Decoding / Resizable BAR: Enabled (exposes the required 64-bit PCIe address space).
2. Registry Force for External DMA Remapping: Because standard drivers often fail the external DMA validation check when strict endpoint protection is active, you must explicitly flag the device as trusted:
   • Path: HKLM\SYSTEM\CurrentControlSet\Enum\PCI\[NVIDIA Hardware ID]\[Instance ID]\Device Parameters
   • Value Created: DeviceDmaRemappingSupported
   • Type: DWORD (32-bit)
   • Data: 1
3. Endpoint DMA Policy: Ensure your endpoint security policy is set to block unauthorised DMA only when the workstation is locked, rather than universally suppressing Thunderbolt PCIe tunnelling.

Part 2: Ubuntu 26.04 / Linux Configuration & Bug Fixes

Getting this Blackwell eGPU stable on Linux required resolving four distinct failure modes:

1. BIOS Configuration (NUC11 / Tiger Canyon)

• Fast Boot: Disabled (Mandatory: Fast Boot skips full PCIe bus probing during POST, which prevents the host from mapping the eGPU BAR spaces).
• Intel VT-d: Enabled.
• PCIe ASPM Support: Disabled (prevents the motherboard from attempting aggressive link power savings across the tunnel).
• Thunderbolt Security Level: Set to Legacy Mode (ensures immediate auto-authorisation during POST).
• Allow UEFI 3rd Party Drivers Loaded: Enabled.

2. The Dreaded DMA Freeze (intel_iommu=pt vs iommu=pt)

• Symptom: The eGPU enumerates in nvidia-smi, but the moment you initiate a high-bandwidth memory transfer or CUDA workload (such as streaming tensors over 500 MB), the entire operating system hard-locks instantly with a frozen screen and unresponsive keyboard.
• Root Cause: In modern Linux kernels, setting intel_iommu=pt is an invalid syntax. Checking dmesg revealed: textDMAR: Unknown option - 'pt' iommu: Default domain type: Translated PCI-DMA: Using software bounce buffering for IO (SWIOTLB) Because the driver rejected the option, it defaulted to Translated and routed all external PCIe DMA through Software Bounce Buffering (SWIOTLB). Linux defaults SWIOTLB to an emergency ceiling of only 64 MiB. A multi-hundred megabyte or 1 GiB DMA stream immediately exhausted the bounce buffers, deadlocking the I/O bus and freezing the CPU.
• Fix: Update your Grub command line to use the generic iommu=pt parameter and expand the fallback SWIOTLB pool: Edit /etc/default/grub (or /etc/default/grub.d/99-custom.cfg): bashGRUB_CMDLINE_LINUX_DEFAULT="quiet splash intel_iommu=on iommu=pt swiotlb=262144 pcie_aspm=off pcie_port_pm=off thunderbolt.clx=0 intel_idle.max_cstate=1"
  • intel_iommu=on iommu=pt: Enforces true 1:1 hardware DMA passthrough without bounce buffer bottlenecks.
  • swiotlb=262144: Allocates a 512 MiB fallback reserve (8x larger than default).
  • thunderbolt.clx=0: Replaces the legacy d3cold=0 parameter to disable Thunderbolt low-power sleep states.
  • Run sudo update-grub and sudo update-initramfs -u.

3. PCIe Link Downshifting & Dynamic Power Management Stalls

• Symptom: At idle, nvidia-smi reports the link downshifted to Gen 2 x4 (5 GT/s). When a compute workload starts, the driver attempts to dynamically jump power states (P5 to P0) while renegotiating link speeds across the Thunderbolt retimer, causing unrecoverable PCIe Transaction Layer Packet (TLP) errors.
• Fix: Lock the driver into permanent AC Maximum Performance mode so the link stays locked at full PCIe Gen 4 x4 (16 GT/s): Create /etc/modprobe.d/nvidia-power.conf: textoptions nvidia NVreg_DynamicPowerManagement=0x00 options nvidia NVreg_PreserveVideoMemoryAllocations=1 options nvidia NVreg_TemporaryFilePath=/var options nvidia NVreg_RegistryDwords="RMSetDynamicPowerManagement=0;PowerMizerEnable=0x1;PerfLevelSrc=0x2222;PowerMizerDefaultAC=0x1;"

4. Transient Clamps and CUDA Toolchain Architecture

• Driver Persistence and Clamping: Run these commands at boot (or via systemd service) to prevent transient inrush voltage spikes from resetting the USB4 bridge: bash sudo nvidia-smi -pm 1 sudo nvidia-smi -pl 150 sudo nvidia-smi -lgc 1200,1500 (Note: The minimum VBIOS power limit on this specific AORUS card is 150 W).
• CUDA Target Architecture for Blackwell GB206: If compiling CUDA binaries or frameworks from source, ensure you target native sm_120. Do not target 120a-real (which is restricted to enterprise B200 accelerators), or the runtime will decline to execute kernels on consumer GB206 silicon.

Final Stability Benchmark

Once these adjustments are applied, the connection is rock-solid:

• Host-to-Device Throughput: 2.78 GiB/s (fully saturating the 40 Gbps Thunderbolt4 tunnel payload ceiling).
• Device-to-Host Throughput: 3.18 GiB/s.
• Thermals: 39°C idle, peaking at only 46°C under full compute load.
• Stability: Zero kernel panics, zero bus resets, and reliable sustained inference across the full 16 GB GDDR7 VRAM.

La falla es que prendi el portatil y me sale el error de Secure Boot Violation. No se como solucionarlo, intente instalar una nueva BIOS y tampoco me sale la USB en Q-Flash, esta en el formato como debería, intente borrando con "Delete all Secure boot variables" y tampoco, el OS type solo me deja con UEFI OS e intente desactivando VMD controller y tampoco.

Hey everyone,

I’m repairing a Gigabyte AORUS 15G KB (2020, i7-10875H) with the GA-RX5GKB Rev. 1.0 motherboard.

The GPU fan stopped working. I’ve already replaced the GPU fan with a brand-new fan and confirmed the fan itself is good. The CPU fan works normally.

While troubleshooting the motherboard, I found that a component has been knocked off the motherboard at the location marked CL72 near the GPU fan connector.

I’ve traced the circuit with a multimeter and found that one side of the CL72 footprint is directly connected to the blue wire/pin 2 of the GPU fan connector.

The GPU fan connector readings are:

• Pin 1 / red: ~12 V
• Pin 2 / blue: 0 V
• Pin 3 / black: ground
• Pin 4 / yellow: ~3.86 V

The CPU fan has the same four-wire arrangement, and its blue wire measures around 3.26 V, while the GPU fan blue line remains at 0 V.

AORUS Control Center also shows:

• Fan 1 (GPU): 0 RPM
• Fan 2 (CPU): ~5000 RPM

So I’m trying to determine whether the missing component at CL72 could be responsible for the GPU fan control issue.

What I need help identifying

Does anyone have an AORUS 15G KB / GA-RX5GKB Rev. 1.0 motherboard, schematic, boardview, donor board, or clear photos of this area?

I’m specifically trying to find out:

1. What component is supposed to be installed at CL72?
2. Is it definitely a capacitor, and what is its capacitance/value?
3. What voltage rating/package/type is required?
4. If possible, can someone provide a photo of an intact CL72 from another board?
5. If anyone has the GA-RX5GKB Rev. 1.0 schematic or BoardView, I'd really appreciate knowing what CL72 connects to.

I don't want to install a random capacitor based purely on its physical size, so I'm trying to identify the correct component before repairing it.

Thanks!

(5K rpm was fans maxed)

Greetings! First of all, I'm using a B860M AORUS ELITE WIFI6E ICE mobo. As shown in figure, I was trying to play riot games which needs secure boot. I tried to turn it on but it told me that secure boot was not active:

So I turned to turn off CSM but it isn't in my BIOS options. Can anyone help or share similar solutions? BIOS Ver. F11

Hello everyone, after running GCC on an Aorus 17 XE (2023 - i7 13th Gen) laptop, GCC found some firmware updates as well as a BIOS update (from FB07/F002 to FB12/F004).

All of them were selected. After installation and on next reboot BIOS gives the error on the image attached and won't load Windows. I can confirm that the BIOS update has been completed successfully and current version shown is FB12.

Tried Deleting all Secure Boot variables from BIOS/Security tab, but Laptop again gives the same error on reboot. Tried Loading Optimized Defaults and again same error on reboot.

I cannot find a way to disable Secure Boot completely in the BIOS in order to properly start Windows, so laptop is currently stuck in this Secure Boot Violation bootloop.

Can you please help, as I need the laptop urgently for my work as well?

Will re-installing the BIOS with a flash drive solve this issue? Or flashing the previous version. (I would prefer keeping the newer BIOS.)

I'm thinking to get this psu but noise is a big concern for me when it comes to pc components. Should I get it?

Okay, let’s pretend for a second that there are not “right” sides in the argb vs non-argb argument. Let’s just assume everyone is allowed to have their own preferences and that some people build computers for other people who need lots of rgb and that’s okay. It’s encouraged even. Because there’s nothing wrong with people who need a little color added to their lives and work/game space.

With that in mind, let me start by saying that I’ve tested over 20 AIOs this year and (for the sake of brevity here) they all worked pretty close to the same give or take and degree or two on my 9850x3d cpu, 5090 gpu, Corsair frame 4000 build. The usual temps were around 71-72 degrees cinebench stress testing for half an hour and around 58-64 gaming. Again, some like the Tryx Panorama, the Lian Li GA II Lite, and the Coolermaster Atmos II, Thermalright FW Ultra 360, were on the cooler side at one degree cooler.

The Noctua NL-LC1-36 AIO ran 5 degrees cooler in both scenarios without breaking a sweet or making a racket (whisper quiet the whole time with my fan tuning). That’s impressive to someone like me that has an issue with accepting that something is running cool enough. I’m an idiot that has to chase one degree cooler. Maybe it’s a symptom of boredom, but who cares. The point is, this thing is awesome and everything the reviewers claim it is.

Now, if you hate the Noctua fan look, and are therefore under the assumption that the fan style means this AIO is not for you, you’re wrong. Despite how anyone feels about Noctua fans, I tested a different fan set, the Tryx FOBR 120mm 3 in 1 argb fan, with the AIO and it worked flawlessly. Same whisper quiet noise level, same temps under every circumstance. If you hate rgb, don’t worry about this part of the post. But if you need it, or a client needs it, it’s still an option with what is the very best AIO out there right now for anyone trying to find out if they can make their system run any cooler.

The Tryx fan is the circular one behind the pixelated glass. I’m using the push/intake method on this build because it provided the best thermal results.

Привет всем! Относительно недавно столкнулся с бсодами (трещит звук и уходит в ребут) в играх, ошибка 0x133 из-за Nvlddmkm.sys

. Ситуация начала появляться по прогрессии. Сначала вызывали игры по типо Starcraft 2, HotS, Wow, но не вызали Ведьмак 3, Киберпанк, Тарков причём игры работают отлично на ультра без трассировки. (фпс 60 +). На данный момент и они стали вызывать бсоды. Нормально работают игры такие как герои 3, готика 2, project zomboid.

Ещё важный нюанс, если запусть допустим ведьмак и оставить стоять в Новиграде, то бсода не будет хоть через 10 часов, тоже и в киберпанке.

Теперь идём дальше. Ноут чистый, термопаста поменяна, температуры в норме, дрова ставились и новые и заводские с сайта Гигабайт, чистил старые через DDU, биос обновил до последней версии (номер не помню, но сверялся, винда 11 официальная переустановлена с 0. Стресс тесты Occt спокойно держат по часу, как на проц так и на видеочипы, что 3070 что встройку - ошибок нет. Пробовал лочить фпс на 60, как в играх так и экране. Включал и отключал Hags - бестолку, играл от батареи и от питания - бестолку.

Привет всем! Относительно недавно столкнулся с бсодами (трещит звук и уходит в ребут) в играх, ошибка 0x133 из-за Nvlddmkm.sys

. Ситуация начала появляться по прогрессии. Сначала вызывали игры по типо Starcraft 2, HotS, Wow, но не вызали Ведьмак 3, Киберпанк, Тарков причём игры работают отлично на ультра без трассировки. (фпс 60 +). На данный момент и они стали вызывать бсоды. Нормально работают игры такие как герои 3, готика 2, project zomboid.

Ещё важный нюанс, если запусть допустим ведьмак и оставить стоять в Новиграде, то бсода не будет хоть через 10 часов, тоже и в киберпанке.

Теперь идём дальше. Ноут чистый, термопаста поменяна, температуры в норме, дрова ставились и новые и заводские с сайта Гигабайт, чистил старые через DDU, биос обновил до последней версии (номер не помню, но сверялся, винда 11 официальная переустановлена с 0. Стресс тесты Occt спокойно держат по часу, как на проц так и на видеочипы, что 3070 что встройку - ошибок нет. Пробовал лочить фпс на 60, как в играх так и экране. Включал и отключал Hags - бестолку, играл от батареи и от питания - бестолку.

I can't change the cpu boost

When i change it and open Valorant I don't see any difference and when i open the Aorus control centre again the cpu boost is returned to normal and won't save

Hi, was just wondering if anyone had designed a mount for the 4th fan that you can screw the fan to it? like a metal mount that can be extended into the place where the rubber one goes but has screw mounting to se the fan fully, after having to take my computer apart so many times and rewire the cables into better places this fan can be a rathe annoying pain in the arse.

My first custom loop project is ready 😍

Collaboration with Gigabyte and Alphacool

It turned out pretty nicely, especially considering it was my first time trying this kind of thing 👌🏻

It’s not perfect and there’s definitely room for improvement but I knew that at the beginning, since I chose the hard way right from the start: using hard tubing, no angled fittings, no dedicated pump mount, mATX case, and dual 360mm radiators.

All the tubes were measured by eye and bent freehand 😅

The visible side looks really clean regarding the wiring, thanks to that B850M Aorus Stealth motherboard, though I still had to tuck away a few cables since every block has ARGB LEDs and DDCzero pump in the reservoir.

I have had a build with this motherboard for about a year and a half and have continuously had problems with spontaneous reboots. The odd thing is that after running OCCT and logging out hwinfo for many hours, there seem to be no voltage or temperature problems. Under gaming/other heavy load, computer really runs fine. then I might open an app at idle and computer will reboot.

Reboots are a tad weird because sometimes onboard boot LEDs will quickly oscillate between boot and dram leds with a clicking, which I thought might be the power supply, but I can't tell. That has always resolved itself and then then system will boot. Unsure if this is related. I did have a Team Group set of RAM but swapped to Kingston as a test and the reboots continue. Bios is fully up to date. Kingston memory appears to be compatible.

I have checked all mobo connections, reseated the CPU cooler (not the CPU yet), don't use led connections off the motherboard, all in an attempt to isolate the reboots. Because it's not at load and seemingly random, I'm really at a loss of how to diagnose further. Any ideas or help would be appreciated.

Hi, I'm planning to add second SSD to my build. Aorus x870 is my motherboard. Currently I have SSD in M2A socket. If I understand this diagram correctly adding new SSD in M2B or M2C socket would cut PCI lanes for my GPU in half and putting in M2D slot would make the SSD itself slower.

1st question: Would connecting SSD to M2D also slow down communication with other stuff connected to AMD chipset (like WiFi and USB ports)?
2nd question: How noticable is performance drop of GPU when PCI lanes drop in half, vs performence drop for SSD and possibly WiFi in M2D slot?

Hello everyone, I have just purchased a B850 AORUS ELITE WIFI7 ICE board used for my first pc. I found that it is rev 1.1 Are there any key differences between each of the revisions? Not sure which one we are up to now

Hello everyone,

I'm planning a PC build and I'm torn between the Gigabyte Aorus Master X870E (X3D) and other boards. The main draw of the Aorus Master, as I understand it, is that the secondary SSD slot runs PCIe 5.0 and connects directly to the CPU rather than through the chipset.

I've seen in some reviews that USB4 can be disabled in BIOS. Since the USB4 controller and the secondary M.2 slot share the same PCIe lanes (with a switch in between), would disabling USB4 free up the full PCIe 5.0 x4 bandwidth for that M.2 slot?

Would appreciate any clarity on how the lane-sharing actually works on this board.

Thanks!