Basilisk V3 disconnecting when not detecting surface | Razer Insider
Skip to main content

When lifting/removing surface from sensor of the mouse, it immediately goes into a dim red light and disconnects from pc. As long as something is covering the sensor the mouse is functioning normally. It also is worth taking note that the free spin stopped working. When waving my finger in front of the sensor (as if wiping it) it also scrolls up and down.

I tried bending the cables and such and I think this is a firmware/software problem. The sensor is also clean so I dont think thats the problem. Ive also tried using it in a different pc without synapse, reinstalling synapse, and reinstalling the mouse driver.

 

Can anybody help?

When lifting/removing surface from sensor of the mouse, it immediately goes into a dim red light and disconnects from pc. As long as something is covering the sensor the mouse is functioning normally. It also is worth taking note that the free spin stopped working. When waving my finger in front of the sensor (as if wiping it) it also scrolls up and down.

I tried bending the cables and such and I think this is a firmware/software problem. The sensor is also clean so I dont think thats the problem. Ive also tried using it in a different pc without synapse, reinstalling synapse, and reinstalling the mouse driver.

 

Can anybody help?

This exact thing is happening to me right now and I NEED help asap

This just started happening to me as well. It started with the RGB light configuration changing to a different color when lifted then slowly went to disconnecting when lifted or when there is nothing covering the sensor as described in the main post.

 

Any news on how to fix this? The mouse functions without issues as long as the sensor is covered.

Have had this problem for a week now, still haven’t found any solutions… it also randomly stops working and only starts working again when the mouse is disconnected and connected again 

I have the exact same problem. Started around year ago. Still haven't found a solution to it. Really great mouse, doesn’t want to throw it away because of this banal problem. Please, help!

This happened to me day 1, about a year ago or more - I thought I could look into it and save me the return, but I should have! It was my spare so I never really used it, never thought much about it. But now that I need it it’s pretty much USELESS because of this driver issue! RAZER should probably recall the batch!!

Reply


CookiesCookie settings