MEG X870E Godlike Cannot Restart via Windows or Case Button But Shutsdown Fine

Captainlooney

Captainlooney

Member
Joined
Jan 4, 2025
Messages
31
I can shut down the system fine through Windows "Shutdown" and can turn on the PC again via the case power button just fine. The issue is when I use either the Restart button on the case or select Restart from Windows. The monitor will go blank/black but all the light are still on, fans are all still spinning, RAM RGB still on, the Dynamic Dashboard retains whatever image it had as normal and it hangs until the Dynamic Dashboard then shows "CPU & DDR Error." Outside of this, the Dynamic Display works as intended with no load issues or blank/black on startup or booting into Windows or through MSI Center. At this point I have to hard shutdown via the case power button and it will boot just fine again.

I'm ruling out the memory because extensive memory stress testing using Karhu, Memtest86, Memtest86+, OCCT all pass several hours. I've tried different configurations as well and they all exhibit the same behavior. 2x24GB, 4x24GB, 2x48GB they all pass all listed memory stress tests fine even with XMP/EXPO and manual timings. I also tried an old 2x32GB G.Skill 6400 kit but it won't memory train. For CPU, it's a 9800X3D, everything works fine whether it's gaming or running Cinebench for 30 minutes, under 72C with 26C average coolant temperature. Zero system instability observed at all even with hours of gaming. It is purely a restart issue. It does not matter, PBO enabled or default, also XMP/EXPO or default JEDEC speeds.

System is currently built in a custom water loop though the same behavior was observed when I ran with an AIO for general testing of the components it would reboot successfully less than half the time (both custom and AIO).

Current System Config:
CPU: AMD Ryzen 7 9800X3D
Motherboard: MEG X870E Godlike
RAM: 4x24GB G.Skill Trident Z5 Royal 8000 (clocked at 6400), also tried 2x48GB G.Skill Trident Z5 Royal 6400 same behavior
GPU: Asus ROG Strix 3080 Ti (for testing while waiting for a 5090 to water block)
M2_1 (boot, Windows 11): Crucial T705 4TB
M2_3 (storage): Western Digital SN850X 8TB
M2_5 (storage): Western Digital SN850X 8TB
Case: Lian-Li V3000 Plus
PSU: Seasonic PRIME TX-1600 Noctua Edition
Dynamic Display Firmware: Up to date with the latest Firmware Utility from 1/16/25
BIOS: Up to date with the latest 1/22/25 7E48v1A24

M2 slots were chosen based on slots that don't share or sap the PCI-e lanes of other components. I am using the EZ Fan Hub via the EZ Bridge cable but am also using an NZXT USB Hub in addition to another powered fan hub to support a full slew of Lian-Li LCD/LED TL Wireless fans. Dual D5 Pumps (Singularity Computers Distros) are connected to the motherboard Pump PWM headers directly.

I am not facing any weird Dynamic Display issue that folks on another thread are battling. I did set a MP4 video for the Dynamic Display so maybe I just escaped the woes that way.
 
Sort by date Sort by votes
FYI:
Lian Li is aware of this issue and they are working on a solution.
Wait patiently and Lian Li will release a new version of L-Connect 3 on their website to fix this issue.
Estimated new version of L-connect 3 will be released on 17th March.

As workaround:
Disable Auto Startup on L-Connect 3 and other system monitoring apps.
 
Upvote 0 Downvote
Svet said:
FYI:
Lian Li is aware of this issue and they are working on a solution.
Wait patiently and Lian Li will release a new version of L-Connect 3 on their website to fix this issue.
Estimated new version of L-connect 3 will be released on 17th March.

As workaround:
Disable Auto Startup on L-Connect 3 and other system monitoring apps.
Click to expand...
ASUS has “ monitoring software reboot workaround “

But MSI doesn’t seems to have this feature, it’s better for MSI over come this issue, and surpass ASUS, if MSI aiming to be the next No.1
 
Upvote 0 Downvote
Svet said:
FYI:
Lian Li is aware of this issue and they are working on a solution.
Wait patiently and Lian Li will release a new version of L-Connect 3 on their website to fix this issue.
Estimated new version of L-connect 3 will be released on 17th March.

As workaround:
Disable Auto Startup on L-Connect 3 and other system monitoring apps.
Click to expand...
How did you find this out?
 
Upvote 0 Downvote
Svet said:
FYI:
Lian Li is aware of this issue and they are working on a solution.
Wait patiently and Lian Li will release a new version of L-Connect 3 on their website to fix this issue.
Estimated new version of L-connect 3 will be released on 17th March.

