Jump to content
Corsair Community

CUE Software + Steam


Ley3198

Recommended Posts

  • Replies 284
  • Created
  • Last Reply

Im hooked up to 2 HDTV's running off an Nvidia GTX 560Ti. One though HDMI (main:1920x1080) and the second through VGA (1360x768).

 

Its not a problem within games, just upon Steam connecting upon start.

 

I notice it happen since i have a wave effect going on and it suddenly stops.

Link to comment
Share on other sites

I have this problem also. Got the K70RBG last friday, working pretty great otherwise, but on launching Steam, any key press effect stops working and even if try to switch profiles nothing changes. It keeps the key lights as they were, but no effects and unable to change until i unplug and replug. Only ever seems to be Steam too, and every time i launch it too.
Link to comment
Share on other sites

I'm using the latest Steam(Not Beta). Latest K70 RGB firmware and using 1 USB 3.0 port. Windows 8.1 64bit. I opened steam and as soon as I hit login, my lighting stopped working. I unplugged my keyboard and opened Steam again and it once again froze the keyboard. I unplugged the keyboard again and open Steam and then it works normally. Steam is the only application i've been seeing that is causing this problem. I do this a forth time and then catch it on video.

 

[ame]https://www.youtube.com/watch?v=BlbJtDrNxWI&feature=youtu.be[/ame]

Link to comment
Share on other sites

It is the opposite for me. Whenever I open Steam, Steam freezes and the keyboard continues to work. I'm on Windows 8.1 as well, but I'm using 2 USB 2.0's. I will try with 1 3.0 and see if the problem persists.

Update - This was actually the first time trying to use 3.0, and the keyboard doesn't work in 3.0. Lights work but I cannot type in all configurations. 2 in, 1 in, 1 in, all show lighting but cannot type.

Link to comment
Share on other sites

It is the opposite for me. Whenever I open Steam, Steam freezes and the keyboard continues to work. I'm on Windows 8.1 as well, but I'm using 2 USB 2.0's. I will try with 1 3.0 and see if the problem persists.

Update - This was actually the first time trying to use 3.0, and the keyboard doesn't work in 3.0. Lights work but I cannot type in all configurations. 2 in, 1 in, 1 in, all show lighting but cannot type.

 

I am using 1 USB 3.0 and all the functions of the keyboard work, you must have tried the wrong USB. Also, i'm currently returning this keyboard, I'll try it again at another time.

Link to comment
Share on other sites

I have been having both issues were Steam will take a VERY long time to load, or it just crashes, and the utility engine no longer recognizes my keyboard. Waiting for Steam to finally load and then playing with the polling switch or unplugging and re-plugging in the USB seems to work it all out so it appears to me that it just has something to do with Steam initially loading. I was hoping that the CUE 1.1.48 and Firmware 1.12 would take care of this but so far it does not seem like it has for me.

 

I am currently using both connectors in USB 2.0

Link to comment
Share on other sites

yup every single time i try to launch steam my keyboard just gets stuck.

i just flicked that back switch all the way to the left then all the way back to the right and in about a minute or so it will go back to normal

 

 

i am also getting a bug where i can only go to my profiles to edit my lighting and etc every so often if i unplug the keyboard and plug it back in it starts working again

 

just got my cherry mx brown k70 rgb today

Link to comment
Share on other sites

I am getting the same problem but my keyboard also randomly crashes on its own, I have to switch the switch on the back forward and back to its original position and then it reboots and crashes a few minutes later again, i have reinstalled all the software, my firmware is up to date, I have restarted my comptuer, I have tried different ports ETC..

 

This is really annoying ;-; I LOVE this keyboard but Corsair what is going on?! Is there anything I can do to help in the bug finding process for solving this? because I gladly would..

Link to comment
Share on other sites

  • 3 weeks later...
  • Corsair Employees

Hi all,

 

Resolving issues with CUE has been our highest priority since launch and while we have resolved many issues, there are still some that we have to continue to work on. We've been seeing issues with a very small number of users who are experiencing problems with the Steam application.

 

One of our users suggested a fix here: http://forum.corsair.com/v3/showthread.php?t=133370

 

Another suggested temporary fix is to start the CUE software after starting up Steam as it was noted that Steam's hardware check on startup causes CUE to malfunction.

 

