Blog Statement: Issues with Legion 5 15AKP10 (Ryzen AI 7 350 + RTX 5060)

 After ½ months of use (purchased on 16 November 2025 and picked up on 17 November 2025), my Lenovo Legion 5 15AKP10, equipped with a Ryzen AI 7 350 processor and RTX 5060 GPU, has begun showing a mix of hardware and software stability issues worth noting. 

1. LiveKernelEvent 141 (GPU Hardware Error) 

On December 1, 2025, Windows logged a LiveKernelEvent 141, which is a GPU-related hardware fault commonly linked to TDR (Timeout Detection and Recovery) failures. The report pointed to amdkmdag.sys, indicating a low-level interaction issue with the AMD GPU driver stack or the system’s graphics pipeline. Errors like this usually happen under heavy load or when the system shifts between power states. These issues can lead to freezes, black screens, or sudden resets. 

2. Lenovo Legion Toolkit Crash After Hibernation 

After waking from hibernation, Lenovo Legion Toolkit (LLT) consistently crashes because of a .NET runtime failure inside coreclr.dll. This occurs when the system resumes and hardware drivers reinitialize while LLT is still trying to access hardware sensors. Community reports, including on the XKaguya fork of LLT, confirm that this is a repeatable problem affecting many users on modern Legion systems. The recommended fix is to repair the .NET 9.x runtime, which restores coreclr.dll. However, the root cause seems related to how Windows manages hibernation and driver state restoration. 

3. User Experience Impact 

Together, these issues show that even a powerful 2025 mid-range gaming laptop can have trouble with driver stability and software interactions, especially with new hardware like Ryzen AI and NVIDIA’s RTX 50-series. Power state transitions, such as sleep and hibernate, are particularly sensitive. Tools deeply integrated with hardware, like LLT, are more likely to crash when system modules do not resume properly. 

4. Workarounds & Recommendations 

To keep the Legion 5 15AKP10 stable: 

  • Keep GPU, chipset, and firmware updated. 
  • Repair .NET 9 runtime if LLT fails to launch. 
  • Avoid using hibernation; prefer Sleep or a full shutdown.
  • Disable Fast Startup to reduce the risk of runtime module corruption. 
  • Relaunch LLT only after the system is fully resumed. 

While the Legion 5 15AKP10 remains strong in terms of performance, these issues highlight that early hardware generations and new driver updates may need time to achieve full stability.

Comments

Popular posts from this blog

UMC Security Advisory - Celxpert Battery Issues

How I Became a Proactive Battery Monitor (Catching Issues Early)

UMC Bans the DeepSeek amid security concerns