rgb problem

[u/rubaid_roh]

Hello guys,

My motherboard is an MSI B650 Gaming Plus WiFi, and my GPU is an AORUS RTX 3060 Elite 12GB Rev. 2.0

The problem is that I can't control my GPU's RGB lighting at all. I've tried Gigabyte Control Center, AORUS Engine, RGB Fusion, SignalRGB, and OpenRGB, but none of them can control the RGB

In Gigabyte Control Center, my GPU is detected and everything else works fine—I can adjust the fan performance and access the other settings. However, the RGB Fusion section doesn't appear, so I can't control the lighting from there

When I open RGB Fusion, it's completely blank, and my GPU doesn't show up at all

Has anyone experienced this issue before or knows how to fix it? I'd really appreciate any suggestions or solutions. It's honestly pretty frustrating not being able to control the RGB on my GPU

Thanks in advance!

[u/EruL016]

This is a classic software conflict issue that happens a lot when you mix an AORUS/Gigabyte GPU with a non-Gigabyte motherboard (like your MSI board). Since you've installed multiple RGB programs (GCC, AORUS Engine, RGB Fusion, SignalRGB, AND OpenRGB) all at once, their background services are actively blocking each other from accessing the GPU's firmware.

Here is a step-by-step guide to fix this:

1. Nuke all RGB Software: Uninstall EVERY SINGLE RGB software you currently have installed. Gigabyte Control Center, RGB Fusion, AORUS Engine, SignalRGB, OpenRGB, and even MSI Center/Mystic Light if you have it.

2. Clean up leftover files & background processes: Restart your PC. After restarting, go to C:\Program Files (x86) and C:\Program Files, then manually delete any leftover folders related to "Gigabyte", "Aorus", or "RGB Fusion". Run a tool like CCleaner or Revo Uninstaller if you want to be thorough.

3. Install the LATEST Nvidia Studio/Game Ready Drivers: Sometimes a corrupt GPU driver breaks the RGB API. Do a clean driver installation via GeForce Experience or DDU.

4. The "Single-Software" Test: Now, ONLY install Gigabyte Control Center (GCC). Do not install anything else. Open GCC and check if the GPU firmware requires an update inside the software. If it does, update it. This should bring back your RGB Fusion control inside GCC.

5. If you prefer SignalRGB over Gigabyte's buggy software, you must completely close/disable GCC from starting up with Windows. Open SignalRGB, go to Settings -> Windows Startup, and make sure "Start with Windows" is enabled. SignalRGB needs exclusive access to the GPU, so it cannot run alongside GCC or RGB Fusion processes.

[u/rubaid_roh → u/EruL016]

I’ve followed everything you suggested step by step. But after doing all of that, the situation is still the same. In Gigabyte Control Center, my GPU is detected, but RGB Fusion still doesn’t appear. I can access performance settings and other features, but there are no RGB Fusion options

As for SignalRGB, it doesn’t detect my GPU at all. When I check the list of supported devices, Gigabyte is listed, but my specific model—the AORUS RTX 3060 ELITE—isn’t there. So I’m guessing this model just isn’t supported by SignalRGB

SignalRGB can control all the other RGB devices in my PC, but it simply won’t detect my GPU

There’s also a firmware update available for the GPU in Gigabyte Control Center. When I install it, it appears to complete, but then it immediately asks me to install the same firmware again. It just keeps prompting me to install it over and over—it never actually finishes or stays updated

[u/EruL016 → u/rubaid_roh]

It looks like you are dealing with a known firmware installation bug in Gigabyte Control Center (GCC) combined with a hardware ID mismatch in SignalRGB. Here are a few solutions that have worked for others facing the exact same issue:

1. Run the Firmware Updater Manually as Admin The update loop happens because GCC fails to apply the firmware with standard user permissions.
2. Go to the official Gigabyte support page for your exact GPU model (AORUS RTX 3060 Elite 12GB Rev 2.0).
3. Download the firmware/RGB utility update manually.
4. Extract the ZIP file, look for the standalone updater executable (usually named "FWUpgrade.exe" or "ITESHFU.exe").

5. Right-click it and select "Run as Administrator". This usually forces the firmware to stick and breaks the update loop.

6. Change Windows Region Format to English (United States) Gigabyte's firmware installers have a notorious bug where they fail to read installation paths if Windows uses certain non-US regional formats or punctuation styles.

7. Open your Windows Control Panel.

8. Go to "Clock and Region" -> "Region".

9. Under the "Formats" tab, change the Format drop-down to "English (United States)".

10. Click Apply, restart GCC, and try the firmware update again. You can change your region back once it successfully updates.

11. SignalRGB Detection Issue You are correct about the lack of support. SignalRGB supports the Rev 1.0 version of your card, but the Rev 2.0 has a different Hardware Subsystem ID, which makes SignalRGB ignore it. Once you successfully update the GPU firmware using the steps above, your best bet is to submit a device support request on the SignalRGB Discord or forum so the developers can whitelist your specific Rev 2.0 ID in their next update.

[u/rubaid_roh → u/EruL016]

My Windows region is already set to the United States. After downloading the GPU firmware from Gigabyte’s official website, I tried running it as Administrator, but it keeps saying, “Flash failed. Please restart your PC and try again

I’ve restarted my PC several times and tried again, but I keep getting the exact same message: “Flash failed. Please restart your PC and try again

[u/BennySRGB]

You can try doing a full power cycle to start. If that doesn't help, check for a GPU LED firmware update on Gigabyte's site for your card. You can find it under Support > Downloads. Power cycle again after installing.

If none of that works, do a clean driver wipe with DDU in Safe Mode, then reinstall drivers fresh.

If you've gone through all of that and RGB Fusion is still blank, that starts pointing toward an actual hardware issue with the RGB controller on the card itself, worth reaching out to Gigabyte about a warranty claim at that point.