If you continue to have an issue with both CUE and steam despite the suggested solutions above, we'd like to know more about your system.

 

If your Steam Application only causes a malfunction in the CUE software, please list the following:

 

a.) Your system hardware and if chipset drivers/BIOS are both updated to the latest versions.

b.) Device Logs by going to SETTINGS -> Support -> View Logs (attach it to your post)

c.) When and how it occurs (what game? did it malfunction mid game or when Steam is on?)

 

If your Steam Application causes CUE to crash/stop responding:

 

Everything above + d.) Windows Dump File (attach it to the post as well).

 

HOW TO:

 

You'll need to create a "Dump Folder" to retrieve the file from the Windows Error Reporting. For the output of the dump files, create a folder under Local Dumps (I named mine CorsairHID) and then create the necessary files in the from the link. The directory should be a Expendable String Value (right click the folder and then select new -> Expendable String value). Name it "DumpFolder." I selected the folder I made on the desktop for the destination.

 

DumpCount and DumpType are DWORD (right click folder -> New -> DWORD (32bit) value. Make sure its under the decimal setting with value 10 and 1 respectively. I have attached a screenshot below to help show how it looks.

 

attachment.php?attachmentid=19498&d=1413239339

 

 

 

This thread will keep all the information in one place for easy tracking so our Software Team can refer to it for additional information.

 

Thanks everyone for assisting with this issue.

ErrorReporting.PNG.29ecc70f0ccbb3812de491a2f0ba4a79.PNG

Link to comment
Share on other sites

Starting CUE After Steam does seem to be a viable workaround, at least for me. CUE itself has been even more unstable for me since the update though. Consistent crashes anytime I switch modes within a profile. I'll post the latter bit in the main "update" thread.
Link to comment
Share on other sites

0035d854 76d4d18f 000007dc 00000000 00000000 ntdll_772f0000!NtDeviceIoControlFile+0x15

0035d8b4 74f93217 000007dc 000b01be 00000000 KERNELBASE!DeviceIoControl+0xee

0035d8e0 66912874 000007dc 000b01be 00000000 kernel32!DeviceIoControlImplementation+0x80

0035d908 6fe91c1b 000007dc 0035e608 00000208 hid!HidD_GetProductString+0x22

0035d924 6fe93229 099b0290 0035e608 00000208 dinput8!fGetProductStringFromDevice+0x49

0035e5c4 6fe9291f 099b0290 0035e5e8 0035e5f8 dinput8!CHid_GetProperty+0x335

0035e864 6fe83dba 099b0290 0035e8c4 0658aa14 dinput8!CHid_GetDeviceInfo+0xce

0035e884 6fe9042f 063a5d58 0035e8c4 648eb3e0 dinput8!CDIDev_GetDeviceInfoW+0x77

0035e8a0 6fe8d06d 0658a9f8 0035e8c4 00000000 dinput8!CDIDEnum_Next+0x8c

0035ed14 648eb52d 06546b50 00000004 648eb3e0 dinput8!CDIObj_EnumDevicesW+0xe1

WARNING: Stack unwind information not available. Following frames may be wrong.

0035ed30 648ec2d1 0035ed84 00130500 70006810 SDL2!SDL_DYNAPI_entry+0x7c1d

0035ed88 64961fcb 645f5e70 645f0101 00000000 SDL2!SDL_DYNAPI_entry+0x89c1

0035ed9c 5500ce79 0035edfb 645f5e70 645f0101 SDL2!SDL_DYNAPI_entry+0x7e6bb

0035edfc 5501b7da 7248b36c 00000000 645f5e70 SteamUI!XMLStringbuf_ToString+0xed0f9

0035ee1c 55014dee 645f5e70 5501ffd0 0035f750 SteamUI!XMLStringbuf_ToString+0xfba5a

0035f710 7000cce9 00000001 0035f6f0 00000000 SteamUI!XMLStringbuf_ToString+0xf506e

0035f744 7000d806 0035f750 00000002 55014440 tier0_s!CValidator::GetNumSockets+0x2c9

0035f768 5501ffee 55014440 00000001 004d4c18 tier0_s!CatchAndWriteMiniDumpExReturnsInt+0x46

0035f780 01054699 00000001 004d4c18 010545c0 SteamUI!SteamDllMainEx+0x1e

0035f8c8 0105549d 00000001 004d4c18 0035f8a8 Steam!StartCheckingForUpdates+0x31f9

0035fb48 010649f9 00000001 004c8e00 011b1180 Steam!GetEUniverse+0x96d

0035fb6c 010cbd02 01030000 00000000 004a3449 Steam!GetEUniverse+0xfec9

0035fbb8 74f9336a 7efde000 0035fc04 77329f72 Steam!CreateInterface+0x62c22

0035fbc4 77329f72 7efde000 77ca1e0b 00000000 kernel32!BaseThreadInitThunk+0xe

0035fc04 77329f45 010cbbfb 7efde000 00000000 ntdll_772f0000!__RtlUserThreadStart+0x70

0035fc1c 00000000 010cbbfb 7efde000 00000000 ntdll_772f0000!_RtlUserThreadStart+0x1b

 

This is the call stack when the problem occurred for me. Pretty obvious what is going on here. Based on my previous RE, DeviceIoControl calls to the keyboard results in keyboard malfunctions if they are sent too fast. After this point, lighting is frozen and sometime the input will remain in its current state as well. It appears that there is no server end queuing implemented to handle these requests in the order that they are sent from user-mode.

 

To reproduce, tell your software guys to spam HidD_SetFeature with their typical packets and they'll see the same result.

Link to comment
Share on other sites

  • Corsair Employees
0035d854 76d4d18f 000007dc 00000000 00000000 ntdll_772f0000!NtDeviceIoControlFile+0x15

0035d8b4 74f93217 000007dc 000b01be 00000000 KERNELBASE!DeviceIoControl+0xee

0035d8e0 66912874 000007dc 000b01be 00000000 kernel32!DeviceIoControlImplementation+0x80

0035d908 6fe91c1b 000007dc 0035e608 00000208 hid!HidD_GetProductString+0x22

0035d924 6fe93229 099b0290 0035e608 00000208 dinput8!fGetProductStringFromDevice+0x49

0035e5c4 6fe9291f 099b0290 0035e5e8 0035e5f8 dinput8!CHid_GetProperty+0x335

0035e864 6fe83dba 099b0290 0035e8c4 0658aa14 dinput8!CHid_GetDeviceInfo+0xce

0035e884 6fe9042f 063a5d58 0035e8c4 648eb3e0 dinput8!CDIDev_GetDeviceInfoW+0x77

0035e8a0 6fe8d06d 0658a9f8 0035e8c4 00000000 dinput8!CDIDEnum_Next+0x8c

0035ed14 648eb52d 06546b50 00000004 648eb3e0 dinput8!CDIObj_EnumDevicesW+0xe1

WARNING: Stack unwind information not available. Following frames may be wrong.

0035ed30 648ec2d1 0035ed84 00130500 70006810 SDL2!SDL_DYNAPI_entry+0x7c1d

0035ed88 64961fcb 645f5e70 645f0101 00000000 SDL2!SDL_DYNAPI_entry+0x89c1

0035ed9c 5500ce79 0035edfb 645f5e70 645f0101 SDL2!SDL_DYNAPI_entry+0x7e6bb

0035edfc 5501b7da 7248b36c 00000000 645f5e70 SteamUI!XMLStringbuf_ToString+0xed0f9

0035ee1c 55014dee 645f5e70 5501ffd0 0035f750 SteamUI!XMLStringbuf_ToString+0xfba5a

0035f710 7000cce9 00000001 0035f6f0 00000000 SteamUI!XMLStringbuf_ToString+0xf506e

0035f744 7000d806 0035f750 00000002 55014440 tier0_s!CValidator::GetNumSockets+0x2c9

0035f768 5501ffee 55014440 00000001 004d4c18 tier0_s!CatchAndWriteMiniDumpExReturnsInt+0x46

0035f780 01054699 00000001 004d4c18 010545c0 SteamUI!SteamDllMainEx+0x1e

0035f8c8 0105549d 00000001 004d4c18 0035f8a8 Steam!StartCheckingForUpdates+0x31f9

0035fb48 010649f9 00000001 004c8e00 011b1180 Steam!GetEUniverse+0x96d

0035fb6c 010cbd02 01030000 00000000 004a3449 Steam!GetEUniverse+0xfec9

0035fbb8 74f9336a 7efde000 0035fc04 77329f72 Steam!CreateInterface+0x62c22

0035fbc4 77329f72 7efde000 77ca1e0b 00000000 kernel32!BaseThreadInitThunk+0xe

0035fc04 77329f45 010cbbfb 7efde000 00000000 ntdll_772f0000!__RtlUserThreadStart+0x70

0035fc1c 00000000 010cbbfb 7efde000 00000000 ntdll_772f0000!_RtlUserThreadStart+0x1b

 

This is the call stack when the problem occurred for me. Pretty obvious what is going on here. Based on my previous RE, DeviceIoControl calls to the keyboard results in keyboard malfunctions if they are sent too fast. After this point, lighting is frozen and sometime the input will remain in its current state as well. It appears that there is no server end queuing implemented to handle these requests in the order that they are sent from user-mode.

 

To reproduce, tell your software guys to spam HidD_SetFeature with their typical packets and they'll see the same result.

 

This isn't happening to everyone though. We'd need to see what is causing the problem overall if your hypothesis is correct. Since most people don't have an issue with steam and its unrepeatable in the lab, we're going to need the complete picture of everything that is happening including your CUE logs. Judging from some of the resolutions we see, this could very well be a Steam issue (for example).

Link to comment
Share on other sites

This isn't happening to everyone though. We'd need to see what is causing the problem overall if your hypothesis is correct. Since most people don't have an issue with steam and its unrepeatable in the lab, we're going to need the complete picture of everything that is happening including your CUE logs. Judging from some of the resolutions we see, this could very well be a Steam issue (for example).

 

It's not Steam. It's DirectInput in this case which Steam just so happens to use (if it's turned on). Any other application that utilizes DirectInput will result in the same behavior if "CDIObj_EnumDevicesW" is called (probably in conjunction with other I/O to the keyboard simultaneously). Whether that "reproduces" the problem doesn't really matter, because HidD_SetFeature spamming should do it rather quickly.

 

Not sure if anyone from Corsair saw the Reddit thread, but I posted this: http://pastebin.com/LMuZivfe

 

Remove the "Sleep(200);" calls and after compilation it should reproduce the problem. If it does NOT, I am more than willing to send you any additional information you may need.

Link to comment
Share on other sites

  • Corsair Employees
It's not Steam. It's DirectInput in this case which Steam just so happens to use (if it's turned on). Any other application that utilizes DirectInput will result in the same behavior if "CDIObj_EnumDevicesW" is called (probably in conjunction with other I/O to the keyboard simultaneously). Whether that "reproduces" the problem doesn't really matter, because HidD_SetFeature spamming should do it rather quickly.

 

Not sure if anyone from Corsair saw the Reddit thread, but I posted this: http://pastebin.com/LMuZivfe

 

Remove the "Sleep(200);" calls and after compilation it should reproduce the problem. If it does NOT, I am more than willing to send you any additional information you may need.

 

Great info, thanks. I'll get back to you.

Link to comment
Share on other sites

a.) Your system hardware and if chipset drivers/BIOS are both updated to the latest versions.

CPU: i7-4790

MOBO: Asus Sabertooth Z97 Mark 1

RAM: 32GB of Corsair Vengeance 1600Mhz

GPU: EVGA GTX760 Dual SC

PSU: Corsair RM750

Keyboard: K70 RGB

Mouse Corsair M65

 

Chipset and BIOS are both current.

 

b.) Device Logs by going to SETTINGS -> Support -> View Logs (attach it to your post)

Logs will be attached below.

 

 

c.) When and how it occurs (what game? did it malfunction mid game or when Steam is on?)

 

It occurs when I start steam, it becomes unresponsive and only started to happen after the most recent update to the keyboard firmware and CUE software. The first time it happened to me was today, and I was attempting to play BioShock Infinite. It happened as soon as I started the game and steam, the game and CUE became unresponsive. I will say that as soon as I unplug the keyboard, steam functions just fine as well as Bioshock Infinite.

 

 

 

If your Steam Application causes CUE to crash/stop responding: Everything above + d.) Windows Dump File (attach it to the post as well).

 

I will not make changes to my registry.

logs.zip

Link to comment
Share on other sites

Archived

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

Guest
This topic is now closed to further replies.

×
×
  • Create New...