ZachN556 Posted September 8 Share Posted September 8 Hi All, I have been trying to find a solution to this problem for a LONG time. iCUE seems to work okay except for the fact that when I press the DPI button on my mouse to switch between the only two DPIs that I use, my CPU load increases up to 30%. Granted I am working with an i3-9100f, but it should still not cause 30% usage just by iCUE. I have tried many fixes from enabling/disabling the Device Memory Mode, Updating all drivers & the iCUE software itself, downgrading the iCUE software, disabling all extra software from running and recently I have reinstalled Windows, activated and run all updates/drivers and I STILL have this issue. As SOON as I toggle to another DPI, the CPU load jumps to 30% and does not drop until I close iCUE and restart it. The normal iCUE CPU load for my computer is around 0.1%-0.3%. Does anyone have any idea what I could do about this? Link to comment Share on other sites More sharing options...
c-attack Posted September 8 Share Posted September 8 This is a known issue and unfortunately it looks like it did not get resolved in 5.18. It seems to trigger only once you've activated the DPI change switch on the mouse. You can use the disable feature in CUE attempt to block the initial trigger. If you do trigger it accidentally, disconnect and reconnect the mouse. That seems to break the CPU lockup for most users. 1 Link to comment Share on other sites More sharing options...
ZachN556 Posted September 9 Author Share Posted September 9 1 hour ago, c-attack said: This is a known issue and unfortunately it looks like it did not get resolved in 5.18. It seems to trigger only once you've activated the DPI change switch on the mouse. You can use the disable feature in CUE attempt to block the initial trigger. If you do trigger it accidentally, disconnect and reconnect the mouse. That seems to break the CPU lockup for most users. Thats unfortunate. I use two different DPIs depending on certain programs or games. Thanks for the info! Link to comment Share on other sites More sharing options...
Mortac Posted September 10 Share Posted September 10 Funny how I reported this crap already back in May, but of course everyone said the issue must be on my end and that I should do driver cleanups or reinstall my computer. Corsair should pay their customers for wasting their electricity bills and causing tear on their hardware. Complete joke of a company. Never again. Link to comment Share on other sites More sharing options...
cearp8858 Posted September 10 Share Posted September 10 this issue got introduced around 4 months ago, happens on my dark core pro se with slip stream but not with my original non slip stream version of the same mouse and on my 5800x3d i get around a 10-12% increase in cpu load i recently sent some dump files to a rep after posting in the reddit mega thread and submitting a support request about this issue and they mentioned that a fix should be in the next release so fingers cross that happens Link to comment Share on other sites More sharing options...
c-attack Posted September 10 Share Posted September 10 4 hours ago, Mortac said: Funny how I reported this crap already back in May, but of course everyone said the issue must be on my end Probably because you went on a long general rant about multiple issues “occurring for years”, didn’t bother to indicate any of the hardware you were using, and then didn’t reply for 4 months. Not a lot to work with there. Other users were forthcoming with details and pieced it together. Now you show up later tagging every post claiming you knew it all along. Congratulations. This issue does not affect every user or even a specific mouse model. It has been difficult to reproduce, but it does happen. Since it’s not an every instance kind of problem, you have to send them the debug logs so they can find the trigger. Link to comment Share on other sites More sharing options...
Mortac Posted September 10 Share Posted September 10 4 hours ago, c-attack said: Probably because you went on a long general rant about multiple issues “occurring for years”, didn’t bother to indicate any of the hardware you were using, and then didn’t reply for 4 months. Not a lot to work with there. Other users were forthcoming with details and pieced it together. Now you show up later tagging every post claiming you knew it all along. Congratulations. This issue does not affect every user or even a specific mouse model. It has been difficult to reproduce, but it does happen. Since it’s not an every instance kind of problem, you have to send them the debug logs so they can find the trigger. It wasn't the only place I was reporting it, though. But maybe Corsair should have someone spend an hour reading (and perhaps responding *gasp*) their forums every once in a while, but I know, too much to ask. Rants are hard to avoid when they keep releasing utter garbage software and they don't know what communication is. Been ignored by them before as you could tell from that post. Link to comment Share on other sites More sharing options...
Mortac Posted September 10 Share Posted September 10 Forum doesn't allow post editing either I've noticed. If they wanted debug logs, they could have asked me for them and we could have resolved this 4 months ago. But they clearly have no interest in solving customer issues. It is not my job to do their work. Didn't fancy replying any more when clearly they aren't active on their own support forums. And I'm not "tagging every post." I commented about the issue in two related threads except my own. Boo hoo. Link to comment Share on other sites More sharing options...
John Hoang Posted September 10 Share Posted September 10 Which mouse? Since I could not see this issue on my Nightsabre Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now