Unexpected Error Message - Musicbee always crash at first start

[Joey2001]

Musicbee 3.3.7056

Since a few weeks I always have the problem, that musicbee crash after the first start, when I hit the play-button or use the key-shortcut to play.
Musicbee was in my autostart. I use windows 10 v1709.
At the same time when musicbee crash, there is a net.runtime error in the log. When I start mb after the crash, everything works as it should.
Thanks for any help.

Musicbee

Code

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <Level>2</Level> 
  <Task>100</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2019-05-25T08:51:20.570576300Z" /> 
  <EventRecordID>79428</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>joe-PC</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>MusicBee.exe</Data> 
  <Data>3.3.7056.26616</Data> 
  <Data>5cc45dbb</Data> 
  <Data>unknown</Data> 
  <Data>0.0.0.0</Data> 
  <Data>00000000</Data> 
  <Data>c0000005</Data> 
  <Data>00000000</Data> 
  <Data>2a70</Data> 
  <Data>01d512d4bdc53267</Data> 
  <Data>C:\Program Files (x86)\MusicBee\MusicBee.exe</Data> 
  <Data>unknown</Data> 
  <Data>78eb63c0-6ece-4c00-bd0d-3a82fa5d2d9c</Data> 
  <Data /> 
  <Data /> 
  </EventData>
  </Event>

Net.runtime

Code

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name=".NET Runtime" /> 
  <EventID Qualifiers="0">1026</EventID> 
  <Level>2</Level> 
  <Task>0</Task> 
  <Keywords>0x80000000000000</Keywords> 
  <TimeCreated SystemTime="2019-05-25T08:51:20.385895600Z" /> 
  <EventRecordID>79427</EventRecordID> 
  <Channel>Application</Channel> 
  <Computer>joe-PC</Computer> 
  <Security /> 
  </System>
- <EventData>
  <Data>Anwendung: MusicBee.exe Frameworkversion: v4.0.30319 Beschreibung: Der Prozess wurde aufgrund einer unbehandelten Ausnahme beendet. Ausnahmeinformationen: System.AccessViolationException bei #=zUhwOZCy35FfXX0jJqObDj1o=+#=zZjIJFZ0QVp2L.#=z9B17IshkgdZJyF0xJA==(Int32, Int32, Int32, #=z_wMYZUhwL27x) bei #=zUhwOZCy35FfXX0jJqObDj1o=+#=zZjIJFZ0QVp2L.#=zk0KtbSlwSnNLlm4Clw==() bei #=zWLLc5KJpK1tV_B_7LQ4yj6dR8ZT0+#=zfvzZDcSa$8Jfu5E7VLtoonk=+#=zNt0XkKoHIHiXoMvynti6f8A=.#=z$9VaTI8PFyC_(System.Object, System.EventArgs) bei System.Windows.Forms.Timer.OnTick(System.EventArgs) bei System.Windows.Forms.Timer+TimerNativeWindow.WndProc(System.Windows.Forms.Message ByRef) bei System.Windows.Forms.NativeWindow.Callback(IntPtr, Int32, IntPtr, IntPtr) bei System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG ByRef) bei System.Windows.Forms.Application+ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr, Int32, Int32) bei System.Windows.Forms.Application+ThreadContext.RunMessageLoopInner(Int32, System.Windows.Forms.ApplicationContext) bei System.Windows.Forms.Application+ThreadContext.RunMessageLoop(Int32, System.Windows.Forms.ApplicationContext) bei #=zgeY_Na03jtcNMBza84h0RpVbwUy0.Main(System.String[])</Data> 
  </EventData>
  </Event>

[Steven]

which visualiser are you using eg. milkdrop?
you are probably going to have to remove the visualiser from your layout

[Joey2001]

Indeed, I use the visualizer in my layout. But that work for a long time.
Was there a change in the last mb-versions? Or in windows?

But I delete it from the layout. I will see, what happened.

Thanks for your quick reply. 

[Steven]

can you send me a link to your settings file with the visualiser still in the main panel (help/ support/ view settings)