Cynosa V2 suddenly stops working | Razer Insider

Cynosa V2 suddenly stops working

  • 20 July 2021
  • 6 replies
  • 34 views

My cynosa V2 had been working fine all day then suddenly stops accepting inputs but it had the lights on so i went to unplug it and replug it into a different port and now it has no lights and has no inputs. Is there an easy way to fix it or do i need to get a new keyboard?

This topic has been closed for comments

6 Replies

Hi! I Would Download a fresh install of Synapse 3 and see if that works. If it doesn't please let me know. Hope this helps!
Teslamotorslover06
Hi! I Would Download a fresh install of Synapse 3 and see if that works. If it doesn't please let me know. Hope this helps!

I did a fresh install and its not detected by synapse as a device.
Ok I would call Razer Customer service at (855) 872-5233 and inform them on the situation and if your keyboard is under warranty they should be abel to send a new one to you free of charge. You will have to return your old keyboard to the address that they give you. Sorry for the inconvinience and hope it gets solved!
Userlevel 4
MistHelix
My cynosa V2 had been working fine all day then suddenly stops accepting inputs but it had the lights on so i went to unplug it and replug it into a different port and now it has no lights and has no inputs. Is there an easy way to fix it or do i need to get a new keyboard?


Have you tried connecting it to a different computer? Let's isolate the behavior by doing a hard reset on your keyboard. Please click this link and follow the steps provided. Let me know if it helps.
Razer.GuitarScar
Have you tried connecting it to a different computer? Let's isolate the behavior by doing a hard reset on your keyboard. Please click this link and follow the steps provided. Let me know if it helps.

I have tried connecting it to my mac and it still didn't work along with me trying to do a hard reset.
Userlevel 4
I see. Please send me the serial number of your device via PM. I'll be needing it to verify its model and look into possible firmware-related solutions. Let's continue from there.



I'll lock this thread now.