Machine-check exception

From Wikipedia, the free encyclopedia
  (Redirected from Machine Check Exception)
Jump to: navigation, search

A Machine Check Exception (MCE) is a type of computer hardware error that occurs when a computer's central processing unit detects a hardware problem.

Microsoft Windows displays the error using the blue screen of death containing the error message (the parameters inside the brackets vary):[1]

STOP: 0x0000009C (0x00000004, 0x00000000, 0xB2000000, 0x00020151) "MACHINE_CHECK_EXCEPTION"

On Linux, a process (such as klogd[2] ) 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

The error usually occurs due to failure or overstressing of hardware components where the error cannot be more specifically identified with a different error message.[clarification needed] Diagnosing the error message can be difficult, although Intel Pentium processors do generate more specific codes which can be decoded by contacting the manufacturer.[citation needed]

Most MCEs require a restart of the system before users can continue normal operation, and indicate a long-term problem of a general nature.[citation needed]

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]

Normal causes for MCE errors include overheating and/or incorrect hardware installation. Specific manually-induced causes include:

  • overclocking (which normally increases heat-output)
  • poorly-fitted heatsink/computer fans (the same problem can happen with excessive dust in the CPU fan)
  • an overloaded internal or external power-supply (fixable by upgrading)

Computer software can also cause MCE errors (normally by corrupting data which programs read or write). For example, software performing read or write operations from or to non-existent memory regions can lead to confusion for the processor and/or the system bus.[citation needed] Accessing memory marked off-limits by UEFI may cause MCE errors.[3]

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.[1]

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
A Linux daemon by Andi Kleen to handle MCEs for modern x86 processors. mcelog can also decode machine checks.
parsemce
A Linux program by Dave Jones to decode MCEs from AMD K7 processors
mced
A Linux program by Tim Hockin to gather MCEs from the kernel and alert interested applications. The primary difference between this app and others is that this is a daemon (it is always running) which means that it can get MCE notifications as soon as the kernel finds them.[citation needed] It does not try to interpret the MCE data, just alert other apps.

See also[edit]

References[edit]

  1. ^ a b "Stop error message in Windows XP that you may receive: "0x0000009C (0x00000004, 0x00000000, 0xb2000000, 0x00020151)"". Microsoft. Retrieved 3 March 2014. 
  2. ^ "KLOGD(8)". UNIX man pages. 1999-08-21. Retrieved 2008-07-29. klogd is a system daemon which intercepts and logs Linux kernel messages. 
  3. ^ "Bug 47121: UEFI boot panics on a new Samsung Series 9 laptop throwing a machine check exception". Linux kernel bug tracker. Retrieved 8 February 2013. 
  4. ^ "Intel 64 and IA-32 Architectures Software Developer's Manual". 

External links[edit]