Key takeaways
- A motherboard header for addressable or standard RGB, controlled by the board maker’s software.
- A fan or lighting hub supplied by a cooler, case, or fan kit, which usually needs its own power from the PSU (often through a SATA or Molex-style lead) and often a USB cable to a motherboard header.
- A proprietary controller that comes with a case or an all-in-one cooler.
- A direct USB connection for items such as keyboards, mice, or RAM with its own link.
When RGB lighting stops working, the fastest fix is to power the PC off, unplug it, and reseat the lighting cable on the correct header, because a loose or wrong-type connector is the most common cause. If every cable is seated properly, the next suspects are conflicting lighting software, a fan hub or controller that has lost its power or USB link, and a lighting setting in the BIOS or firmware.
Quick Diagnosis: Match the Symptom to the Cause
| Symptom | Common cause | First thing to try |
|---|---|---|
| Nothing lights up at all | Cable unplugged, wrong header, or hub without power | Power off, unplug, reseat the lighting cable and the hub power lead |
| Lights work in BIOS but not in Windows | Software not running, or a service stopped | Restart the vendor app or reinstall it |
| Lights work in Windows but flicker or change at random | Two programs fighting for control | Close all but one lighting program |
| Only part of a strip or fan lights up | Break in the daisy chain or a bad connector | Swap the first unlit device to find the break |
| Wrong colors (all red, or green when blue is set) | Channel order mismatch or wrong header type | Check the header type printed on the board and in the manual |
| Lights go dark when the PC is off | Standby lighting is off in firmware | Look for a lighting or standby option in BIOS |
| Lights died after a Windows or driver update | Service or SDK conflict | Update or reinstall the lighting app and restart |
Step 1: Power Down and Check the Physical Connections
Switch off the power supply, unplug the mains cable, and press the power button once to drain residual charge before reaching inside. Lighting cables are small and easy to leave half-seated, particularly after moving a case or swapping a GPU. Reseat each cable until it is flush with its header and no pins are visible.
Look at where each lighting cable ends. There are generally four paths:
- A motherboard header for addressable or standard RGB, controlled by the board maker’s software.
- A fan or lighting hub supplied by a cooler, case, or fan kit, which usually needs its own power from the PSU (often through a SATA or Molex-style lead) and often a USB cable to a motherboard header.
- A proprietary controller that comes with a case or an all-in-one cooler.
- A direct USB connection for items such as keyboards, mice, or RAM with its own link.
If a hub has a power lead that was never connected, the lights may sit completely dark even though the fan spins from another cable. Check the hub’s manual for which leads are mandatory.
Step 2: Confirm You Have the Right Header Type
Motherboards commonly offer two kinds of lighting header. A 4-pin header carries 12V for standard RGB devices, with one shared supply pin and separate red, green, and blue pins. A 3-pin header carries 5V for addressable RGB (often labelled ARGB or by a similar name), where each LED can be set individually over a data line. These are not interchangeable. Motherboard makers warn in their manuals that plugging a 5V addressable device into a 12V header can damage the lights, so read the label printed beside the header and match it to the device.
Orientation matters as well. Headers are keyed, and the 5V pin is generally marked on the board, so a cable should only go on one way. If a cable needs force, stop and check the manual instead of pushing it on. A connector inserted offset by one pin can leave the lights dead or damage the controller, so do not guess.
| Header | Pins | Typical use | Control |
|---|---|---|---|
| Standard RGB | 4-pin, 12V | Older strips and some fans | One color across the whole device |
| Addressable RGB | 3-pin, 5V | Modern fans, strips, coolers | Per-LED effects |
| Vendor hub / USB | Varies | Cooler or fan kit ecosystems | Maker software |
Step 3: Sort Out the Software
A very common cause of strange lighting is several programs trying to control the same hardware. A motherboard utility, a memory maker’s tool, a cooler’s control app, a peripheral suite, and a third-party aggregator can all send commands at once. The result is flickering, effects that reset, or devices that appear in one app and vanish in another.
- Close every lighting application and end it in the system tray.
- Launch just one, preferably the one from the maker of the hub or controller that the devices plug into.
- If devices still do not appear, restart the PC and open that app again.
- If it still fails, uninstall the extra lighting tools, reboot, and reinstall only what you need.
Open-source projects such as OpenRGB aim to control many brands from one interface, and some users choose it to replace several vendor apps. Reviewers and project documentation note that running it alongside vendor software that talks to the same device can cause conflicts, so use one controller at a time. Windows also now has its own built-in lighting settings in recent versions, which can add one more source of commands; if lights behave oddly after an update, check that page in Settings for options that override the effect.
Step 4: Check Firmware and BIOS Options
Many motherboards include a lighting option in BIOS or UEFI that turns onboard and header LEDs off, or controls whether lights stay on while the PC is shut down. The name and location vary by maker and model, so look in the lighting or advanced section of your board’s manual instead of relying on a menu path from a different board. Some boards also have a power-saving mode that cuts power to lighting in standby.
BIOS changes can affect stability, and a failed update can leave a board unable to boot, so change only the lighting option and leave other settings alone. If a BIOS update is the suspected fix, follow the maker’s update instructions exactly and do not interrupt it.
Step 5: Isolate the Faulty Part
When one device is dark and the rest work, swap places to find out whether the device, the cable, or the header is at fault.
- Plug the dark device into a known-good header or the first spot on a hub. If it lights, the original port or the earlier device in the chain was the issue.
- Plug a working device into the suspect port. If it also stays dark, the port, cable, or hub channel is the problem.
- With daisy-chained fans or strips, a failure in one unit can stop everything after it, because the data signal passes through each LED in sequence. Remove the first dark unit and see whether the rest recover.
Common Mistakes
- Using a 12V cable on a 5V header, or the reverse. This is the one mistake that can cause real damage, so read the printed labels.
- Forgetting the hub’s separate power lead. Data from USB alone does not feed the LEDs on many hubs.
- Installing every vendor app at once. More software means more conflicts.
- Splitting a header too many times. Splitters and long chains can exceed what a header or hub is rated for, so check the maker’s stated limit for connected LEDs or devices.
- Ignoring a loose USB cable. A hub with a missing internal USB link will not show up in software at all.
- Assuming the LEDs are dead. Most cases are cable, software, or setting problems.
When to Stop and Contact the Maker
If a device stays dark after you have tried a different header, a fresh cable, and a clean software setup, the LEDs or controller may be faulty and the warranty is the correct route. Stop immediately and unplug the PC if you notice a burnt smell, discoloured connectors, or heat around a lighting cable. Do not open a power supply to investigate; send it to the maker or a qualified technician. If you are unsure which header is which, the board manual and the device manual are the authoritative references.
Decision Table: What to Do Next
| If this is true | Do this |
|---|---|
| Nothing lights, even in BIOS | Recheck cables, hub power, and header type |
| Lights work only before Windows loads | Reinstall the single lighting app and remove duplicates |
| One device never appears in software | Check its USB link and power lead |
| Some of a chain stays dark | Swap the first dark device to find the break |
| Everything fails after hardware changes | Reseat what you disturbed and confirm header labels |
| Still dead after all of this | Contact the maker about the warranty |
Frequently Asked Questions
Why did my RGB stop working after a Windows update?
An update can restart or replace services that lighting apps depend on, or add a built-in lighting feature that competes with them. Restart the lighting app, then reinstall it if devices do not return. Keep only one app in control of each device.
Can I plug an ARGB device into an RGB header?
Motherboard makers state that 5V addressable devices and 12V standard devices are not interchangeable, and mixing them can damage the lights. Match the pin count and voltage printed on the board and in the device manual before connecting anything. If you want an addressable device on a board with only a 12V header, use a controller designed for it.
Why does only half of my fan lighting work?
Daisy-chained addressable lights pass data from one LED to the next, so a faulty unit or loose connector can leave everything after it dark. Reseat each link, then remove the first unlit fan to see whether the chain recovers. If a fan stays dark in a different spot, it is the faulty piece.
Do I need the manufacturer’s software for RGB to work?
Many devices light up in a default pattern without software, but changing colors or effects usually needs the maker’s app or a compatible third-party tool. If a hub shows no devices at all, check its USB and power connections first. Software only controls what the hardware can reach.
Why do my lights go off when the PC is shut down?
That is often a deliberate power-saving or standby setting. Some boards have a firmware option for lighting in the off state, and the name differs between makers, so consult your manual. Lights that go dark in standby are not necessarily broken.
Is it safe to keep using lights that flicker?
Flicker is typically a software conflict or a loose connector, and it is usually harmless once fixed. If you see heat, smell something burnt, or notice damaged plastic around a connector, power the PC off and contact the maker or a technician.
FAQ
Why did my RGB stop working after a Windows update?
Can I plug an ARGB device into an RGB header?
Why does only half of my fan lighting work?
Do I need the manufacturer’s software for RGB to work?
Why do my lights go off when the PC is shut down?
Is it safe to keep using lights that flicker?
More from Amazon
Programs that pair well with the guide above. Offers and eligibility are set by Amazon and may change.
Free shipping on eligible items, Prime Video and more. Eligible new members can start with a free trial.
Start a Prime free trialAd-free music streaming. Eligible new subscribers can start with a free trial.
Try Music Unlimited freeA Prime membership for ages 18-24 with a trial period. Eligibility is set by Amazon.
See Prime for Young AdultsAudiobooks and podcasts to listen to on the go. Eligible new members can start with a free trial.
Try Audible freeAs an Amazon Associate we earn from qualifying purchases.