c-attack

Ok. Does seem like a bug and something they’ll need to correct. A lot of the devices with older or more limited hardware save capabilities seem to have some issues with the revamp into Device Memory Mode. It appears to have a problem with the hardware mode to software mode handoff and there have been some other complaints about this in both directions (Software <-> DMM). I can’t think of a workaround for this, but you might delete the existing software lighting effect pattern and then re-add it. A next step would be to export the profile, delete it, then re-import the saved profile, but this is all fishing and no guarantees it will do anything to resolve the issue.

This is not going to be related to most of the discussion in this thread. The problem here was a sensor data problem going back to last year. CUE 5.14 introduced a bunch of new issues and yours is a new one. There are multiple reported issues with presets and custom curve behavior in the new version. This is first I have seen reported for any Pro XT AIO. One thing that might be related is your curve profile is not appropriate for a water cooled system. You have set up a graph for cpu temp based cooling with the bulk of your curve above 60C. Normal operating temperature is typically 25-40C for liquid temp, with an effective max of around 50C and a critical device level at 60C. In your current curve you have the fan set to run below 20% PWM and it may not be capable of that and turned itself off. Try checking in increasing 5% blocks to see if the fan activates at a specific point. I don’t have a Pro XT to test, but most with a zero rpm mode turn on around 25%.

You have to enable XMP or DOCP to activate the 4600 set of timings. Whether or not that is beneficial is another matter. Most AMD DDR4 boards will drop you down a gear to go to that frequency and it may not be worthwhile. There’s also the question of whether a 5700G can run 4600 at all.

After Windows loads, the KB goes dark, and you then you open CUE... is the lighting effect that should be on K55 Pro there and displayed as active? Or is it deleting the lighting effect each time?

Meaning a 13700KF or 14700KF? Their website clearly lists 12700KF compatibility and they created a QVL list specifically for your CPU. There are a ton of Corsair kits going up to 6600. I might understand if you were trying to run 6600 and having problems booting to windows, but that usually isn't a Q-code 55. Also, if it can't boot at 4800 JEDEC, something else is wrong. All motherboards should be able to boot at 4800, even when things are not quite perfect. A Q-code 55 is a fundamental block and indicates a major issue with RAM, CPU , or MB, although it can include really simple stuff like not having the module seated properly or the CPU block is too tight, etc. So you tried a different kit already and it still won't boot? That is worrisome. Also, be aware Asus Support may stop trying if you reveal you are not using a memory kit from the QVL. Not being tested does not mean the CPU shouldn't boot. Don't let them steer you that direction. Unfortunately, if it does not change with a new RAM kit, then it may indeed be a CPU or MB issue and that can be a nightmare to prove and resolve.

If it’s being that difficult and won’t boot at default, there may be an issue with the RAM. Any board should be able to boot at the default 4800. If it won’t boot either stick alone, then there is likely a hardware problem with the RAM, CPU, or motherboard. The RAM is the easiest to swap in/out. Try something else.

It isn’t quite literally no memory installed and also will pop if there is no communication between CPU and RAM. Besides an actual CPU issue, this is more commonly seen when you over-tighten the CPU block and put too much pressure on the CPU and pins. Try one stick in A2. If it does not boot, check the cpu mount.

I don’t think so. It’s likely how the mouse is set up. Both front R/L and rear R/L buttons lead to the same place and then a switcher sets the active side of the mouse. Could have been deliberate to prevent accidental activation on the fingers side, but also there aren’t any mice in that price bracket with an extra two programmable keys. However, the mouse probably should not be marketed as having “8 fully programmable buttons”.

It is. The scroll wheel effectively "slips" and creates an oppositional movement to the direction you were going. If you are still in the warranty period for your mouse, contact Corsair Support as a means to replacement. If the warranty has expired, there are a lot of online videos and directions about how to take the wheel off and clean it. This works for a fair number of people.

It’s left OR right side buttons… not both.

You need to contact Corsair Support so they can send you the FW file and instructions to side load it. The later is fairly simple and available, but getting the right FW file is critical. Using the wrong one will turn your KB into a paperweight. Get a leg up on Support by doing some things in the original ticket. Include your full name and address, even though it’s obviously in your account data. Provide your purchase invoice for the KB, even though this isn’t a warranty claim. Take a picture of the KB serial number and include it in the ticket. Hopefully that gives the responder no choice but to give you what you need first time and not a week of back and forth emails.

This is a known issue and CUE does not properly hand off to Device Memory Mode before it enters S3 sleep. Enabling Device Memory Mode with the proper black static color prior to entering sleep is the only known workaround, although if you quit CUE prior to entering S3 it should do the same. This is something they will need to correct. DMM is the “new” Hardware Mode in a toggle state. However, it’s not just a UI change and altering the software<->hardware exchange seems to have caused a lot of other issues.

It's in the CPU block area, although the difference in temperature for the liquid between post heat pick up and post radiator heat release is only about 1C difference. That's about as much heat as it can take out of the water in a single pass. This is normal. Your CPU and coolant temp are only the same when your CPU Voltage is zero. No voltage and heat from the underlying pins and the CPU, block, and liquid can all be the same temp. As soon as you start applying voltage to the underside of the CPU it will heat up. The CPU is cooled conductively, not by the liquid. All CPU cooling methods are conductive. It's how they get rid of their waste heat that varies a little. The liquid serves as a transport from the CPU block (heat pick up) to the radiator (heat drop off), where you try to blow it somewhere else. Ideally, your liquid temp never goes up at all and it dumps all added heat in a single pass. That isn't possible on any normal consumer market water cooling system. The liquid temp is the baseline or lowest possible CPU temp, so for each +-1C of coolant temp, you change your CPU temp by the same +-1C. With a AMD 7700x, you may see high CPU temperature (voltage + material limits), but you probably don't make a ton of watts at the CPU and thus the AIO doesn't have that much to get rid of. 10-20 min of CPU-Z might only raise your coolant temp 4C depending on fan speed. Keep that in mind when setting up fan curves. You don't need to be super aggressive. Fans dissipate heat from the water. They won't cool the underside of the CPU.

You need to list your fan type and controller. There were major changes to CUE and particularly the CUE Link system two weeks ago. I also assume you are referring to Murals, which can have it's own configuration issues. Do your fans show in their normal Profile Name -> Lighting Effects page?

The “preview” is not real nor has it ever been. It always was the software version. So if you preview color wave in the Hardware Lighting section, it shows you a color on every fan for all prior generation devices. Then when you actually quit CUE, you get one color wave per channel. CUE Link devices and fans have higher hardware mode capabilities and can do the full version of most effects. QX and RX fans can do more, but it can get complicated with the linked devices and it uses a “lowest capable device” system to set possible effects. Pairing the CUE Link AIO on the same hub as QX fans may lower the number of lighting effects options or change the hardware mode output. With this new DMM toggle state, even linked devices like a CUE Link XD5 and XC7 Elite will use one wave per channel. It’s not clear yet if this is a deliberate necessity or error. CUE Link devices are missing their custom/static color option, so there is at least one thing to correct. I can’t replicate your flashing, but I suspect that’s because I don’t have a CUE Link AIO in the system and that will be the lowest capable lighting device. All of this unrelated to the FW change allowing 24 devices, but is central to the new Device Memory Mode introduced with CUE 5.14 and it's functionality.