Machine-check exception

From Wikipedia, the free encyclopedia
Jump to navigation Jump to search

A machine-check exception (MCE) is a type of computer hardware error that occurs when a computer's central processing unit detects an unrecoverable hardware error in the processor itself, the memory, the i/o devices or on the system bus. It is not caused by software. The error usually occurs due to component failure or the overheating or overclocking of hardware components. Most machine check exceptions halt the operating system and require a restart before users can continue normal operation. Diagnosing the failure can be difficult because so little information about what caused the problem is captured.

Modern versions of Microsoft Windows handle machine check exceptions through the Windows Hardware Error Architecture. When WHEA detects a machine check exception, it displays the error in a Blue Screen of Death, with the following parameters (which vary, but the first parameter is always 0x0 for a machine check exception):[1]

 *** STOP: 0x00000124 (0x0000000000000000, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000) 

Older versions of Windows handle similar exceptions through the Machine Check Architecture. In this case the Blue Screen of Death will show an error similar to the following:[2]

 STOP: 0x0000009C (0x00000030, 0x00000002, 0x00000001, 0x80003CBA) 

On Linux, a process (such as klogd[3]) writes a message to the kernel log and/or the console screen (usually only to the console when the error is non-recoverable and the machine crashes as a result):

CPU 0: Machine Check Exception: 0000000000000004
Bank 2: f200200000000863
Kernel panic: CPU context corrupt

Problem types[edit]

Most of these errors relate specifically to the Pentium processor family. Similar errors may occur on other processors and will cause similar problems.

Some of the main hardware problems that cause MCEs include:

Possible causes[edit]

Machine checks are a hardware problem, not a software problem. They're often the result of the overclocking or overheating, causing errors, or hitting a thermal limit where the CPU must shut itself down to avoid permanent damage. But they can also be caused by bus errors introduced by other failing components, including memory, i/o devices and i/o controllers. Possible causes include:

  • Poor CPU cooling due to a CPU heatsink and fan that's clogged with dust or come loose.
  • Overclocking beyond the highest clock rate at which the CPU is still reliable.
  • Failing memory.
  • Failing i/o controllers, on either the motherboard or separate cards.
  • Failing i/o devices.
  • Inadequate or failing power supply.
  • Poor case cooling due to inadequate or clogged case fans or filters.

Cooling problems are usually obvious upon inspection. Memory can be checked by booting to a diagnostic tool, e.g., on Windows with the Windows Memory Diagnostic utility. Non-essential failing i/o controllers and devices can be identified by unplugging them if possible or disabling the devices and drivers to see if the problem disappears. If the failures typically only occur fairly soon after the OS is booted or not at all or not for days, that may be suggestive of a power supply problem, the failure occurring when power demand peaks as the OS wakes up any physical drives and other devices.

Decoding MCEs[edit]

As noted previously, decoding MCE errors can prove difficult. Normally the manufacturer (especially processor manufacturers) will be able to provide information about specific codes. Consult the Intel 64 and IA-32 Architectures Software Developer's Manual[4] Chapter 15 (Machine-Check Architecture), or the Microsoft KB Article on Windows Exceptions.[5]

Programs to Decode MCEs[edit]

  • mcat: A Windows command-line program from AMD to decode MCEs from AMD K8, Family 0x10 and 0x11 processors.
  • mcelog[6] A Linux daemon by Andi Kleen to handle MCEs for modern x86 processors. mcelog can also decode machine checks.
  • parsemce[7] a Linux program by Dave Jones to decode MCEs from AMD K7 processors.
  • mced[8] a Linux program by Tim Hockin to gather MCEs from the kernel and alert interested applications. It does not try to interpret the MCE data, it just alerts other programs.

See also[edit]

References[edit]

  1. ^ "Bug Check 0x124: WHEA_UNCORRECTABLE_ERROR". MSDN. 2016-09-29. Retrieved 2017-07-13.
  2. ^ "Bug Check 0x9C: MACHINE_CHECK_EXCPETION". Microsoft Support. 2018-03-31. Retrieved 2018-03-31.
  3. ^ Steve Lord, Greg Wettstein. "klogd(8) - Linux man page". Retrieved 2017-07-13. klogd is a system daemon which intercepts and logs Linux kernel messages.
  4. ^ "Intel® 64 and IA-32 Architectures Developer's Manual: Vol. 3A / System Programming Guide, Part 1". Intel. May 2011. Retrieved 2017-07-13.
  5. ^ "Stop error message in Windows XP that you may receive: "0x0000009C (0x00000004, 0x00000000, 0xb2000000, 0x00020151)"". MSDN. 2015-12-07. Retrieved 2017-07-13.
  6. ^ "mcelog: Advanced hardware error handling for x86 Linux". 2015-04-20. Retrieved 2017-07-13.
  7. ^ "parsemce: Linux Machine check exception handler parser". 2003-07-22. Retrieved 2017-07-13.
  8. ^ mcedaemon on GitHub

External links[edit]