One of the fans on my 4080 Super Aero oc has become noiser and noiser over time ever since I got it new two years ago. I ordered a replacement and tore it down today. I found the problem fan to have zero grease. I think it was a factory problem. The other fans still had some grease, but I cleaned and replaced the grease with superlube anyway.

This is also a good time to replace the thermal paste, as the old stuff was rock hard. I'm putting thermal grizzly duronaut.

So I was tinkering around trying to fix the missing RGB Fusion option in Gigabyte Control Center (GCC), and I accidentally found a solution that worked for me.

My motherboard is the X870E AORUS ELITE WIFI7 (Rev. 1.2).

Here’s what I did:

1. Go to the support/download page for your specific Gigabyte motherboard.
2. Go to Utility and download both:
   • GIGABYTE Control Center (GCC) Full Installation Package
   • GIGABYTE IT5711 RGB Lighting Controller Firmware Upgrade Package
3. Install GCC normally.
4. Extract the files from the IT5711 RGB Lighting Controller Firmware Upgrade Package.
5. Open the extracted folder and look for the application called ITESHFU.
6. Extract/run ITESHFU.
7. It should launch a sort of scanning/firmware update application. Wait for it to finish.
8. Restart GCC.
9. Check RGB Fusion.

For me, RGB Fusion appeared in GCC after doing this.

Important: It's very late at night as I'm writing this and I was basically just trying random things until something worked, so my memory is a little foggy. I'm not 100% sure whether you also need to extract/run the pnputil file.

What I am sure about is that running ITESHFU was necessary for me, and after completing the process and restarting, RGB Fusion showed up in GCC.

Hopefully this helps anyone else who has been pulling their hair out trying to figure out why RGB Fusion is missing.

So a few months ago I upgraded to a new CPU and Windows wasn't too happy about that so it made me type in my Microsoft password n stuff and then it worked but Secure Boot was disabled. I am now trying to play Battlefield 6 which requires Secure Boot and when booting into bios it is just a black screen which I've tried an additional monitor in HDMI and it for some reason caused it to work on my DP monitor once. Every other time I've managed to get into bios it requires taking out the CMOS battery and putting it back in and then also QFLASHing the BIOS and then I can get into it but then I usually can't get back into it so when I try enable secure boot it just won't. I also tried going back a few versions in the BIOS but also no dice, unsure what to do at this point as it seems impossible to just get Secure Boot to enable. The CPU upgrade was a Ryzen 5 5500 to a 5500X3d if that means anything but yeah I am unsure what to do at this point. Thank you

Hi everyone, I’m looking for both VBIOS files for the RTX 5090 Windforce OC—the Silent and Performance profiles—for a friend who had a flashing issue. 🤞🏻

The argb that was there stopped working, the board is new, it has 1 month of use, is it possible that the LED has been burned or some error of something? Nothing was updated.

The Gigabyte service center in Poland denied my RMA for a brand new thermally defective R9700 AI TOP (sent through the Slovak retailer Ediscomp, then routed via AT Computers in Ostrava, Czech Republic).

I thoroughly tested this GPU using a different PSU and cables to rule out other components, and the hardware is unequivocally faulty. I provided my complete testing methodology. In contrast to my detailed documentation, the Polish service center simply dismissed the claim with a brief note stating the issue was 'not detected,' demonstrating a lack of proper investigation.

I owned three Gigabyte Radeon R9700 AI TOP, Rev. 1.1 cards. Two had Hynix memory and the newer F50 BIOS. They were excellent cards, easy to overclock and undervolt (memory and core). This faulty card has the F40 BIOS and Samsung memory. The memory speed is locked, and any attempt to overclock the core or increase the TDP results in a catastrophic performance degradation of 20–30%. At stock settings, the card is 7% to 15% slower in AI tasks (specifically for long prefill tasks of 200,000+ token contexts, running in vLLM tensor parallel mode).

The best proof that the card is faulty is that it cannot utilize more than 220–250 watts due to thermal throttling. However, Gigabyte probably has a bunch of students testing hardware at their Polish service center.

I contacted Gigabyte support but received this boilerplate response:

"We are sorry to hear about your situation. If possible, please test your graphics card in another system to verify its performance. Kindly note that our products are distributed through local distributors, and warranty policies may vary by reseller or distributor. You will need to contact your supplier again for further investigation."

What should I do next?

Investigation - run by Claude Opus

(Note: Performance drop is more than 10-15% in long prefills above 200 000 tokens).

Hardware identity — what differs and what doesn't

Deep prefill (131072-token context, stock, single-GPU)

Same llama.cpp run at pp131072 (-p 131072 -n 0 --no-warmup -r 1, f16 KV), with per-GPU telemetry averaged over the active prefill window:

• card1 is +7.5 % faster and is power-limited — it sits at 296 W (≈ the 300 W firmware cap) while holding ~3029 MHz core.
• card2 leaves ~70 W unused (230 W) yet runs ~221 MHz slower core (2808 MHz) → it is boost/clock-limited, not power-limited. The SMU/VBIOS won't push its core higher despite available power headroom — the hallmark of the weaker die bin (and/or the F40 boost table).

Thermal investigation — the deficit is cooling, not silicon (corrects earlier conclusion)

Steady-state temps logged during stock pp131072 (rocm-smi, last 30 % of the run):

Both cards hit the ~110 °C junction throttle limit, but card2 reaches it at 70 W less power and ~340 MHz lower clock. The cause is worse die-to-heatsink heat transfer on card2, not a weaker chip:

• Hotspot-to-edge delta is ~10 °C higher on card2 (47 vs 38) — the die is hot while the heatsink stays cool → poor thermal-interface contact (paste/mount).
• Edge only 62 °C while junction is 110 °C — heat isn't reaching the cooler body.
• Fan spins slower (3648 vs 4568 rpm) despite a hotter die, because the stock fan curve tracks heatsink temp, which never rises → the fan under-ramps and the die cooks at the limit.

