Blackwidow Ultimate 2014 key repeat/spamming | Razer Insider
Skip to main content
Recently, the following started happening on my 2014 Blackwidow Ultimate.



Out of nowhere, arbitrary keys will start repeating. For example, it will start spamming 3333333333....or some other key.



  • Hitting any other key does not stop it

  • Logging off does not stop it (and makes it impossible to log back in)

  • It seems like it happens more often right when waking the computer (after it goes to sleep after 30 minutes). This makes it impossible to log in again.

  • If I quit Synapse the problem immediately goes away (but obviously, so do my macro's)



I have uninstalled synapse 2.0, re-installed, deleted my macros (ie. all of them)....nothing changes.



Best guess: Something in a Windows 10 update is conflicting with the software?



Anyone have any suggestions? There are lots of posts about similar issues, but I am sure this is not a hardware issue.
To add to my own post....

Definitely can confirm it occurs when waking from sleep. Just occurred, and I received a run of 333333333... until i shut down synapse.
hi, my blackwidow ultimate is having exactly the same problem. Pls help!
No solution yet, however I'm curious if our systems have anything in common.



I also noticed that aside from the repeating keys, my lighting stopped turning off when I went into sleep mode (even though it was set to turn off), and the computer would constantly wake up as soon as it slept.



I went into my device manager, and under "Universal Serial Bus Controllers" found 2 entries called "USB Root Hub". Double-clicked, then chose the "Power Management" tab. The box "Allow computer to turn off this device to save power" was not checked. When I check that, the computer does go to sleep and the power light does go off. Unfortunately, when it came back up the keyboard would light up but I couldn't type anything. Have to remove, then re-attach it.



I feel like its getting closer, but would love someone from razer (or another user) to chime in here. Definitely a software problem.
I have right now a setup that seems to be working, though only time will tell:

- Uninstalled Razor Synapse 2.0

- Deleted the Blackwidow under "Keyboards", then rebooted. The keyboard gets detected again on reboot.

- Re-installed Synapse 2.0 and rebooted

- On reboot, I logged in and switched it to offline mode. I *do not* want it auto-updating

- Downgraded the firmware using Razer_BlackWidow_Ultimate_(2013)_FirmwareUpdater_v2.05.03. I literally just googled that and found it.



Synapse always wants to update, so it is imperative that you do not let it. I should really block this from the Windows firewall, though I wasn't able to.



For reference my USB power settings are:

- USB Root Hub Power Management is set to "Allow computer to turn off device"

- Under "Mice" for some reason an entry always appears for the Blackwide. It has a power management setting "Allow this device to wake computer" which is NOT set.



So far so good, after 1 day. I'm guessing Razer's firmware is the culprit, and am shocked that I don't get asked before it updates. Definitely something I will consider for my next keyboard, as all my Logitech stuff seems to be working fine without any issues.
Forget the above...problem has reappeared.
Ok, now problem has gone away. My computer even sleeps normally. In the hopes this helps someone:





  • In device manager, under keyboard, removed every entry

  • In device manager, under "Mice", removed every entry.



  • Uninstalled synapse and deleted

  • Rebooted.

  • Reinstalled Synapse 2.0

  • Downgraded to firmware 2.21 (Search for Razer_BlackWidow_Ultimate_(2013)_FirmwareUpdater_v2.05.03)

  • Turned off online updating

  • In Device Manager, USB Root Hub entries (I had 2 of them) have Power Management are set to "Allow computer to turn off device"

  • In control Panel/Hardware and Sound/Power Options - in my power plan selected "Change plan settings", then "Change advance plan settings

  • Under USB settings/USB selective suspend setting/"Plugged in" set to Disabled



I think that's it.



Honestly, this is a keyboard. Why is this even an issue?