As shown in the following illustration:
Reason analysis:
This behavior occurs when a system file is corrupted or if the resource manager fails to load a Third-party plug-in, or if some software installation conflicts occur.
Solution:
The "View Reliability History" feature of the Windows System Reliability Monitor enables you to quickly find programs that affect system stability. Reliability Monitor provides a general picture of system stability and trend analysis, with detailed information about individual events that may affect the overall stability of the system, such as software installation, operating system updates, and hardware failures. The monitor starts collecting data when the system is installed. This feature is available for Windows 7 and Windows 8 systems.
1. Open Operations Center in Control Panel and find the View Reliability History link under Maintenance options. You can also type "
reliability Monitor" or "
View reliability History " directly in the Start menu search, or search for "reliable" directly, and then open the View Reliability History link. (Windows 8 system can press the
Windows key +w to search) the following figure:
After opening, the following interface appears:
2. Click on the Red Fork section, the following will show the exception of the program. Double-click the program name to display a detailed error message.
3. According to the display program name and path, the corresponding software uninstall test is back to normal.
As shown in the figure, the Armsvc.exe process causes a resource manager exception. This process, through an online search, understands that the Adobe Acrobat Update Service is attached to the software Adobe Acrobat update service or Adobe Reader x. Open the
Control Panel ---
programs and features (or open
Control Panel ---
uninstall program ), locate the appropriate software, and then restart the computer after uninstalling to test for normal recovery. If you need this software, you can download the installation to the official website of the software.
If it is shown as another process or software, it can be done.
Note:
If the contents of the "Reliability history" are empty, make sure that the following system log related service items are set to start automatically and that the current running state is "started":
