Disconnecting and reconnecting?

this sucks i got a razer setup and tried everything to wiping my hard drive lol this is crazy every product i get ends up braking in a year or so razer lasted the longest most durable i found so far but this disconnecting sucks mad thoughts even my keyboard flashes and disconnects

foxyfate
Yeah my headset went a few days with no disconnect issues and now it's acting up again after this last Razer Synapse update.

I can 100% agree that it's the program causing this, btw. I have the same issue for so long now. Got the headset replaced- worked for 1-2 months- and then broke again. I updated everything, even paid for a program to check if everything is updated- I bought some extra stuff for my USB ports to give them more power- I made sure I barely run anything to not make anything overwork- Nothing.

What I did notice tho, one night, the headset did not connect with Synapse at all. It was not glowing, it was not showing up.. And guess what? It didn't disconnect a SINGLE time. I find it very stupid, that there is no fix for it. At this point, I wish I didn't spend this much money on the headset + trying to fix it. Such a shame honestly. That got me to the point where I won't buy any Razer products at all anymore. Not the first time something broke without any reason.

I have the same problem since the first day I used the headset phones (Razer Kraken Kitty), and I'm sick about. I'm going to request a refund to amazon, because this is a shame.

Another one for the club My Nari Ultimate is doing the same, has been since the latest update if I close Synapse 3 I get no disconnection turn it on problem will present either immediately or may take up to 5 min's it's like the driver is being kicked out for some reason by Synapse's

I did an RMA and since then it's been fine. But I would not be surprised if it starts bugging out again. I almost want to think it may also be a design issue.

thakyZ
Well double explaining wouldn't be a problem. But what I have done is I tried for quite a while my headset on my phone and it seems fine, no disconnecting or anything.

I noticed that the THX audio device at time just straight up doesn't work. So I go and fiddle around with it by restarting Razer Synapse and disable the device while doing so. It seems to *sometimes* work after that, but then there is still the issue of the Razer Kraken device disconnecting every so often, which I still think is the fault of my Motherboard but I am still not sure, as the updates that supposedly fix the issue on my motherboard don't seem to work.

I have also tried to reinstall Windows and Razer Synapse.
I also tried to go and uninstall Razer Synapse uninstall all drivers. Then unplug all devices. Then inserted a non-razer keyboard and mouse and reinstall razer synapse after a restart. When reinstalling I log into Razer and then go to the update section and I plug the mouse in first. Which I let it update and then I click update, and I do that with every device up to the headset. And still it likes to disconnect even then.

Were you ever able to get a resolution? I have exactly your problem and I've spent more than a month dealing with Razer support. They don't having staffing issues as much as they have incompetency issues.

I also have the same problem. I got my Razer Kraken Kitty 1 year ago and it was completely fine. This year, the issue appeared. When I increase the volume they do the popping sound and disconnect. Even though, Razer Synapse is turned off. Now, I think that I'm gonna uninstall it and see if they will disconnect or not.

Also, I tested them on the other PC, on which Razer Synapse wasn't installed, and they were doing the same thing. Disconnecting all the time when I wanted to increase the volume.

I'm really disappointed in Razer. I thought that the headphones will work for a lot of time without any issues T_T
Even though, my Mamba Wireless mouse works perfectly.

TheShykid_
Hey!

so I recently just finished my dream razer setup with Blackwidow keyboard, basilisk mouse, kraken kitty headset and goliathus mouse pad.. I updated my computer and my synapse right after connecting everything and it worked fine in the start but then it started disconnecting and reconnecting.. all of it.. and the headset is making a popping sound.. I have no idea what it is at all! Please help :/

It is a pity really, both me and my wife have bought the Razor Kraken and the Razor Kraken Kitty headsets, first my wife started to complain about her headphones disconnecting and making a popping sound, she had them for almost a year. So we switched out, because my headset wasn't having the issue, me wearing her Kraken Kitty and she wearing my Razor Kraken headset. So initially I didn't experience it until push came to shove being in a video conference call, then it started acting out, I had to switch back to my laptop's speakers because I could literally not follow the conversation, due to the constant disconnecting and reconnecting. I doubt that it is a windows setting causing this, since we tried it on several different laptops.