As workaround:
Disable Auto Startup on L-Connect 3 and other system monitoring apps.
Click to expand...
where is the new version? you lied or lian li lied?
 
Upvote 0 Downvote
leilapch156102e5 said:
Final Diagnosis: Embedded Controller (EC) Lockup on Restart

Your testing has confirmed a persistent EC (Embedded Controller) issue in BIOS A24.

🔹 What We Know for Sure:

1. If you don’t open any system monitoring or RGB apps → Restart works fine. ✅

2. If you open any system monitoring or RGB app, even once → Restart fails (Post Code 0D). ❌

3. Even if you close the app before restarting → Restart still fails. ❌

4. Cold boot (shutdown + power cycle) always works fine. ✅

🔹 Why This Happens

1. These apps communicate with the EC (Embedded Controller) to pull system data (voltages, temps, fan speeds, RGB).

2. Once the EC is “polled” or written to, something in its memory/firmware does not reset properly when restarting.

3. Even closing the app doesn’t fix it, because the EC is already in a bad state until the system fully powers off.

4. Cold boot (shutdown + power cycle) clears the EC, making the system work again.


🔹 What Can You Do? (Workarounds)


1. Avoid opening system monitoring or RGB apps unless necessary.

2. If you open any of these apps, always do a full Shutdown instead of Restart.

3. Test disabling EC polling in HWiNFO (Settings → Uncheck “EC Support”).

4. Try OpenRGB instead of G.SKILL’s RGB software (which may not trigger the bug).

5. Wait for MSI to release a new BIOS update to fix EC handling on restarts.

🔹 What You CANNOT Fix Right Now


• Since this is a BIOS/EC firmware issue, no Windows setting or app tweak will fully solve it.

• The issue will persist until MSI releases a BIOS update with a fix.

Final Conclusion:

✅ It’s not your fault. It’s MSI’s BIOS (A24) issue with EC handling.

❌ No point in troubleshooting further. The only fix is a BIOS update.

For now, just use Shutdown instead of Restart when any system monitoring or RGB app has been opened.
—————————
My responds to ChatGPT, “Fxxk MSI”
Click to expand...
Thank you for this. It explains why Corsair iCUE triggers this.
 
Upvote 0 Downvote
leilapch156102e5 said:
where is the new version? you lied or lian li lied?
Click to expand...

That's the info I got it's estimated date,
I guess should be out soon.

From their website I see this:
We saw some users reporting V2.0.25 having compatibility issues with Windows User Account Control or when using hardware monitoring software on AM5 platform.
Click to expand...
We are looking for the cause of issue, but meanwhile for those that encountered the issue, please roll back to V2.0.24.
Click to expand...

Captainlooney said:
How did you find this out?
Click to expand...

The info is from my MSI's contacts who are in contact with Lian Li about this issue.
 
Upvote 0 Downvote
Svet said:
That's the info I got it's estimated date,
I guess should be out soon.

From their website I see this:





The info is from my MSI's contacts who are in contact with Lian Li about this issue.
Click to expand...
i see, not yet, lian li haven't roll out any updates yet, even without L-Connect 3 on startup, any other hardware info software opened, my system would not warm boot, it would just stuck on restart. Cold boot has no issue, god damn MSI !!!!!!!!!!!!!!!
 
Upvote 0 Downvote
I had the same problem and for me it was caused by MSI Center being installed. Removing it allowed me to restart normally again. I don't even know what L-Connect is.
 
Upvote 0 Downvote
dpgagno15a902ed said:
MSI Afterburner/RTSS for monitoring. Bios A27.
Click to expand...
thanks bro

I am on A24, I had MSI center, MSI afterburner, Tryx AIO’s Kanali, Lian Li’s fans controller L-Connect 3

Kanali and L-connect needed, controlling the lcd on the AIO, and controlling the fans speed & RGB

I will try using the MSI center uninstall tool, and if that will fix my [***CENSORED***]
 
Upvote 0 Downvote
Same here — cold boot always works fine.
But if I run OCCT and then restart Windows after the test, I consistently get C5–AB.

What worked for me was uninstalling NZXT CAM.
But it still really bothers me — why is everyone else getting 0D, and I’m the one stuck with C5?
 
Upvote 0 Downvote
L-Connect 3 v2.0.26 is out and it mentions the "0d" issue in the update note.
lian-li.com

L-Connect3 - RGB and fan control in one go

