Razer Blackwidow v3 keys dont register | Razer Insider
Skip to main content
Answer

Razer Blackwidow v3 keys dont register

  • June 17, 2025
  • 4 replies
  • 131 views

Hello,

I have Razer Blackwidow v3 purchased 2 years ago. Recently few keys (example W, Left Ctrl, Space) are registering inconsistently. To explain this better, when I play any game and press and hold W to move the character forward, then it does not register even after spamming the key. It works sometimes and then suddenly it stops. I have observed that the problem keeps occurring if the keyboard is not used for a couple of days.

Things that I have tried:

1 - cleaning the keycaps and outer switch

2 - Factory reset the keyboard

3 - Uninstall the keyboard drivers and re-install

4 - Disable synapse and try

It is confirmed that the issue is in the keyboard as I tried this on a different system. I am not sure if the switches have worn out or its a different issue. Any help would be appreciated. Thanks

 

Best answer by FiszPL

Switch issue.

You can also try to pour few drops of pure isopropyl alcohol into the switch, press it few times and let it evaporate. If it’ll not help - then you’ll need switch replacement (requires soldering).

This topic has been closed for replies.

4 Replies

FiszPL
Vanguard
Forum|alt.badge.img+1
  • VANGUARD
  • Answer
  • June 18, 2025

Switch issue.

You can also try to pour few drops of pure isopropyl alcohol into the switch, press it few times and let it evaporate. If it’ll not help - then you’ll need switch replacement (requires soldering).


W00_Die
  • Insider Mini
  • June 18, 2025

I have been experiencing this same issue. I’m pretty certain that it’s  and issue with Synapse 4 because the key’s immediately start working again after I focus the Synapse application. From what I noticed is that it only effects lower case “h” and “c” and possibly “k”. When the issue occurs I can type the uppercase variant’s, of the before mentioned keys, just fine but still get no input when lowercase until I tab out of the game and refocus the Synapse application.

 

It makes me wonder if this issue could be caused buy “Full-screen Windowed” games/applications because I stumbled into similar Issue while using OBS and an eye tracker where the stream video would bug out the second the game was tabbed back into (Counter-Strike 2). Some other person experienced the same exact issue but in Call Of Duty. So in both of those games, they have quite a few compatible issues caused by their Anti-Cheat systems, it’s been reported to cause issues with programs that capture/hook into the game window (Discord Overlays and OBS Game Capture Sources)

 

So Idk what’s that all about but... I feel like I'm onto something potentially?


W00_Die
  • Insider Mini
  • July 16, 2025

Ignore most of my previous reply. I might’ve found the culprit. On Razer's website under "Open Source Software Notices for Razer Synapse" the software is named "(15) Key Code”. I glanced into the Github repository and saw that they mentioned an issue with key press events and how key presses may behave weirdly, especially with upper and lower case keys. This is caused by using the incorrect library for the “Keypress” events, they clarified that you cannot use the KeyCode library with KeyPress events stating “event.keycode and event.which properties of keypress events correspond to ASCII codes, as opposed to keyboard codes. This means non display characters will not be fired on keypress, lowercase characters come out wrong and it's just confusing.”


Here’s the link to the github issue:
https://github.com/timoxley/keycode/wiki/wtf%3F-keydown,-keyup-vs-keypress

 

They even provided an example of the issue:

—   —   —   —   —   —   —   —   —   —   —   —   —   —   

Example: pressing the 'a' key

document.addEventListener('keydown', function(e) {
  // e.keyCode is 65
  console.log("Key Down", keycode(e.keyCode)) // => 'a' keycode correctly identifies letter 
})

document.addEventListener('keypress', function(e) {
  // e.keyCode is 97 :/
  console.log("Key Press ", keycode(e.keyCode)) // => 'Numpad 1'?? But we pressed 'a'! 
  // keycode has no idea what it's doing, lol.
})

—   —   —   —   —   —   —   —   —   —   —   —   —   —   

 


Razer.ScarletRouge

Hey there, ​@razor_911!

 

I understand you're having key input issues with your Razer Blackwidow V3. Please try these troubleshooting steps on this link to help resolve the issue. 

 

If the issue persists after performing the troubleshooting steps, please send me a private message together with your device's serial number and proof of purchase in PDF format for a possible warranty claim. You can upload your proof of purchase to your Google Drive and send me the link. Make sure that the link is set the sharing settings to "Anyone with the link can view". Thank you!


 

*Thread locked to curb conversation to PM.