[SOLVED] Windows 11 infinite shutdown

[PlotArmorNotFound]

Hi everyone,

I own a Lenovo Legion 5 Gen 7 laptop (CPU: AMD 6800H, GPU: NVIDIA RTX 3060) with Windows 11.

I have noticed that often when attempting to turn off the computer, it gets stuck in an infinite shutdown (after I press "Shut down" on the start menu). The fan continues to work faintly and the light on the on/off switch does not turn off. In the end, I am forced to hold the switch for a few seconds until the PC forcefully shuts down. So far this has always happened when turning off the laptop immediately after gaming. I have tried waiting for the fans to become slower after closing the game applications but it still happens.

Before, the screen was completely black when this happened. A few days ago I (1) deactivated fast startup and (2) used the Windows Update troubleshooter, which allegedly made some changes to my system. After that the problem disappeared for a few days but finally reappeared today after gaming for a few hours. This time the screen showed the "Shutting down" text and the wheel animation, other than that everything was the same.

I am worried that this always forces me to hold the on/off switch, which is not great for the computer. Other than this, my laptop works flawlessly. I would appreciate any idea as to what is causing the issue. Many thanks in advance.

 

[Colif]

can be caused by the bios having a conflict with windows and not following instructions.

Have you checked Lenovo website for laptop and run the auto update feature to make sure you not missing any drivers?

 

[kerberos_20]

power management is handled by bios, but windows is able to override it...on desktop you can configure it, on laptops such configuration is an optional feature (in bios)

can you check eventviewer what power events you have there?

 

[PlotArmorNotFound]

can be caused by the bios having a conflict with windows and not following instructions.

Have you checked Lenovo website for laptop and run the auto update feature to make sure you not missing any drivers?

Hi! Thanks for the reply and sorry for being so late, as I was observing the behavior these last few days. I did check the Lenovo website and scanned for outdated drivers, but it said everything is up to date. Same with the AMD drivers and the Windows version. The problem does not seem to appear when I run the Windows Update troubleshooter as mentioned in the original post. It always says it detected some issues and made some changes to the system.

 

[PlotArmorNotFound]

power management is handled by bios, but windows is able to override it...on desktop you can configure it, on laptops such configuration is an optional feature (in bios)

can you check eventviewer what power events you have there?

Hi, thanks for the reply! I checked the power-related events and there is nothing out of the ordinary. Just a bunch of times the system returned from a low-power state (after reopening the lid, I assume) as shown by the Power-Troubleshooter events. Maybe I am not looking in the right place? I also run a sleep study, and there is one abnormal shutdown recorded from a few days ago. Unfortunately the information on it is clearly wrong:

- Battery Information
Remaining Charge Capacity At Entry [mWh]         0
Full Charge Capacity At Entry [mWh]         0
Remaining Charge Capacity At Exit [mWh]         0
Full Charge Capacity At Exit [mWh]         0
- System Event Log
BootAppStatus         0
Checkpoint         0
CheckpointStatus         0
SystemSleepTransitionsToOn         0
CsEntryScenarioInstanceId         0
LongPowerButtonPressDetected         0
LidReliability         0
InputSuppressionState         Disengaged
PowerButtonSuppressionState         Disengaged
LidState         Opened

You mention these settings can be changed from the BIOS... What option should I be looking for?

 

[Colif]

is there anyway to reset the bios to defaults as that can help fix conflicts with windows.

can you search for control panel
change icon size to large
choose power options
click "choose what the power button does"
Is Fast startup enabled? It shouldn't be, I am just checking
If it is, click "change settings currently unavailable" next to the blue/yellow shield
untick "Turn on fast startup" and click save changes

If its not on, thats good. I was just checking. It is meant to be off in win 11

that might help if the problem is a driver

Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

It doesn’t delete anything, it just stops non Microsoft programs running with start. Easy to reverse.

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.

 

[PlotArmorNotFound]

is there anyway to reset the bios to defaults as that can help fix conflicts with windows.

can you search for control panel
change icon size to large
choose power options
click "choose what the power button does"
Is Fast startup enabled? It shouldn't be, I am just checking
If it is, click "change settings currently unavailable" next to the blue/yellow shield
untick "Turn on fast startup" and click save changes

If its not on, thats good. I was just checking. It is meant to be off in win 11

that might help if the problem is a driver

Try a clean boot and see if it changes anything - make sure to read instructions and make sure NOT to disable any microsoft services or windows won't load right - https://support.microsoft.com/en-au/help/929135/how-to-perform-a-clean-boot-in-windows

It doesn’t delete anything, it just stops non Microsoft programs running with start. Easy to reverse.

if clean boot fixes it, it shows its likely a startup program. You should, over a number of startups. restart the programs you stopped to isolate the one that is to blame.

Thanks! Fast startup is indeed disabled (I turned it off originally to try if it fixed the issue). I will try your method over a number of startups and see if I can identify the culprit.