DIAGNOSE ERROR LOGS BEEPS

System Error Log
The System Error Log contains a listing of system errors. Click an error link to view the entire error log. You can search by error type or date, and specify how many errors you want to display per page.

Types of error
Windows errors can be classified into various categories , such as :

1.    System errors – These are moderately dangerous types of errors among those that can pop up on your PC. System errors are caused by malfunctioning hardware components, corrupted operating  system modules, etc.

2.    Runtime errors – Runtime errors are caused by corrupted or malfunctioning system files or software executables. Most runtime errors cause the application that caused it to shut down. However, more serious runtime errors may cause the system to become unstable or unresponsive, leaving you with no choice but to reach for the Reset button.

3.    Stop errors – Stop errors are caused by corrupted hardware, especially malfunctioning RAM modules and bad sectors on hard disks. Stop errors can be difficult to resolve at times. If you get Stop errors continuously on your PC, call up a system engineer to check your PC

4.    Device Manager errors – These are usually caused by corrupted driver files or malfunctioning hardware components. In case of the former cause, the problem is usually solved simply by reinstalling or updating the drivers. However, the latter cause can often be solved only by replacing hardware components.

5.    POST code errors – POST code errors are caused by malfunctioning hardware components, and are characterized by short beep sounds from the tiny internal speaker of your motherboard. POST code errors occur when you press the power button to turn on your PC. If you are getting POST code errors in your PC, you should get your CPU checked by a system engineer.

6.    Application errors – These can be caused at any point of time. As the name suggests, these are caused by applications while those are running. These are usually caused by glitches in the program code itself. These are usually resolved by updating the program to its latest version.

7.    Browser Status Codes – These are caused by problems faced by browsers when trying to access a website. These can be caused by misplaced web pages in the server of the website itself, or due to connection problems. For instance, a 404 error would indicate that the browser is trying to access a webpage that does not exist in the specified location.

Event Viewer
Event logs are special files that record significant events on your computer, such as when a user logs on to the computer or when a program encounters an error. Whenever these types of events occur, Windows records the event in an event log that you can read by using Event Viewer. Advanced users might find the details in event logs helpful when troubleshooting problems with Windows and other programs.

Event Viewer tracks information in several different logs. Windows Logs include:
•    Application (program) events
-Events are classified as error, warning, or information, depending on the severity of the event. An error is a significant problem, such as loss of data. A warning is an event that isn't necessarily significant, but might indicate a possible future problem. An information event describes the successful operation of a program, driver, or service.
•    Security-related events.
-These events are called audits and are described as successful or failed depending on the event, such as whether a user trying to log on to Windows was successful.
•    Setup events
-Computers that are configured as domain controllers will have additional logs displayed here.
•    System events
-System events are logged by Windows and Windows system services, and are classified as error, warning, or information.
•    Forwarded events
-These events are forwarded to this log by other computers.





How to open the event viewer in Windows 7
1.    Open Event Viewer by clicking the Start button 
2.    Clicking Control Panel,
3.    Clicking System and Security,
4.    Clicking Administrative Tools, and then
5.    Double-clicking Event Viewer.   (If you're prompted for an administrator password or confirmation, type the password or provide confirmation.)
6.    Click an event log in the left pane.
7.    Double-click an event to view the details of the event.

How to Interpret an Event
Each log entry is classified by type, and contains header information, and a description of the event.
Event Header
The event header contains the following information about the event :
•    Date
The date the event occurred.

•    Time
The time the event occurred.

•    User
The user name of the user that was logged on when the event occurred.

•    Computer
The name of the computer where the event occurred.

•    Event ID
An event number that contained identifies the event types. The Event ID can be used by product support representatives to help understand what occurred in the system.
•    Source
The source of the event. This can be the name of a program, a system component, or an individual component of a large program.

•    Type
The type of event. This can be one of the following five types : Error, Warning, Information, Success Audit, or Failure Audit.

•    Category
A classification of the event by the event source. This is primarily used in the security log.


Event Types
The description of each event that is logged depends on the type of event. Each event in a log can be classified into one of the following types:
•    Information
An event that describes the successful operation of a task, such as an application, driver, or service. For example, an Information event is logged when a network driver loads successfully.

•    Warning
An event that is not necessarily significant, however, may indicate the possible occurrence of a future problem. For example, a Warning message is logged when disk space starts to run low.

•    Error
An event that describes a significant problem, such as the failure of a critical task. Error events may involve data loss or loss of functionality. For example, an Error event is logged if a service fails to load during startup.

•    Success Audit (Security log)
An event that describes the successful completion of an audited security event. For example, a Success Audit event is logged when a user logs on to the computer.

•    Failure Audit (Security log)
An event that describes an audited security event that did not complete successfully. For example, a Failure Audit may be logged when a user cannot access a network drive.

Error messages in the log
•    ErrorID Uniquely identifies an error. Use this field to search for a specific issue or to report a specific issue to the Desire2Learn help desk.
•    Error Groups related errors. Use this field to search for a list of errors of the same type.
•    IP Identifies the IP an error came from. Use this field to investigate information technology issues, such as firewall issues.
•    URL Allows you to find errors in specific tools or areas of the system. Use this field to search for errors in a specific tool or area, e.g. \content\myfiles\.
•    User Identifies errors that affect a given user. Use this field to help troubleshoot errors for a specific individual. For example, an individual making a help desk call.
•    Role Identifies errors that affect a given role. Use this field to quickly find and trouble shoot errors affecting a specific role.
•    Error Type
o    401: Not authorized errors resulting from users trying to access pages that they don't have permission to access.
o    404: Page cannot be found errors used to find broken links.
o    500: External system errors resulting from server setup problems or tool dependencies.
•    Sort By Specify which field to sort results based on.
•    Errors/Page Specify how many errors to view per page.

How to Archive a Log

If you want to save your log data, you can archive event logs in any of the following formats:
•    Log-file format (.evt)
•    Text-file format (.txt)
•    Comma-delimited text-file format (.csv)
•    Xml (Xml File Format) (.xml)

No comments:

Post a Comment