Rainy system error can not escape the palm of your hand (a)

Whether it is hardware or software problems, in order to correct the error, you must first find out the cause of the problem, in the error correction, Windows XP provides us with a powerful The event viewer tool, but its readability is too poor, and the book-like record is not something that ordinary users can understand (see Figure 1).

Microsoft may have realized this for a long time. The event viewer has been greatly improved in Vista, which not only greatly enhances readability, but also tracks the events that users care most about. In addition, considering that it is really a non-professional who really promotes the popularity of personal computers, Vista also has built-in "Reliability and Performance Monitor". With it, most people may become experts in system faults, if added Task Manager, Winows Defender, memory diagnostic tools, etc., can really make a system error, my prophet.

Event Viewer Expert's Diagnostic Tool

To open the Open Event Viewer, click “Start”, enter “MMC” (without quotes) in the search bar ) and press the Enter key to enter the system console window, then click “ File & Rarr; Add /Remove Management Unit & rdquo;, in the pop-up window, "Available Management Unit", select "Event Viewer". Next, click “Add”,“Local Computer”. & ldquo; After & rdquo; after & ldquo; event viewer & rdquo; can surface.

Tips:

★ You can also open the event viewer in other ways: one is under the “Start” menu, and the other is right-clicking. On the desktop, “computer”, then select “Manage”. The event viewer function opened in these two modes is weaker. It is better to display the remote and local computer logs at the same time in the system console for comparison, which is more conducive to finding the cause of the failure.

Step 1: Recognize the Event Viewer

The Event Viewer window of Vista defaults to the three-pane mode, which is the tree structure area, the event display area, and the operation area. For those who are used to Windows Explorer or Outlook Mail Reader, it is undoubtedly the most friendly interface, which provides us with a convenient query (see Figure 2).

In addition, it can be classified according to the nature of the event, such as: "Windows logs", "Applications and services" and so on. It can also be sorted by time, for example, within 24 hours, within a week, etc. No matter what you want to find, you can quickly cut into the subject and hit the nail.

More importantly, select a log (such as an event with ID 11706, please remember this ID, which will be used later), the content will be automatically displayed in another pane and no longer The book of heaven, as shown in Figure 3.

Inside the table: I tried to build a mini version of Office 2003 and installed it. The installation process did go wrong, as shown in Figure 3, which is detected in the event viewer. Wrong record. From this, it can be confirmed that the event viewer can really check the autumn.

Step 2: Favorites Log

Good content has to be collected and tasted. This well-known technology is also used in the event viewer. It is implemented by creating a custom view. During the creation process, we can define the events of interest according to our needs according to time, event level, event source, and even keywords. Once the customized view is created successfully, it can be saved in the list under “Custom View” and can be viewed at any time.

Not only that, but we can also export our own records or import other people's records, through sharing, consultation and other measures to improve the accuracy of query failure. In this case, I am most concerned about the operation of the mini version of Office 2003, then collect it. Click “Create Custom View", and the dialog box shown in Figure 4 pops up. Since this event has appeared, you can select “Press Log” and check all items under “Event Log”. Specifically specify its ID number, which is 11706.

In the next window, you can assign a name to the custom view and a short description of the event. In this case, the name entered is “Mini Office ”. When you are done, expand the console under “ console root node → event viewer → custom view & rdquo;, you can observe the new view "mini Office", in the future, just open it to observe and “Mini Office” related logs.

In essence, custom views or collections are designed to filter out the most useful data from a large number of logs. If it is only a temporary filter, it can also be achieved by filtering the current log. Click “Filter current log& quoquo; on the right side of the main window, and then follow the prompts.

Step 3: Tracking Logs

It is wasteful to use the Event Viewer only to view information negatively. We can also track events that we are interested in so that we can keep abreast of the situation and make countermeasures. Tracking events, the implementation principle is very simple, first specify what events to be tracked (trigger source), and then specify what response measures should be taken once the relevant information of the event to be tracked is captured, such as: alerting the user to attention, starting the relevant program Solve and so on. It is particularly worth mentioning that when specifying response measures, multiple linkage measures can be specified, embodying a (trigger source) versus multiple (response) design concept.

In this example, we use Mini Office as an example. And configure two response events: display the message and send the message to the administrator.

1.Create basic tasks

After selecting the log related to mini Office, click “Add task to this event",“Create basic task>The wizard will automatically run. As shown in Figure 5, it can be seen that the wizard is divided into 4 steps, in which the first 2 steps can take the default setting, and when the 4th step is to specify the response event, you can only select “start the program”,“ send an email ”, “display information & rdquo; and so on. In this case, we select “display message”, as prompted, enter what you want to display. This task cannot be observed in the Event Viewer, it will appear in the "Task Scheduler" as shown in Figure 6.

