Hey folks, I'm having a frustrating issue with my Lenovo Legion Pro 5 16IRX9. Every time it goes to sleep and I try to wake it up, it just restarts and shows the Legion splash screen. I lose all my open applications in the process. This problem started after I modified my power plan settings. I used to have the display and sleep settings set to never turn off, but I changed them to auto-sleep after a couple of hours. I've come across similar complaints online from as far back as 2022, but there's no solid fix suggested other than turning off sleep altogether. This doesn't seem like a simple wake issue; it acts more like an unexpected shutdown. I checked the Event Viewer logs and noticed a Kernel-Power Event indicating the system rebooted without a standard shutdown and a WHEA-Logger event suggesting a fatal hardware error. Here are my current specs: Updated BIOS, Intel 14th Gen i9, Windows 11, and I'm using dGPU mode. I've already tried updating the BIOS, reinstalling firmware, adjusting power management settings, and disabling Fast Startup without any luck. Any insights on this?
3 Answers
I dealt with a similar problem on my Legion 5 Pro a few years back, and it got solved by updating some drivers. You might want to check for any updates that might help your situation. Posting this in a Lenovo-specific community could also get you some tailored advice.
This happened to me on an AMD desktop machine running Windows 10. The fix for me was to update the BIOS to the latest version. Not sure if that applies here, but it might be worth checking. Also, be cautious about potential over-voltage issues with the latest Intel processors.
It might be a hardware issue since that behavior isn't very common. If I were you, I'd consider doing a clean reinstall of Windows to rule out any software problems before digging deeper into hardware checks. If the problem continues after that, try to troubleshoot the hardware as much as you can since it's a laptop.
I appreciate the input, but I doubt it's hardware since hibernation works fine without any restarts. My guess is this has to do with S3 sleep settings causing the trouble.