Jump to content
Corsair Community

Strafe RGB not responding when using complicated rgb profile.


soupbat

Recommended Posts

Hello

 

I recently bought my first ever mechanical keyboard, the strafe rgb. I was extremely pleased with it for the first day or two until i started downloading profiles (from Rgb share, not random websites).

 

I noticed that when using a profile with flashing colours or moving parts and all that my keyboard would completely lock up. No response at all. All lights would freeze and my mouse that I plugged into the usb passthrough would stop responding as well. The only way to fix this is to unplug and re-plug the keyboard. But it would soon do the same whether it be 1 minute or 1 hour later.

 

I have tried changing the polling rate and have plugged my mouse into the computer itself but the same thing happens. The only way to stop it is to have a static profile which kinda ruins the whole rgb thing for me.

 

Any help would be much appreciated.

Thanks, Chris

Link to comment
Share on other sites

check your logs. are there any error reports.

 

This is my log here.

Im not sure if the "failed" parts are errors or just buggy profiles

 

[2016-01-17T18:53:34]: UserSessionInfo: locked changed to 0.

[2016-01-17T18:53:34]: UserSessionInfo: connected changed to 1.

[2016-01-17T18:53:34]: UserSessionInfo: local changed to 1.

[2016-01-17T18:53:35]: UserSessionInfo: locked changed to 0.

[2016-01-17T18:53:35]: UserSessionInfo: connected changed to 1.

[2016-01-17T18:53:35]: UserSessionInfo: local changed to 1.

[2016-01-17T18:53:37]: UserSessionInfo: locked changed to 0.

[2016-01-17T18:53:37]: UserSessionInfo: connected changed to 1.

[2016-01-17T18:53:37]: UserSessionInfo: local changed to 1.

[2016-01-17T18:53:37]: Device profile (meta) for device vid=4d9 pid=a09f not found.

[2016-01-17T18:53:37]: Device profile (meta) for device vid=7545 pid=897 not found.

[2016-01-17T18:53:37]: Device profile (meta) for device vid=4d9 pid=a09f not found.

[2016-01-17T18:53:37]: Failed to open device: vid=1b1c pid=1b20 path=\\?\hid#vid_1b1c&pid_1b20&mi_00#8&1f8e6fc4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-01-17T18:53:37]: Device profile (meta) for device vid=54c pid=5c4 not found.

[2016-01-17T18:53:37]: Failed to open device: vid=1b1c pid=1b20 path=\\?\hid#vid_1b1c&pid_1b20&mi_01&col01#8&32be8c02&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

[2016-01-17T18:53:37]: Device profile (meta) for device vid=4d9 pid=a09f not found.

[2016-01-17T18:53:37]: Device profile (meta) for device vid=4d9 pid=a09f not found.

[2016-01-17T18:53:37]: Created new device object: STRAFE RGB; ready: 0

[2016-01-17T18:53:37]: Attached to device object STRAFE RGB: b=1 a=1

[2016-01-17T18:53:37]: Device profile (meta) for device vid=4d9 pid=a09f not found.

[2016-01-17T18:53:37]: Device profile (meta) for device vid=4d9 pid=a09f not found.

[2016-01-17T18:53:37]: Attached to device object STRAFE RGB: b=1 a=0

[2016-01-17T18:53:37]: Initializing STRAFE RGB...

[2016-01-17T18:53:37]: Initialized (st=1) STRAFE RGB.

[2016-01-17T18:53:37]: Device insertion processing complete for STRAFE RGB.

Link to comment
Share on other sites

C:\Users\(insert username)\AppData\Roaming\Corsair\HID

 

try deleting everything in that folder.

 

Done. Thanks. All seems well for now but as I said before ill just have to wait and see.

 

Thanks for all the help and ill report back as soon as something happens

Link to comment
Share on other sites

Ok. It happened again.

 

I was playing payday 2 and switched profile mid game. About a second later my keyboard locked up again and it held down the keys i was pressing so i walked out and got detected by the cops...

 

Anyways. Im not sure if its a defect in the product now

Link to comment
Share on other sites

The first profile was not linked to the game. In fact it was the rainbow wave that is pre installed on CUE.

 

I assigned the scroll lock key to swap through profiles so I didnt have to tab out but even before this it still froze. Im not sure if its the profiles though because I was using the visualizer on corsair effects engine and it was still freezing but im not sure if thats linked into CUE.

 

These are the others in order that I switched through.

 

I couldnt find the link for this one but it is called "Phazon blue"

 

http://gaming.corsair.com/en-gb/rgbshare/rainbow-fireworks-ad95

 

http://gaming.corsair.com/en-gb/rgbshare/rainbow-random-6b0d

 

It froze on the last one (Rainbow Random)

 

Thanks.

Link to comment
Share on other sites

Ok uninstall CUE, go in to the reg search for Corsair and deleted everything that pertains to CUE. Then go and delete the C:\Users\(your username)\AppData\Roaming\Corsair\HID and delete the HID folder. Restart. Reinstall CUE.

 

What do you mean by go into the reg? Do you mean regedit?

Link to comment
Share on other sites

Alright. So once again it froze. This time it was using the visor effect with a blue background, So not that complicated.

 

Im not too sure now whether its a problem with software and that or whether its a problem with the led controller, but i dont know why that would freeze the usb pass-through

 

Hope you guys can help

 

Thanks

Link to comment
Share on other sites

Make sure your BIOS, chip[set drivers and Windows is up to date.

Please fillout your system specs.

http://forum.corsair.com/v3/profile.php?do=extra

 

Some motherboards have a third party controller for USB ports which are known to cause some issues with the keyboards. It will be best to plug the keyboard into a port that is controlled by either an AMD/Intel chipset. Usually this information can be found in your motherboard's manual.

Link to comment
Share on other sites

Make sure your BIOS, chip[set drivers and Windows is up to date.

Please fillout your system specs.

http://forum.corsair.com/v3/profile.php?do=extra

 

Some motherboards have a third party controller for USB ports which are known to cause some issues with the keyboards. It will be best to plug the keyboard into a port that is controlled by either an AMD/Intel chipset. Usually this information can be found in your motherboard's manual.

 

Ok Thanks. Ill look into it and update soon

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...