Tairom

A lot of the comments over the last couple of pages have turned a bit snippy. Ultimately this is due to building frustration with the situation Corsair has chosen to place their customers in. But as far as the forum here is concerned, it was/is due to my being extremely vocal on the issue and the beta team trying to defend Corsair in their absence in the thread. The early parts of the thread are very important in an informative way, and as such, 2 days ago I decided to go through my posts here and delete anything that was of a commentary nature and leave anything that was diagnostic. Unfortunately, replies to some of that commentary are still here, and apparently generating more commentary. So, I would like to ask my fellow users to please stick to just being helpful and not let the thread devolve into a war of words that will eventually get the thread locked down. Things to realize before posting: -Users with Beta Team in their user tag are NOT Corsair employees, but loyal enough that they will defend Corsair feverishly. -Corsair employees have "Corsair" in their username, but will only appear on the forums to comment on the joke threads or similar. They WILL NOT address their customers issues here or ever admit any mistakes the company may have made. -If you do not work for Corsair, the frustration vented here is not directed at you. You may be the recipient, but you are not the target. It is impossible to hit a target that never shows up (see point #2). My point is, let's try to bring the tone down a bit and realize that the people you are communicating with did not cause your frustration, and though they cant technically resolve your frustration, they are trying to make the problem better until Corsair decides your particular problem is important enough to officially address.

Not that it is unexpected, but just confirming that the high CPU utilization bug persisted trough Windows 10 preview build upgrade from 17686 to 17692.

Well, I personally think people have been looking at it backward. Everyone is looking at the device definition XMLs. But, like you said too many devices are causing the issue to appear. So wouldn't it make more sense that the command processor that is reading the XML files is more likely at fault? Something "common" among the different device XMLs is tripping up the processor IMO. Early on in the conversation, someone compared the XML files of the H115i cooler between this build and the previous build. They found that only 10-12 lines had any difference and changing any of those lines made no difference in the problem.

Really? The team has mostly been in Taipei up until Monday. Today is Thursday. The process is to identify as many issues as possible, write fixes for them, internally test said fixes, rewrite fixes when and where needed, and address any new issues created by changes made to address old issues. And, you think 3 1/2 business days is "enough" time? How about making sure you're not still asleep and dreaming when you decide to post how someone else is doing their jobs. BTW, if you look up many of my posts on these forums, I am very critical of Corsair, but only where it is realistic. I am definitely not a Corsair fanboi. If anything, I am considering replacing all of my Corsair equipment with other brands.

Out of curiosity, are you guys referring to Void Pro USB or wireless? I have the wireless and lighting effects are active. I was running 14-20% CPU but to drop below 2% all I had to do was remove the H115i XML profile file.

OK, just read DevBiker's post about the H115i being a known problem with this build.

Well, I tried to eliminate each of the possibilities one at a time. Nothing I did had an effect. After each change, I exited and restarted the iCue software, then monitored the CPU usages for at least 2 minutes without doing anything else on the computer. Here are the things I did and in the order I did them. 1- Moved all XML files that did not directly pertain to my hardware to a sub-folder 2- Unplugged Void Pro Wireless USB Dongle 3- Unplugged Void Pro Wireless USB Cable 4- Moved Void Pro Wireless XML files to separate sub-folder 5- Unplugged ST100 Stand 6- Moved ST100 XML file to separate sub-folder 7- Unplugged MM800C 8- Moved MM800C XML file to separate sub-folder 9- Unplugged Glaive Mouse 10- Moved Glaive mouse XML file to separate sub-folder 11- Unplugged K95 Plat. USB pass-through port 12- Unplugged K95 Plat keyboard 13- Moved K95 XML Files to separate sub-folder Obviously, I was unable to "disconnect" my AXi1200 PSU or my H115i CLC. So as things stand now, I am typing this from my tiny tablet Bluetooth keyboard and using an old Logitech mouse atm. The only devices showing in iCue right now are the PSU and CLC. iCue is registering 10.2% CPU while minimized and 16.1% CPU load while closed to the system tray. iCue settings are as follows: Debug logging is unchecked Start on system startup, enable SDK, Show only connected devices are all checked OSD is not checked or enabled No items are assigned to the dashboard No items are checked in the sensor logging section What more can I provide testing for Sol?