2.Create advanced tasks

Double-click the “Event Viewer Task” in the “Task Scheduler” and click ““ Operation” in the pop-up window. → Add & rdquo;, will also pop up a dialog box similar to the one shown in Figure 5, enter the email account and password.

Step 4: Log Extension

Logging is in XML format, which is the underlying technical support hidden behind the Event Viewer. One of its benefits is that it is provided to third-party events. View tools for expansion.

Reliability Monitor Ordinary Diagnostic Tool

The Event Viewer is powerful and is aimed at IT technicians. Although the performance viewer only provides viewing functions, no tracking, collection, filtering, etc., but it is easy to use, mainly for ordinary computer users. Troubleshooting can also be done using the Reliability Monitor. The Reliability Monitor quickly displays a history of system stability, allowing you to view event details that affect reliability every day, helping us understand the results and taking action based on the results to improve reliability.

Right-click on the “computer” on the desktop, select “Manage”, and then expand in the pop-up window. Computer Management (Local) & Rarr; System Tools & Rarr; Reliability and Performance & Rarr The monitoring tool → reliability monitor & rdquo; can open it, as shown in Figure 7. It divides the factors affecting computer stability into five major parts, including: software installation (uninstallation), application failure, hardware failure, Windows failure, and other failures. The Reliability Monitor retains a history of up to one year of system stability and reliability events. These records are displayed in the form of a chart.

1. Curves

Performance Monitor divides system stability into ten levels from 1 to 10. The higher the number, the more stable it is. According to this standard, the performance monitor reviews the stability of the day, obtains a graphical point representing the size of the number, and then connects the graphical points of the day to form a curve, which is very visual and intuitive. In order to ensure the reliability of the curve, it excludes some situations, such as:

· special time period. Does not include periods when the system is off or in hibernation.

· When data is insufficient. When the system is running for less than 24 hours after installation and a reliable system stability index cannot be calculated, the curve will appear as a dotted line. When the recorded data can generate a reliable system stability index, the curve will automatically be converted to a solid line.

2. Icons

The stability index is shown in the top half of the chart, in the column for this date when one or more reliability events of each type are detected An icon will be displayed.

· For software installation and uninstallation, a "information" icon indicating a success event of this type (blue bubble with an i in the middle) or a warning indicating that the type failed ” icon (yellow triangle with an exclamation point in the middle).

· For all other reliability event types, there will be an "error" icon (a red circle with a cross in the middle) indicating that the type failed.

3. The specific situation of the event

By looking at the "System Stability Report" in the lower part of the chart, you can get the specific situation of each event. From the event attribute, it will be listed. Which program or which version of the hardware is recorded at what time; whether there is a problem, what kind of problem has occurred, and so on.

From the perspective of viewing, you can only pay attention to the specific situation of a certain day, but also the situation at all times. There are different ways in each of the two ways. When we look at the specific situation at all times, we can compare the performance of the same software or hardware at different times to better understand the performance of the object of interest, which is very useful for troubleshooting. .

For example: from the chart, on April 3, 2007, there was no fault, but by April 6, 2007, there was a red and crossed error sign, which visually saw the curve slip. . Then check the "System Stability Report" on April 6th. It can be observed that the error program is WinWORD.exe. The specific performance is to stop responding. At this time, we must pay attention to it. After memorizing: I installed the mini version at that time. Office 2003. With this clue, the solution to the problem comes out, uninstall it or reinstall the official version. After solving the problem, you can observe that the curve is rising and rising (April 8).

Problem Reporting and Solution Automation Diagnostic Tool

Dr. Watson is a system failure analysis tool for past versions of Windows. This tool has been used in Vista. “ Problem Reports and Solutions & rdquo; replaced. The tool's diagnosis of system hardware and software problems is done automatically, and once the problem is detected, it can automatically send a report to Microsoft to find a solution. You can also view the solution returned from Microsoft.

Click on "Start → All Programs & Rarr; Problem Reports and Solutions" to open it (see Figure 8). From the point of view of use, the two commonly used are: “View problem history” and “Check for new solutions”.

For example: I have previously found out the problems caused by the mini version of Office, which is reflected here, and gives a solution to the problem —— download Microsoft Office System Software, It is very targeted.

With these tools, I believe everyone can be a master of troubleshooting.