Show
Note Home users: This article is intended for use by support agents and IT professionals. If you're looking for more information about blue screen error messages, please visit Troubleshoot blue screen errors. The preferred way to shut down Windows is to select Start, and then select an option to turn off or shut down the computer. When you use this standard method, the operating system closes all files and notifies the running services and applications so that they can write any unsaved data to disk and flush any active caches. If your computer shuts down unexpectedly, Windows logs Event ID 41 the next time that the computer starts. The event text resembles the following information: Event ID: 41 Description: The system has rebooted without cleanly shutting down first.This event indicates that some unexpected activity prevented Windows from shutting down correctly. Such a shutdown might be caused by an interruption in the power supply or by a Stop error. If feasible, Windows records any error codes as it shuts down. During the kernel phase of the next Windows startup, Windows checks for these codes and includes any existing codes in the event data of Event ID 41. EventData BugcheckCode 159 BugcheckParameter1 0x3 BugcheckParameter2 0xfffffa80029c5060 BugcheckParameter3 0xfffff8000403d518 BugcheckParameter4 0xfffffa800208c010 SleepInProgress false PowerButtonTimestamp 0Converts to 0x9f (0x3, 0xfffffa80029c5060, 0xfffff8000403d518, 0xfffffa800208c010)How to use Event ID 41 when you troubleshoot an unexpected shutdown or restartBy itself, Event ID 41 might not contain sufficient information to explicitly define what occurred. Typically, you've to also consider what was occurring at the time of the unexpected shutdown (for example, the power supply failed). Use the information in this article to identify a troubleshooting approach that is appropriate for your circumstances:
Scenario 1: The computer restarts because of a Stop error, and Event ID 41 contains a Stop error (bug check) codeWhen a computer shuts down or restarts because of a Stop error, Windows includes the Stop error data in Event ID 41 as part of more event data. This information includes the Stop error code (also called a bug check code), as shown in the following example: EventData BugcheckCode 159 BugcheckParameter1 0x3 BugcheckParameter2 0xfffffa80029c5060 BugcheckParameter3 0xfffff8000403d518 BugcheckParameter4 0xfffffa800208c010
Note Event ID 41 includes the bug check code in decimal format. Most documentation that describes bug check codes refers to the codes as hexadecimal values instead of decimal values. To convert decimal to hexadecimal, follow these steps:
When you convert a bug check code to hexadecimal format, verify that the "0x" designation is followed by eight digits (that is, the part of the code after the "x" includes enough zeros to fill out eight digits). For example, 0x9F is typically documented as 0x0000009f, and 0xA is documented as 0x0000000A. In the case of the example event data in this article, "159" converts to 0x0000009f. After you identify the hexadecimal value, use the following references to continue troubleshooting: Scenario 2: The computer restarts because you pressed and held the power buttonBecause this method of restarting the computer interferes with the Windows shutdown operation, we recommend that you use this method only if you've no alternative. For example, you might have to use this approach if your computer isn't responding. When you restart the computer by pressing and holding the power button, the computer logs an Event ID 41 that includes a non-zero value for the PowerButtonTimestamp entry. For help when troubleshooting an unresponsive computer, see Windows Help. Consider searching for assistance by using keywords such as "hang," "responding," or "blank screen." Scenario 3: The computer is unresponsive or randomly restarts, and Event ID 41 isn't recorded or the Event ID 41 entry or lists error code values of zeroThis scenario includes the following circumstances:
In such cases, something prevents Windows from generating error codes or from writing error codes to disk. Something might block write access to the disk (as in the case of an unresponsive computer) or the computer might shut down too quickly to write the error codes or even detect an error. The information in Event ID 41 provides some indication of where to start checking for problems:
Typically, the symptoms described in this scenario indicate a hardware problem. To help isolate the problem, do the following steps:
If you perform these checks and still can't isolate the problem, set the system to its default configuration and verify whether the issue still occurs.
Note If you see a Stop error message that includes a bug check code, but Event ID 41 doesn't include that code, change the restart behavior for the computer. To do this, follow these steps:
|