fyew-jit-tiv Posted January 26, 2016 Author Share Posted January 26, 2016 Back on the subject........ Here are the resolutions that work.... 1024x768 1152x864 1200x960 When i get to 1280x720 the problem starts. Unplug all other monitors leaving just one (any resolution) Cue works Fine. Again please note that this is happening on two different systems that are setup totally different that only have Corsair products in the middle. Link to comment Share on other sites More sharing options...
Toasted Posted January 27, 2016 Share Posted January 27, 2016 I have a 1440p monitor and a 1080p monitor, Give me a few days and i'll see what happens on my side. Link to comment Share on other sites More sharing options...
fyew-jit-tiv Posted January 27, 2016 Author Share Posted January 27, 2016 I have a 1440p monitor and a 1080p monitor, Give me a few days and i'll see what happens on my side. Thanks Fella. Looking forward to your response. :D: Link to comment Share on other sites More sharing options...
Toasted Posted January 30, 2016 Share Posted January 30, 2016 I was not able to produce the issue you are seeing. I had created profiles for Chrome, File Explorer and Microsoft Word. The profiles switched fine. This was with the STRAFE RGB FW 1.33 and CUE 1.14.43. Link to comment Share on other sites More sharing options...
fyew-jit-tiv Posted January 30, 2016 Author Share Posted January 30, 2016 I was not able to produce the issue you are seeing. I had created profiles for Chrome, File Explorer and Microsoft Word. The profiles switched fine. This was with the STRAFE RGB FW 1.33 and CUE 1.14.43. THanks for that but check this.... I got hold of a K65 RGB today and yes everything works..... Can someone explain this because I can't.....! Link to comment Share on other sites More sharing options...
Jkraghify Posted January 31, 2016 Share Posted January 31, 2016 THanks for that but check this.... I got hold of a K65 RGB today and yes everything works..... Can someone explain this because I can't.....! Maybe you changed a setting unknowingly? As far as I know, the profile switching is controlled by the computer - not by the keyboard. It shouldn't matter which keyboard you use. Link to comment Share on other sites More sharing options...
fyew-jit-tiv Posted January 31, 2016 Author Share Posted January 31, 2016 Maybe you changed a setting unknowingly? As far as I know, the profile switching is controlled by the computer - not by the keyboard. It shouldn't matter which keyboard you use. Nope.... Because I plug back in the Strafe and the problem returns... I have tried everything from removal of software to removal of reg keys and even re-install OS with NO 3rd party software or hardware installed.... I only get this with the Strafe. Unfortunately I have to give back the K65. Link to comment Share on other sites More sharing options...
Toasted Posted February 1, 2016 Share Posted February 1, 2016 Upload your latest CUE logs when you plug the STRAFE keyboard in and attempt to switch profiles. It may show something useful. You can access the logs by clicking Settings > Support > View logs. Link to comment Share on other sites More sharing options...
fyew-jit-tiv Posted February 1, 2016 Author Share Posted February 1, 2016 Upload your latest CUE logs when you plug the STRAFE keyboard in and attempt to switch profiles. It may show something useful. You can access the logs by clicking Settings > Support > View logs. Thanks for response..... Here is what I have done... Again I have re-installed OS. No third party H/Software Just CUE and Corsair Hardware. I am also doing this on the X99-M WS as it has USB 3.0, 3.1 & 2.0 and tested with all usb ports. Here is the log files requested. [2016-02-01T10:53:31]: UserSessionInfo: locked changed to 0. [2016-02-01T10:53:31]: UserSessionInfo: connected changed to 1. [2016-02-01T10:53:31]: UserSessionInfo: local changed to 1. [2016-02-01T10:53:31]: UserSessionInfo: locked changed to 0. [2016-02-01T10:53:31]: UserSessionInfo: connected changed to 1. [2016-02-01T10:53:31]: UserSessionInfo: local changed to 1. [2016-02-01T10:53:31]: UserSessionInfo: locked changed to 0. [2016-02-01T10:53:31]: UserSessionInfo: connected changed to 1. [2016-02-01T10:53:31]: UserSessionInfo: local changed to 1. [2016-02-01T10:53:31]: Created new device object: M65 RGB; ready: 0 [2016-02-01T10:53:31]: Created new device object: VOID Wireless; ready: 0 [2016-02-01T10:53:31]: Created new device object: STRAFE RGB; ready: 0 [2016-02-01T10:53:31]: Device profile (meta) for device vid=1b1c pid=1c06 not found. [2016-02-01T10:53:31]: Attached to device object STRAFE RGB: b=1 a=0 [2016-02-01T10:53:31]: Device profile (meta) for device vid=eef pid=1 not found. [2016-02-01T10:53:31]: Initializing STRAFE RGB... [2016-02-01T10:53:31]: Failed to open device: vid=1b1c pid=1b12 path=\\?\hid#vid_1b1c&pid_1b12&mi_00#7&1cd728ca&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-02-01T10:53:31]: Device profile (meta) for device vid=eef pid=1 not found. [2016-02-01T10:53:31]: Failed to open device: vid=1b1c pid=1b20 path=\\?\hid#vid_1b1c&pid_1b20&mi_01&col01#7&19951019&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-02-01T10:53:32]: Initialized (st=1) STRAFE RGB. [2016-02-01T10:53:32]: Attached to device object STRAFE RGB: b=0 a=0 [2016-02-01T10:53:32]: Attached to device object VOID Wireless: b=1 a=1 [2016-02-01T10:53:32]: Failed to open device: vid=1b1c pid=1b20 path=\\?\hid#vid_1b1c&pid_1b20&mi_00#7&31589c5e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-02-01T10:53:32]: Attached to device object VOID Wireless: b=1 a=5 [2016-02-01T10:53:32]: Initializing VOID Wireless... [2016-02-01T10:53:32]: Failed to open device: vid=1b1c pid=1b12 path=\\?\hid#vid_1b1c&pid_1b12&mi_01&col01#7&349ab50f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-02-01T10:53:32]: Attached to device object M65 RGB: b=1 a=1 [2016-02-01T10:53:32]: Attached to device object M65 RGB: b=1 a=0 [2016-02-01T10:53:32]: Initializing M65 RGB... [2016-02-01T10:53:32]: Device profile (meta) for device vid=d8c pid=5 not found. [2016-02-01T10:53:32]: Initialized (st=1) VOID Wireless. [2016-02-01T10:53:32]: Device insertion processing complete for STRAFE RGB. [2016-02-01T10:53:32]: Device insertion processing complete for VOID Wireless. [2016-02-01T10:53:34]: Initialized (st=1) M65 RGB. [2016-02-01T10:53:35]: Device insertion processing complete for M65 RGB. There are a few errors but in jargon one does not understand. I hope you do. Another thing to note I looked in the advanced report in cue and found this ::: Video hardware Adapter name : NVIDIA GeForce GTX 980 Ti Driver files : nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um,nvwgf2um Driver version : 10.18.13.6175 RAM : 1 MB Max refresh rate : 75 Min refresh rate : 23 Notice the ram is wrong should be 6GB. This is also the case with my other system which carries a TitanX. Cue reports 1MB video ram and it should be 12GB. Not sure if that proves/shows anything. Link to comment Share on other sites More sharing options...
Elestriel Posted February 1, 2016 Share Posted February 1, 2016 1B20 is your Strafe RGB and 1B12 is the M65. It's really weird that in the logs, it says it's trying to attach to a VOID Wireless, but shows the PID of the M65. It also appears to be looking for 1C06, which I find really strange because that's not a Corsair controller ID that I know of. I don't think you ever mentioned having a VOID. Have you tried any of this without it connected or plugged in? Link to comment Share on other sites More sharing options...
fyew-jit-tiv Posted February 1, 2016 Author Share Posted February 1, 2016 1B20 is your Strafe RGB and 1B12 is the M65. It's really weird that in the logs, it says it's trying to attach to a VOID Wireless, but shows the PID of the M65. It also appears to be looking for 1C06, which I find really strange because that's not a Corsair controller ID that I know of. I don't think you ever mentioned having a VOID. Have you tried any of this without it connected or plugged in? I cant answer why this looks weird but the one thing I do know is this problem is related solely to Cue and the Strafe. I mentioned in another post that I got use of a K65 for a day and all work as it should but soon as I connected the strafe the problem starts. As for the Void I'm sure I did mention it but if I didn't then for sure I have tried this without Void on a clean install. I don't and never had the Void connected to my other system which shows the same problem. Whats your take on Cue only showing 1MB video ram for both my GPUS? Link to comment Share on other sites More sharing options...
Toasted Posted February 1, 2016 Share Posted February 1, 2016 I wouldn't worry about CUE showing only 1MB of video RAM. Its the same on my side as well. If you did not have the VOID Dongle connected and CUE shows it attaching it, could be a hardware id issue. If possible, disconnect any CUE devices apart from the STRAFE RGB and restart CUE. Then upload the latest log here. Link to comment Share on other sites More sharing options...
fyew-jit-tiv Posted February 2, 2016 Author Share Posted February 2, 2016 I wouldn't worry about CUE showing only 1MB of video RAM. Its the same on my side as well. If you did not have the VOID Dongle connected and CUE shows it attaching it, could be a hardware id issue. If possible, disconnect any CUE devices apart from the STRAFE RGB and restart CUE. Then upload the latest log here. Kinda disagree that the GPU readings shouldn't matter but for now I'm willing to follow you on this and see what happens. Here is the results you requested. [2016-02-02T09:23:52]: UserSessionInfo: locked changed to 0. [2016-02-02T09:23:52]: UserSessionInfo: connected changed to 1. [2016-02-02T09:23:52]: UserSessionInfo: local changed to 1. [2016-02-02T09:23:53]: UserSessionInfo: locked changed to 0. [2016-02-02T09:23:53]: UserSessionInfo: connected changed to 1. [2016-02-02T09:23:53]: UserSessionInfo: local changed to 1. [2016-02-02T09:23:53]: UserSessionInfo: locked changed to 0. [2016-02-02T09:23:53]: UserSessionInfo: connected changed to 1. [2016-02-02T09:23:53]: UserSessionInfo: local changed to 1. [2016-02-02T09:23:53]: Created new device object: STRAFE RGB; ready: 0 [2016-02-02T09:23:53]: Device profile (meta) for device vid=1b1c pid=1c06 not found. [2016-02-02T09:23:53]: Attached to device object STRAFE RGB: b=1 a=0 [2016-02-02T09:23:53]: Device profile (meta) for device vid=eef pid=1 not found. [2016-02-02T09:23:53]: Initializing STRAFE RGB... [2016-02-02T09:23:53]: Device profile (meta) for device vid=eef pid=1 not found. [2016-02-02T09:23:53]: Failed to open device: vid=1b1c pid=1b20 path=\\?\hid#vid_1b1c&pid_1b20&mi_01&col01#7&19951019&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-02-02T09:23:53]: Initialized (st=1) STRAFE RGB. [2016-02-02T09:23:53]: Attached to device object STRAFE RGB: b=0 a=0 [2016-02-02T09:23:53]: Failed to open device: vid=1b1c pid=1b20 path=\\?\hid#vid_1b1c&pid_1b20&mi_00#7&31589c5e&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} [2016-02-02T09:23:53]: Device profile (meta) for device vid=d8c pid=5 not found. [2016-02-02T09:23:53]: Device profile (meta) for device vid=1c4f pid=3 not found. [2016-02-02T09:23:53]: Device insertion processing complete for STRAFE RGB. Look forward to hearing from you. :biggrin: Link to comment Share on other sites More sharing options...
Toasted Posted February 3, 2016 Share Posted February 3, 2016 Weird. The VOID Wireless entries aren't present so that means the STRAFE RGB is fine, So the cause of the auto switching problem is probably unknown as it could be anything. I would suggest starting over see if that resolves the problem. Backup your existing profiles in CUE then open %Appdata%\Corsair and delete everything in it, this will 'reset' CUE. Create a new profile and link it to any program and see whether it works fine. If it doesn't switch and you have made sure the automatic profile switching is enabled, put in a support ticket and ask for instructions for a 'hard reset'. I don't think the 'hard reset' will resolve do much but its worth a try. Link to comment Share on other sites More sharing options...
fyew-jit-tiv Posted February 11, 2016 Author Share Posted February 11, 2016 This problem has been diagnosed as a CUE problem by tech support. Looks like I was right after all. Not a problem with the X99 boards, Not a problem with Wacom or any 3rd party USB drivers. Just simply a CUE problem in which the developers are now looking at. Link to comment Share on other sites More sharing options...
fyew-jit-tiv Posted February 11, 2016 Author Share Posted February 11, 2016 @Elestriel I make a formal public apology for the bickering that had taken place on these forums. Except it or not that is your choice (I will except if you don't) but I hope you understand that I couldn't except your diagnosis to this problem knowing all along that the issue was related to cue and cue alone. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.