cancel
Showing results for 
Search instead for 
Did you mean: 

Asus B650E-E Audio Driver Sonic Stuio Not Working

Orodruin
Level 9

Hello everyone.
There's an interesting audio driver issue I'm having. I want to share it.
I am an ASUS ROG B650E-E Motherboard user. After downloading and installing the motherboard's audio driver from ArmoryCrate or from its own page, I encounter the problem of Sonic Studio not opening after a while.

wf5dvl8dks541.webp

This problem usually occurs after a windows update.
I get this error especially after a major update.


The interesting thing is that I was using an X570 Crosshair motherboard before and I had the same problem.
What exactly causes this problem? Frankly, I'm tired of installing drivers every few months. The audio driver works fine, but Sonic Studio won't open. I would like anyone who has knowledge about this to help, especially since I use the sound features in Sonic Studio.

 

AMD RYZEN 9 7900X3D | ASUS ROG STRIX B650E-E GAMING WIFI | ASUS ROG STRIX LC III 360 ARGB | G.SKILL TridentZ5 NEO RGB 2X24GB 6400Mhz CL32 | ASUS TUF Gaming GeForce RTX™ 4070 Ti SUPER | Asus ROG Strix SCOPE | Asus ROG GLADIUS II CORE | XPG SX8200PRO 2x2TB nVME | XPG SX8100 2x2TB nVME | Corsair RM1000x Shift 80+ Gold | Corsair 5000D Case
197 Views
1 ACCEPTED SOLUTION

Accepted Solutions

Jiaszzz_ROG
Customer Service Agent

Hello, @Orodruin 

We recommend you continue to monitor the situation. 
If you encounter any further difficulties or have any concerns, please feel free to start another discussion thread or PM me anytime.

Thank you.

sharing complete hardware info & software config details will help us better understand the issue 🙂

View solution in original post

6 REPLIES 6

DvLAx3l
Level 10

still don't understand why ASUS not like to update/unify the audio drivers with the latest one with Armoury Crate console comand... SS3 is a total crap and it's counted as cheat for the RIOT VANGUARD anticheat...

- CPU : AMD Ryzen 7 7800X3D (SP97)
- Mobo : ASUS ROG Crosshair X670E Hero // Bios 2007 (AGESA FireRangePi 1.1.7.0 PatchA)
- GPU : AMD Radeon RX 6700XT (XFX SWFT 309) waiting for 7900XTX/RTX 4090 // Monitor : LG 27GR95QE-B OLED 240Hz
- RAM : 32GB (2*16GB) Corsair Dominator CMT32GX5M2X7800C36 Hynix A-Die @ 6400C28 GDM OFF @1.68V
- SSD : 1* Samsung 980 PRO 1Tb NVMe M.2 PCIe 4.0 x4 + 1* Samsung 870 EVO 2TB SATA + 1* Samsung 850 PRO 512GB SATA
- CPU cooler : Corsair H150i elite LCD (360mm)
- PSU : Corsair HX850i (OCP multi rail)

Jiaszzz_ROG
Customer Service Agent

Hello, @Orodruin 

Based on your description, does SS3 show the error message you provided and fail to run correctly every so often, especially after a Windows OS update?
How often does this issue occur, and which Windows versions are involved in the update?
When the problem occurs, can it be resolved by rebooting, or does it require uninstalling and reinstalling the software?
Please try the following steps to see if they resolve the issue:
1. Disable driver signature enforcement:
Go to Start → Settings → Update & Security → Recovery → Advanced startup → Restart now → Troubleshoot → Advanced options → Startup Settings → Restart → Press F7 to Disable driver signature enforcement
2. Uninstall Sonic Studio 3
3. Reinstall the audio driver and reboot
After completing these steps, check if the issue persists.

Thank you.

sharing complete hardware info & software config details will help us better understand the issue 🙂

Hello;

I encounter this problem every month after the monthly Windows 11 updates released by Microsoft. It can occur with almost every Windows update.

For example, I encountered this problem after the March 2024 update.
I'm also experiencing this problem after the Spring and Autumn major updates released each year.

I uninstalled the driver as you said.
I restarted Windows with "disable driver signature verification".
I uninstalled the old driver.

I reinstalled the latest and updated driver which I shared below.
- Realtek USB Audio Drivers (UAD - ASUS ROG SS3-DTS Legacy):
Drivers: 6.3.9600.2355 WHQL [09/03/2023]
SS3-SSVM Extension Driver: 1.3.18.0 WHQL [13/07/2022]
SS3-SSVM VAD Media Driver: 1.0.3.0 WHQL [07/06/2022]
SS3 APO AudioProcessingObject Driver : 3.7.0.0 WHQL [20/02/2024]
DTS APO4x Extension Driver: 1.14.0.0 WHQL [17/12/2023]

There doesn't seem to be a problem for now.
However, I do not know if I will experience driver problems again after the new monthly routine Windows update.
If I encounter the same problem, I will write under this heading again.
That's why I'm not marking the issue as "solved".

This is the process I go through.
I was experiencing the same problem with my X570 Crosshair motherboard that I used before.

AMD RYZEN 9 7900X3D | ASUS ROG STRIX B650E-E GAMING WIFI | ASUS ROG STRIX LC III 360 ARGB | G.SKILL TridentZ5 NEO RGB 2X24GB 6400Mhz CL32 | ASUS TUF Gaming GeForce RTX™ 4070 Ti SUPER | Asus ROG Strix SCOPE | Asus ROG GLADIUS II CORE | XPG SX8200PRO 2x2TB nVME | XPG SX8100 2x2TB nVME | Corsair RM1000x Shift 80+ Gold | Corsair 5000D Case

Jiaszzz_ROG
Customer Service Agent

Hello, @Orodruin 

We recommend you continue to monitor the situation. 
If you encounter any further difficulties or have any concerns, please feel free to start another discussion thread or PM me anytime.

Thank you.

sharing complete hardware info & software config details will help us better understand the issue 🙂

There doesn't seem to be a problem for now. But if there is a problem, I will definitely contact you.

Thank you very much for your help. @Jiaszzz_ROG 

AMD RYZEN 9 7900X3D | ASUS ROG STRIX B650E-E GAMING WIFI | ASUS ROG STRIX LC III 360 ARGB | G.SKILL TridentZ5 NEO RGB 2X24GB 6400Mhz CL32 | ASUS TUF Gaming GeForce RTX™ 4070 Ti SUPER | Asus ROG Strix SCOPE | Asus ROG GLADIUS II CORE | XPG SX8200PRO 2x2TB nVME | XPG SX8100 2x2TB nVME | Corsair RM1000x Shift 80+ Gold | Corsair 5000D Case

Jiaszzz_ROG
Customer Service Agent

Hello, @DvLAx3l 

As mentioned in our response to your discussion thread, we recommend contacting the game provider to whitelist the software if needed.

Thank you.

sharing complete hardware info & software config details will help us better understand the issue 🙂