Event id for reboot windows xp

If the right to log on as a service is revoked for the specified user account, restore the right by using either of the following methods, as appropriate to your situation. Right-click the organizational unit OU in which the user right to log on as a service is granted, and then click Properties.

By default, this is in the Domain Controllers OU. In the right pane, right-click Log on as a service , and then click Security. In the right pane, right-click Log on as a service , and then click Properties. If the password is changed on the user account that the service uses to log on, configure the password to match the current password for that user.

To do this, follow these steps:. If the service still does not work with the specified user account, configure the service to log on to the built-in system account. NOTE: In most situations, it is not necessary to configure a service to interact with the desktop. You do not need to select the Allow service to interact with desktop check box.

You may receive this error message if the remote procedure call RPC service is not started because of a logon failure with that service or a dependency service. Some services have dependency services, and these services do not start until their dependency services start first for example, the Workstation service. If you cannot start the Services tool, use Registry Editor to configure the service to use the built-in system account.

Click Start, and then click Run. Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. Every environment is different, and some of the events ranked with a potential criticality of High may occur due to other harmless events.

Refer to Windows security audit events for a list of many security event IDs and their meanings. You can also download Security Audit Events for Windows 7 and Windows Server R2 and Windows 8 and Windows Server Security Event Details , which provide detailed event information for the referenced operating systems in spreadsheet format.

Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Note Refer to Windows security audit events for a list of many security event IDs and their meanings. Submit and view feedback for This product This page.

View all page feedback. In this article. Administrator recovered system from CrashOnAuditFail. Users who are not administrators will now be allowed to log on. Some auditable activity might not have been recorded. IPsec dropped an inbound packet that failed an integrity check.

If this problem persists, it could indicate a network issue or that packets are being modified in transit to this computer. Verify that the packets sent from the remote computer are the same as those received by this computer. This error might also indicate interoperability problems with other IPsec implementations.

IPsec dropped an inbound packet that failed a replay check. If this problem persists, it could indicate a replay attack against this computer. The inbound packet had too low a sequence number to ensure it was not a replay.

IPsec dropped an inbound clear text packet that should have been secured. This is usually due to the remote computer changing its IPsec policy without informing this computer. This could also be a spoofing attack attempt. If it does generate a Stop error, it might not finish writing the error codes to disk.

The next time the computer starts, it might not log Event ID Or, if it does, the bug check code is zero. Conditions such as the following might be the cause:. The PowerButtonTimestamp value is zero. This behavior might occur if you disconnected the power to a computer that was not responding to input. Typically, the symptoms described in this scenario indicate a hardware problem. To help isolate the problem, do the following:. If you perform these checks and still cannot isolate the problem, set the system to its default configuration and verify whether the issue still occurs.

If you see a Stop error message that includes a bug check code, but Event ID 41 does not include that code, change the restart behavior for the computer. To do this, follow these steps:. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info.

Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note Event ID 41 includes the bug check code in decimal format. To convert decimal to hexadecimal, follow these steps: Select Start , type calc in the Search box, and then select Calculator. On the left side of calculator, verify that Dec is highlighted. Use the keyboard to enter the decimal value of the bug check code.