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:. Your email address will not be published.
Notify me of followup comments via e-mail. This site uses Akismet to reduce spam. Learn how your comment data is processed. Think you for this I was struggling on my assignment I finally got an idea on what I was looking for. Watching The Net. Comparing normal mode and safe mode entries enables you to determine which services run in normal mode only-one of which must be the cause of the startup problem if Windows is able to start in safe mode successfully.
The following lines are sample Ntbtlog. Note that not every "Did Not Load Driver" message necessarily indicates an error that would prevent Windows from booting, because many drivers are not required for Windows to start. To repair problems caused by problematic drivers when you can start safe mode, follow these steps:. For the services that run only in normal mode, disable those services one at a time, trying to restart your computer in normal mode after you disable each service.
Continue to disable services individually until your computer starts in normal mode. To repair problems caused by problematic drivers when the computer does not start in safe mode, follow these steps:. SYS Note that not every "Did Not Load Driver" message necessarily indicates an error that would prevent Windows from booting, because many drivers are not required for Windows to start. To repair problems caused by problematic drivers when you can start safe mode, follow these steps: Restart the computer and enable boot logging.
Keeping tabs on a machine -- knowing what is happening, knowing what is running, knowing what is starting at bootup -- is one of the key elements in maintaining a healthy system. To keep control over what is running, you can always use a tool like Autoruns, but for some, that tool is overkill. If you just want to analyze what occurs during the boot process on a Windows 7 machine, you should consider using msconfig.
With msconfig, you can set up a boot logger that will log every driver that is loaded during the boot process.
Once you have this information, you can troubleshoot numerous problems. Here's how to enable the boot log using Windows built-in msconfig.
When the reboot completes, open the msconfig tool. In order to view the log file, do the following:. Every time you reboot Windows, new entries will be added to this log; this means the log can get long, and too many entries will cause problems troubleshooting.
Since there is no method of log rotation here, you might save the file in a dated folder, so you know exactly what you are dealing with. You can also delete the old entries from the log file to save this from growing too large. Once you complete troubleshooting, you might consider disabling the feature, as msconfig will continue logging.
0コメント