Jump to content
Corsair Community

CUE 1.12.75 CPU Utilization


Maara

Recommended Posts

Is this with the program running in the background or open?

Do you have any CUE devices connected?

 

My k95 is connected, the CUE is running in the background..

Tested few times and it really makes unreasonable cpu load even its doing nothing.. I was not facing such issue before the most recent update (but I skipped 1 or 2 versions)

Link to comment
Share on other sites

Can you upload your latest log file? CUE might be encountering errors (Not 100% sure though)

What OS are you on?

 

Log files can be accessed by clicking Settings > Support > View logs.

 

Sure.. I just tried few things and noticed that this happens when there are more users logged on the computer.

When I switch to another user, the CUE starts there and causes the cpu utilization. As long there is only one user logged on the pc, everything is ok.

I am sure that someone mentioned this issues in some other topic so I am obviously facing the same problem.

Here is the log:

 

[2015-11-28T15:28:15]: UserSessionInfo: locked changed to 0.
[2015-11-28T15:28:15]: UserSessionInfo: connected changed to 1.
[2015-11-28T15:28:15]: UserSessionInfo: local changed to 1.
[2015-11-28T15:28:18]: UserSessionInfo: locked changed to 0.
[2015-11-28T15:28:18]: UserSessionInfo: connected changed to 1.
[2015-11-28T15:28:18]: UserSessionInfo: local changed to 1.
[2015-11-28T15:28:23]: Created new device object: K95 RGB; ready: 0
[2015-11-28T15:28:23]: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_01&col01#8&1f53435&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2015-11-28T15:28:23]: Device profile (meta) for device vid=1532 pid=7 not found.
[2015-11-28T15:28:23]: Attached to device object K95 RGB: b=1 a=1
[2015-11-28T15:28:23]: Device profile (meta) for device vid=1532 pid=7 not found.
[2015-11-28T15:28:23]: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_00#8&5452a31&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2015-11-28T15:28:23]: Attached to device object K95 RGB: b=1 a=0
[2015-11-28T15:28:23]: Initializing K95 RGB...
[2015-11-28T15:28:23]: Initialized (st=1) K95 RGB.
[2015-11-28T15:28:25]: Device insertion processing complete for K95 RGB.
[2015-11-28T16:24:03]: UserSessionInfo: connected changed to 0.
[2015-11-28T16:24:03]: Requesting working state leave because session disconnected.
[2015-11-28T16:24:03]: Leaving working state.
[2015-11-28T16:24:03]: UserSessionInfo: connected changed to 0.
[2015-11-28T16:25:08]: UserSessionInfo: locked changed to 1.
[2015-11-28T16:25:08]: UserSessionInfo: locked changed to 1.
[2015-11-28T16:25:09]: UserSessionInfo: connected changed to 1.
[2015-11-28T16:25:09]: UserSessionInfo: connected changed to 1.
[2015-11-28T16:25:22]: UserSessionInfo: locked changed to 0.
[2015-11-28T16:25:22]: Requesting working state enter because session connected.
[2015-11-28T16:25:22]: Entering working state.
[2015-11-28T16:25:22]: UserSessionInfo: locked changed to 0.
[2015-11-28T16:25:22]: Device vid=1b1c pid=1b11 is marked 'slow startup'.
[2015-11-28T16:25:22]: Device vid=1b1c pid=1b11 is marked 'slow startup'.
[2015-11-28T16:25:22]: Device profile (meta) for device vid=1532 pid=7 not found.
[2015-11-28T16:25:22]: Device vid=1b1c pid=1b11 is marked 'slow startup'.
[2015-11-28T16:25:22]: Device profile (meta) for device vid=1532 pid=7 not found.
[2015-11-28T16:25:22]: Device vid=1b1c pid=1b11 is marked 'slow startup'.
[2015-11-28T16:25:22]: Device vid=1b1c pid=1b11 is marked 'slow startup'.
[2015-11-28T16:25:28]: Created new device object: K95 RGB; ready: 0
[2015-11-28T16:25:28]: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_01&col01#8&1f53435&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2015-11-28T16:25:28]: Attached to device object K95 RGB: b=1 a=1
[2015-11-28T16:25:28]: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_00#8&5452a31&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2015-11-28T16:25:28]: Attached to device object K95 RGB: b=1 a=0
[2015-11-28T16:25:28]: Initializing K95 RGB...
[2015-11-28T16:25:28]: Initialized (st=1) K95 RGB.
[2015-11-28T16:25:29]: Device insertion processing complete for K95 RGB.

Link to comment
Share on other sites

I am facing exactly the same problem. I upgraded to 1.12.75 yesterday (from 1.8.122) and found that each logged-in user had CUE running at 17% - but the first logged-in user was running at 0%

 

This is on my Win7 desktop, and on both my Win8 and Win10 laptops.

 

In addition, when I switch users I get an error message saying that the keyboard isn't connected - this remains for around 6 seconds, during which the keyboard functions only as a basic keyboard - it then springs into life.

 

I saw somewhere a suggestion that this was because of the way that USB is handled in Windows but, as a programmer, I know that this isn't the case (or more likely the way that CUE is handling USB) - and it doesn't happen on 1.8.122, so I've reverted to 1.8.122 and it's working find on all three machines.

 

My 1.12.75 logs are pretty much as the previous post (complete with the 6 second delay before "Created new device object") - my 1.8.122 logs didn't show that delay (nor did they show "Created ne device object"

 

Note that I can't copy the logs because they were deleted during the rollback.

Link to comment
Share on other sites

We are currently looking into this

 

Same problem here with latest CUE on Windows 10 and Strafe RGB purchased few days ago. This is very annoying and me think to uninstall CUE to get rid of the problem...

 

Any news on the problem? I am thinking of buying a full Corsair PC but this not a very good user experience so far just for the keyboard (at this price)...

Link to comment
Share on other sites

  • 2 weeks later...

I am running the latest Windows 10 build and I routinely see CUE utilization in the 35-40% range on an overclocked I5-4690K CPU running at 4.55 ghz.

 

I have a K95 RGB keyboard that CUE is supporting. I also have a Corsair headset and water cooler in the system and thus iLink and the Corsair headset software is running as well

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...