[SUPPORT VIDEO] How to Fix a Razer Keyboard with Spamming Issues | Razer Insider
Sticky

[SUPPORT VIDEO] How to Fix a Razer Keyboard with Spamming Issues


Userlevel 7


This video will show you how to fix a Razer keyboard with spamming issues. A Razer keyboard that spams keys or does not register input when pressed can be due to a faulty switch or other hardware issues, faulty firmware, driver or the device is in "Demo Mode."

Please note that any damages caused by upgrading or modifying your Razer product are not covered by Razer's Warranty Policy. For more information, see Razer's Warranty Policy.

Visit the Support Page: Keys on Razer keyboard are physically stuck, sticky, loose, unresponsive, spamming, or repeating when pressed

- - -

Insiders, what do you think the next Support video should be? Comment with a topic. Great suggestions will be rewarded with the repeatable "Nice" achievement.

Also, for every 20 comments on this thread and the YouTube video, I'll be giving away a random "Great" Achievement. Insiders, be sure to leave your Insider ID in the YouTube comment to be eligible.

Lastly, for those of you who subscribe to the Support channel, we'll be doing massive Silver giveaways for each milestone, so be sure to tell your friends, smash that like button and subscribe to the channel.

This topic has been closed for comments

26 Replies

buzztoolsPhlox821
This does not deal with the most important issue : The inability to access the "@" key.
My brand new Pro 17 arrived with an inability to access @, which prevents anyone from putting in an email address. CS was worse than useless and the supervisor worse, I only fixed the problem by spending hours going through #razer complaints to fix it. The "British" keyboard reaches @ by hitting Shift and the " key. No one at #razer claimed to know about the problem which makes them worse than useless. CS was rude and did NOT GET BACK TO ME AS I ASKED THEM.
THIS LEVEL OF FAILURE MAKES ME FEAR GREATLY.

That can happen to other Windows computers too. It's happened to me, and it's happened to my dad's PC. Both are custom built systems. It's a Windows issue. I understand Razer support were not knowledgeable about this, but to be fair, I don't expect them to know about all the issues with Windows.