I remember someone RMA'ing it, getting a replacement board, and the same problem 1 to 2 weeks later. This was prior to it being confirmed that Aura was the problem and the individual thought it was a mobo issue.

If you do successfully exchange it, for the love of color, DON'T run Aura until it's fixed, lol.

My system is running pretty well now EXCEPT for Aura and the RGB system. I've got a solid reliable CPU overclock, and as of the AGESA 1.0.0.6 beta BIOS I can get my 3200mhz memory working at rated speed without a Bclk increase.

Unless some major thing happens, this system is here for the long haul. I've used for lots of stuff now and very happy with it as it stands. Fix the RGB and Asus has mostly delivered what they promised with this board.

Now, I had to manually adjust a lot of things that should be done by the BIOS and that's not trivial -- for folks without technical savvy this board could be a nightmare. So Asus/AMD still have a problem. But for someone like me it's a win right now, RGB or no RGB.

I've speculated that maybe it's a bit of both. To sum up: the lighting is controlled by a dedicated microcontroller that talks on a serial bus called I2C. The microcontroller has RAM and a ROM burned with the program to do the lighting effects.

What I think may have happened is that there is a flaw in the microcontroller that has resulted in some kind of data corruption that freezes or crashes the program. If there isn't a way to reinitialize that controller's data, it may not be recoverable without an RMA. Not the same thing quite as a hardware failure, just some code on the lighting controller that has an unanticipated path to failure.

What has confused the issue is another RGB problem involving RGB RAM (which I don't have) which creates a problem when the lighting control software and other "direct hardware access" type of programs conflict. What is needed is what's called a "mutex" or "mutual exclusion" object that acts as a go between and prevents conflicts. This is a common approach when programs must both access the same hardware. It was not done for Aura and the other software that may be conflicting with Aura and may explain the memory problems as well. The problem can be so severe that the SPD data on DIMM's becomes corrupted and the memory ceases to function until the SPD is rewritten with good data.

So, a host of problems involving the lighting and the fact that we may have one common symptom for multiple causes is hamstringing getting it definitively fixed. Some folks have found short term workarounds that seem to fix it but it eventually breaks again. I've had some arguments on this very board with some folks who claim to have "solved the problem" but the solution usually involved the digital equivalent of clicking your ruby slippers together and chanting "there's not board like ROG, there's no board like ROG" until you get back to Kansas...

Yes, I have tried I think every "Fix" I came across. I went as far as installing a fresh copy of windows, which wasn't a big deal since it was rather "fresh" to begin with. Also rolled back the Bios to 1002. Cant even get a flicker. What made me think it was more a hardware issue is originally the MB did not show in the Aura software but after leaving it unplugged for a few hours it has been back in the software every time. Just nothing lights up. My memory on the other hand (Trident Z RGB) has worked almost flawlessly. I shall get back to clicking my shoes together and chanting all various sorts of old movie lines. Instead, maybe I should go calculate the air-speed velocity of an unladen swallow.

African or European?...