Cracking audio and sound volume fluctuations in Razer Blackshark V2 SE after update Synapse 3 20240718 (3.9.630.62714) | Razer Insider
Skip to main content
Question

Cracking audio and sound volume fluctuations in Razer Blackshark V2 SE after update Synapse 3 20240718 (3.9.630.62714)

  • 20 July 2024
  • 7 replies
  • 261 views

Hello, I had a problem with my Razer USB Sound Card device. Yesterday my Razer Synapse 3 updated to version 20240718 (3.9.630.62714). After that, the sound in my Razer Blackshark V2 SE headphones became terrible. The sound began to fluctuate in volume and there is a feeling as if someone in real time turns the equalizer, so the sound becomes unbearable. Also, if you start watching a Youtube video for example, the sound only comes on after 2-3 seconds and after that it also sounds terrible.
I tried a lot of things to fix this problem, namely: 

  1. Plugged the sound card into different USB ports.
  2. Uninstalled the Razer Synapse 3 program and sound card drivers in different ways (including using the official Razer utility: https://mysupport.razer.com/app/answers/detail/a_id/5776/~/how-to-use-the-device-detection-troubleshoot-tool).
  3. Turned off, uninstalled and changed Dolby Access settings (didn't help, it's not the problem).
  4. Installed past versions of Razer Synapse 3 that were saved on my computer, but those versions did not see my sound card.
  5. Installed a newer version of Razer Synapse 4, but the problem persisted.
  6. Rolled back the sound card drivers.
  7. Checked for an update in Windows.

In the end, the only thing that partially helped was disabling “Sound Enhancements” or turning on “Disable all additional effects” in the Windows 11 sound settings. But the problem is that it disables the entire Razer Synapse 3 program (i.e. all my profiles, EQ settings, and THX Sounds (spatial sound)) when doing so. Also, if I connect my headphones via 3.5 mm jack (i.e. disable the external sound card), the sound works fine.

Now I'm already desperate to solve this problem myself, that's why I'm writing here. But still, what else can I do to solve this problem with sound?
If someone now has the same or similar problem with sound, please write here, because it is possible this problem with the latest version of Razer Synapse 3 20240718 (3.9.630.62714).

 

Also, anyone who has a Razer USB Sound Card running Razer Synapse with the latest update without problems, please post here. I want to see if I'm the only one with this problem.

7 Replies

i started getting that this morning as well!  i hope someone is able to find a fix too…  in the meantime i suppose i will just use the direct connection instead of the Sound card.

Exactly the same problem here and i did also everything you mentioned up there, still nothing unless turning off enhancments.

i hope they fix this soon

please reply if anyone find a solution

I reinstalled my Windows (there were other reasons for this) and that didn't solve the problem.

i started getting that this morning as well!  i hope someone is able to find a fix too…  in the meantime i suppose i will just use the direct connection instead of the Sound card.

Exactly the same problem here and i did also everything you mentioned up there, still nothing unless turning off enhancments.

i hope they fix this soon

please reply if anyone find a solution

Found a temporary alternative to Razer Synapse for headphones - SteelSeries Sonar (Sonar | SteelSeries). It has its own equalizer and spatial sound + other settings.
P.S, I hope Razer will fix its software as soon as possible, because I read Reddit and there people also complain about it, for various reasons.

I also have the same problem but when watching a video on youtube, after 3 seconds the sound becomes very loud. i tried some sounds here and there and it was normal but only for 15 seconds.

I found a solution guys

Just uninstalled synapse/sound card and installed an older version of synapse

Problem solved

I installed the latest Razer Synapse Beta. In the process it redownloaded and installed the USB Sound Card. That seems to have fixed the issue.

Reply