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
9800x3d
2x32gb royal neo 6000 cl26 expo
BIOsA24, DD3 FW/Data latest from 16-Jan
TX-1600 atx3 (latest)

8 TL-120, at first 2 sets on mobo, 1 set ez hub, then CPU_Fan header that set flickering, I changed it to ez hub, so 2 sets on ez hub, 1 set on PUMP_SYM2, AIO > PUMP_SYM1, the LED flickering went away

under bios, under windows, all test ran, stabled

then, same [***CENSORED***] like you, upon windows restart, post code 07 0d loop, or just 0d

redo everything, cleared cmos, reseat ram, power cycle, everything, then each time cold boot is fine, more importantly shut down and/or force power off, then just a simple power cycle, cold boot is fine every time

I begin to rule out things, for my case, not DD3, not Tryx AIO Kanali software, not Lian Li L-Connect, not AMD Adrenalin, not afterburner, not anything that is plug to Realtek controlled IO usb port (but I did changed all the usb things I use, plugged to x870 chipset controlled usb port from IO)

Then! Bingo! I have a 8.8” ips display, it’s software [***CENSORED***] up something, then I had disabled auto start for: MSI center disabled auto start, L-connect disabled auto start, anything pulling system info I had disabled

then no more restart windows 0d, clean
 
Last edited:
Upvote 0 Downvote
I had this problem too. But then it went away. I never exactly found it where it was coming from. I suspect the PSU as I changed that. Could also have been related to the BIOS (a24) which I had to downgrade to a22 as a24 would not boot with USB devices attached for me.
 
Upvote 0 Downvote
leilapch156102e5 said:
9800x3d
2x32gb royal neo 6000 cl26 expo
BIOsA24, DD3 FW/Data latest from 16-Jan
TX-1600 atx3 (latest)

8 TL-120, at first 2 sets on mobo, 1 set ez hub, then CPU_Fan header that set flickering, I changed it to ez hub, so 2 sets on ez hub, 1 set on PUMP_SYM2, AIO > PUMP_SYM1, the LED flickering went away

under bios, under windows, all test ran, stabled

then, same [***CENSORED***] like you, upon windows restart, post code 07 0d loop, or just 0d

redo everything, cleared cmos, reseat ram, power cycle, everything, then each time cold boot is fine, more importantly shut down and/or force power off, then just a simple power cycle, cold boot is fine every time

I begin to rule out things, for my case, not DD3, not Tryx AIO Kanali software, not Lian Li L-Connect, not AMD Adrenalin, not afterburner, not anything that is plug to Realtek controlled IO usb port (but I did changed all the usb things I use, plugged to x870 chipset controlled usb port from IO)

Then! Bingo! I have a 8.8” ips display, it’s software [***CENSORED***] up something, then I had disabled auto start for: MSI center disabled auto start, L-connect disabled auto start, anything pulling system info I had disabled

then no more restart windows 0d, clean
Click to expand...
Any issues since? I know it's really finicky which USB headers are being used. It'll cause a constant boot cycle with error code b4 (or 64, however that thing is displayed). I have not figured out what causes the restart issue, that has not gone away for me regardless of how I swapped around the USB devices.
 
Upvote 0 Downvote
Captainlooney said:
Any issues since? I know it's really finicky which USB headers are being used. It'll cause a constant boot cycle with error code b4 (or 64, however that thing is displayed). I have not figured out what causes the restart issue, that has not gone away for me regardless of how I swapped around the USB devices.
Click to expand...
for the time being, I use the system as normal, when ever if I need to restart, I just shut down, then cold boot, that’s the only way to avoid 0d upon restarting windows….

Gemini and ChatGPT both are telling me try rolling back BIOs to A20, if persists, then try A22, in order to reset the EC (embedded controller), I am lazy to do it, on bios page, if examining closely,

A22
Description:
- Fix HW Monitor abnormal behavior.

this is probably saying the EC issue I am facing, A24 is stable for me, but minor things here n there doesn’t seems to work flawlessly, out the box was bios A20 (same post 0d upon windows restart, whenever there is app pulling system info data)

A20, A24, both stable in terms of cpu & ram, DD3 has no issue so far (since I updated the FW & data once windows was installed)
 
Upvote 0 Downvote
leilapch156102e5 said:
for the time being, I use the system as normal, when ever if I need to restart, I just shut down, then cold boot, that’s the only way to avoid 0d upon restarting windows….

Gemini and ChatGPT both are telling me try rolling back BIOs to A20, if persists, then try A22, in order to reset the EC (embedded controller), I am lazy to do it, on bios page, if examining closely,

A22
Description:
- Fix HW Monitor abnormal behavior.

this is probably saying the EC issue I am facing, A24 is stable for me, but minor things here n there doesn’t seems to work flawlessly, out the box was bios A20 (same post 0d upon windows restart, whenever there is app pulling system info data)

