Problem with Synapse (on board memory? ) | Razer Insider
Skip to main content
Question

Problem with Synapse (on board memory? )


Hello ! 
I have the exact same problem 



I’m using Deathadder v2 hyper x speed, so this mouse HAVE on board memory.
I always used macros, but this … “bug(?)” appeared suddenly two days ago for no reasons.
I’m trying everything, looking everywhere on the internet : nothing fix it.
Everything is updated on razzer apps.
What can i do? 

Did this topic help you find an answer to your question?

8 Replies

anybody has a clue or something? 


FiszPL
Vanguard
Forum|alt.badge.img+1
  • VANGUARD
  • 7137 replies
  • March 30, 2025

Is is NOT A BUG. It’s only an information that complex keybinds, like macros won’t work without Synapse running in the background.

To save macros into mouse/keyboard onboard memory it’ll require to have at least 4 profile memory, and DA v2 Hyperspeed have only 1 onboard memory (for storing DPI / Hz and simple keybinds).


I’m actually in contact with razer customer service that tell me it’s a bug so…

My mouse is supposed to have onboard memory.
I had my macros working, changed nothing, and it doesn’t work anymore overnight

What do you mean by “without Synapse running in the background”? I have synapse launched like i used to do. My macros stopped working three days ago without any reason / update.
So i don’t understand how my macros worked if it’s not supposed to , like you said, because my mouse has only 1 onboard memory. 
It doesn’t make any sense


FiszPL
Vanguard
Forum|alt.badge.img+1
  • VANGUARD
  • 7137 replies
  • March 31, 2025
leetLavenderBlue664 wrote:

I’m actually in contact with razer customer service that tell me it’s a bug so…

My mouse is supposed to have onboard memory.
I had my macros working, changed nothing, and it doesn’t work anymore overnight

What do you mean by “without Synapse running in the background”? I have synapse launched like i used to do. My macros stopped working three days ago without any reason / update.
So i don’t understand how my macros worked if it’s not supposed to , like you said, because my mouse has only 1 onboard memory. 
It doesn’t make any sense

Again… this sign is only an information, it is not a bug

Unless macro won’t work at all - this is a bug. Synapse is auto-updating in background, so that’s why it may stopped working.

If you still using Synapse 3, then you might try newer Synapse 4 and check if it’ll work or not: https://www.razer.com/synapse-4


I will try to explain the situation more clearly and with a better translation.

I have been using the Synapse software and its macros/profiles (configured within the software) for a little over two years, if I remember correctly. Everything was working fine—I used it regularly, almost daily—until about 3–4 days ago, when it suddenly stopped working (with the issue I have been describing from the beginning, which did not exist before).

Following this, you explained to me that this is normal because my mouse model does not have onboard memory. In that case, how do you explain that it worked perfectly for two years? If it is possible to use macros without onboard memory but with Synapse running, then something must be preventing Synapse from functioning correctly on my computer since, once again, everything was working fine before.

Once again: this issue occurs on both Synapse 3 and Synapse 4. There is therefore a real technical issue, and it is not caused by my hardware. 


FiszPL
Vanguard
Forum|alt.badge.img+1
  • VANGUARD
  • 7137 replies
  • April 1, 2025
leetLavenderBlue664 wrote:

I will try to explain the situation more clearly and with a better translation.

I have been using the Synapse software and its macros/profiles (configured within the software) for a little over two years, if I remember correctly. Everything was working fine—I used it regularly, almost daily—until about 3–4 days ago, when it suddenly stopped working (with the issue I have been describing from the beginning, which did not exist before).

Following this, you explained to me that this is normal because my mouse model does not have onboard memory. In that case, how do you explain that it worked perfectly for two years? If it is possible to use macros without onboard memory but with Synapse running, then something must be preventing Synapse from functioning correctly on my computer since, once again, everything was working fine before.

Once again: this issue occurs on both Synapse 3 and Synapse 4. There is therefore a real technical issue, and it is not caused by my hardware. 

As said earlier - macros not working = bug. Also as said earlier - synapse is auto-updating in background, maybe they broke something with it with some update - dunno (it’s working fine for me on Synapse 4).

The information on the screenshot, that you’ve highlighted = not a bug, it’s only notification.

You can try clean reinstalling Synapse if you haven’t tried it yet:

  1. Uninstall Synapse
  2. Download & run this tool: https://rzr.to/Tf53xj to remove any razer drivers/leftovers
  3. Then restart your PC
  4. After reboot install Synapse again (as administrator).

Yes, i tried what you said, it changed nothing.
 

I’ve investigate, the problem come from Synapse installer (3 or 4 it’s the same problem).
It seems that i can’t completely install Synapse.
Synapse service can’t be launched because the path was not found on my folders.

 i can see that synapse doesn’t even install “synapse3” directory. It stopped at “razer” : 

I tried everything to install synapse properly : total uninstall of current synapse via revo uninstaller + regedit deleting key from razer + reinstalling everything as admin in Safe Mode with Networking without any protection / firewall => still the same issue


FiszPL wrote:

Is is NOT A BUG. It’s only an information that complex keybinds, like macros won’t work without Synapse running in the background.

To save macros into mouse/keyboard onboard memory it’ll require to have at least 4 profile memory, and DA v2 Hyperspeed have only 1 onboard memory (for storing DPI / Hz and simple keybinds).

Okay, so today I have proof that the issue doesn't come from my computer, that it is indeed a bug, and that it's directly related to Razer and not a mistake on my part somewhere on my PC or anything else: I tested it today on my second computer, and I have exactly the same problem.

 


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings