3 weeks ago
As the title suggests, I’m experiencing an issue with my 2-week-old ASUS ROG G615LR laptop. The speakers generally sound great, but after a few minutes of playback, the left speaker starts cutting in and out intermittently, while the right speaker continues to function normally.
Here’s what I’ve tried so far:
Reinstalled both Realtek and ASUS TI audio drivers multiple times.
Disabled all software audio features, including device enhancements and spatial audio, to rule out software conflicts — no improvement.
Uninstalled and reinstalled the Realtek Audio Console; the issue persisted even when it was uninstalled.
Did the same with Dolby Access — no change.
Performed a clean reinstall of Windows 11.
I’d appreciate any suggestions or potential solutions to help resolve this issue.
Thank you.
Solved! Go to Solution.
3 weeks ago
did you install unofficial drivers before? I encountered the same bug on the G814JV (2023) after flashing the BIOS via a programmer, the checksums changed (different from the asus original)
I know exactly how this bug is caused if I install Realtek UHD Audio Driver Nahimic PCEE4 DTS X Creative DD DDP ATMOS G RC4 in Realtek Audio Console during tests, the left and right speakers create a sound dump in the left channel. Fix long experiments with reinstalling R272 R280 R281 R282 R283 (ISST driver for HDA) + patch rltkapo64.dll (pirate)
and finally manually installed updated audio drivers via the catalog microsoft
https://www.catalog.update.microsoft.com/Search.aspx?q=intelaudio%5Cfunc_01%26ven_10ec%26dev_0294%26...
My model also has an AlC3288 audio chip (under the hood), and Windows displays this chip as ALC294. If I look at the G615LR driver download page, I see some drivers compatible with my device.
Important, in my case, when loading the boot balance is fine, a bug appears - left sound in the system. And even formatting will not fix it! These chip settings are stored somewhere deep, until initialization occurs through the old driver / pirated Dolby / Realtek patches, it is possible to restore the balance. Most likely, the audio chip has more settings options, but Microsoft is putting pressure on Asus in order to cut down on functionality. This is not an easy way to fix this problem, I had to install 2 operating systems on 1 SSD in different partitions, and I noticed that if the sound failed in one Windows, the settings are displayed on the second Windows. Horrible closed software! Some of the settings are stored in the Hub, this causes many problems.
study this message, the Realtek bug was encountered on the Internet ~10 years ago and is still present today
https://rog-forum.asus.com/t5/rog-zephyrus-series/speakers-under-water-issue-yes-i-know-not-the-firs...
2 weeks ago
I finally managed to resolve the issue. The first step was updating the Realtek audio driver using DriverIdentifier—a highly effective utility for sourcing the latest compatible drivers. I then proceeded to update the Texas Instruments (TI) audio driver. Interestingly, after installing the latest available TI driver, I noticed the issue’s frequency dropped by approximately 50%, which strongly suggested that the TI driver was a contributing factor.
To isolate the root cause, I uninstalled the TI driver and attempted to roll back to an earlier version—one older than the factory-installed version. However, Windows Device Manager continued to detect and register it as the latest version. After further investigation, I found that residual driver components—specifically .bin files named under the “TAS2xxx” schema—were being retained in the C:\Windows\System32\Drivers directory.
To address this, I took ownership of the folder and granted myself the necessary permissions to delete these TI-related files. Once all TAS files were permanently removed, I reinstalled the older version of the TI driver. This time, Device Manager correctly registered the intended version, and the intermittent left-channel speaker issue was fully resolved.
However, the next day, MyAsus automatically pushed a TI driver update in the background—without any prompt. Although I subsequently disabled automatic driver updates, the new version had already been installed. Interestingly, this driver version appears to be even newer than what was listed on DriverIdentifier. So far, I haven’t observed any recurrence of the issue with this version, which suggests that the latest TI driver may have addressed the underlying bug.
3 weeks ago
did you install unofficial drivers before? I encountered the same bug on the G814JV (2023) after flashing the BIOS via a programmer, the checksums changed (different from the asus original)
I know exactly how this bug is caused if I install Realtek UHD Audio Driver Nahimic PCEE4 DTS X Creative DD DDP ATMOS G RC4 in Realtek Audio Console during tests, the left and right speakers create a sound dump in the left channel. Fix long experiments with reinstalling R272 R280 R281 R282 R283 (ISST driver for HDA) + patch rltkapo64.dll (pirate)
and finally manually installed updated audio drivers via the catalog microsoft
https://www.catalog.update.microsoft.com/Search.aspx?q=intelaudio%5Cfunc_01%26ven_10ec%26dev_0294%26...
My model also has an AlC3288 audio chip (under the hood), and Windows displays this chip as ALC294. If I look at the G615LR driver download page, I see some drivers compatible with my device.
Important, in my case, when loading the boot balance is fine, a bug appears - left sound in the system. And even formatting will not fix it! These chip settings are stored somewhere deep, until initialization occurs through the old driver / pirated Dolby / Realtek patches, it is possible to restore the balance. Most likely, the audio chip has more settings options, but Microsoft is putting pressure on Asus in order to cut down on functionality. This is not an easy way to fix this problem, I had to install 2 operating systems on 1 SSD in different partitions, and I noticed that if the sound failed in one Windows, the settings are displayed on the second Windows. Horrible closed software! Some of the settings are stored in the Hub, this causes many problems.
study this message, the Realtek bug was encountered on the Internet ~10 years ago and is still present today
https://rog-forum.asus.com/t5/rog-zephyrus-series/speakers-under-water-issue-yes-i-know-not-the-firs...
2 weeks ago
I finally managed to resolve the issue. The first step was updating the Realtek audio driver using DriverIdentifier—a highly effective utility for sourcing the latest compatible drivers. I then proceeded to update the Texas Instruments (TI) audio driver. Interestingly, after installing the latest available TI driver, I noticed the issue’s frequency dropped by approximately 50%, which strongly suggested that the TI driver was a contributing factor.
To isolate the root cause, I uninstalled the TI driver and attempted to roll back to an earlier version—one older than the factory-installed version. However, Windows Device Manager continued to detect and register it as the latest version. After further investigation, I found that residual driver components—specifically .bin files named under the “TAS2xxx” schema—were being retained in the C:\Windows\System32\Drivers directory.
To address this, I took ownership of the folder and granted myself the necessary permissions to delete these TI-related files. Once all TAS files were permanently removed, I reinstalled the older version of the TI driver. This time, Device Manager correctly registered the intended version, and the intermittent left-channel speaker issue was fully resolved.
However, the next day, MyAsus automatically pushed a TI driver update in the background—without any prompt. Although I subsequently disabled automatic driver updates, the new version had already been installed. Interestingly, this driver version appears to be even newer than what was listed on DriverIdentifier. So far, I haven’t observed any recurrence of the issue with this version, which suggests that the latest TI driver may have addressed the underlying bug.
a week ago
Brother, after hearing your experience, it seems like you are thinking step by step like a human being, like a conscious user. First, understanding the root cause of the problem and updating the Realtek and TI drivers that was a realistic decision. Then, when you realized that the problem was with the TI driver, the idea of deleting the .bin file while installing the old version was a very wise step. In the end, even after updating MyAsus, the problem did not occur anymore, so it is understood that the bug was fixed in the latest update.Brother, your thinking is completely humane and reasonable. Just as you understood the problem and solved it step by step, you can also use the Fix My Speaker tool if necessary. Very humane and logical thinking!
a week ago
Thanks a lot mate. Happy to share what I learned and solved 😄.