Talk:Machine-check exception

message: :Image:Machine Check Exeption.JPG is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is  other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page.  Note that any fair use images uploaded after 4 May, 2006, and lacking such an explanation will be deleted one week after they have been uploaded, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
BetacommandBot (talk) 17:40, 29 November 2007 (UTC)
thread_title: Fair use rationale for Image:Machine Check Exeption.JPG

message: `Overheating can cause electrons to become more animated and thus escape from the silicon tracks, resulting in corrupted data.'  Those poor, overheated electrons.  I tend to doubt this is really accurate, but am not sure what to replace it with, so I'll leave it be for now.  dougmc (talk) 15:17, 29 April 2009 (UTC)
thread_title:  Overheated electrons 

message: "MCEs require a restart of the system before users can continue normal operation: " This is not true, under linux a big class of mce errors can happen and will just influence one process, or nothing at all.  — Preceding unsigned comment added by 213.61.9.75 (talk) 09:40, 5 June 2012 (UTC)
replies: text: It's also not true for mainframe operating systems such as z/OS and z/VM, where there is extensive RAS code to continue running after, e.g., CPU, memory, errors. Shmuel (Seymour J.) Metz Username:Chatul (talk) 16:04, 18 May 2020 (UTC)
thread_title:  linux restart 

message: This covers how to decode MCEs from AMD CPUs under Windows, but not Intel CPUs. Is there a way? --Chealer (talk) 17:28, 19 October 2011 (UTC)
thread_title:  Decoding MCEs from Intel CPUs under Microsoft Windows 

message: According to the Arch Linux wiki, rasdaemon is now the standard option for monitoring and mcelog is not even supported by the kernel in some distributions. The article's claim that mcelog is the tool for 'modern' hardware is outdated. 86.5.88.131 (talk) 00:39, 26 November 2022 (UTC)
replies: text: Thank you for your comment. rasdaemon has been added to the article and mcelog is now described as deprecated. --Soluvo (talk) 07:41, 24 February 2023 (UTC)
thread_title:  Include rasdaemon 

message: There should be material on what recovery support is available in various operating system. As an example, if a memory failure occurs in z/OS for a page frame that was not altered since the contents was last paged in, z/OS can assign a new page frame and schedule a page-in operation. Further, some machine checks, e.g., single bit ECC error, need no action other than recording the data. Various systems can assign work on a failing CPU without damage to the job running at the time of failure. Shmuel (Seymour J.) Metz Username:Chatul (talk) 17:11, 20 February 2023 (UTC)
thread_title:  Recovery