Troubleshoot operating system startup failures based on NT kernel (2)

Solve

Whenever a problem occurs, Windows may stop responding (hang) or prompt for error messages because of missing files required by the operating system or corrupted files. Solving such problems requires scientific use of the methods provided by Windows, including Safe mode, Recovery Console, and Emergency Repair Disk. The startup process refers to selecting the appropriate system entry on the boot loader until the desktop appears and the hard drive stops ringing, and if the boot loader selection menu does not appear, you will need to restore the missing boot loader menu by installing the CD or by hand.

The troubleshooting process follows the program loaded in the first Windows environment, then the core operating system is sequential, and if the failure is related to the former uninstall or restore the damaged program, if the fault is related to the latter need to restore the core operating system of the main file.

The diagnosis of a program loaded in a Windows environment first determines whether the problem is caused by an incompatible or corrupted program, usually by entering safe mode. If you start your computer in Safe mode or in Safe mode with network support and you can perform the operation normally (an operation that has previously been performed), the problem is likely to be an environment-related issue. Excluded by using Msconfig to exclude add-ins and delete registry add-ons. If the newly added device or changed driver is causing the problem, you can use Safe mode to remove the device or undo the change. In this way, the default settings and the most basic device drivers are excluded from the possible cause of the problem. If the problem still occurs after you start your computer in Safe mode or in Safe mode with network support, your environment-related problems may still be the cause of the problem, and features or filter drivers that are installed by Third-party software are loaded in Safe mode, and after you determine which driver is causing the problem, You can remove (uninstall) the driver or program, or turn off (disable) the driver or service.

If the device or service is not in the Windows user interface, only use the Recovery Console to close the driver or service. Use the Recovery Console listsvc command to list all available services, drivers, and the startup type of their current Windows installation, and to disable or start Windows system services or drivers with the disable and the Enable command. Troubleshoot the service or driver that is causing the problem.

If none of the above methods are resolved, Automated System Recovery (ASR) should be the last way to recover a system failure. ASR and overwrite installation can restore core system files.