Create Endless Possibility of RGB:Fully customize each part of ARGB for a highly personal gaming rig. User Friendly Interface.Monitor at one stop. System Info,Fan/Pump RPM,Quick/Sync Lighting,SL Fan Lighting,AL Fan Lighting,Setting.
lian-li.com lian-li.com
1743580716953.png
 
Upvote 0 Downvote
Upvote 0 Downvote
leilapch156102e5 said:
Final Diagnosis: Embedded Controller (EC) Lockup on Restart

Your testing has confirmed a persistent EC (Embedded Controller) issue in BIOS A24.

🔹 What We Know for Sure:

1. If you don’t open any system monitoring or RGB apps → Restart works fine. ✅

2. If you open any system monitoring or RGB app, even once → Restart fails (Post Code 0D). ❌

3. Even if you close the app before restarting → Restart still fails. ❌

4. Cold boot (shutdown + power cycle) always works fine. ✅

🔹 Why This Happens

1. These apps communicate with the EC (Embedded Controller) to pull system data (voltages, temps, fan speeds, RGB).

2. Once the EC is “polled” or written to, something in its memory/firmware does not reset properly when restarting.

3. Even closing the app doesn’t fix it, because the EC is already in a bad state until the system fully powers off.

4. Cold boot (shutdown + power cycle) clears the EC, making the system work again.


🔹 What Can You Do? (Workarounds)


1. Avoid opening system monitoring or RGB apps unless necessary.

2. If you open any of these apps, always do a full Shutdown instead of Restart.

3. Test disabling EC polling in HWiNFO (Settings → Uncheck “EC Support”).

4. Try OpenRGB instead of G.SKILL’s RGB software (which may not trigger the bug).

5. Wait for MSI to release a new BIOS update to fix EC handling on restarts.

🔹 What You CANNOT Fix Right Now


• Since this is a BIOS/EC firmware issue, no Windows setting or app tweak will fully solve it.

• The issue will persist until MSI releases a BIOS update with a fix.

Final Conclusion:

✅ It’s not your fault. It’s MSI’s BIOS (A24) issue with EC handling.

❌ No point in troubleshooting further. The only fix is a BIOS update.

For now, just use Shutdown instead of Restart when any system monitoring or RGB app has been opened.
—————————
My responds to ChatGPT, “Fxxk MSI”
Click to expand...
Thank you! Been looking for this. I have been having this issue for a couple of weeks now on my X670E Carbon Wifi after i updated my bios to the Jan 2025 version.
I am running Corsair ICUE on autostart which explains why it triggers. MSI Center and HWINFO64 are installed but do not autostart with Windows.
Can confirm that when i disabled Corsair ICUE on startup, it restarts normally.
 
Upvote 1 Downvote
dlommerde9129f02ab said:
Thank you! Been looking for this. I have been having this issue for a couple of weeks now on my X670E Carbon Wifi after i updated my bios to the Jan 2025 version.
I am running Corsair ICUE on autostart which explains why it triggers. MSI Center and HWINFO64 are installed but do not autostart with Windows.
Can confirm that when i disabled Corsair ICUE on startup, it restarts normally.
Click to expand...
Found this topic after suffering the same things. So we just don't use ICUE until msi makes a bios update for us? I use a X670E Carbon Wifi on 7D70v1M also.
 
Upvote 0 Downvote
I think a lot of people are suffering from this same issue. While it's great that Lian-Li made a fix, I doubt every hardware monitor software developer is going to make such a specific targetted fix for MSI 870-based boards. This appears to have impacted people with Godlike, MAG Tomahawk, and Carbon WiFi boards at minimum. Maybe others as well. Here's my story (similar to OP): https://forum-en.msi.com/index.php?...ng-my-mag-x870e-tomahawk.411377/#post-2328797

I hope MSI produces a BIOS fix for all these boards. That's going to be the only reliable thing.
 
Upvote 0 Downvote
justin.j.wood155002df said:
I think a lot of people are suffering from this same issue. While it's great that Lian-Li made a fix, I doubt every hardware monitor software developer is going to make such a specific targetted fix for MSI 870-based boards. This appears to have impacted people with Godlike, MAG Tomahawk, and Carbon WiFi boards at minimum. Maybe others as well. Here's my story (similar to OP): https://forum-en.msi.com/index.php?...ng-my-mag-x870e-tomahawk.411377/#post-2328797

I hope MSI produces a BIOS fix for all these boards. That's going to be the only reliable thing.
Click to expand...
I know asus boards have a update and a work around made right into the bios that fixed everything. Think it was called memory context restore (for asus only). We can hope msi does something similar.
 
Upvote 0 Downvote
Back
Top