cancel
Showing results for 
Search instead for 
Did you mean: 

Sonic Studio won't open in WIndows 10 v1607

Terepin
Level 10
It starts in tray bar, but configuration window won't open. I'm gonna try newer version I found on the Internet.

EDIT: Nope, neither them work. Bummer.
EDIT2: This one work: http://dlcdnet.asus.com/pub/ASUS/misc/audio/Realtek_Audio_Win7-81-10_V6017629_Sonic_2216.zip?_ga=1.1...
566 Views
150 REPLIES 150

same here

I have deactivated the auto driver install. So I was able to install the latest driver.

But Sonic Studio still won't open!

Hopefully ASUS figures it out soon, I rather enjoyed the sonic studio settings.

I'm still debating whether to install the 1902 BIOS?

MrAgapiGC
Level 15
I am ****ing sick with these ASUS ****. there is a program that clean these asus virus crap. the audio app WAS the only app that work on my computer. now NONE i have a generic board now. not a 300 USD ROG gamming board.

What a disappointment

I try all. there is no way to install it. HELP ASUS HELPPPPPPP. I am sending a SOS to anyone . my last app from ASUS is not work. I have 300 usd GENERIC BOARD now.

There are any ROG or ASUS people reading these????

UPDATE: 801pm local time. After going to all post and trying all.... There is no way to put the Sonic Studio (new and old) to work.

I want my money back. it is imposible to run a ROG board here. PLEASE HELP!!!!!

These is the error. But the driver is install. at least!!!!!
Faulting application name: SonicStudio.exe, version: 2.2.25.34225, time stamp: 0x57763913
Faulting module name: KERNELBASE.dll, version: 10.0.14393.0, time stamp: 0x57898e34
Exception code: 0xe0434352
Fault offset: 0x000d96c2
Faulting process id: 0x255c
Faulting application start time: 0x01d1f36c216971c1
Faulting application path: C:\Program Files\ASUSTeKcomputer.Inc\SS2\UserInterface\SonicStudio.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 51734f58-1086-4db8-a7d0-a29942cbd433
Faulting package full name:
Faulting package-relative application ID:

- System

- Provider

[ Name] Application Error

- EventID 1000

[ Qualifiers] 0

Level 2

Task 100

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2016-08-11T01:03:11.600723200Z

EventRecordID 2979

Channel Application

Computer MrAgapiGCPC

Security


- EventData

SonicStudio.exe
2.2.25.34225

- System

- Provider

[ Name] .NET Runtime

- EventID 1026

[ Qualifiers] 0

Level 2

Task 0

Keywords 0x80000000000000

- TimeCreated

[ SystemTime] 2016-08-11T01:03:11.562947900Z

EventRecordID 2978

Channel Application

Computer MrAgapiGCPC

Security


- EventData

