[SOLVED] Razer Cynosa v2 "device descriptor failed"

[nickname1400]

Hi, I've had my keyboard since December now and its been great, no problems until yesterday. Its a Razer Cynosa v2. I turned on my pc and noticed it wasnt typing or working at all. I have another keyboard so I was able to do some debugging, in device manager it says "Device Descriptor Request Failed" and windows cannot recognise the device. It's obviously a driver issue as there have been messages regarding it "could not find any drivers" so I tried updating windows and rolling back updates, and I cant seem to find any drivers online or synapse. There will be sometimes where the keyboard works after restart but only for 10 mins or so. Just looking for options here.

 

[Colif]

does keyboard work in other devices?
does keyboard work in bios?
does it work in safe mode?

Spoiler

go to settings/update & security/recovery
under advanced startup, click restart now button
this restarts PC in a blue menu
choose troubleshoot
choose advanced
choose startup options
click the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode

 

[nickname1400]

does keyboard work in other devices?
does keyboard work in bios?
does it work in safe mode?

Spoiler

go to settings/update & security/recovery
under advanced startup, click restart now button
this restarts PC in a blue menu
choose troubleshoot
choose advanced
choose startup options
click the restart button
choose a safe mode (it doesn't matter which) by using number associated with it.
Pc will restart and load safe mode

Doesn't work in BIOS but power is supplied (backlighting works).
Doesn't work in safe mode.
Haven't been able to check other computers but will this afternoon.

 

[Colif]

How did it go? if it doesn't work in 2 different PC, I would suspect its the keyboard itself.

 

[nickname1400]

How did it go? if it doesn't work in 2 different PC, I would suspect its the keyboard itself.

Still havent been able to try, if it were the keyboard itself, is there much I can do apart from replacing it? It is under warranty.

 

[Colif]

I wonder if razer will answer your question.

it appears to be a common problem with the keyboard, you might want to arrange an rma if 2nd PC also can't see it.

 

[nickname1400]

Okay, so I've plugged it into my laptop, seems to be working fine at the moment. It isnt displayed as a "razer keyboard" in device manager but as a standard PS/2 Keyboard so I cant tell if its running the same way as it would on my PC. It also sometimes takes some time for it to stop working so I'll let it run for a while but so far, no problems.

I wonder if razer will answer your question.

it appears to be a common problem with the keyboard, you might want to arrange an rma if 2nd PC also can't see it.

I also sent in a support request with razer so hopefully they can provide some insight. If it is a driver problem, would it be possible to transfer the seemingly working one from my laptop to my PC?

 

[Colif]

does it use Synapse for the drivers?
Does Synapse see it?

Do I need software drivers to use the Razer Cynosa Chroma?
You may use the standard keyboard functions by simply plugging the Razer Cynosa Chroma to any available USB port on your computer. However, you will need to download the software and drivers in order to enable advanced features such as macro recording and profile settings.

Razer support link

looks like there is a firmware update - link

 

[nickname1400]

does it use Synapse for the drivers?
Does Synapse see it?


Razer support link

looks like there is a firmware update - link

I believe it does use synapse for drivers. I'll download it on my laptop and see what happens. But it is not seen on synapse on my PC.

 

[Colif]

look at my razer support link, it shows a way to get synapse to see device

 

[nickname1400]

look at my razer support link, it shows a way to get synapse to see device

Seems the link doesnt work, however, after plugging the keyboard back into my PC, it has since worked, no problems at all for a couple of hours now, not sure what happened but it seems to have fixed itself.