Not Starting - KERNELBASE.dll & XML Parse Error

s.k.hocking@gmail.com

📁 Original board: Chameleon › Troubleshooting, tips and tricks

I'm sure this is just my system causing this issue, but I get the following errors with KERNELBASE.dll when trying to start Chameleon.exe. Windows 10, 10.0.1.19044

I've tried re-registering KERNELBASE.dll and done an SFC check that hasn't resolved anything. Tried with Windows defender on/off etc.

Any ideas? I'm not getting any issues as far as I can see from other applications, but doesn't mean much imo.

Regards

Application: Chameleon.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.FormatException
at System.Number.StringToNumber(System.String, System.Globalization.NumberStyles, NumberBuffer ByRef, System.Globalization.NumberFormatInfo, Boolean)
at System.Number.ParseInt32(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)
at System.Int16.Parse(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)
at System.Convert.ToInt16(System.String)
at A.
.(System.String)
at window6.Window6..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 MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(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 DynamicClass.(System.Object)
at A..(System.Object)
at window6.App.Main()`

Faulting application name: Chameleon.exe, version: 1.0.0.0, time stamp: 0x62a0fcdd
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1766, time stamp: 0x270baf18
Exception code: 0xe0434352
Fault offset: 0x0012c3a2
Faulting process ID: 0x185c
Faulting application start time: 0x01d8830c8d0c180a
Faulting application path: C:\Program Files (x86)\SaveTheHuman5\Chameleon\Chameleon.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 42e1f346-65ed-43de-88f9-a57cf1dad477
Faulting package full name:
Faulting package-relative application ID:`

Fault bucket 1188268845167558488, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0
Problem signature:
P1: Chameleon.exe
P2: 1.0.0.0
P3: 62a0fcdd
P4: mscorlib
P5: 4.8.4515.0
P6: 624cf315
P7: 10a8
P8: 5c
P9: System.Windows.Markup.XamlParse
P10:`

Edit:
I uninstalled Chameleon completely including midi driver. Rebooted Windows, re-installed Chameleon, rebooted and it opens one time after the fresh install. As soon as I try and start Chameleon again, it doesn't open and the application logs the above error each time. It seems the KernalBase.dll and XamlParseException error is quite common problem with applications not starting on Windows but haven't found a solution yet : (

PabloMartin

I take a look on this issue deeply today, I have now an idea of what can cause the problem.

s.k.hocking@gmail.com

@savethehuman5 I think this is actually because I have Visual Studio IDE installed and various SDKs. I've had various strange issues with music software like this before and it's nearly always due to the SDKs & Visual Studio screwing something up that's impossible to work out and fix. Rather than waste days of our lives, I've reinstalled Windows without Visual Studio or any SDKs and Chameleon opens and closes just fine now. (Have requested new licence activation due to new windows version I assume). Regards!

PabloMartin

Yes, can create interference withs some apps some times.
Anyway is possible this is a bug, and yur action of clean all fixes, so i continue checking duet I think I found something.
Your license is unlocked again.

PabloMartin

OK I can confirm there is a bug, cant determine why affect some user and why other no, but have some relative clear idea.
Your post result in a very useful guide to reach the proper way to address this.
Working on it now.

PabloMartin

<r>I mark this post as solved, anyway there is a new version can handle issue like this. 
Unfrotunately the clean install delete the chance of debug. 
If same issue back the tool inside of software should show the error instead a crash, with some info useful for me to debug. 
Will see in the future.

<URL url="https://pablomartin.com/forum/">https://pablomartin.com/forum/</URL></r>

s.k.hocking@gmail.com

@savethehuman5 Great work, I will let you know how I get on. For now I don't need Visual Studio, but will have to install it again in a couple of week I think, so will let you know. Thanks!

PabloMartin

Will see!