LEDkeeper2 Errors and DC installs Foreign Version of C++ (Troubleshooting Dragon Center / Mystic Light issues on x570)

mickydimartino

New member
PRIVATE E-2
Joined
Jul 20, 2020
Messages
6
PROBLEM: x570 Carbon Pro Currently dark and not responding to Mystic Light: Motherboard IO Cover, Mystic Light, JRainbow1 and JRainbow2

I think I've nailed down a few issues After clean windows installs and watching logs, events and changes to directories, files & registry, I am hoping it can lead us towards a fix from MSI or someone that knows more about this stuff. I've been trying to avoid RMA and was hoping I could find a solution (ugh). It was working fine one day and next morning it was dark... this was weeks ago. I have tried literally everything posted on both this forum and MSI_Gaming subreddit.

NOTES:
-I'm not sure which version of DC was originally working but it would have been a June download.
-I have done much of the following multiple times: Uninstall DC using diagnostic tool; updated bios, pushed bios back, cleared cmos, install DC 2.5, Install 2.7, Install directly from Microsoft Store.
-Always rebooted between uninstalls and installs.
-Changed file properties of all DC Services to Run as Administrator
-Originally I had Razer Synapse 3 for Keyboard, Wraith Prism Coolermaster Settings Software and EVGA Precision X1 but on new win installs I'm using a plain jane old Dell keyboard and have not re-installed any of the above or any other software for that matter (even though they were all working happily last month).

The MSI SDK does not come bundled with the Dragon Center Installation download. Trying to get older versions of Dragon Center to work (I think) may be irrelevant because it is always downloading the most recent version of the file OneDC_SDK.exe during installation. I really wish MSI would leave us some links to older versions of the Dragon Center Software, including their SDK.
I have been in this rabbit hole for too long and hoping someone can help :) I hope this all makes sense, thanks for any input

ISSUE 1 - Foreign Version of Microsoft Visual C++ 2013x86
Dragon Center installs 2 versions of Microsoft Visual C++. It installs 2015(x86) and 2013(x86). I noticed the 2013x86 version 12.0.30501 is in a foreign language and I've learned this can cause problems (something about unicode?). So I uninstalled all versions of C++ and tried to trick the Dragon Center installation by downloading it directly from Microsoft.
I installed both the latest 2013 and 2015-2019 Redistributable x86 and x64 packages. This did bypass DC from installing the 2015x86 standalone but not the 2013x86.
I then downloaded and installed the specific version 12.0.30501 Microsoft Visual C++ 2013x86 (ENGLISH) directly from Microsoft hoping that was the end-all answer. Nope. During Dragon Center installation, it just adds the foreign version again so I end up with 2 programs of v12.0.30501
So I don't know -- is it supposed to be using a foreign version?

ISSUE 2 - LEDKeeper2.Exe
errors have been consisent and start right after first run of DC and always in a group as follows (Event Viewer)

---------
Error, Application Error, Event ID 1000
Faulting application name: LEDKeeper2.exe, version: 1.0.0.73, time stamp: 0x5f0fe5e4
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x07482ae3
Faulting process id: 0xa9c
Faulting application start time: 0x01d666ce5ec2687c
Faulting application path: C:\Program Files (x86)\MSI\One Dragon Center\Mystic_Light\LEDKeeper2.exe
Faulting module path: unknown
Report Id: 6793abe0-164d-4651-b0f4-0a4c63e0d1c6
Faulting package full name:
Faulting package-relative application ID

-------------
Error .NET Runtime, Event ID 1026
Application: LEDKeeper2.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NullReferenceException
at MSI_LED.CControl.set_Running(Boolean)
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()

-------------------

Information, Windows Error Reporting, Event ID 1001

Fault bucket 1290053290384213533, type 5
Event Name: CLR20r3
Response: Not available
Cab Id: 0

Problem signature:
P1: LEDKeeper2.exe
P2: 1.0.0.73
P3: 5f0fe5e4
P4: LEDKeeper2
P5: 1.0.0.73
P6: 5f0fe5e4
P7: 31c
P8: 9b7
P9: System.NullReferenceException
P10:

Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFF20.tmp.mdmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERFFFC.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WERC.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2F.tmp.txt

These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_LEDKeeper2.exe_21626f5619492f171d7a8958abfb7c7343b94f_cd160637_e2b8df7f-c229-4a9b-a771-84c45168f9d3

Analysis symbol:
Rechecking for solution: 0
Report Id: 49eaa090-5610-4b59-970f-774a6b13a76c
Report Status: 268435456
Hashed bucket: 07bde93aed31d80b41e730a1f2acc61d

----------------------------
 

fatedust

Member
FIRST LIEUTENANT
Joined
Apr 9, 2020
Messages
574
Have you tried the latest version of Dragon Center 2.0.57.0? >>here<< (Utility > Win10 64 > MSI Dragon Center)
During the installation, usually it will ask you to download MSI SDK by calling out your internet browser.
And DC will install Mystic Light 1.0.0.73, maybe this version could solve your problem.
 

mickydimartino

New member
PRIVATE E-2
Joined
Jul 20, 2020
Messages
6
Have you tried the latest version of Dragon Center 2.0.57.0? >>here<< (Utility > Win10 64 > MSI Dragon Center)
During the installation, usually it will ask you to download MSI SDK by calling out your internet browser.
And DC will install Mystic Light 1.0.0.73, maybe this version could solve your problem.
Yes I did try 2.0.57 the day it was released in the Microsoft Store. I then tried the direct download of 57 when MSI added it to their site.
 

mickydimartino

