Severe Audio Volume Spike and System Sounds Ignoring Volume Mixer – Razer BlackShark V2 Pro (2023) | Razer Insider
Skip to main content
Question

Severe Audio Volume Spike and System Sounds Ignoring Volume Mixer – Razer BlackShark V2 Pro (2023)

  • November 4, 2025
  • 1 reply
  • 104 views

firstparkSlateGray988

I’m experiencing a persistent and very frustrating audio issue with my Razer BlackShark V2 Pro (2023) headset on Windows 10.

After a few seconds of silence, the next sound played suddenly becomes extremely loud for a brief moment (a sharp volume spike), before returning to normal. This happens consistently — for example, when watching videos, opening a tab in opera with browser-sounds activated, or receiving a system notification.

Additionally, Windows system sounds completely ignore the volume mixer. Even if I mute system sounds or set them to 0%, they still play at maximum volume through the headset and then reset themself in the audimixer to 100%. These two issues combined make normal use very uncomfortable.

 

What I’ve tried (none of these fixed the issue):

  • Reinstalling and uninstalling Razer Synapse 4

  • Enabling / disabling Windows Enhancements

  • Turning off all Spatial Sound options (I don’t want any spatial audio)

  • Setting “Do nothing” under Communication settings in Windows Sound Control Panel

  • Installing/Deinstalling Realtek audio driver

The only temporary workarounds I found are:

  • Setting the spatial sound format to Windows Sonic for Headphones (which I don’t want to use), or

  • Disabling all enhancements in Windows — but this also disables the Razer EQ, Bass Boost, and all Synapse audio features, which defeats the purpose of having this headset.

     

    Summary:

  • Audio volume spikes occur after short periods of silence.

  • System sounds ignore the Windows volume mixer.

  • Problem persists across reboots and driver reinstalls.

  •  
  • I do not use or want any spatial sound features (THX or Windows Sonic).

1 Reply

Vekez_3
  • Insider Mini
  • November 11, 2025

Experiencing the exact problem with the same headset. Nothing seems to work for me either. THis started happening immidietly after I updated to synapse 4.