Dragon Center Mystic Light problems

migirelan152f02d2

New member
Joined
Jan 27, 2021
Messages
2
Hi,
I've been trying to ascertain why I can't see Mystic Light in Dragon Center when I have the application open. I have checked the other potential solutions - run as administrator, scan for updates to see if mystic light can be installed, I have even reset windows once. Checking the event viewer, I can see I have errors when opening Dragon Center:
.NET Runtime
"Application: LEDKeeper2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at MODAPI.Motherboard.SB_SMS_QuickCommandEx(Byte, Byte, Boolean)
at MODAPI.Motherboard.LoadModules()
at MODAPI.Motherboard.Init()
at MODAPI.Motherboard..ctor()
at MODAPI.Motherboard.get_Instance()
at MSI_LED.MicronBallistix..ctor()
at MSI_LED.App.Application_Startup(System.Object, System.Windows.StartupEventArgs)
at System.Windows.Application.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.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 System.Windows.Application.Run()
at MSI_LED.App.Main()"

Followed by application error:
" Faulting application name: LEDKeeper2.exe, version: 1.0.1.10, time stamp: 0x5fffe10a
Faulting module name: SB_SMBUS_SDK.dll, version: 0.0.0.0, time stamp: 0x5e766873
Exception code: 0xc0000005
Fault offset: 0x00009676
Faulting process id: 0x2e88
Faulting application start time: 0x01d6f44d2587f6e6
Faulting application path: C:\Program Files (x86)\MSI\One Dragon Center\Mystic_Light\LEDKeeper2.exe
Faulting module path: C:\Program Files (x86)\MSI\One Dragon Center\Mystic_Light\SB_SMBUS_SDK.dll
Report Id: e7103d36-76b0-4d1c-9407-c53a5863cf61
Faulting package full name:
Faulting package-relative application ID:"


Does anyone know how to handle this type of error?
 

cryofitzba156902dc

New member
Joined
Dec 2, 2020
Messages
14
Hi,
I've been trying to ascertain why I can't see Mystic Light in Dragon Center when I have the application open. I have checked the other potential solutions - run as administrator, scan for updates to see if mystic light can be installed, I have even reset windows once. Checking the event viewer, I can see I have errors when opening Dragon Center:
.NET Runtime
...
Does anyone know how to handle this type of error?
@migirelan152f02d2
I'm seeing the same Event Viewer entries after upgrading Dragon Center from v2.0.98 to v2.0.100.
The Mystic Light menu item also disappeared for me as well.
Looking at the logged info, it seems that Mystic Light portion of Dragon Center is crashing due to Crucial Ballistix memory, which I have.
at MSI_LED.MicronBallistix..ctor()

I have Asus Armoury Crate installed as a workaround in the past. I'm going to try uninstalling that to see if Dragon Center works.
 

migirelan152f02d2

New member
Joined
Jan 27, 2021
Messages
2
@migirelan152f02d2
I'm seeing the same Event Viewer entries after upgrading Dragon Center from v2.0.98 to v2.0.100.
The Mystic Light menu item also disappeared for me as well.
Looking at the logged info, it seems that Mystic Light portion of Dragon Center is crashing due to Crucial Ballistix memory, which I have.
at MSI_LED.MicronBallistix..ctor()

I have Asus Armoury Crate installed as a workaround in the past. I'm going to try uninstalling that to see if Dragon Center works.
Let me know how that goes, I'd be interested to see if it has an impact.
 

cryofitzba156902dc

New member
Joined
Dec 2, 2020
Messages
14
Let me know how that goes, I'd be interested to see if it has an impact.
Uninstalling Asus Armoury Crate didn't help. It looks like the new v2.0.100 introduced the new file which isn't working right. I had to manually run the uninstall program within the directory where Dragon Center and Mystic Light files are to properly clean up the install. I then installed the old v2.0.96 to get things back working. v2.0.98 will probably work as well after a clean uninstall, but I didn't bother trying since neither version was able to control the 4 sticks of Crucial Ballistix memory I have.

I'm now back to using Asus Armoury Crate to avoid the fast rainbow color change.
 

rammston155202db

New member
Joined
Feb 5, 2021
Messages
1
I have an MPG B550 Gaming Carbon Wifi with an Ryzen9 5900X and Crucial Ballistix RAM and have exactly the same problem. May i ask were you get the old Dragon Center Version?
 

929hit

New member
SERGEANT
Joined
Jan 22, 2008
Messages
25
Thanks for the link (I guess)! That got me to a solid color and then when I rebooted it bricked ALL the RGB on this board. That's why they removed it from the new version obviously.
I pulled the CMOS battery for 10 minutes and still no lights at all. I'm about to see if re-flashing the BIOS will help and then I get to tear it all down and take it to Kohl's for the super easy Amazon return.

I didn't try OpenRGB because it specifically says it could do this to an MSI board so they removed support. Turns out there must be nothing wrong with their software, just an unfortunate defective run of motherboards.
 

929hit

New member
SERGEANT
Joined
Jan 22, 2008
Messages
25
Update: BIOS flash set the RGB back to the solid color that I had set in Dragon Center. So it unbricked the RGB but did not reset it to the default of rainbow rave lights. There's no way of resetting the RGB controller and it's obviously easy to brick just by addressing it with MSI's own software. MSI needs to do a course correction with RGB if they care so much about it. This is ugly.

And Dragon Center just *screams* bloated malware. It's truly shocking to see software in 2021 installing that much sketchy junk just for RGB control. It should be the size of cpu-z.
OpenRGB is 21.6MB
Dragon Center is 521MB - That's half of a GIG of spyware that you have to agree to allow before using and also have to grant administrator privileges.
 
Last edited:

cryofitzba156902dc

New member
Joined
Dec 2, 2020
Messages
14
Update: BIOS flash set the RGB back to the solid color that I had set in Dragon Center. So it unbricked the RGB but did not reset it to the default of rainbow rave lights. There's no way of resetting the RGB controller and it's obviously easy to brick just by addressing it with MSI's own software. MSI needs to do a course correction with RGB if they care so much about it. This is ugly.

And Dragon Center just *screams* bloated malware. It's truly shocking to see software in 2021 installing that much sketchy junk just for RGB control. It should be the size of cpu-z.
OpenRGB is 21.6MB
Dragon Center is 521MB - That's half of a GIG of spyware that you have to agree to allow before using and also have to grant administrator privileges.
Most RGB control software are bloatware. Hopefully the next Dragon Center release will fix the problem.

BTW, I think I had to go into the install folder of Dragon Center (in my case):
  • C:\Program Files (x86)\MSI\One Dragon Center\Mystic_Light
and run "unins000.exe" to cleaning uninstall Mystic_Light and the associated libraries as part of uninstalling Dragon Center before installed the older v98 version. I had to try to few things to get Dragon Center working again, but I am back being able to use Mystic Light portion of Dragon Center to control my MB RGB headers.

Still can't control my Crucial Ballistix RAM (4 sticks), so still stuck using Asus Armoury for that :(
 
Top