Razer Megalodon and 64 bit Windows 7
- November 30th, 2009
- Posted in Anything Else . Hardware & Technology
- Write comment

I use my Megalodon headset mainly for gaming, and some music every now and then too. Since the upgrade to Windows 7 64 Bit, the Megalodon now cuts out completely after a couple minutes – going from perfect sound to no sound. Apart from the sound cutting out, the microphone no longer performs as it did on Windows XP, with what I can only describe now to be a crackly distorted version of its once perfect and better than the rest sound it had.
After a quick Google search it became clear that I wasn’t alone, there are also plenty of forum posts and a Facebook discussion dedicated to this issue with the Megalodon.
Everyone is waiting in vain it seems for a solution, as Razer’s support team clings to the copying and pasting of their favourite useless generic responses like a fat kid on a cupcake. This doesn’t go down too well with myself or the mass of angry Megalodon owners who feel they have been wholly cheated on purchasing a R1600 ($215) headset.

Razer have released a very promising looking firmware updater since, which promised the fix, but turned out to be a massive let down as it merely takes an extra 30 minutes for the sound to cut out. You can join in on the dissappointment by following this link.
Others have found hope, as you can buy a self powered USB hub and plug the Megalodon into that. This makes it pretty obvious that the Megalodon has power management issues with the newer OS’s. All in all, I stand with the majority of folks who say, “why should I buy something else to make it work!?”
Razer have let me down badly, and I don’t think I will ever buy another thing from them. This kind of thing will surely bring them down, and hopefully they fix it soon, before I’m forced to get a refund. What was in my opinion (and many others) a highly anticipated product has become a nightmare and major let down – the Megalodon is a fantastic headset when it works, but sadly Razer have gone from hero to zero.
If you have any advice for myself and others until this is fixed, please drop a comment below.













@ZeBuLoN
Agreed, I too am still running the beta.
@Dax Frost
Hey Dax,
I really appreciate what your doing and it’s been really helpful for me since I’m going to get a Megalodon myself in a few days. I’m just wondering, did the 32-bit have this problem? And I’m guessing as of now, the beta firmware is the best way to go to solve this?
Thanks in advance and keep doing what your doing Dax Frost
Hey @Redness,
If you’re running 32 bit you should be 100% fine.
No one has had any issues with 32 bit.
Additionally, if you do upgrade to 64 bit, there is already a solution here.
I contact Razor support, because I had the same problem. Here is the answer :
“1. Try plugging the device into a different USB port on the system. If the device is plugged into a USB port on the front of the system, try a USB port in the back.
2. Disconnect all other USB devices.
3. Remove any USB Hubs. Plug the device directly into a USB on the system.
4. Try the product on another system, without using any drivers. Does the problem still occur?
5. If the problem is occurring in an application, does the problem occur outside the application directly in the operating system?”
I tried what they said. My computer is a laptop, so it doesn’t have a front USB port. But I tried to connect the device without any other device connected trough USB. And it works! I saw that I have to connect the Megalodon before connecting my keyboard to have a sound…
I can’t understand…It’s too weird, but it…is…
Hi @Nico,
there is already a solution here.
i did a rma for my megalodon, and i received a brand new one. got still that “cracking” problem, but only with older games. the new ones are working fine, but older games, like stronghold, are not playable at all.
To solve all your problem, if your USB port is not 3.0 or over 900mA , your megalodon will crash. It’s a power issue. I know it cause I got the same problem as all of you. then I bought a usb 3.0 card and I got no more problem. Hope this help
SemiBruceLee