DevBiker

Profiles are in %AppData%\Roaming\Corsair\CUE5. By default, this is C:\Users\[UserName]\AppData\Roaming\Corsair\CUE5. But typing "%AppData%" in the Start ... Run dialog will get you there. You can then zip up the CUE5 folder; that's your full backup. Restore the folder to get it all back. You will need to have iCUE completely shut down when you do this.

It's really hard to write those instructions. You have to keep it small and there are just so many options that you could go with that it's impossible to cover them all. It sounds like the fans aren't being detected at the controller (the Link hub) level. Even with the previous firmware, this would trigger a warning mode. Check your connections. Are you using a splitter? That would probably be the easiest, cleanest way to handle the front and side fans. Actually, using a hub with 2 right angle would be better from an aesthetic perspective but more expensive. You could run them chain to chain but my inclination would be that it'd be a little awkward. But my case has a completely different setup so that's really just a gut feel. If you are feeling creative ... you could, I think, keep it under the 7 device limit. But it would involve contortions that would be somewhat unnatural ... and more cables.

Yes, the cooler itself does have a finite lifetime. At some point, it is going to die, probably when it is most disruptive (because ... Murphy). Corrosion ... liquid evaporation/loss ... just plain old wear and tear ... sooner or later, it'll catch up. And yes, I'm sure it was a very good, top end unit at the time. Just like your motherboard and CPU were ... at the time. That is the nature of technology ...

