Check boot log windows xp

They can manipulate it to display error messages and warnings even if your computer is working correctly. There are many identified events related to shutting down and restarting a Windows 10 PC.

However, we will show you the most common four in this article, and they include the following:. You can quickly figure out the events on your computer after shutting down or restarting using the Windows Event Viewer. You can also access some of the events using the Command Prompt, as we will show you below.

Generally, there are two methods to check the events related to shutdown or restart on your computer. From Windows 10 Fall Creators Update, the OS can automatically reopen apps that were running before your computer shut down or restarted. This information is handy for Windows users who upgraded their OS to the recent release. If the first method is not convenient for you, you can use Windows Command Prompt to check the system log by following the steps below:.

You can use the Command Prompt to view shutdown and startup log on Windows If you have computer issues like corrupt keys or junks files, it may be challenging to view restart and shutdown events on your PC. We always advise people to use our registry cleaner to get rid of problematic files that can harm their computer. Auslogics BoostSpeed helps to remove all harmful files in the registry. These problems might require that you reinstall the operating system.

Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk. The ISO should be of same version of Windows or a later version. Under the following registry subkey, check for lower filter and upper filter items for Non-Microsoft Drivers:.

For each third-party driver that you locate, click the upper or lower filter, and then delete the value data. Search through the whole registry for similar items. Process as an appropriate, and then unload the registry hive. To fix problems that occur after you install Windows updates, check for pending updates by using these steps:. Highlight the loaded test hive, and then search for the pendingxmlidentifier value. If the Stop error occurs late in the startup process, or if the Stop error is still being generated, you can capture a memory dump.

A good memory dump can help determine the root cause of the Stop error. For details, see the following articles:. For more information about page file problems in Windows 10 or Windows Server , see the following:. Check the functionality that is provided by the driver.

If the driver is a third-party boot driver, make sure that you understand what it does. If the driver is not important and has no dependencies, load the system hive, and then disable the driver.

If the Stop error indicates general registry corruption, or if you believe that new drivers or services were installed, follow these steps:. 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 This article is intended for use by support agents and IT professionals. Note Starting in Windows 10, version , Windows no longer automatically backs up the system registry to the RegBack folder.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. Submit and view feedback for This product This page.

When facing a system crash or startup up problems on Windows Computers, troubleshooting the problem can be difficult to resolve. The first step with recovery is to use Windows Safe Mode option during startup. One Safe Mode option that will help troubleshoot boot problems is to enable Boot Logging which will create a log and help identify the device or driver that is causing the problem during startup.

When Boot Logging is enable, Windows boots normally, until the device or driver that is causing the problem either crashes the system or completes starting up but causes an error message in the Event Log.

While booting, Windows creates a log file that lists every step processed that is attempted and completed. You can then reboot in to Safe Mode and review the log file named ntbootlog.

Below is an example of ntbootlog. SYS Loaded driver pci. SYS Loaded driver intelide. SYS Loaded driver disk. SYS Loaded driver fltmgr. Vista menu will look slightly different than XP. You will be returned to the menu screen and you should see Enable Boot Logging in blue displayed at the bottom of the screen don't worry if this screen is not displayed and Windows starts to boot :. If the problem does not cause Windows to crash, and after startup has completed, you can review the ntbootlog.

Look for any signs of problems loading device drivers. If you find problems, go into Device Manager and disable the device or uninstall the program, then reboot again. If the problem does not occur then you know it was that device and you should check the vendor website for new drivers or known issues.

If your problem does cause Windows to crash, reboot into Safe mode by selecting Safe Mode from the Advanced Menu screen. When reviewing ntbootlog. More than likely the problem will be toward the end of the file since that was the last item logged before crashing.

When you identify the problem, either uninstall the application or go in to Device Manager and disable the device. Reboot your Computer and see if the problem still exist. If it boots without crashing, check the vendor website for new drivers or known issues.

If you are still having problems, enable Boot Logging again to see if new events are logged after you have disabled the device or uninstalled the program.

If you are unable to fix the problem, you may need to have a Computer shop troubleshoot the problem for you. Notes on Boot Logging:. Filed under Windows Tips by Mike Boyds. Think you for this I was struggling on my assignment I finally got an idea on what I was looking for. I'm running windows Vista Ultimate 64bit and i get a blue screen at start up now and then seem only to be when the pc has ben off for a while.

I've tried using boot logging but i cant find the file in windows can you please help me out. Another option you may want to try is to disable automatic reboot option when a blue screen of death occurs.

This will allow you to see the stop error message. Have you resolved this issue? I am having the same problem. The only time I get it is when I have had my notebook turned off for hours…It is a new HP…it has done this since day one…It is under warranty..