Find out why computer shut down

The unexpected shut down may occur in many ways, sometimes putting your PC at sleep for a longer period may lead to random shut down. The system may or may not notify you about the shutdown. In some cases, users have received a message regarding the sudden requirement of shutdown in 10 minutes or 30 minutes even if all the drivers are updated. Let us find out the root of this unexpected behavior of Windows 10. In this article, you will learn three methods using which you can find the cause of unexpected shutdown on Windows 11/10. Let’s now see them in detail:

1] Through Event Viewer

To find the cause of the unexpected shutdown using Event Viewer, use the following suggestions: Click on Start, type Event Viewer, and then select the result from the top of the list. After heading into Event Viewer, expand Windows Logs from the left and then select System. Now do right-click on System and select the Filter Current Log option.

Inside the Filter Current Log window, select the Filter tab. Then go to the All Event ID textbox and enter the following ID number separated by a comma as shown in the below snapshot.

41: It indicates that your system is crashed, power lost, or not responding which in turn leads to incorrect shutdown using the clean shutdown option.1074: This event is logged for manual shutdown or restart. It is also applied for the event when the system automatically restarts to install new updates to your computer.6006: It is triggered after the new update installation, especially when the system is lost during the shutdown.6005: This is an error that occurs when the system goes for a reboot.6008: This event is a clear indicator of random automatic shutdown, which may be caused due to error 41.

Now click the OK button and then double-click a log to verify the information. As soon as you complete the above steps, you will see the real causes of your device shut down unexpectedly. Read: How to check the Shutdown and Startup Logs.

2] By using PowerShell

Another method to find the cause of the unexpected shutdown on Windows 10 is using Windows PowerShell. So, if you prefer a command-line interface over GUI, you can use the following instructions to do so:

Open an elevated PowerShell prompt Once it opens, type the following command and press Enter: Go to the log description section and know the possible causes and time for the shutdown. Let us talk about them in detail. First of all, open an elevated PowerShell prompt. To do so, right-click on Start and select Windows PowerShell (Admin) option from the menu list. If a UAC prompt is triggered and asks for your permission, click on the Yes button. Inside the elevated PowerShell app area, copy and paste the following command and hit Enter: After running the above command, the possible causes and times for the shutdown will be listed. To do this, you can go to the log description section and check them.

3] Use Command Prompt

To find the real cause and time of the unexpected shut down of your computer, follow the below suggestions:

Run Command Prompt as administrator on your computer. Type the following command and hit Enter: Now press the Enter key and you’re done. You will see all the possible causes that had led your computer to shut down unexpectedly. If you need, you can read the above steps in detail form. So, to find the cause of the unexpected shutdown of your computer, you first need to open an elevated command prompt. To do so, right-click on the Start menu and open the Run dialog. In the text field, type cmd to search for Command Prompt. Then press Ctrl+Shift+Enter to open Command Prompt with admin privileges. Also, click the Yes button if a UAC prompts on the screen. Now copy and paste the following command-line and press Enter: If you want to view more or fewer event logs, you can do it by doing some minor changes in the above command line. To do that, set /c:100 with your preferred number and run the command again. You will see the possible causes and times for the shutdown that occurred on your computer. You can go to the log description section and check them. Hope it helps.