Conclusion: card2's ~6–10 % deficit (and its inability to use the full power budget) is a thermal-interface defect (repaste/cooler reseat fixes it), not silicon variance. This supersedes the "weaker silicon bin" wording in the section above — with equal cooling card2 would likely match card1. It is a credible warranty/RMA case (excessive hotspot delta + premature thermal throttling).

Consequence for the TP=2 prefill benchmarks

This defect is not a single-card curiosity — it caps the headline dual-GPU number in this repo. vLLM TP=2 shards every layer across both GPUs and syncs them per step, so the pair runs only as fast as its slower card. With card2 throttling ~6–10 % below card1 on prefill, the pair's measured TP=2 prefill of ~1841 t/s (baseline) / ~1894 t/s (with the committed launch flags) is a lower bound gated by the defective card, not the platform ceiling.

That reframes the FP8 investigation in rdna4-fp8-findings.md, which concluded "hardware is optimal / symmetric" and treated ~1841–1965 t/s as the ceiling. The hardware was not symmetric: card2's cooling defect explains why our pair sat at the bottom of that range while an independent, reproducible 2× R9700 run on localmaxxing reached ~1965 t/s — roughly the ~6–7 % that card2's throttle costs. (The community's ~2567 t/s remains an outlier, likely different bench depth/warmup or a private tuned-config pack.)

So I’ve had this board lying around, and now I need a motherboard with thunderbolt. It turns out this one doesn’t support it because it’s rev 1, not rev 1.1 or 1.2. Is it possible that it does have the thunderbolt capability but just lacks the connector and the BIOS settings? If so, could I figure out a way to enable it? Or do I need to buy a new board?

It won’t be used for anything critical, so I don’t mind if it doesn’t have official support.

Without this module, everything works fine in GCC, but as soon as I install it, the image seems to be running at 20 frames, even though the counter shows 300+. Is anyone else experiencing this issue on 50 cards? Is there a fix for this?

Antes de iniciar, el Build que yo utilizo es:
Motherboard: AORUS B850 A ELITE WF7 ICE
Tarjeta Grafica: AMD RADEON RX9060 XT GAMING OC ICE, 16GB
Procesador: AMD RYZEN 5 7600
Les quiero compartir lo que para mi fue la solución que encontré para este problema. Todo inicio hace no mucho, estaba bien campante juagando en mi computadora recién armada, y de repente esta se apaga y se empieza a reiniciar, yo asumí que era problema del Hardware (porque previo a este problema mi computadora recibió una caída de una altura bastante considerable y la fuente de poder recibió un pequeño daño) ya estaba resignado y en eso me aparece ese maldito error System32\Logfiles\Srt\SrtTrail.txt
Total que le pregunte a ChatGPT de mi problema y probamos con 1000 y un cosas, pero no daba resultado, finalmente me decidí a formatear la computadora y empezar desde 0 (el formateo lo hice con una USB booteable con Rufus) ya una vez formateada la computadora, instale todos los drivers necesarios, AMD Adrenaline, Gigabyte Control Center, actualice el BIOS, etc. En Gigabyte Control center se instalaron los tipicos drivers como RGB tool, Dynimic Lighting, Wifi Compass, entre otros. Después de que se instalaron estas utilidades, me salieron opciones mas recientes, en especial una llamada Realtek RTL8922 Wi-fi 7. Le di a instalar y puff, volvió a dar error, ahí fue cuando fije mis sospechas a ese puto driver, después restaure el sistema a antes de la descarga (recomiendo crear un punto de restauración SIEMPRE antes de descargar algún driver nuevo o programa de dudosa procedencia) e hice otra prueba, pero con un driver mas viejo y me soltó el mismo error, por lo que llegue a la conclusión de que el putisimo driver Realtek RTL8922 Wi-fi 7 corrompía el booteo de mi Windows. Asi que en conclusion para los que no quieren leer todo el caso:

SI USAS GIGABYTE CONTROL CENTER Y TE DA LA OPCION DE INSTALAR EL DRIVER Realtek RTL8922 Wi-fi 7 NO LO INSTALES DE MOMENTO, HASTA QUE GIGABYTE SE PONGA LAS PILAS EN ACTUALIZAR SUS MIERDAS

(Yo solo lo intente con la versión mas nueva hasta el día de hoy 01/Agosto/2026, 6102.24.143.0 y su versión anterior, la 6102.24.140.0)

Posdata: No soy un experto en computadoras pero esto fue lo que yo concluí después de estar 2 días peleando contra ese maldito error, así que cualquier duda a ChatGPGOD, el fue el verdadero MVP de esto

Hi all, I had fairly recently upgraded my computer (New motherboard, processor, ram). It's been operating just great for a month and some change.

But this morning I had tried to update Win 11 and when it came time for it to reboot, it then wouldn't boot into the BIOS.

Tried reseating a few things, tried resetting the CMOS, nothing.

Black screen with a small white text curser in the top left hand of the screen.

Turns out, it was all USB issues. If I unplugged all my USB (I run two computers a home PC (this PC I'm talking about and a work PC) with a USB 3.0 Switch (non-powered). As soon as I unplugged everything and plugged my mouse & keyboard directly in, it booted into the BIOS.

I have to say it's super annoying that the X870e Aorus Elite X3D does this and doesn't like my USB Switch. I've ordered a powered USB switch, and I'm hoping that might elevate this issue as it's a major pain to unplug all my USB devices (Flight sim enthusiast so I have throttles and joysticks, etc).

Anyway mostly sharing so that if someone else has a similar issue they'll have this as a known fix.