F5F Stay Refreshed Hardware Desktop L-Connect leading to restart issues on Windows 11

L-Connect leading to restart issues on Windows 11

L-Connect leading to restart issues on Windows 11

E
edibo
Member
Find
220
07-07-2025, 11:54 AM
#1
MSI attributes the problem to L-connect 3 and plans further testing. I’ll update this once the removal resolves the issue. Currently, L-connect 3 seems to prevent Windows from restarting properly on every board. MSI has already notified Lian li, who is developing a fix soon. If your PC freezes during a restart (not due to cold boot) and you have L-connect 3 installed, close any running programs and exit applications before powering on again until the new version is available. This post was incorrect and outdated; my goal is to highlight the matter so more makers can address it. As of now, only ASUS mentions a known solution called "Monitoring Software reboot workaround" in their BIOS. For X670(E) or X870(E) boards with a postcode display (uncertain if it works without one), running Windows 11 and having multiple monitoring tools active can cause the issue. The DRAM LED stays on and the debug code "0d" appears on your postcode screen. Running several monitoring programs together—especially Turtzx, OCCT, CPU-Z, AIDA64, L-connect, ASUS Armoury Crate—can trigger this. It might be due to memory leftovers from hardware monitoring software during restarts. To make it easier to reproduce, launch several monitors simultaneously with them open and restart your PC. In my experience, the problem appears after a Windows update or when booting into Safe Mode. Adding OCCT alongside L-connect usually worsens the situation. If you can recreate this, please report it to your motherboard maker. Other brands appear to ignore this for months despite ongoing reports. More submissions increase the chance they’ll act. Here are some links:
- ASUS forum thread about error code 0d
- Reddit discussion on hardware monitoring issues
- Full list of reports and troubleshooting steps
Reply
Reply
E
edibo
07-07-2025, 11:54 AM #1

MSI attributes the problem to L-connect 3 and plans further testing. I’ll update this once the removal resolves the issue. Currently, L-connect 3 seems to prevent Windows from restarting properly on every board. MSI has already notified Lian li, who is developing a fix soon. If your PC freezes during a restart (not due to cold boot) and you have L-connect 3 installed, close any running programs and exit applications before powering on again until the new version is available. This post was incorrect and outdated; my goal is to highlight the matter so more makers can address it. As of now, only ASUS mentions a known solution called "Monitoring Software reboot workaround" in their BIOS. For X670(E) or X870(E) boards with a postcode display (uncertain if it works without one), running Windows 11 and having multiple monitoring tools active can cause the issue. The DRAM LED stays on and the debug code "0d" appears on your postcode screen. Running several monitoring programs together—especially Turtzx, OCCT, CPU-Z, AIDA64, L-connect, ASUS Armoury Crate—can trigger this. It might be due to memory leftovers from hardware monitoring software during restarts. To make it easier to reproduce, launch several monitors simultaneously with them open and restart your PC. In my experience, the problem appears after a Windows update or when booting into Safe Mode. Adding OCCT alongside L-connect usually worsens the situation. If you can recreate this, please report it to your motherboard maker. Other brands appear to ignore this for months despite ongoing reports. More submissions increase the chance they’ll act. Here are some links:
- ASUS forum thread about error code 0d
- Reddit discussion on hardware monitoring issues
- Full list of reports and troubleshooting steps

Reply
Reply
J
Jelmerro
Member
Find
202
07-07-2025, 11:54 AM
#2
It doesn't necessarily reset the system every time to memory mode. There are distinct BIOS configurations for this feature, often referred to as Memory Context Restore or Memory Reference Code (MRC fast boot). The exact setting varies by manufacturer and may appear in different sections—sometimes alongside Fast Boot, other times within memory options. A search function can help locate it.
Reply
Reply
J
Jelmerro
07-07-2025, 11:54 AM #2

It doesn't necessarily reset the system every time to memory mode. There are distinct BIOS configurations for this feature, often referred to as Memory Context Restore or Memory Reference Code (MRC fast boot). The exact setting varies by manufacturer and may appear in different sections—sometimes alongside Fast Boot, other times within memory options. A search function can help locate it.

Reply
Reply