Jump to content
Corsair Community

Strafe not detected after Start up


Dynamic577

Recommended Posts

Hey there.

 

When i start my Computer my Strafe RGB stays red & white (wasd and arrow keys). The Corsair Software doesnt see the Keyboard aswell. The only Solution is here to unplug and replug the Keyboard and everything is fine. This happens 3 times out 10 Start ups. i tried to play around in UEFI with USB legacy Support i tried the usb 2 ports aswell as the usb 3. Firmware Update ist up to date.

 

I love this Keyboard very much especially the MX Silent Switches which are awesome for Streaming (noise) :).

 

So i hope you can help me out!

 

Regards

Link to comment
Share on other sites

My Strafe RGB is causing problems also! For one it doesn't work at all when plugged into a 3.0 USB ( this may be a mobo issue) so I have the keyboard connected to 2 USB 2.0 ports.

The problem I'm having is that in game some of the keys I have configured for the games seem to intermittently stop working! They will resume working without any sort of reconnecting or steps required on my part but obviously it can be a serious problem in game!

Can you think of any reason why this may be happening and how it could be corrected? I wish there was some way I could demonstrate this issue but since it occurs randomly there is no way I can. Thanks

Link to comment
Share on other sites

  • 4 months later...

In my personal case, now (since the last update), this bug happen at every start.

The keyboard work perfectly, but CUE didn't detect it anymore.

So, logically, any the CUE features don't work. Very annoying, since it was for that that i choose this KB.

I add that my mouse, M65_RGB, is perfectly detected, and the CUE features work with it.

So at each startup or each reboot, i have to unplug/plug the keyboard. And, only then, CUE detect the keyboard and the features come back.:mad::mad:

 

I have the sensation that this came progressively.

When i bought it, it was working fine, but with the time the bug became more frequently, and now it's with every windows boot.

 

So tonight i was angry, i say to myself that, "this is enought, i have to found a solution to make this KB works without unplug it". (My computer USB connectors are very hard to acces).

Then i read 1,2,3...10... forum, and i found that a lot of people have this problem...:eek:

And it is when i read someone who was talking about the HIDDEN BIOS MODE... (Some kind of super power?):sunglasse

Then just for the fun to try, I test to switch it to bios mode.

Ho ! the leds blink, hum... marvelous !!! Okay keep focus !

And when i come back to normal mode... the birds stop sing, all the annimals become quiet and even the clouds stop to move and... THIS... IS... O-K-AY ! CUE detect it and the features works!!!!

When the KB re-come to the normal mode the CUE detect it! Why ? I don't care ! Now, i didn't have to make anymore some strange movement to uplug/plug this ... USB after each restart.

 

So guys, try to switch to BIOS mode with ("F1" + "Lock Windows key") and go back to normal mode with the same keys again.

NB : The "Lock Windows key" is the top right key of the keyboard!!!

 

 

 

 

 

 

 

But this is not normal... :evil:

Corsair Team we count on you to find a solution !:D:

All the power saving are disabled in the bios and in windows.

I try to plug it on a USB HUB or directly on the motherboard same thing.

Try to update many driver, boring and same thing.

I think i lose enough time to try to solve by myself... And lot of people have the same matters...

 

W10 Pro 64bits

Soft CUE : V:1.16.42

M65 RGB : FW: 2.02 Bootloader 0.23

Strafe RGB : FW 2.04 Bootloader 0.14

Link to comment
Share on other sites

  • 11 months later...
In my personal case, now (since the last update), this bug happen at every start.

The keyboard work perfectly, but CUE didn't detect it anymore.

So, logically, any the CUE features don't work. Very annoying, since it was for that that i choose this KB.

I add that my mouse, M65_RGB, is perfectly detected, and the CUE features work with it.

So at each startup or each reboot, i have to unplug/plug the keyboard. And, only then, CUE detect the keyboard and the features come back.:mad::mad:

 

I have the sensation that this came progressively.

When i bought it, it was working fine, but with the time the bug became more frequently, and now it's with every windows boot.

 

So tonight i was angry, i say to myself that, "this is enought, i have to found a solution to make this KB works without unplug it". (My computer USB connectors are very hard to acces).

Then i read 1,2,3...10... forum, and i found that a lot of people have this problem...:eek:

And it is when i read someone who was talking about the HIDDEN BIOS MODE... (Some kind of super power?):sunglasse

Then just for the fun to try, I test to switch it to bios mode.

Ho ! the leds blink, hum... marvelous !!! Okay keep focus !

And when i come back to normal mode... the birds stop sing, all the annimals become quiet and even the clouds stop to move and... THIS... IS... O-K-AY ! CUE detect it and the features works!!!!

When the KB re-come to the normal mode the CUE detect it! Why ? I don't care ! Now, i didn't have to make anymore some strange movement to uplug/plug this ... USB after each restart.

 

So guys, try to switch to BIOS mode with ("F1" + "Lock Windows key") and go back to normal mode with the same keys again.

NB : The "Lock Windows key" is the top right key of the keyboard!!!

 

 

 

 

 

 

 

But this is not normal... :evil:

Corsair Team we count on you to find a solution !:D:

All the power saving are disabled in the bios and in windows.

I try to plug it on a USB HUB or directly on the motherboard same thing.

Try to update many driver, boring and same thing.

I think i lose enough time to try to solve by myself... And lot of people have the same matters...

 

W10 Pro 64bits

Soft CUE : V:1.16.42

M65 RGB : FW: 2.02 Bootloader 0.23

Strafe RGB : FW 2.04 Bootloader 0.14

 

YES! This fixed my problem!! Switching into and out of BIOS mode gets it recognized in CUE immediately! I've got a Strafe RGB.

 

Mine also has been progressively bugging out more and more since I've had it. Really curious to hear if anyone else other than us (surely) has had this issue, and whether it could be firmware, hardware, drivers, etc. I have a pulsate running on a few keys (WASD), and fading from colors on key press on all my other keys. I've also scripted some stuff like enter press - does the wipe effect across the keyboard. I wonder if it's possible/likely some sort of memory leak/error condition is happening after running it a while? How could this be debugged?

 

Thanks everyone for any help you can provide! I did also just update CUE with no improvement.

Link to comment
Share on other sites

If you are having this issue you will need to download the drivers for your USB controller from the manufacturer's website. Also, make sure your UEIF/BIOS is fully initializing the USB controllers.

 

It has worked well for a long time, and now is steadily degrading.. not sure how I could be missing a driver. Gigabyte's website doesn't list Win10 USB drivers, looks like they were only necessary for 8.1 and earlier and now are included with MS Win10 system drivers. Checked USB 3.0 & 3.1 drivers in device manager for updates and I had the latest (MS Driver.) Ran the Intel driver update utility to detect my hardware & update drivers and it didn't identify anything.

 

Based on some of the other threads it looks like a bunch of garbage might be getting created elsewhere with USB devices?

 

http://forum.corsair.com/v3/showthread.php?t=154018

Link to comment
Share on other sites

Archived

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

×
×
  • Create New...