Table of contents
Collapse the table of content
Expand the table of content

Hardware Errors and Error Sources

Last Updated: 9/16/2016

A hardware error is a malfunction of a hardware component in a computer system. The hardware components contain error detection mechanisms that can detect when a hardware error condition exists. Hardware errors can be classified as either corrected errors, or uncorrected errors.

  • A corrected error is a hardware error condition that has been corrected by the hardware or the firmware by the time that the operating system is notified about the presence of the error condition.

  • An uncorrected error is a hardware error condition that cannot be corrected by the hardware or the firmware. Uncorrected errors are classified as either fatal or nonfatal.

    • A fatal hardware error is an uncorrected or uncontained error condition that is determined to be unrecoverable by the hardware. When a fatal uncorrected error occurs, the operating system generates a bug check to contain the error.
    • A nonfatal hardware error is an uncorrected error condition from which the operating system can attempt recovery by trying to correct the error. If the operating system cannot correct the error, it generates a bug check to contain the error.

The notion of a hardware error source is a fundamental concept of the Windows Hardware Error Architecture (WHEA). A hardware error source is any hardware unit that alerts the operating system to the presence of an error condition. Examples of hardware error sources include the following:

  • Processor machine check exception (for example, MC#)

  • Chipset error signals (for example, SCI, SMI, SERR#, MCERR#)

  • I/O bus error reporting (for example, PCI Express root port error interrupt)

  • I/O device errors

A single hardware error source might handle the error reporting for more than one type of hardware error condition. For example, a processor's machine check exception typically reports processor errors, cache and memory errors, and system bus errors.

Note The system management interrupt (SMI) is handled by the firmware, not by the operating system.

A hardware error source is typically represented by the following:

  • One or more hardware error status registers

  • One or more hardware error configuration or control registers

  • A signaling mechanism to alert the operating system that a hardware error condition exists

In some situations, there is not an explicit signaling mechanism and the operating system must poll the error status registers to test for an error condition. However, polling can only be used for corrected error conditions because uncorrected errors require immediate attention by the operating system.

Starting with Windows Vista, the operating system maintains a list of all of the hardware error sources that can be discovered on a particular hardware platform. WHEA uses a discovery mechanism when the operating system starts to determine which of these hardware error sources exist on a particular system. The means by which this information is exposed to the operating system is platform-specific. The operating system collects this information from a combination of ACPI tables, firmware interactions, and other platform-specific mechanisms.

Note Windows Vista does not collect hardware error source information from ACPI tables. However, starting with Windows Server 2008 and Windows Vista SP1, the operating system uses ACPI tables to collect hardware error source information.

Send comments about this topic to Microsoft

© 2016 Microsoft