New member
PRIVATE E-2
Joined
Jul 20, 2020
Messages
6
Does anyone have a working version of Mystic Light [within Dragon Center] that is willing to check something out? I'm wondering if the foreign Visual C++ has anything to do with it or not.

Control Panel-> Programs and Features->
Double click on "Microsoft Visual C++ 2013 Redistributable (x86) 12.0.30501". Is the dialog box in English or foreign (Asian)?

You can close the dialog box without making any changes. TIA
 
Joined
Jul 31, 2020
Messages
4
Does anyone have a working version of Mystic Light [within Dragon Center] that is willing to check something out? I'm wondering if the foreign Visual C++ has anything to do with it or not.
Control Panel-> Programs and Features->
Double click on "Microsoft Visual C++ 2013 Redistributable (x86) 12.0.30501". Is the dialog box in English or foreign (Asian)?
You can close the dialog box without making any changes. TIA
My Mystic light doesn't seem to work either, and I can confirm that the dialog box for me (after clicking 'Modify') is also entirely in Chinese, and it was definitely installed when I tried to update Mystic Light to the latest version. My symptoms include excessive processor and power usage that slows my computer down to a crawl, after having it run for a few hours, and requires a reboot to fix. I still have a copy of the Dragon Center install file from late 2019, but I'm not sure where to share it...
 
Joined
Jul 31, 2020
Messages
4
After Uninstalling the latest mystics light, the weird C++ version mentioned previously, and Dragon Center, I reinstalled an older copy of Mystic light that I found listed in an old Manual. Here's version 1.0.0.37 from 2017-03-30 : http://download.msi.com/uti_exe/Mystic_Light.zip and the one I'm testing out now (so far, no crashes or slowdowns, but it's only been an hour), version 3.0.0.50 (2019-02-21): http://download.msi.com/uti_exe/Mystic_Light_3.zip It also helped me restore my OLED panel (the mobo screen with Lucky Dragon gifs) that had gone blank after I uninstalled the buggy versions.
 

fatedust

Member
FIRST LIEUTENANT
Joined
Apr 9, 2020
Messages
574
Double click on "Microsoft Visual C++ 2013 Redistributable (x86) 12.0.30501". Is the dialog box in English or foreign (Asian)?
I just noticed that mine is also in Chinese too. But strangely is that I don't have any issue with the latest DC and Mystic Light so I guess this is not a problem...?
I would suggest use this >>removal tool<< to completely uninstall the UI & SDK of Dragon Center and reinstall it again.
 
Joined
Jul 31, 2020
Messages
4
I just noticed that mine is also in Chinese too. But strangely is that I don't have any issue with the latest DC and Mystic Light so I guess this is not a problem...?
I would suggest use this >>removal tool<< to completely uninstall the UI & SDK of Dragon Center and reinstall it again.
I think the key buggy factor for myself and Micky, is that we both have RGB LEDs on our RAM modules, that aren't that friendly with DC's software. Mine are the "G.Skill Trident Z" models. What are yours?
 

fatedust

Member
FIRST LIEUTENANT
Joined
Apr 9, 2020
Messages
574
Well...I'm not using RGB RAM modules😅
But I can control my motherboard IO cover, motherboard side LEDs, JRainbow1 and my mouse by Mystic Light.
How about updating to a newer version Mystic Light 1.0.0.76? It's working fine on my X570 GAMING PRO CARBON WIFI.
 

plutomate

Active member
MAJOR GENERAL
Joined
Jul 30, 2015
Messages
3,926
Some people report LED not responding problem and once they do Clear CMOS + unplug power cord for like 15mins, the LED comes back alive. i believe by completing remove power from the motherboard, it should clear whatever is glitch on the LED controller (MCU), I see you clear CMOS but did not unplug power cord!!! Perhaps you can try that as well.
 
Joined
Jul 31, 2020
Messages
4
Well...I'm not using RGB RAM modules😅
But I can control my motherboard IO cover, motherboard side LEDs, JRainbow1 and my mouse by Mystic Light.
How about updating to a newer version Mystic Light 1.0.0.76? It's working fine on my X570 GAMING PRO CARBON WIFI.
Where do I find the older version, 1.0.0.76? Did they list in the release notes for .76 that they fixed this issue?
I'm running what I thought was a better, version 3.0.0.50
 

Ripo

New member
Joined
Aug 22, 2019
Messages
1
Hi, I have that exact same problem with my MEG Ace x570, same error codes and same Foreign Version of Microsoft Visual C++ 2013x86 .
I updated mystic light to the new version that came out today and still the error continues, going to get a fresh windows install to hopefully erase any traces of the previous version since this seems more like a software issue from MSI, this is really the last straw and to anyone curious to purchase their products I cant recommend this brand. First the 2080Ti that I bought came and had heating issues, had to return it and with store credit bough a Aorus that is inferior in specs but never had a single issue, now the X570 never really got a good start since DC is the worst piece of software I ever installed, just tired of this if the fresh install doesn't work Im selling a cheap x570 but wouldn't sell to a friend or family member, i don-t doubt the hardware is good in theory, in practice the worst on the market in my opinion. Good luck with the next updates, but i doubt there wont be an issue somewhere else if not in the SDK in the DC App eventually.
 

fatedust

Member
FIRST LIEUTENANT
Joined
Apr 9, 2020
Messages
574
I'm using Dragon Center v2.0.57.0 and it updated Mystic Light to v1.0.0.76. I don't know where to find the release notes...
Some people report LED not responding problem and once they do Clear CMOS + unplug power cord for like 15mins, the LED comes back alive.
Have you tried what @plutomate suggested?
 
Top