Application: SonicStudio.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at SonicStudioMB.IPolicyConfig.GetPropertyValue(System.String, Boolean, SonicStudioMB.PropertyKey ByRef, SonicStudioMB.PropVariant ByRef) at SonicStudioMB.PerfectVoiceTab.IsRealtekNoiseSuppressionEnabled() at SonicStudioMB.PerfectVoiceTab..ctor() Exception Info: System.Windows.Markup.XamlParseException at System.Windows.Markup.WpfXamlLoader.Load(System.Xaml.XamlReader, System.Xaml.IXamlObjectWriterFactory, Boolean, System.Object, System.Xaml.XamlObjectWriterSettings, System.Uri) at System.Windows.Markup.WpfXamlLoader.LoadBaml(System.Xaml.XamlReader, Boolean, System.Object, System.Xaml.Permissions.XamlAccessLevel, System.Uri) at System.Windows.Markup.XamlReader.LoadBaml(System.IO.Stream, System.Windows.Markup.ParserContext, System.Object, Boolean) at System.Windows.Application.LoadBamlStreamWithSyncInfo(System.IO.Stream, System.Windows.Markup.ParserContext) at System.Windows.Application.LoadComponent(System.Uri, Boolean) at System.Windows.Application.DoStartup() at System.Windows.Application.<.ctor>b__1_0(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at System.Windows.Application.Run(System.Windows.Window) at SonicStudioMB.App.Main()

57763913
KERNELBASE.dll
10.0.14393.0
57898e34
e0434352
000d96c2
255c
01d1f36c216971c1
C:\Program Files\ASUSTeKcomputer.Inc\SS2\UserInterface\SonicStudio.exe
C:\WINDOWS\System32\KERNELBASE.dll
51734f58-1086-4db8-a7d0-a29942cbd433
Learn, Play Enjoy! We help and collaborate, NOT complain!

Bahz
Level 13
@Itzycharles
Which board do you have and please provide your full system specifications then I can pass this information over to our software team to look into.

EDIT:
The issue had already been previously reported and our service team has already highlighted this issue to our software team so they're looking into this

Bahz
Level 13
Can everyone also list out the Realtek driver versions you have tried? Current version of Sonic Studio is bundled with V6.0.1.7829

I really don't get the issue peeps are having with this?

I fresh installed 1607 today, and the system installed, what it thought were, latest drivers.

Headed to device manager to update manually to the 7874 set (I prefer sound quality of this set), pointed to update folder, and drivers updated OK.

I then installed SSII from the folder in driver set downloaded from ASUS support, Everything works just fine. SSII opens and works running manually, and also does so from within Sound Manager.

Win10 x64 - HERO Alpha board.

scaramonga wrote:
I really don't get the issue peeps are having with this?

I fresh installed 1607 today, and the system installed, what it thought were, latest drivers.

Headed to device manager to update manually to the 7874 set (I prefer sound quality of this set), pointed to update folder, and drivers updated OK.

I then installed SSII from the folder in driver set downloaded from ASUS support, Everything works just fine. SSII opens and works running manually, and also does so from within Sound Manager.

Win10 x64 - HERO Alpha board.


Didn't Try your method yet, but I will do so and report back.

But currently, the SS2 used to work flawlesly before the RedStone Windows update. After the Update the App just stopped launching.
So, I know for sure that RedStone1 Windows Update has changed how driver installation works in windows and the need of driver signing.

I have tried the Realtek Driver Version: V6.0.1.7829
Also I have tried the Realtek Driver Version: 6.0.1.7848
Non works regarding the SS2.

the App Sonic Radar Works normally for your Info.

ondersma80
Level 8
If you do a fresh install of 1607 the latest download on asus.com works for the Maximus VIII Hero Alpha, just did this myself.

As for the anniversary update, you will find several drivers might revert to their defaults also. For example, the cause of my reinstall was Rapid Storage Technology. Before the update, I had 14.8 installed. I noticed after the update SATA drives were running off the "standard SATA AHCI controller" provided by Windows. Intel RST was still installed but the console would not open. I even uninstalled it, reinstalled and it would not open. Did the fresh install and it installs and opens fine.

If you read my comments from the past, you will find I am generally pretty loyal to MS. Unfortunately, Microsoft seems to be making some bad misteps with this Win 10 updating regime. These threshold and anniversary updates are just in place upgrades... you download a 3.5 GB file and it upgrades like a new OS. That never worked well and probably never will. The problem is most users would never notice the system was using driver x vs driver y after the update. For those that notice and care, fresh installs every six months to a year fellas.

In saying that. There does seem to be a problem with any driver set on 1607 ATM. This is latest 7899 (which I just installed to see if it would fix these errors), and while all works well, the event viewer, task manager, and reliability tool, are all filled with errors relating to the Realtek file - ATKEX_cmd.







Anyone check to see if they have the same please?

scaramonga wrote:
In saying that. There does seem to be a problem with any driver set on 1607 ATM. This is latest 7899 (which I just installed to see if it would fix these errors), and while all works well, the event viewer, task manager, and reliability tool, are all filled with errors relating to the Realtek file - ATKEX_cmd.

Anyone check to see if they have the same please?


Damn man whats all that creepy stuff? haha no you shouldnt have stuff like this