Start with evidence
Run the tests that separate the likely branches
Decision table
What the observation changes
ObservationWhat it meansNext action
Only one key duplicates in raw testA local switch/socket path is plausible.After power-off/safe handling, reseat or substitute a known-good compatible switch per Razer guidance.
Fault follows the switch to another socketSwitch is strongly implicated.Replace that compatible switch.
Fault stays with socket after switch swapSocket/PCB/firmware becomes more likely.Reset firmware/profile and use Razer support.
Sequence
Work from reversible checks to escalation
- 01
Record chatter in DeviceOK.
- 02
Disable macros/remaps.
- 03
Compare a known-good compatible switch if comfortable and within warranty guidance.
- 04
Retest raw events.
Likely areas
Keep these branches separate
Individual switchSocket/contactProfile/macroKeyboard PCB/firmware
Repair boundary
When to stop changing settings
Use Razer support for socket/PCB faults or if switch work would conflict with warranty/safe handling.