We've since returned the Headphones to the shop where we bought it, hopefully sending in the unit back to the supplier, might resolve the issue. However since waiting for any feedback from the supplier, my Kraken Headphones has also started to intermittently disconnecting. I am starting to wonder if I should rather spend my hard earned money elsewhere - I'm not willing to spend such a high amount of money on a product that spazzes out within a year.

I thought this might be an isolated incident, but since I found this thread, I thought sharing my experience might help someone when choosing a headset provider.

I also doubt that I will receive any form of feedback from Razor on this post, just as all the wonderful feedback the other users who had feedback from Razor. I mean who cares about customer feedback right?

Kind regards
The guy who seriously considers that the only Razor you should buy is the one you shave with.

This whole situation is such BS. I got my headset in April and it worked completely fine until a week or so ago. Now I'm going through the same problems everyone else is in the thread. If I manage not to move the headset's cable it doesn't disconnect AS often, but it still disconnects. And I know this is a software issue because every time my kraken kitty disconnects my keyboard, an ornata chroma that i've had for 4+ years with no problems disconnects and reconnects at the same time with the headset.

Same thing is happening to me

I've been having this issue for months. MONTHS. And just on my latest headset, I had this same issue with the Kraken Kitty before this one... so double the time, I guess. A year? Way too much time considering the price tag on Razer products.

Anyways, I've tried the above solutions, been fiddling with various tests of trial and error. Here's what I've learned:

• It is definitely a Synapse problem. Usually every time it updates, it breaks for weeks. My theory is that there is spaghetti code somewhere that borks on the backend.
  
  
  
• When swapping from audio to audio and voice input, the headset is more likely to freak out than not. The headset also really hates lower volumes having a steady connection, and if you have a haptic setting? ggwp
  
  
  
• I can set my watch to it rapidly flickering its connection starting at the same time every night. My theory is this coordinates with Synapse uploading your profile setting backups to their cloud (potentially shorting the wires with the voltage surge, then causing an infinite loop?), and may be tied to it pinging the latest cloud settings whenever the mic is accessed by a program.
  

Now. How I got it to be bearable:

• Yelled at my PC a lot. It made me feel better. Also got my money back for the USB docks I bought and instead invested in Amazon's vast selection of cord lengths.
  
  
  
• Utilized Windows Firewall and my antivirus to block all Razer processes from accessing the internet. There's no internal way in the program to disable the cloud connection and sync. Make sure you are logged into your Razer account in the program prior to disabling internet access.
  
  
  
• Disabled any of the extra modules I wasn't using. Chroma Studio is really all you need unless you have the specific devices/connections the other modules utilize. Chroma Studio, on its own, can handle your RGB and coordinating it across your devices. (Uninstalling the modules is a pain in the rear-end. Be prepared for flickering connections and Synapse to freeze up repeatedly.)
  
  
  
• For funsies, ran the repair tool from the uninstall interface, used a program to wipe up any dust in the registry.
  

Other fun activities I really shouldn't have to do to get the quality I want from this headset for the price I paid:

• Disabled Realtek's devices from the device manager. For some reason, Realtek and Razer like to conflict.
  
  
  
• Installed my RGB programs (I use an ASUS standalone for my GPU) on separate drives.
  
  
  
• Regularly use the Bluetooth re-pairing tool to refresh my headset connection. Also, regularly update my Bluetooth driver.
  
  
  
• Keep my headset charged. I do think there is some merit in some of the disconnections being tied to voltage in some way, because the flickering happens frequently when the power is low but not low enough to trigger the low battery warning, especially if my volume is low. (These disconnects are frequent and occasionally disable the mic until I reboot them. However, they are not as rapid as my nightly "settings syncing to the cloud" epilepsy attack issues are.)
  

TL;DR, Razer: Fix your internal wiring for the voltage, and fix your program (or give us some options to disable the constant sync plz&ty).

Xeillious
I tried this and so far and my mouse still is disconnecting.

I judged too soon, but after a couple of days without using the mouse, it seems to be working fine. The computer probably would need a restart before you'd see if it works or not.

(edit) I'm not going to continue making posts going back and fourth but the bottom line is that it stops for about a couple of hours and then continues on like it was never fixed. Sorry about the confusion.