A20, A24, both stable in terms of cpu & ram, DD3 has no issue so far (since I updated the FW & data once windows was installed)
Click to expand...
Thank you for the reply. Ok, so the "restart" issue is still sporadic for you. I too have to shut down and cold boot to avoid the 0d hang up on restart. It doesn't seem to be a high priority for MSI at the moment or it's only affecting a handful of boards. It took me awhile to figure out it didn't like the NZXT USB Hub that I used to support multiple Lian-Li TL LCD Fan groups, it kept boot cycling a few times before reaching Windows. After managing the USB headers (2 'devices' per header) through splitter cables rather than hubs, the boot cycling issue stopped, but that's a separate issue than the 0d restart issue.
 
Last edited:
Upvote 0 Downvote
Captainlooney said:
Thank you for the reply. Ok, so the "restart" issue is still sporadic for you. I too have to shut down and cold boot to avoid the 0d hang up on restart. It doesn't seem to be a high priority for MSI at the moment or it's only affecting a handful of boards. It took me awhile to figure out it didn't like the NZXT USB Hub that I used to support multiple Lian-Li TL LCD Fan gorups, it kept boot cycling a few times before reaching Windows. After managing the USB headers (2 'devices' per header) through splitter cables rather than hubs, the boot cycling issue stopped, but that's a separate issue than the 0d restart issue.
Click to expand...
unless I misunderstood ChatGPT, the EC chip do play a role in managing those in someway, after the fans on the aio started flickering (plugged to CPU_FAN header), I changed them plugging them to EZ connect hub, so I have the AIO pump to PUMP_SYS1, Rear and AIO fans to EZ Connect hub, Bottom fans to PUMP_SYS2, all of them works fine no more flickering

just wondering which bios are running on? Off topic, is your DD3 working flawlessly from day 1?
 
Upvote 0 Downvote
leilapch156102e5 said:
unless I misunderstood ChatGPT, the EC chip do play a role in managing those in someway, after the fans on the aio started flickering (plugged to CPU_FAN header), I changed them plugging them to EZ connect hub, so I have the AIO pump to PUMP_SYS1, Rear and AIO fans to EZ Connect hub, Bottom fans to PUMP_SYS2, all of them works fine no more flickering

just wondering which bios are running on? Off topic, is your DD3 working flawlessly from day 1?
Click to expand...
My DD3 is working just fine, it's just MSI Center craps out after updating the version (unless clean install) and it refuses to communicate with the DD3, the only fix for that was to uninstall MSI Center and install it clean. My PUMP_SYS1 and PUMP_SYS2 headers are being used by my custom loop's dual D5 Pumps. For "extra" fan headers I have to rely on the on the EZ Connect Hub and another external aRGB/PWM Fan Hub (powered by dual SATA) for additional 6 slots each respectively (too many components need aRGB and PWM headers). I am still using the latest BIOS 1/22/25 7E48v1A24 as in the original post.

For LED flickering, at least on my Wireless TL LED fans, it's a power issue. The PWM header can only provide so much power for a number of fans, after adjusting what it plugs into where or supplementing with an adapter cable that has a SATA PSU + the PWM cable or using a powered Fan Hub all that flickering went away. For the Wireless TL LCD fans, it only requires a PWM + dedicated USB Header (sharing too many on one USB header causes other issues including flickering).
 
Upvote 0 Downvote
Captainlooney said:
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.
Click to expand...
I'm having the same problem as you, any new developments now, the bios and firmware have been updated to the latest, but the problem persists.
 
Upvote 0 Downvote
liangmeng00151502d5 said:
I'm having the same problem as you, any new developments now, the bios and firmware have been updated to the latest, but the problem persists.
Click to expand...
pretty much we are having similar issues upon restarting windows, it stucked, needed hard shutdown, then cold boot is fine

both Gemini and ChatGPT is telling me that EC (embedded controller) has issues, where I tested, any app opened in windows that pulls system info data, any app, single app or multiple app, even if you closed them before restart, windows will stuck

at first when I was in BIOs A20, same happened but I didn’t realized, then I flashed to A24, none of the apps were setup to run on start up, windows restart okay, then after all stress testing done, running those app MSI center, MSI afterburners, etc, same thing happens, and I do catch it every time post code 0d

so I would just shut down, cold boot, no issue

I think I will try out bios A22, as its description is -Fix Monitor abnormal behavior, as for A24 seems like it is only adding supports for stuff
 
Upvote 0 Downvote
leilapch156102e5 said:
pretty much we are having similar issues upon restarting windows, it stucked, needed hard shutdown, then cold boot is fine

both Gemini and ChatGPT is telling me that EC (embedded controller) has issues, where I tested, any app opened in windows that pulls system info data, any app, single app or multiple app, even if you closed them before restart, windows will stuck

at first when I was in BIOs A20, same happened but I didn’t realized, then I flashed to A24, none of the apps were setup to run on start up, windows restart okay, then after all stress testing done, running those app MSI center, MSI afterburners, etc, same thing happens, and I do catch it every time post code 0d

so I would just shut down, cold boot, no issue