Upgraded my daughter's gaming system to the new 2500X. Overall experience was excellent. I have always had a soft spot for the smaller cases, even if I don't use them on my daily machine. Fortunately, my 14 yo daughter is the perfect recipient for smaller systems. Previously, her system was in the 280X - even went to the extreme of putting in a custom loop, which was not easy. This time, it was upgrading to a new Link AIO and RX fans. The 2500 is noticeably larger than it's 280X predecessor(?) - it has to be in order to fit a 360mm radiator. But it's still smaller than a full mid tower and fits between the 2000D (which she's also had) and larger cases. The top is full mesh; we won't have the same issues with top exhaust that we had with the full glass on the 280X so running the radiator in the top as exhaust will work well. There's room for a 280mm radiator up there as well. In fact, putting a custom loop in the 2500 with the XD3 - or even an XD5 - shouldn't be difficult at all. You could do radiators in the top, bottom (but you'll have the bottom of the board blocked; make sure to connect the motherboard headers!) with a single layer of fans and push/pull on the side. You could even be super-clever and mount a pump in the back with a reservoir mounted in the front and use the side grommets to transition from front to back. Cable management, even without the nifty Project Zero motherboards, is a breeze, especially with the Link system. There's plenty of channels for routing the cables. And the back makes for plenty of space to just shove cables in when you are done messing with them. (That's the "Mullet Method" - pretty in the front, messy in the back.) And while I have an SFX PSU (Corsair SF750) in this one, there's plenty of room for a traditional ATX sized PSU (at the cost of space in the back, of course). I have a mix of RX and QX in here. The QX fans came with the radiator and the RX fans were separate. For aesthetic reasons, I did want to RX on top and bottom, with the logo facing out and right-side up. It's easy to pop them out and rearrange them based on how the fans are installed. I did discover, however, that the RX fans do not have the temp sensor that the QX fans have! That made it really easy to decide to put the QX fans on the side intake and the exhaust. This kept the balance and aesthetic with the RX fans (top/bottom) while also providing data on the intake temperature and the exhaust temperature. In particular, I like to control my case airflow fans based on the exhaust temperature; as the inside of the case heats up due to GPU waste heat, I want those fans to move more air. For the radiator, it's going to be controlled based on liquid temperature. One thing that I'll need to watch for is to make sure that the case airflow fans flow ramp up enough so that waste GPU heat isn't an issue for the radiator; we do want to ensure that the air flowing through the radiator is actually cooler than the liquid. But it's only a 3060 in there and there's plenty of airflow, so I don't think it'll be an issue. And since there's no glass to block the path of the exhaust, we won't get into a situation where the radiator temperature goes out of control. The entire side is also mesh, so there will be good cooling in the compartment for any spinning rust drives that you may put in there. This build, however, is NVMe only. One more thing - the new fan screws that come with the RX fans and the 2500 are really amazing. I guess I've been building PCs to long; it seems silly to get excited about *fan screws*. But these things are a breeze to work with. I really like them; they are super-easy to thread on a brand new fan and even easier if you want to swap something around. And no more killing your wrist trying to thread the screw the first time. How everything is connected: Link Hub Port 1: AIO => AIO Fans => Rear Exhaust Fan Link Hub Port 2: Splitter Cable with bottom fans on one side, side fans and XG7 adapter going to a single Corsair RGB Strip on the other side. This is where things got tricky. Initially, this was connected to the bottom fans (bottom fans => Side Fans => XG7) with no splitter, leaving a cable in the side area that I felt looked icky. So I rigged up some spliced-together cables to get what I wanted so that the Link cables were all hidden. (https://www.reddit.com/r/Corsair/comments/1bxkry3/a_sacrifice_has_been_made/). IMHO, Corsair really needs to have a cable to cable connector in addition to the current 4-point splitter but I digress. Using the XG7 to control the strip allowed me to eliminate both the Lighting Node Pro AND all peripheral (Molex/SATA) connections! Big thanks to Corsair for providing the 2500X, AIO, and RX Fans and making this build possible! And a shout out to the product teams that developed the Link cable system ... it is such a big difference from the old way. PS: Ugh. It was pointed out to me that the rear fan is backwards. Dammit. What happened was that I originally had an RX fan there. But then I discovered that the RX has no temp sensors and swapped it for a QX while still keeping balanced looks. Now ... it took me all of 9 minutes from the time I got the message in Discord to the time that it was fixed. Between the amazing fan screws, Link cabling, and a really easy case to get into, maintenance and little tweaks and upgrades is going to be super simple. That was part of the test and review - yeah, that's it. That's the ticket. The Toys: Compared to 280: First Boot in the new home:

Oh, that's just Asus being Asus. The motherboard temps are really mostly useless, IMHO - you don't know where they are or what they are measuring. And then you add in the sensors that aren't really there and report crazy numbers that are, interestingly. those numbers are the greatest value allowed for a signed byte.

Yes, that would actually be better. The Commander Core will let you set the pump and fan speeds based on coolant temp. You can then use the temp sensor in your exhaust flow and use the internal case temp for your case airflow fans. It takes a little work but it really lets you balance noise and cooling, as well as see the results of things that you do. Plus ... you 'd have the autodetect feature that the Lighting Node Core doesn't have. 😉

That's gonna be an oldie. The LGA 1700 barcket isn't going to be compatible with anything that was current at that time. IF you happen to have an AM4 bracket, that will work with AM5. While I understand "if it ain't broke, don't fix it" ... I have to wonder if it's worth the risk? They do have a finite lifetime, after all.

Rule of thumb for system builds: If you have to fight to get it in there, you're probably doing it wrong.

Oh! And don't run HWInfo. Or, if you do, go into the "Safety" section in settings and disable Corsair Link/Asetek support.

Crud ... no identification. It's probably in the dump. That's in %LocalAppData%\Corsair\CrashData but we don't have a way to see what you sent. See if you can grab the logs from that folder (C:\Users\[User Name]\AppData\Local\Corsair\CrashData) OpenGL drives are included in the driver package from nVidia. You may want to do a fresh install/clean install of the drivers. It can't hurt. And a 1060 will handle video from YouTube just fine. My family room machine has a 1030 - no problems at all with video.

I don't miss the point. At all. You miss the point. @c-attack reiterated it. You blew your chance to have it replaced. Sometimes things break. Sometimes it's a defect. Corsair does have a warranty and they are usually really good about it. But you'll never get the chance to see. And since you reiterated that you were made that throwing it at the wall broke it (more than once) ...

You through it against a brick and concrete wall and are complaining that it broke? I have no words.

What about any other monitoring tool? Anything like Aida or HWInfo? These have issues with iCUE that we can normally work around. One thing to now about the crash, though, is certainly the GPU usage. iCUE does use GPU for display; it's just how the QT UI library works. It uses OpenGL rather than DirectX so it is a different API than the games. OpenGL does have different drivers but both are part of the GPU driver stack. Not sure yet, though, if that would be a cause of the crash or merely part of the aftermath. You should have the opportunity to get a crash log and send it. Make sure that you do that. If there's an ID or something, get a ticket with support to look into it. Also ... take a look at the message. IIRC, it usually displays a module that caused the crash (e.g. 'goober.dll'). If you can post that, it might be interesting.

Well, temper tantrums will do that. Plastic does break, no matter how good it is, if you hit it hard enough on something hard enough or even at just the right (wrong?) angle. Congratulations? What's the wall look like? And your tantrum has killed any possibility of an RMA. So bonus! Perhaps you should seek some help with that temper? Just a suggestion; it can cause life problems that are bigger, more serious, and far more expensive than broken meeces.