slogan19

Different case, 680X, but I had an issue with a faulty power button. The entire control panel module was replaced under warranty, I just had to submit proof of purchase. Swapping it out was a bit of a pain, but better than breaking the whole system down for sure.

I had an issue with mine as well in a new build around Thanksgiving. I got the case early so I already had 8 fans in and everything wired up with a CoPro. I bench test and everything is fine with the components. I get everything installed, plug in the psu, everything lights up and then goes dead. Hit the power button, nothing. I made sure the case panel was wired up correctly to the motherboard, still nothing. I disconnect the case wires from the motherboard, push the on button on the motherboard and it works flawlessly. The only possibility then is the power button on the case is bad. I opened a ticket and was sent a new one a few days later. Side note there...I asked support if there was an installation procedure and was told "just screw it in". Well, when it arrives I discover that it mounts from the top, I assumed from their short and sweet answer that it mounted from inside the rear compartment. So, just screwing it in first requires removing the entire top panel which requires removing the top glass and even then the top panel has a flange that slides under the front panel so I had to pry it loose at the top as well. After that, it was indeed as simple as screwing it in. Other than the control panel, the case was in perfect condition and purchased from Newegg.

Here's what I did in the same case. I'm sure it's not optimal airflow, but the cpu (5 3600x) stays around 50 and gpu (rtx 2070) around 70 during gaming so it's fine. 3 in front as intake of course. 2 120 LL as intake in the top pushing through a 100i radiator mounted below (I used the MLs in a different computer). 1 140 LL in the rear as exhaust. 2 140 LL in the bottom as exhaust. My case sits on the floor so you get optimal ring bling. Plus, it helps keep my feet warm. I didn't do any adjustments to fan speeds, they're all set to quiet. The top fan speeds are controlled by the cooler, the rest into a CoPro. And it is quiet, my external hard drive is the loudest part of my system at idle even with 8 fans. Under load the video card fans run around 75% to keep it around 70C. So, I have a lot more cooling I could be doing even despite the less than optimal configuration and the temps are fine the way it is.

Wanted to relay my experience. Just got a new monitor last night, Dell s3220dgf. I have an RTX 2070 card. I tried out Freesync/G sync compatibility last night and it worked fine. I added the ls100 this morning and enabled video lighting. I went to play Metro Exodus, not the best choice to test as it takes over lighting anyway, but regardless, noticed g-sync compatibility wasn't working. After playing around with a number of things using the pendulum demo I narrowed it down to an iCue conflict (not my detective skills, iCue happened to crash while I was testing and I noticed sync was working). Further digging pinned it on the video lighting. So, I did a google search and here I am. In the demo with the video lighting on I can't even select g-sync, it won't let me, and my monitor is pegged at 164hz. Switch it to audio lighting and G sync works as it should.

I just did an install in a new 680x case. System bench tested fine, I get everything installed, apply power, it turns on for a couple of seconds and switches off. If I unplug the front panel connectors and power on via motherboard, both via start button and jumping pins, it operates as normal. I've submitted a ticket about the power button as it's the only conclusion I can come to. The light works fine and when I push it it pushes in, but it would appear the circuit is stuck. Unless anyone else has another suggestion. It's been running for 12 hours when powered on via motherboard start button and front panel connector unplugged so everything else seems to be fine. My first question is if I swap the pins to put the connector for the reset button as the power button will that work as a temporary solution so I don't have to reach in the case to turn it on? Second question, how hard is a power button to swap out? thanks!

No crashes since renaming the two CPUID files. It would really be nice for this to get figured out. This isn't an old system like my X79. This is an off the shelf computer from Micro Center on a b450 board. I haven't installed chipset or usb drivers so maybe that could solve my problem, but it seems like you would want the product to work with Windows drivers. Anyway, hopefully the rename is a permanent solution, I still had problems despite renaming on the X79. If you need a test system I will be replacing that one next week and will have it available after that. Although, this clearly isn't a board specific problem.

Crashed again with node unplugged from usb, I guess I'll try renaming cpuid.

It crashed again, I've unplugged the LNP from USB, still plugged in to SATA, will update.

Also, I had the same fan/hub/LNP in my previous office computer which had a Crosshair Formula IV board and it worked fine for 4 days without issue.

I didn't try unplugging the LNP, do you mean just as a test? You may be on to something in that I had iCUE installed on the system on Tuesday and it ran fine, it didn't actually crash until I added the fan/hub/LNP. Although there's not much of a sample size. The firmware on the LNP is the latest. I was trying to keep it as simple as possible so I don't have any Asrock software installed (none came pre-installed as far as I can tell). The only thing I saw pre-installed aside from all the usual Windows stuff was Nvidia software. Should I try updating motherboard drivers? I did enable the hardware monitoring in the iCUE software dashboard and checked the boxes for all my components. I also had enable sdk turned off. I forgot to mention these in my original post. thanks for your help

I need help from the community, sorry if this runs long it's a bit of a story. I'm planning a new build in a Corsair ecosystem. I already have the case, 680x, extra fans installed, commander pro, rgb strips, etc, just waiting on the expensive stuff to hopefully go on sale next week. Part of why I'm doing this new build is my existing computer has the black screen crash issue with iCUE. It's on an X79 platform and seems to be a popular issue with that board. The build I'm planning is going to be X570 with a Ryzen 5 3600. This week I also upgraded my office computer, just an off the shelf PowerSpec G502 from Micro Center. It has an Asrock b450 Pro4. It ran fine for 2 days. Last night, I threw in a data drive, an optical drive, changed out the rear exhaust for an ll120 that I have left over from next week's build and a lighting pro. I hook everything up, works fine. I go in this morning and it's crashed, same black screen, still running and the only recourse is to power cycle. So, I'm very discouraged. I don't want to abandon Corsair, I like the product. I'm planning to buy your memory, your psu, already have your case and a boatload of your fans. I do however want it to work without being paranoid that it's going to crash. The computer I'm about to build will be a media streamer and I want it to be up 24/7 without worrying about having to go down to the basement to reset it. Like I said, the new computer ran fine for 2 days prior to adding components and iCUE last night. Given that and the nature of the problem I have to think it's iCUE causing the problem. I haven't tried renaming cpuid yet, maybe that will fix the issue on the office computer. Although I don't think I should have to do that, if that aspect of the software is causing this many problems then take it out already. My question is should I rethink my main build? Is there a platform that is more stable for iCUE than others? Will a z390 system be better than the x570 I'm planning? It seems silly to base a system around your lighting, but I already have those components and want them to work consistently. For the developers, why can't this be figured out? I was ok with the problem not being able to be solved on the old computer, it's an older motherboard, you can't be expected to make sure every piece of hardware ever invented is compatible. However, the office computer is an off the shelf computer on a newer motherboard, how can I still have this same issue? This is very frustrating. I haven't tried updating chipset drivers, apparently I can't easily update the BIOS without possibly losing my Windows license. Is there anything I can try short of renaming cpuid? Again, it doesn't seem like I should need to mod your software for it to not crash my computer. thanks for your time. I'm sorry if this comes off mean, I'm just really disheartened that I'm having the same issue with a new computer as I did with my old one. And since part of the reason I'm changing is because of this issue to begin with it makes me just want to give up on the project, or at least the product line. However, clearly plenty of people are getting this to work without issues so there must be a solution.