chris1971 Posted December 14, 2015 Share Posted December 14, 2015 Hello all, today I received my new m65 RGB in the mail and after talking with Corsair techs and searching for hours for a fix, I've decided to make an account and try you guys :) The problem is that when the mouse is plugged in either 2.0 or 3.0 usb port, windows stops all power management programs. Completely. I have a power profile set to shut the monitor off after one minute and hard disks to never shut off. If I unplug the mouse, everything resumes and works normal, my screens will power off after one minute. Once I plug the M65 back in, they stay on no matter what I try. I have tried setting different power option profiles and still nothing. I should also add that no screen savers will work either when the mouse in plugged in, and yet they work once the mouse is unplugged. I've tried everything I can think of, including disabling the USB selective suspend setting, and enabling it. both to no affect. I have all updated/current drivers and current firmware installed. I have also searched the forum to no avail. Any help will be appreciated.. Thank you all in Advance, Chris. **EDIT** I have this narrowed down to something inside the mouse that is constantly sending a signal that keeps the monitors from seeing no activity and shutting off. Using my old mouse, when the screens turn off after one min, I can unplug and plug it back in without waking them. I tried this with other mice as well. When I plug in the M65 RGB, the screens wake after approximately 1-2 seconds. Is this normal for this mouse to do this? Link to comment Share on other sites More sharing options...
terabyte Posted December 14, 2015 Share Posted December 14, 2015 Have you tried leaving the mouse plugged in BUT closing/uninstalling CUE? Does the issue still happen when CUE is closed or uninstalled? Just wondering if it's something within CUE itself that does it. Link to comment Share on other sites More sharing options...
chris1971 Posted December 14, 2015 Author Share Posted December 14, 2015 Hi. I have tried the mouse with CUE and with it uninstalled. I have not, however tried plugging the mouse in and uninstalling CUE. I will try that now. No go, leaving the mouse plugged and uninstalling CUE made no difference. Link to comment Share on other sites More sharing options...
terabyte Posted December 15, 2015 Share Posted December 15, 2015 Hmm okay, it was worth a try. Try going into the mouse properties and disable the mouse from being able to re-activate the computer, maybe that's what causing it. Are you still using Win 7 as mentioned in your system info? If so you should be able to go inside something called "Devices & Printers" and right click on the mouse listed there, then choose properties and look around there. Link to comment Share on other sites More sharing options...
chris1971 Posted December 15, 2015 Author Share Posted December 15, 2015 I have gone into mouse settings and set to not wake. That are all the settings I can find that relate to this problem. I talked to Corsair tech Art today and after being forwarded to the head tech guy, didn't catch his name, and was told they haven't ever heard of this issue and seeing how this does the same problem on my win10 laptop, to return it and try the replacement. Hopefully the second one doesn't do this. :( Link to comment Share on other sites More sharing options...
chris1971 Posted December 15, 2015 Author Share Posted December 15, 2015 So I had just purchased this mouse last week, received it yesterday, and am told by both Corsair and place of purchase, Canada Computers that I will have to pay for shipping to return and for the replacement? Oh I don't think so. I will sell this mouse locally along with my K70 and 750D. Corsair, you just lost my loyalty. Buyers beware I guess. :mad::mad::mad: Update as of 9pm est. A big THANK YOU! to Corsair for coming thru and replacing this mouse at no cost to me. Faith renewed. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.