[SOLVED] Application crash. Kernelbase.dll & .net related.

M

Milanista

Well-known member
Joined
Dec 19, 2017
Posts
71
Hi Team;

App-v application keep crashing with these 2 events. Kindly assist.

Faulting application name: AppVStreamingUX.exe, version: 5.1.86.0, time stamp: 0x55b04319
Faulting module name: KERNELBASE.dll, version: 6.3.9600.18895, time stamp: 0x5a4b1cf7
Exception code: 0xe0434352
Fault offset: 0x00000000000092fc
Faulting process id: 0x1678
Faulting application start time: 0x01d3b65d2360e5e8
Faulting application path: C:\Program Files\Microsoft Application Virtualization\Client\AppVStreamingUX.exe
Faulting module path: C:\windows\system32\KERNELBASE.dll
Report Id: 6292115e-2250-11e8-8112-005056b802e6
Faulting package full name:
Faulting package-relative application ID:


**********************************************************

Application: AppVStreamingUX.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.COMException
at System.Windows.Media.Composition.DUCE+Channel.SyncFlush()
at System.Windows.Media.MediaContext.CompleteRender()
at System.Windows.Media.MediaContext.CreateChannels()
at System.Windows.Media.MediaSystem.ConnectChannels(System.Windows.Media.MediaContext)
at System.Windows.Media.MediaContext..ctor(System.Windows.Threading.Dispatcher)
at System.Windows.Media.MediaContext.From(System.Windows.Threading.Dispatcher)
at System.Windows.Media.Visual.VerifyAPIReadWrite()
at System.Windows.Media.VisualCollection.Add(System.Windows.Media.Visual)
at System.Windows.Controls.UIElementCollection.AddInternal(System.Windows.UIElement)
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.Add(System.Object, System.Xaml.XamlType, System.Object, System.Xaml.XamlType)

Exception Info: System.Windows.Markup.XamlParseException
at System.Windows.Markup.XamlReader.RewrapException(System.Exception, System.Xaml.IXamlLineInfo, System.Uri)
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 Microsoft.AppV.Client.StreamingUX.App.OnStartup(System.Windows.StartupEventArgs)
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.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.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at Microsoft.AppV.Client.StreamingUX.App.Main()
 
I've never used App-V before, so I probably won't be able to provide much help unfortunately. However, the error indicates that there may be an error in one of the .XML files which it is trying to process.

Do you know which .XML files it reads? Any configuration files which you use?
 
I assume that you attached Process Monitor to the App-V process?

There appears to be two buffer overflows in the QueryInformationFile function and the QueryAllInformationFile function, however, I don't believe that they're causing the application to crash due to the different successful requests afterwards. The application probably acquired the information it needed to, and happily processed the other requests.

Have you installed the latest version of App-V? The application only appears to be throwing generic exceptions unfortunately. You'll probably need to break into the application using Windows Debugger and checking what is happening during start-up.

Do have you have the latest version of .NET installed?
 
Last edited:
Yes i open procmon and launch the AppVStreamingUX.exe. Earlier before the apps crash i did dism and sfc /scannow and rebooted the server. Can doing both causing this?

I have the latest app-v client and .net 4.6.1. Not the latest but it works previously.
 
No, but did they provide you with any errors which were fixed?

Have you tried updating to the latest .NET framework and seeing if they would make a difference?
 
Thanks, that sub-forum does get rather busy so it may take a few days for people to respond, however, please feel free to PM one of the members of the Windows Update team if you haven't received a response.
 

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top