I think I will try out bios A22, as its description is -Fix Monitor abnormal behavior, as for A24 seems like it is only adding supports for stuff
Click to expand...
I have a mix of peripheral brands, including Razer, Asus, Lian Li, and MSI center, and if the software for all of these peripherals is turned off, it can cause some of the RGB lights and screens to not be personalized, which has an impact on the experience. The key is not to know exactly which software affects, can only try one by one. Then reboot failure this problem is not every reboot must appear, which further increases the difficulty of troubleshooting.
leilapch156102e5 said:
pretty much we are having similar issues upon restarting windows, it stucked, needed hard shutdown, then cold boot is fine

both Gemini and ChatGPT is telling me that EC (embedded controller) has issues, where I tested, any app opened in windows that pulls system info data, any app, single app or multiple app, even if you closed them before restart, windows will stuck

at first when I was in BIOs A20, same happened but I didn’t realized, then I flashed to A24, none of the apps were setup to run on start up, windows restart okay, then after all stress testing done, running those app MSI center, MSI afterburners, etc, same thing happens, and I do catch it every time post code 0d

so I would just shut down, cold boot, no issue

I think I will try out bios A22, as its description is -Fix Monitor abnormal behavior, as for A24 seems like it is only adding supports for stuff
Click to expand...
 
Upvote 0 Downvote
leilapch156102e5 said:
pretty much we are having similar issues upon restarting windows, it stucked, needed hard shutdown, then cold boot is fine

both Gemini and ChatGPT is telling me that EC (embedded controller) has issues, where I tested, any app opened in windows that pulls system info data, any app, single app or multiple app, even if you closed them before restart, windows will stuck

at first when I was in BIOs A20, same happened but I didn’t realized, then I flashed to A24, none of the apps were setup to run on start up, windows restart okay, then after all stress testing done, running those app MSI center, MSI afterburners, etc, same thing happens, and I do catch it every time post code 0d

so I would just shut down, cold boot, no issue

I think I will try out bios A22, as its description is -Fix Monitor abnormal behavior, as for A24 seems like it is only adding supports for stuff
Click to expand...
And I'm also concerned that a consistent hard shutdown will harm the hardware, so I'm afraid to keep trying it
 
Upvote 0 Downvote
Captainlooney said:
Shutting down from Windows is safer than forcing one via the Power Button.
Click to expand...
Yes, I quite agree. I can short term accept avoiding this issue by shutting down and cold booting for the time being, but I don't know if this issue can be solved in the short term, it's really hard to accept that such an expensive motherboard is limiting the user's basic usage needs.
 
Upvote 0 Downvote
leilapch156102e5 said:
I think I will try out bios A22, as its description is -Fix Monitor abnormal behavior, as for A24 seems like it is only adding supports for stuff
Click to expand...
What is fixed in A22 will be carried to A24, so I don't think A22 will be better.
As for the BIOS note, if I remember right A22 fixed the problem that sometimes BIOS Hardware Monitoring will freeze, which is a different issue.

Maybe everyone in this thread can try to list the peripherals apps or monitoring apps that are installed in your system, such as HWiNFO64, iCue, L-Connect..., etc.
 
Upvote 0 Downvote
fatedust said:
What is fixed in A22 will be carried to A24, so I don't think A22 will be better.
As for the BIOS note, if I remember right A22 fixed the problem that sometimes BIOS Hardware Monitoring will freeze, which is a different issue.

Maybe everyone in this thread can try to list the peripherals apps or monitoring apps that are installed in your system, such as HWiNFO64, iCue, L-Connect..., etc.
Click to expand...
L-Connect 3 (Auto Startup)
HWiNFO64 (Auto Startup)
MSI Center (Auto Startup)
GPU Tweak 3 (Not Auto Startup, for Astral 5090 Power Pin monitoring)
MSI Afterburner (Auto Startup for applying GPU OC Profiles)

I will say that I've observed this restart issue while I was quick testing using an AIO before building out the custom loop with a smaller suite of only the first 3 entries, so the GPU tools probably aren't it.
 
Upvote 0 Downvote
fatedust said:
What is fixed in A22 will be carried to A24, so I don't think A22 will be better.
As for the BIOS note, if I remember right A22 fixed the problem that sometimes BIOS Hardware Monitoring will freeze, which is a different issue.

Maybe everyone in this thread can try to list the peripherals apps or monitoring apps that are installed in your system, such as HWiNFO64, iCue, L-Connect..., etc.
Click to expand...
MSI Center (DD3, board, ram & gpu RGB, but it does pull system info)
MSI afterburners (essential for any user)
L-Connect (fans speed, rgb)
Tryx Kanali (just the aio display for picture/video)
Turing 8.8” display app thing (secondary display)

If none of these startup, opening none of these, restart is fine, DD3 at default

opening any of them, restart post code 0d, shut down no issue, cold boot is fine
 
Upvote 0 Downvote
Captainlooney said:
L-Connect 3 (Auto Startup)
Click to expand...
Have you tried to roll back to V2.0.24?
1741077422792.png
 
Upvote 0 Downvote
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”
 
Upvote 1 Downvote
Back
Top