Conexant HD Audio cuts out in Windows 10

Update June 6 2019: Win 10’s 1903 update borked the Chromecast sound again when it installed Conexant audio drivers. I deleted the Conexant audio drivers as below and all is good until the next time.

Well here we go again. Those stupid sons of bitches at Microsoft have seen fit to keep updating my drivers to Conexant, even though I don’t want Conexant’s useless garbage. Last night I perferformed a removal as below, then went through my registry to delete all of the Conexant entries. We’ll see how it goes on June 7.

*

I’ve been having a problem with my Windows 10 Conexant HD Audio driver cutting out every 18 minutes while using my Chromecast (any version) to transmit to my television. It started a while ago, and it’s obviously a driver problem.

I would send a movie. It would have sound for 18 minutes before going silent. I had to turn off casting and turn it back on, and thus I had sound for another 18 minutes.

Win-X, select Device Manager, double-click on Sound, video and game controllers.

Select Conexant HD Audio driver. Double-click. Select Uninstall. Re-boot to have the uninstall take effect.

When your screen comes back up, you’ll have a red x on your speaker icon on the taskbar. Right-click and select Troubleshoot sound problems. It should find drivers for you. They probably won’t be Conexant drivers, but that’s okay. Conexant drivers don’t work properly with Windows 10 anyway.

Here’s another possible solution, although in my case, I didn’t try it, so I don’t know if it works. If the Conexant HD Audio cutting out returns, I’ll give it a try. I doubt that will happen, though. I no longer have the Conexant HD Audio drivers on my Windows 10 system. Nope. Doesn’t work.

A problem with Conexant audio means that you may hear no sound in Windows 10 even though everything appears to be working correctly. While this is being investigated, Microsoft suggests running msconfig.exe and heading to the Boot tab. Click the Advanced options button, check the Maximum memory box and set the value to 3072. Apparently, 4096 worked, too, but like I said, I didn’t try either setting.