L-Connect causing failed restarts in windows 11

[Rockett]

Edit: MSI support claim its just L-connect 3 causing the issue, will do some more testing later and amend this post if removing it solves the issue.

 

After testing, I can confirm L-connect 3 is causing windows to fail to restart across all motherboards. MSI has reported the issue to Lian li, a fix is in the works soon.

 

If your PC is getting stuck trying to restart (not from cold boot) and you have L-connect 3 installed, make sure to close the programs service and exit the application before restarting your PC for the time being until there is a new version.

 

 

 

Old post outdated and wrong:

Spoiler

I'm sharing this to raise awareness in hopes that more motherboard manufacturers will address this issue. As of now, ASUS is the only one with a known workaround called "Monitoring Software reboot workaround" in their bios.

 

If you own an X670(E) or X870(E) chipset motherboard with a postcode display (uncertain if it affects models without one) and run Windows 11, there's a problem when restarting your PC while hardware monitoring software is running. This issue is represented by the DRAM LED staying illuminated and the debug code "0d" appearing on your postcode display.

 

Having multiple hardware monitoring programs can trigger this, though some seem more likely than others. To replicate it easily, try running multiple monitoring programs simultaneously with them open on your desktop and then restart your PC. In my case, I have only L-Connect and Turzx running and typically experience the issue when restarting after a Windows update or booting into Safe Mode (which is quite mild) Just adding OCCT open in the desktop to the mix and restarting my PC I get this issue every restart.

 

So far, I have confirmed that the following programs can trigger the restart failure but believe it is probably all of them:

    -L-Connect

    -ASUS Armoury Crate

    -HWinfo

    -AIDA64

    -OCCT

    -CPU-Z

    -Turzx

 

I am not sure if it's just having a combination of hardware monitoring programs running at the same time causing the problem.

 

If your system gets stuck, fully powering it off and turning it back on will bypass the issue.

 

I can only speculate but I guess it's related to hardware monitoring software leaving something behind in memory during PC restarts causing the problem, as others have claimed turning off fast boot (so the RAM goes through training every boot) also is a solution.

 

If you can replicate this problem, please report it to your motherboard manufacturer. Other manufacturers seem unaware of this issue, despite it persisting for at least five months. The more reports they receive, the more likely they are to address it.

 

List of reports:

https://rog-forum.asus.com/t5/gaming-motherboards/asus-rog-x670e-hero-shows-code-quot-0d-quot-after-system-restart/td-p/1030169/page/15

 

https://forum-en.msi.com/index.php?threads/msi-mag-x870-tomahawk-wifi-random-error-code-0d-when-starting-restarting.408687/page-3#posts

 

https://www.reddit.com/r/gigabyte/comments/1g9tdtx/motherboard_debug_led_indicates_0d_error_on/?utm_source=embedv2&utm_medium=post_embed&embed_host_url=https://linustechtips.com/index.php

 

TLDR:

If you experience DRAM LED on and 0d postcode display on PC restarts, try uninstalling all your extra hardware monitoring software.

If you have an ASUS motherboard and experience this turn on "Monitoring Software reboot workaround"

 

[Mumintroll]

24 minutes ago, Rockett said:

I can only speculate but I guess it's related to hardware monitoring software leaving something behind in memory during PC restarts causing the problem, as others have claimed turning off fast boot (so the RAM goes through training every boot) also is a solution.

 

 

I don't think turning off fast boot will force it to memory train everytime, because there is a separate bios setting for it.

It's called different depending on manufacturer. Memory Context Restore, or Memory Reference Code (MRC fast boot) something along those lines.

 

That setting can be found in different places depending on the manufacturer, sometimes in the same place as Fast boot is, sometimes in the memory settings.

But there's a search option one can use for that.