Synapse 4 pegs a CPU core: Ambient Awareness on Huntsman Elite floods "mutexLockBatchCount exceeded" | Razer Insider
Skip to main content

Synapse 4 pegs a CPU core: Ambient Awareness on Huntsman Elite floods "mutexLockBatchCount exceeded"

  • Nov 13, 2026 5:56 AM UTC
  • 0 replies
  • 4 views

CITRINEbizWheat764

Synapse 4 (RazerAppEngine 4.0.896, Windows 11 Pro build 26200) burns about 90% of a CPU core whenever my Huntsman Elite is set to Ambient Awareness (full screen). main.log gets this line about every 80 ms, nonstop:

sendFeatureReportInBatch mutexLockBatchCount exceeded key: 550-{A071A02F-D2D2-11F0-BE08-806E6F6E6963}-2-0-0-

It started on Nov 10 at 9:51 PM, a few milliseconds after my Basilisk V3 Pro 35K reconnected over Bluetooth. Since then it comes back within 10 seconds of every Synapse launch. Restarting Synapse, resetting the keyboard's USB device and clearing Synapse's cache didn't change anything. With the keyboard's interface 2 disabled, it logs "sendFeatureReportInBatch device not found" at the same rate instead.

Switching the Huntsman from Ambient Awareness to Static stopped it within 4 seconds, and CPU went back to normal. It looks like Ambient Awareness sends screen frames to this keyboard faster than the batched feature reports can finish, and the lock never recovers.

Setup: Huntsman Elite on USB, Basilisk V3 Pro 35K on Bluetooth, Kiyo webcam. Synapse auto-updated on Oct 28. I can send logs from Razer Log Collector.