Start with evidence
Run the tests that separate the likely branches
Keyboard TestPress keys and verify that the browser receives the expected keyboard events.
Run →Keyboard Chatter TestLook for duplicate key presses that may indicate switch chatter.
Run →Keyboard Repeat Rate TestHold a key and observe browser repeat events to compare repeat behavior after changing keyboard or operating-system settings.
Run →NKRO Keyboard TestCheck how many simultaneous key presses your browser receives.
Run →Decision table
What the observation changes
ObservationWhat it meansNext action
One key repeats in raw chatter testA key-specific switch/sensor issue is more likely than an app macro.Reset profile/actuation for that key and retest.
Many keys change after profile resetConfiguration was likely involved.Rebuild actuation/rapid-trigger settings gradually.
Only one game shows repeatsApp/game mapping is higher priority.Check game bindings/macros before hardware service.
Sequence
Work from reversible checks to escalation
- 01
Capture raw key events.
- 02
Reset suspect profile/actuation settings.
- 03
Reconnect direct to host.
- 04
Retest outside games/Synapse macros.
Likely areas
Keep these branches separate
Actuation/rapid-trigger configurationKey-specific chatterSynapse profileUSB pathKeyboard hardware
Repair boundary
When to stop changing settings
Persistent single-key raw duplicates after profile reset across hosts should go to Razer support.