I cant seem to change the sensitivity button keybind and reset the onboard memory of my Deathadder v2 x hyperspeed | Razer Insider
Skip to main content
Question

I cant seem to change the sensitivity button keybind and reset the onboard memory of my Deathadder v2 x hyperspeed

  • February 10, 2026
  • 1 reply
  • 7 views
T

Hi,

So I have been owning the razer Deathadder v2 x hyperspeed for a long time now and when I bought it I had set some keybinds for the sensible stage button and it got saved in the on board memory and now I want to change it but when I change it is works when the software is open or open in background and when the software closes it doesn't work and the sensitivity stages buttons go back to the keybinds I set a long time ago that I don't want and is causing me trouble

What I have tried-

1.try reset the settings of the mouse from the synapse app

2.try manually reset the mouse from the button combinations which prolly don't even work

3.try installing synapse 3 to use the omm page in it

4.try find the razer omm

 

I can't find the razer synapse 3 and whenever I find a link it redirects to synapse 4 and its annoying and I LOWK regret getting this mouse but pls help me dude I know it's the omm but I can't change it

1 Reply

Razer.Zionzedd

Hi technoDarkLavanexus565,

 

Thank you for sharing your experience and the steps you tried. Please know that Razer has effectively discontinued Razer Synapse 3 effective February 3, 2026. You can know more when you visit: https://mysupport.razer.com/app/answers/detail/a_id/3783/~/razer-synapse-3-support-and-faqs Anyhow, the Razer DeathAdder V2 X HyperSpeed has one onboard memory profile that stores DPI stages and basic keybinds. The issue where settings revert when Synapse closes is common and often happens because the mouse is not properly overwriting the old, stored "ghost" profile. PM me your Razer mouse’s SN: (Follow steps here: https://mysupport.razer.com/app/answers/detail/a_id/548/~/how-to-find-the-serial%2C-product%2C-or-part-number-on-a-razer-device), so I can give you a device’s specific steps to fix this once and for all.

 

*Thread locked to PM

CookiesCookie settingsAccessibility statement