I spent an entire weekend chasing this one. New Z790-E build, 64GB of G.Skill Trident Z5 RGB seated in slots A2 and B2 exactly like the manual says, Armoury Crate installed fresh, and both sticks showing up in Windows, POST, even XMP running fine. But Aura Sync? Completely blind to them. The devices panel showed my board, my ARGB fans, even the header strips. No RAM. Not even greyed out. Just not there.
What makes RAM RGB so much harder to troubleshoot than other devices is that it’s not plug-and-play like your fans or LED strips. RAM sticks don’t connect to software through USB or a simple header. They use a shared communication bus called SMBus, which the board, the RAM, and potentially other apps all have to share. One misconfigured setting in BIOS, one other RGB app with its hands in the same bus, one update that breaks the HAL layer, and your RAM disappears from software entirely. The hardware is fine. The LEDs work. The detection chain is just broken somewhere.
This guide walks through every layer of that chain. I’m going to give you the fixes in order of how often they actually work, include the brand-specific quirks for G.Skill, Corsair, Kingston, and TeamGroup, explain the SPD corruption risk that most guides don’t mention at all, and tell you when it’s time to stop fighting AC and use something else.
Why RAM RGB Detection Is Different From Everything Else
Before the fixes, a quick explanation that’ll save you from going down wrong paths.
Your fans, LED strips, and ARGB headers connect to Armoury Crate through a relatively simple chain: the header on your board, the HAL driver, the LightingService. If that chain is broken, you restart services and it usually comes back.
RAM RGB is different because it uses the System Management Bus, or SMBus. This is a low-speed bus built into your motherboard chipset that was originally designed for hardware monitoring. Temperature sensors, voltage regulators, power management chips, they all talk to the CPU over SMBus. At some point the RGB LED controllers in RAM sticks started using it too, because it was already there.
The problem with SMBus is that it’s shared. Every device on the bus talks to the same line. When two software applications both try to communicate with your RAM’s LED controller over SMBus at the same time, you get bus collisions. The data gets corrupted, the controller stops responding, and the RAM disappears from software. In severe cases with specific older software combinations, those collisions could corrupt the SPD data on the RAM itself, which is a much bigger problem than missing RGB. More on that later.
This is why “I have iCUE and Armoury Crate both installed” is such a common setup for people reporting this exact problem. Both apps want SMBus access to your RAM sticks and they don’t cooperate well by default.
Quick Checks Before You Spend Hours Debugging
These take under five minutes and solve 30% of cases:
- Reseat your RAM. I know, I know. But a RAM stick with slightly loose contact to the slot sometimes drops off SMBus even though it’s passing POST and running Windows fine. Power off completely, press the clips, pull both sticks, reseat them firmly. Try the far slots first (A2/B2 on most boards), then try the near slots if that doesn’t help.
- Check if Armoury Crate actually needs an update. If you’ve been on the same AC version for a while, open it and check for updates. Conversely, if you just updated and RAM disappeared, that’s the most important clue you have (see the AC 6.3.9.0 section below).
- Close every other RGB app before testing. iCUE, G.Skill Lighting Control, OpenRGB, SignalRGB, Dragon Center, all of it. Completely closed, not minimized to tray. Then restart LightingService (services.msc, right-click, Restart) and open AC fresh. This rules out bus conflicts before you go any deeper.
- Make sure your RAM actually has RGB. This sounds obvious but not every Trident Z or Vengeance has RGB LEDs. Some models in the same product line are non-RGB versions that look identical in spec sheets. Check your specific part number on the manufacturer’s site.
Fix 1: Use the Rescan Feature in Armoury Crate
There’s a rescan option buried inside Armoury Crate that most people never find, and it solves a surprising number of RAM detection failures without any of the heavier fixes below.
In Armoury Crate, go to the Devices tab, then click on your Motherboard entry. Look for a rescan button or option within the motherboard settings panel. On some AC versions it’s labeled “Rescan” and on others it’s a refresh icon. Click it and wait 30 to 60 seconds for AC to re-enumerate all attached devices on the SMBus.
This works because LightingService does an initial device scan on startup, and if the RAM controllers weren’t fully initialized when the scan ran (which can happen if AC starts before Windows has finished loading all chipset drivers), the sticks just don’t appear. Forcing a rescan after everything is fully loaded often brings them right back.
I’ve seen this fix cited repeatedly in ROG Forum threads for Z890 Maximus Hero users specifically, where the RAM detection seemed to be timing-dependent on that board generation.
Fix 2: Enable DRAM SPD Write in BIOS (Critical for Intel Platforms)
This is the most common BIOS-level fix for RAM RGB not being detected, and it’s almost entirely undocumented in ASUS’s own help materials. The setting is called DRAM SPD Write or SPD Write Enable, and on Intel Z690, Z790, and Z890 boards it’s disabled by default as a security measure.
Here’s why it matters: when Aura Sync wants to control your RAM’s RGB, it needs to both read from and write to certain registers in the RAM’s LED controller. Those registers are accessed over the same protocol as the SPD (Serial Presence Detect) data. On Intel platforms, ASUS disables the write portion of this by default to protect your SPD data from accidental corruption. Side effect: Aura Sync can’t properly initialize or control the LED controllers.
How to enable it:
- Restart and enter BIOS (Del key during POST on most ASUS boards)
- Press F7 or click Advanced Mode if you land in Easy Mode
- Navigate to AI Tweaker (Intel boards) or Extreme Tweaker (AMD boards)
- Look for DRAM Timing Control or scroll down to memory-related settings
- Find DRAM SPD Write or SPD Write Enable and set it to Enabled
- Save and exit (F10)
On AMD X670 and X670E boards, this setting is generally not required, since the AMD platform handles SMBus access differently. If you’re on AMD and don’t see the setting, don’t panic. It’s likely not what’s causing your problem.
Corsair actually has official documentation for this specific setting on their support site, because it affects Corsair RAM RGB detection too, not just G.Skill. The page is titled “How to Enable SPD Write on your ASUS Z690 motherboard” and the same process applies to Z790 and Z890.
One important note: enabling DRAM SPD Write does very slightly increase the theoretical risk of SPD data corruption if software misbehaves on that bus. See the SPD corruption section later in this guide for context on how seriously to take that risk.
Fix 3: The AC 6.3.9.0 Bug and What to Do About It
If your RAM RGB disappeared after a specific Armoury Crate update, you need to read this section before doing anything else because the cause is known and the fix is different.
Armoury Crate version 6.3.9.0, which pushed out in December 2025, included a HAL-SDK update that broke RGB detection for multiple RAM brands. Users on the ROG Forum reported T-Force RAM, G.Skill sticks, and others all disappearing simultaneously after this update. The same update also broke ARGB header detection for some users. As of late January 2026, ASUS had not yet released a fix, though that may have changed by the time you’re reading this.
How to confirm this is your problem: check your AC version by opening the app and going to Settings or About. If you see 6.3.9.0 or 6.2.9.0 and your RAM disappeared around the same time as your last AC update, you’ve found your cause.
Your options:
Option A: Roll back to an earlier version. Uninstall the current AC using the official uninstall tool (as covered in our uninstall guide), download an earlier version installer if you have one, or wait for ASUS to push a patched version through the update system. The version before 6.3.9.0 that was generally stable for RAM RGB was 6.1.18.0.
Option B: Use SignalRGB as a temporary replacement. Multiple users in the affected ROG Forum thread confirmed that SignalRGB correctly detects and controls T-Force and G.Skill RAM even while AC 6.3.9.0 breaks it. If you need RGB control right now and can’t wait for ASUS to fix their software, SignalRGB is a working bypass.
Option C: Wait for ASUS to patch it. If you’re not in a hurry, keep AC updated and check the ROG Forum thread (search for “6.3.9.0 RAM detection”) periodically. ASUS does eventually fix these regressions, usually within a few update cycles.
Fix 4: iCUE and Armoury Crate Conflict (Corsair RAM Users)
If you’ve got Corsair RAM (Vengeance RGB, Dominator Platinum, or any other Corsair DDR5 kit with RGB) and you also run iCUE, you’re in a known conflict situation that requires a specific configuration to resolve.
By default, iCUE takes exclusive control of Corsair RAM’s SMBus address when it detects those sticks. Armoury Crate can’t then access them because iCUE has locked the bus address. The result: Corsair RAM appears in iCUE fine but vanishes from Armoury Crate.
The fix requires three things to be in place simultaneously:
- Disable exclusive device control in iCUE: Open iCUE, go to Settings, then General. Find “Enable Full Software Control” or “Exclusive DRAM Lighting Control” and disable it. The exact label has changed across iCUE versions but it’s usually under memory-specific settings.
- Install the Corsair RGB Memory Plugin for ASUS AURA SYNC: This is a separate plugin that bridges Corsair’s memory SDK with Armoury Crate. The version that works is v2.1 (the .msi installer). Newer versions have had compatibility issues. Search for “Corsair RGB Memory Plugin ASUS AURA SYNC v2.1 msi” to find it. There’s a ROG Forum thread from 2024 discussing the exact version to use.
- Version match your software: The combination that community members have confirmed working is AC 6.1.18, iCUE 5.27.149, and the Corsair plugin v2.1. If you’re on different versions, conflicts get unpredictable.
Even with all three in place, the coexistence isn’t always stable across AC updates. ASUS and Corsair don’t coordinate their release cycles, so a new AC update can quietly break the plugin compatibility. This is one of those situations where I’d honestly recommend picking one software to control your RAM and sticking with it rather than fighting the coexistence forever.
Fix 5: Close All Competing RGB Software
This sounds like something you’d check first, and you should, but I’m putting it here because the “close” needs to be thorough. Minimizing to the system tray is not closing. The process needs to actually stop running.
Check Task Manager (Ctrl + Shift + Esc, Details tab) for any of these processes:
- iCUE.exe or CorsairHID.exe
- LIGHTING_SERVICE.exe (G.Skill Lighting Control)
- OpenRGB.exe
- SignalRGB.exe
- LedTool.exe (Kingston FURY Control)
- MSICenter.exe or DragonCenter.exe
- GigabyteRGBFusion.exe
If you see any of them running while you’re trying to get Armoury Crate to detect your RAM, end them. Then restart LightingService in services.msc and trigger a rescan in AC.
I’d also specifically call out G.Skill Lighting Control Software here. There’s a documented case from an LTT forum thread where running G.Skill’s own software simultaneously with Armoury Crate caused RAM animation freezes, color flickering, and in some cases appeared to start interfering with SPD data. Don’t run both. Pick one.
Fix 6: Full Power Drain to Reset DIMM RGB Controllers
RAM LED controllers have their own tiny microcontrollers with state that can get stuck. A normal restart doesn’t clear this because your system’s 5V standby power keeps the SMBus active even when Windows is “off.” You need a full capacitor drain to reset the controller to a clean state.
How to do it properly:
- Shut down Windows completely (Start, Power, Shut Down, not restart)
- Turn off the PSU power switch on the back of your case, or unplug the power cable from the PSU
- Press the power button on the case once to drain remaining capacitor charge
- Wait at least 30 seconds
- Plug back in / flip the PSU switch
- Boot normally
This has been specifically recommended by ASUS support for Z890 Maximus Hero users seeing inconsistent RAM detection, and it works more often than you’d expect. The DIMM RGB controller resets to its factory state on cold boot from no standby power, which clears whatever stuck state it was in.
Fix 7: Reinstall the Aura Service Component
Sometimes the Aura lighting stack gets partially corrupted, specifically the HAL (Hardware Abstraction Layer) components that interface with RAM controllers, while the rest of Armoury Crate seems fine. In this case a full AC reinstall isn’t always necessary. You can try reinstalling just the Aura Service component.
Stop LightingService in services.msc first. Then navigate to C:\Program Files\ASUS\ArmouryCrate\ and look for a component installer or setup file specifically named for Aura or LightingService. On some AC versions there’s a separate installer for this component. Run it, let it reinstall over the existing installation, restart the service, and test detection.
If you can’t find a standalone installer, a full AC reinstall using the official uninstall tool followed by a fresh install does the same thing. Just make sure you’re doing a genuine clean reinstall as covered in the uninstall guide, not an install on top of an existing broken one.
Brand-Specific Notes: G.Skill, Corsair, Kingston, and TeamGroup
G.Skill Trident Z RGB (DDR4 and DDR5)
G.Skill RAM has been the most consistently reported brand for Aura Sync detection issues, especially the Trident Z5 RGB DDR5 kits on Z790 and Z890 boards. The specific pattern I’ve seen: sticks are visible in BIOS and Windows Device Manager but absent from AC’s device list entirely.
For G.Skill specifically, the DRAM SPD Write BIOS setting (Fix 2 above) is almost always the fix on Intel platforms. G.Skill’s own forum has documented cases where users had to enable this setting explicitly, and there’s a confirmed report on the G.SKILL tech forum about Trident Z Neo RGB showing corrupted SPD entries after software conflicts, which is a good reminder to back up your SPD data before experimenting.
Also worth noting: don’t run G.Skill’s own Lighting Control software at the same time as Armoury Crate. Their software and AC’s LightingService both want SMBus access to the same LED controller addresses on the sticks, and they’ll fight each other. Use one or the other.
Corsair Vengeance and Dominator RGB
Corsair RAM detection in AC is its own ecosystem because Corsair uses a slightly different LED controller address scheme compared to other brands. The full Fix 4 procedure above (disable iCUE exclusive control + install Corsair plugin v2.1) is the specific path for Corsair users.
One additional Corsair-specific issue: iCUE 5 introduced changes to how it writes to RAM LED controllers, and there’s a confirmed Corsair Community forum thread about iCUE 5 corrupting SPD data on RAM modules under specific conditions. If you run iCUE and you haven’t backed up your SPD data with Thaiphoon Burner, read the SPD corruption section below before your next iCUE update.
Kingston FURY Beast and Renegade RGB
Kingston FURY RGB detection issues are less common in AC specifically than G.Skill or Corsair, but they do happen. The main culprit is usually the Kingston FURY Control software conflicting on SMBus. If you have Kingston’s software installed, close it completely before running Armoury Crate. The DRAM SPD Write BIOS fix also applies to Kingston RGB sticks on Intel boards.
Kingston doesn’t use a third-party plugin system like Corsair, so if AC can’t see FURY RGB sticks after the BIOS fix and SMBus conflict cleanup, it’s most likely a LightingService HAL issue rather than a brand-specific protocol problem. A clean AC reinstall usually resolves it.
TeamGroup T-Force RGB (DDR5)
TeamGroup T-Force was one of the two brands most affected by the AC 6.3.9.0 HAL-SDK regression. If your T-Force sticks disappeared after a December 2025 AC update, Fix 3 above is your first move. TeamGroup support has confirmed this is an Armoury Crate compatibility issue, not a hardware defect. As of late January 2026 the issue was still being tracked on the ROG Forum, so check that thread for current status.
The community workaround of using SignalRGB for T-Force control while waiting for an AC fix has worked for multiple users. SignalRGB detects T-Force DDR5 RGB correctly even when AC 6.3.9.0 can’t.
The SPD Corruption Risk: What It Is and How to Protect Yourself
I want to cover this properly because most guides either skip it entirely or mention it in one sentence. SPD data corruption is a real risk when running RGB software on RAM, and if it happens it can mess up your system stability in ways that look completely unrelated to lighting software.
SPD stands for Serial Presence Detect. It’s a small chip on every RAM module that stores your RAM’s specifications: speed, timings, voltage, XMP/EXPO profiles, manufacturer ID, and other metadata. Your motherboard reads this chip during POST to understand what RAM you’ve installed. If the SPD data gets corrupted, your board might fail to POST, might drop to low speeds, or might show incorrect RAM specs.
The corruption happens through SMBus. RGB software that controls RAM LED controllers writes to addresses on the SMBus. If that software has a bug, uses the wrong address, or gets into a conflict with another app writing simultaneously, those writes can land on SPD data addresses instead of LED controller addresses. The data gets scrambled.
Real documented cases:
- An Overclock.net thread from 2025 documents a user whose TeamGroup DDR5 7600 modules were killed by OpenRGB, with the SPD data corrupted to the point where the sticks wouldn’t POST
- The G.SKILL tech forum has a documented report of Trident Z Neo RGB SPD corruption from combined Aura and G.Skill software use
- Corsair’s own community forum has a thread about iCUE 5 corrupting SPD data on specific RAM modules under specific conditions
How to protect yourself:
Back up your SPD data with Thaiphoon Burner before running any new RGB software on your RAM. Thaiphoon Burner is a free tool that reads and exports your complete SPD data to a file. If corruption happens later, the paid version can write correct data back to the chip from your backup. Think of it as a snapshot you hope you never need to use.
Download it, run it, select your RAM module(s) from the dropdown, and click the export or save option. Store the file somewhere safe. This takes five minutes and it’s the kind of insurance that feels unnecessary until the day it isn’t.
Also: never run two RGB apps that control RAM simultaneously. That’s the highest-risk scenario for SMBus conflicts. One app at a time on the bus. If you’re switching from one RGB software to another, close the first completely, restart Windows, then open the second. Don’t just alt-tab between them while both are running.
When to Give Up on Armoury Crate for RAM Control
I’m going to say something that ASUS definitely wouldn’t: sometimes the right answer is to stop using Armoury Crate for RAM RGB entirely. Not permanently, but until AC catches up to your specific hardware or fixes a specific regression.
The two main alternatives:
OpenRGB is free and open-source and supports a wider range of RAM RGB controllers than Armoury Crate does in some configurations. The catch is that OpenRGB’s documentation warns about the SPD corruption risk on some RAM models (the TeamGroup DDR5 7600 case above was using OpenRGB), so you need to confirm your specific modules are on OpenRGB’s safe-to-use list before trusting it with your RAM’s SMBus address.
SignalRGB has proven to detect and control RAM brands that AC 6.3.9.0 broke, with multiple confirmed user reports in the ROG Forum thread. If you just need working RAM RGB right now and AC can’t deliver it, SignalRGB is currently the more reliable option for affected setups. The free tier handles basic effects and covers most RAM brands.
Neither of these is a permanent verdict against Armoury Crate. ASUS does fix regressions eventually. But there’s no reason to have your RAM sitting at stuck rainbow or dead LEDs for months while waiting for a patch when working alternatives exist.
Frequently Asked Questions
Why does Armoury Crate show my motherboard and fans but not my RAM?
Fans and ARGB strips connect via physical headers on the board, which LightingService detects reliably. RAM connects through SMBus, which requires additional conditions to work: the DRAM SPD Write BIOS setting must be enabled on Intel boards, no other software can have exclusive SMBus access to those addresses, and the AC HAL-SDK version must support your specific RAM’s LED controller. Any one of those conditions failing causes RAM to disappear from AC while other devices remain visible.
Does enabling DRAM SPD Write increase the risk of corrupting my RAM?
Slightly, in theory. With SPD Write enabled, software that misbehaves on SMBus could potentially write to your SPD data area. In practice, current versions of Armoury Crate are generally safe on this front, but it’s still a good idea to back up your SPD data with Thaiphoon Burner before enabling this setting, as insurance. The risk is low but not zero.
My RAM showed in Armoury Crate yesterday and disappeared today. What happened?
Most likely causes: an automatic Armoury Crate update (6.3.9.0 is the known problem version), another RGB app that auto-started and grabbed SMBus access, a Windows update that reset a service, or Windows 11 Dynamic Lighting activating and causing conflicts. Check your AC version, check Task Manager for competing RGB processes, and try the rescan and power drain fixes first.
Can I damage my RAM by using RGB software to control it?
Yes, in specific circumstances. Running multiple RGB apps simultaneously that both try to access the same SMBus RAM address is the highest-risk scenario. There are documented cases of SPD data corruption from OpenRGB with specific DDR5 modules, from iCUE 5 under specific conditions, and from running G.Skill Lighting Control and Armoury Crate simultaneously. Back up your SPD data with Thaiphoon Burner and never run two RAM RGB apps at the same time.
G.Skill has its own lighting software. Should I use that instead of Armoury Crate?
Use one or the other, never both simultaneously. G.Skill Lighting Control gives you direct control of Trident Z RGB effects with good reliability, but it only controls the RAM. If you want synchronized lighting across your whole build (board, fans, headers, and RAM together), Armoury Crate with DRAM SPD Write enabled is the path to that. If you only care about the RAM itself, G.Skill’s software is simpler and more stable for that specific device.
Why does only one of my two RAM sticks show up in Armoury Crate?
Usually a slot-specific SMBus communication issue. Try swapping the sticks between slots. If the “visible” stick stays visible regardless of which physical slot it’s in, the other stick’s LED controller might be faulty or its SMBus address isn’t being recognized by AC’s HAL. If the visibility follows the slot (slot A2 always works, B2 never does), it’s a board-level SMBus routing issue for that specific slot. Try different slot combinations (A1/B1, then A2/B2) and check the motherboard manual for dual-channel pairing recommendations.
Will a BIOS update fix RAM not being detected in Armoury Crate?
Sometimes. BIOS updates can include AGESA microcode updates that fix chipset SMBus initialization behavior. There are documented cases, especially on Z890 and X670E boards, where specific BIOS versions improved RAM RGB detection reliability. Check the ROG Forum thread for your specific board model plus “RAM RGB detection” and see if a BIOS version gets recommended. Before updating BIOS, make sure you have a stable version and understand the risks of failed BIOS updates on your specific board.