Re: USB ports cutting in and out

Hi EA_Illium,

Thanks for your reply. I am playing on Steam, Windows 11. I have trouble shooted this problem and it is 100% related to the RAZER Viper Ultimate Wireless Headset. The moment I switch to the Viper headset as the Audio Output, it causes all the issues I mentioned. Switching in-game to a different Audio Output such as my Aux speakers or Apple Airpods completely resolves any issues. I have been in touch with Razer support and notified them of the problem. However, it should be stated that this issue only occurs when playing the Dead Space Remake specifically. Other games such as The Witcher Complete Edition, A Plague Tale Requiem, Diablo II Resurrected & The Callisto Protocol do not have any audio issues when using the Viper Headset. 

Worth mentioning that others online have had ongoing issues with Razer Audio products having sound cutting in and out also.

Hi @asmith985 How many other devices do you have connected to the device? Would it be possible to get a DxDiag?

No worries EA_Illium. DXDiag attached cheers.

USB devices: Mouse, Keyboard, Headset, 1 x external HDD, XBOX controller.

They are attached to an Asus Maximus Extreme Z790 MB with a 1600 Corsair PS.

Cheers

Hi @asmith985 You mentioned you have an Xbox controller connected, when the M+K seems to cut out does the controller still work? Or, do you notice if your controls in settings just get switched over to gamepad inputs?

Hi again,

I did not use the controller to play this game. It was in its charging dock which was USB connected. And I have since finished Dead Space (using my apple airpods for audio which did not have the issues I had with the Razer Blackshark V2 Pro Wireless Headset - sorry I think I mistakenly called it a Viper Headset before).

Not a lot else I'm prepared to do to continue trouble shooting this issue to be honest. It is a very specific issue with the Razer Headset. I reported it to Razer who started asking their typical '20 irrelevant proforma questions', so I cancelled the support ticket. Think I will just let this problem slide since I found a work around. It's on Razer to investigate it further - or not.

I did appreciate your help regardless.

Kind regards,

asmith985