Most dead RGB comes down to four things: the wrong header (a 3-pin 5V ARGB device plugged into a 4-pin 12V RGB header, which can permanently kill the strip), a pin-1 orientation mistake, a hub with no SATA power, or two lighting apps fighting each other. Check the header type first, then power, then software — in that order.
- Start Here: A 60-Second Triage
- ARGB vs RGB Headers: The Number One Cause of RGB Not Working on a PC
- Orientation and the Blocked Pin
- Hubs, Daisy-Chains and Power Limits
- When Motherboard Software Fights Vendor Software
- BIOS Settings That Silently Kill Lighting
- Isolation Testing: Dead Fan vs Dead LED
- Driver and Service Restarts
- Common Traps
- Frequently Asked Questions
Quick answer: Our top pick in 2026 is the ARGB — our #1 rated choice. See the full ranked comparison, alternatives and buying advice below.
Start Here: A 60-Second Triage
Lighting faults fall into three buckets: electrical (wrong header, no power), mechanical (connector off by a pin), or software (two apps claiming the same device). Work in that order — a software fix on a fried strip is wasted time.
- Do the fans still spin? Blades turning with a black ring is a lighting-only fault; a dead fan is a power problem, not RGB.
- Is anything lit at all? One sector of a strip glowing, or only the first LED of a fan, points to a broken data chain rather than a dead device.
- Did it work before? Lighting that died after a Windows update, BIOS flash or new app install is nearly always a software conflict.
If you are still assembling, our walkthrough on routing case cables covers where each header sits on a typical ATX board.
ARGB vs RGB Headers: The Number One Cause of RGB Not Working on a PC
This is the mistake that destroys hardware. Modern boards carry two incompatible lighting headers that look similar enough to force together.
3-pin 5V ARGB (addressable RGB, labelled ARGB, ADD_HEADER, JRAINBOW or ADD_GEN2) sends 5 volts plus a data line, so each LED can show a different colour. 4-pin 12V RGB (labelled RGB_HEADER, JRGB or RGB_LED) sends 12 volts across separate red, green and blue channels — the whole strip shows one colour at a time.
Plugging a 5V ARGB device into a 12V RGB header pushes more than double its rated voltage into the LEDs. It usually kills them instantly — sometimes with a brief flash — and the damage is not recoverable. The reverse mistake is less destructive but produces dim, wrong or absent colours.
| Header | Pins / voltage | Typical board labels | What it drives | If you cross-connect |
|---|---|---|---|---|
| ARGB | 3-pin, 5V (one pin blocked) | ADD_HEADER, JRAINBOW, ADD_GEN2, ARGB | Addressable fans, per-LED strips, AIO pump caps | On a 12V header: LEDs are destroyed, usually permanently |
| RGB | 4-pin, 12V | JRGB, RGB_HEADER, RGB_LED | Single-colour strips, older fan rings, some coolers | On a 5V header: dim, wrong colour, or nothing at all |
| ARGB Gen 2 | 3-pin 5V, keyed differently | ADD_GEN2 (ASUS) | Gen 2 devices that report their LED count | Standard 3-pin devices work but lose auto-detection |
| Proprietary | Vendor-specific (e.g. 4-pin ARGB) | Corsair, Lian Li, NZXT hubs | That brand’s fans only | Do not adapt without the vendor’s own cable |
The safe rule: match the label on the board to the label on the device, count the pins, and never use a passive 5V-to-12V adapter. Fans pre-wired to a proprietary controller should stay on it — our case fan installation guide covers the airflow side, but lighting stays on the bundled hub.
Orientation and the Blocked Pin
ARGB connectors carry three wires in a four-wide shell: the second position is blank, and the matching header has a blocked or missing pin. Push the plug on one position over and the device gets 5V and ground but no data, so it stays dark or freezes on one static colour — a classic cause of “RGB fans not lighting up”.
The arrow moulded into the plug marks the 5V pin and must line up with the arrow silkscreened beside the header. Use a phone torch rather than feel, and treat a connector that slides on with no resistance as a sign you are off by one.
Hubs, Daisy-Chains and Power Limits
A motherboard ARGB header typically supplies around 3 amps at 5V. Each LED draws little, but six fans plus strips add up, and an overloaded header rarely fails loudly — it browns out, showing flicker, colour drift toward white, or the last device in the chain going dark while the first few work.
A powered ARGB hub solves this: it takes SATA power straight from the PSU and uses the motherboard header only for the data signal, so LED current never crosses the board. If your hub has a SATA lead and you left it unplugged, nothing downstream will light. That is one of the most common “hub is broken” reports, and it takes ten seconds to check.
Two more hub rules: respect the per-port device count, because a port rated for one fan will not reliably run three daisy-chained; and remember that chains are directional, so one bad connector in the middle kills everything after it. Unplug at the halfway point to find the break. Our notes on planning a cooling upgrade cover how many devices a controller can realistically feed.
When Motherboard Software Fights Vendor Software
If the hardware is fine and lighting still misbehaves, you have a software conflict. Motherboard suites — ASUS Aura Sync, MSI Mystic Light, Gigabyte RGB Fusion, ASRock Polychrome — each install a service that claims every lighting device it can see, and vendor apps such as Corsair iCUE, Razer Synapse and NZXT CAM do the same. Run two at once and you get lights stuck on rainbow, settings that revert seconds after you apply them, or a device that never appears.
“iCUE not detecting” a device is the signature symptom. The fix is to pick one owner per device:
- Close every lighting app from the tray, then end leftover services in Task Manager (Aura, LightingService, Mystic Light, RGBFusion, Corsair.Service).
- Uninstall the suite you do not intend to use. Partial uninstalls leave services behind, so reboot afterwards and confirm they are gone.
- Reopen the app you kept. In iCUE, check the device list in Settings and apply any firmware update a commander or hub is waiting on — stale hub firmware is a frequent detection failure.
- If both suites must coexist, use the bridge mode — iCUE’s “Enable full software control” or Aura’s plugin handoff — rather than letting both poll the same device.
If the dead device is a keyboard or mouse rather than a fan, start with our guide to gaming keyboards and check whether it stores profiles onboard.
BIOS Settings That Silently Kill Lighting
Two BIOS options catch people out. The first is a global LED toggle under an Onboard Devices, Advanced or vendor lighting menu — a BIOS reset or firmware update can flip it back to a default you did not choose. The second is the sleep setting, worded as “turn off LEDs in sleep/hibernate/soft off” or “Onboard LED in S5”. If your RGB only fails after a sleep cycle and returns on a full restart, that is your setting. ErP/EuP power saving forces the same behaviour and overrides it.
Isolation Testing: Dead Fan vs Dead LED
Before replacing anything, prove which half failed. Change one variable at a time so each result actually means something.
| Step | Test | What it proves | Next move |
|---|---|---|---|
| 1 | Move the suspect device to a header you know works | Whether the fault is the device or the header | Lights up? The original header or hub port is dead |
| 2 | Plug a known-good fan into the suspect header | Whether the header itself outputs anything | Still dark? Suspect the board header or BIOS toggle |
| 3 | Connect the device on its own, nothing else in the chain | Whether the header is overloaded | Works alone but not in the chain? Add a powered hub |
| 4 | Confirm the fan spins while the ring is dark | Separates the motor circuit from the LED circuit | Spins but dark? LED or data fault, not power |
| 5 | Set a static colour in software, not an effect | Removes animation and sync from the equation | Static works, effects do not? Software or sync issue |
| 6 | Swap the extension or splitter cable | Cheap cables fail more often than devices | Fixed? Discard the cable, do not reuse it |
Note what changes at each step; the record matters if you end up filing a warranty claim — the same discipline we recommend when diagnosing a PC that won’t display.
Driver and Service Restarts
When the wiring is right and one app owns the device, a stuck service is the last suspect. Restart the lighting service from services.msc rather than relaunching the app, which is only a front end. Prefer a full shutdown over a restart, because Windows Fast Startup carries the same broken driver state across reboots — hold Shift while clicking Shut Down, or disable Fast Startup in Power Options while troubleshooting.
Then check Device Manager for a controller under an error flag. Many ARGB commanders present as USB devices on an internal USB 2.0 header, and a loose cable there makes the controller invisible to software even while the lights still have power. Our case selection notes explain why some enclosures make these headers easier to reach.
Common Traps
- 5V-to-12V adapters. They exist, they are dangerous, and no build needs one.
- Wrong LED count in software. Setting a 20-LED strip to 8 leaves the rest dark and mimics hardware failure.
- Sync on a dead chain. Sync only mirrors what devices report — fix the wiring first.
- Front-panel RGB button. If the case lighting button is unplugged or mapped to the reset pins, effects will not cycle.
Frequently Asked Questions
Can I plug a 3-pin ARGB device into a 4-pin RGB header?
No, and attempting it is the single most damaging mistake in PC lighting. A 3-pin device expects 5 volts; a 4-pin header supplies 12 volts across separate colour channels. Forcing the connector on delivers roughly double the rated voltage to the LEDs and usually destroys them within seconds, with no way to recover the strip. Always match the label printed beside the header to the label on the device, and never use a passive adapter between the two standards.
Why are my RGB fans not lighting up even though they spin?
A spinning fan with dark LEDs means the motor circuit is fine and the lighting circuit is not — they run on separate cables. Check that the second, thinner ARGB lead is actually plugged in, that it sits on the correct pins with the blocked position aligned, and that any hub it feeds has its SATA power connected. If the fan is mid-chain, a single failed connector before it will leave everything downstream dark while earlier fans work normally.
Why is iCUE not detecting my hub or fans?
Detection failures almost always trace to a competing lighting service or a missing internal USB connection. Close and uninstall the motherboard suite you are not using, end any leftover background services in Task Manager, then reboot with Fast Startup disabled. Confirm the commander or hub appears in Device Manager as a USB device, since most controllers talk to software over an internal USB 2.0 header. If it appears but stays unsupported, apply any pending firmware update from within iCUE.
My lights turn off when the PC sleeps. How do I keep them on?
That behaviour is controlled in BIOS, not in Windows. Look for an option worded like “turn off LEDs in sleep, hibernate and soft off” or “Onboard LED in S5” and disable it so lighting persists while the system is suspended. Also disable ErP or EuP power saving, because that setting cuts standby power to the headers and will override your LED preference regardless of what the lighting app is set to do.
How many ARGB fans can one motherboard header run?
Header limits are stated in amps rather than device count, and a typical 5V ARGB header supplies around 3 amps. In practice three to five standard fans is a sensible ceiling, but a strip with a high LED density can consume as much as several fans. Symptoms of overload are subtle — flicker, colours drifting toward white, or the final device in a chain going dark. A powered hub taking SATA power directly from the PSU removes the limit entirely and is the correct fix for a six-fan build.
Ready to decide? Our #1 pick for 2026 is the ARGB.
Live price & availability on Amazon.
Top picks from this guide
ThermalrightThermalright ARGB and Fan HUB X12 IR Black Hub Controller…$12 \xc2\xb7 99/100
ASUSASUS TUF Gaming ARGB PWM Fan Hub$32 \xc2\xb7 98/100
ThermalrightThermalright ARGB and Fan HUB X12 IR White Hub Controller…$12 \xc2\xb7 96/100
ThermalrightThermalright ARGB Fan HUB Controller Support 8 Groups of Fans,…$12 \xc2\xb7 95/100
