Problem with mystic light - led firmware abnormal - MAG B365M MORTAR

A

antonio.t.82

New member
Joined
Mar 4, 2021
Messages
7
Hello,
today, out of the blue, my mystic light stopped working, but this is not even the problem, per se
The issue is that windows continuosly tries to recognize the device and fails, evey second of every minute of every hour, for eternity, seems like it's bricked.

this is my complete setup
OS Name Microsoft Windows 11 Home
Version 10.0.26200 Build 26200
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name ROAR
System Manufacturer Micro-Star International Co., Ltd.
System Model MS-7C67
System Type x64-based PC
System SKU Default string
Processor Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz, 2904 Mhz, 6 Core(s), 6 Logical Processor(s)
BIOS Version/Date American Megatrends Inc. 1.30, 05/06/2020
SMBIOS Version 2.8
Embedded Controller Version 255.255
BIOS Mode UEFI
BaseBoard Manufacturer Micro-Star International Co., Ltd.
BaseBoard Product MAG B365M MORTAR(MS-7C67)

I have tried the following
  1. - uninstalled msi center and reinstalled
  2. - clear cmos
  3. - tried third party apps to hoping they would take control of the device and correctly install it but it did not work
  4. - tried scanning for LED drivers on msi center as suggested on a reddit post but it does not show up, i only see the bios update.
I havent tried the bios update, i was hoping not to be forced to do that

does anyone have any idea? is there a LED drivers to be downloaded somewhere, i searched everywhere, also asked gemini and chatgpt but they were not able to help find it.

thanks to anyone who is willing to help.
 
Sort by date Sort by votes
I checked the windows event registry and in the last hour i had over 1000 of these events

1780145260894.png
 
Upvote 0 Downvote
Svet said:
Here I've prepared it to try re-flash it:
7C67_v0002
Click to expand...
Hi,
to begin with, thank you for taking the time to help me

I tried the tool and this is the response in the log file

03/06/2026 16:06:58 //==================== Start Update Tool ====================//
03/06/2026 16:06:58 // CheckModel - MB Manufacturer: Micro-Star International Co., Ltd.
03/06/2026 16:06:58 // CheckModel - MB Model: MAG B365M MORTAR(MS-7C67)
03/06/2026 16:06:58 // CheckModel - Pass.
03/06/2026 16:06:58 // CheckConnect - Device not connected.
03/06/2026 16:06:58 // CheckBinfile - PID_BIN: 7C67
03/06/2026 16:06:58 // CheckBinfile - LED: v02
03/06/2026 16:06:58 // CheckBinfile - MB & Binfile match.
03/06/2026 16:06:58 // CheckBinfile - Pass.
03/06/2026 16:06:58 // CheckVersion - Device is not open.
03/06/2026 16:06:58 // Command - UI
03/06/2026 16:07:00 //==================== End Update Tool ====================//
Click to expand...
It fails to detect the device
In the devices list of windows "mystic light" appears for a split second, and dissappears immediatly, continuosly, therefore within windows it's impossible to flash it.
I shall try from command prompt in safe mode.
Be right back
(i described all this without trying safe mode directly for further reference)
 
Last edited:
Upvote 0 Downvote
Nope, not working from command prompt in safe mode.

i tried writing a script in a bat file to open and kill the tool ever 3s hoping to find that exact moment that windows detects the device but it's not working.
i guess ill'have to live without my rgb lights, unless there is a way to work around this problem

for the record, i managed to screenshot it the second it appears on my devices list.

1780498257809.png
 
Upvote 0 Downvote
antonio.t.82 said:
Hi,
to begin with, thank you for taking the time to help me

I tried the tool and this is the response in the log file


It fails to detect the device
In the devices list of windows "mystic light" appears for a split second, and dissappears immediatly, continuosly, therefore within windows it's impossible to flash it.
I shall try from command prompt in safe mode.
Be right back
(i described all this without trying safe mode directly for further reference)
Click to expand...

Try short the JT1 pin header as described here: (Power off, remove power, clear CMOS, unplug any ARGB / LEDs, short the 2 pins of JT1)
and here:

Then re-try with FW flashing.
 
Upvote 0 Downvote
Svet said:
Try short the JT1 pin header as described here: (Power off, remove power, clear CMOS, unplug any ARGB / LEDs, short the 2 pins of JT1)
and here:

Then re-try with FW flashing.
Click to expand...

I found that thread before opening this one but it referred to a different motherboard so i wasn't sure it applied
I am a few days away for work, will try sunday afternoon and will update

thank you very much for the time you are dedicating to this issue
 
Upvote 0 Downvote
antonio.t.82 said:
I found that thread before opening this one but it referred to a different motherboard so i wasn't sure it applied
Click to expand...

Yes it's applied, just your JT1 is located at different place on your mainboard and of course use the FW from here I sent you for your board.

Here I've marked it along with pins you need to short:
360.jpg


antonio.t.82 said:
I am a few days away for work, will try sunday afternoon and will update

thank you very much for the time you are dedicating to this issue
Click to expand...

Got it :emot-tip-wink:
 
Upvote 0 Downvote
antonio.t.82 said:
Tried, twice, not working

I always get "connect to device fail", i click "ok"
then i get this
Click to expand...
Since it won't update via the tool supplied and you're still getting error v.00
This indicates the board need to be fixed inhouse please arrange for an RMA
 
Upvote 0 Downvote
Back
Top