jlfreund Posted May 13 Posted May 13 I'm trying to figure out if an issue I'm seeing on my new MinisForum UM870 computer is a LaunchBox bug or Minisforum HW problem, so that I can make an RMA request to MinisForum if necessary before the time runs out. Ever since starting to setup that new computer with LaunchBox for my arcade cabinet, I noticed a recurring problem when using LaunchBox where the entire monitor would go black. I can reliably (but partially) recover by switching the monitor input to a different computer, then back to the UM870. Somehow re-syncing the monitor brings the picture back, but with some side effects, such as Windows app icons or wallpaper is missing. Never anything in the Windows EventViewer, but one time, after recovering, I saw a Windows app crash for LaunchBox, which I reported on the LaunchBox bug forum, here. I've discussed more about the symptoms on this Reddit thread. Anyway, I was hoping to hear from the LaunchBox guys whether this bug will be accepted, and whether they think it's more likely that the LaunchBox crash is a symptom of some system-specific (ie HW or configuration) issue -- in which case I should go ahead and request an RMA, or whether it's more likely that LaunchBox is triggering some bad behavior with my system, in which case an RMA would probably be a waste of time. Excerpt of stack: App: LaunchBox Version: 13.21 Theme: Default Type: System.NullReferenceException Site: Void CreateWindow(Boolean) Source: PresentationFramework at System.Windows.Controls.Primitives.Popup.CreateWindow(Boolean asyncCall) at System.Windows.Controls.Primitives.Popup.OnIsOpenChanged(DependencyObject d, DependencyPropertyChangedEventArgs e) at System.Windows.FrameworkElement.OnPropertyChanged(DependencyPropertyChangedEventArgs e) at Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.