Download your favorite Linux distribution at LQ ISO.
Go Back > Forums > Linux Forums > Linux - Hardware
User Name
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?


  Search this Thread
Old 04-09-2016, 11:59 AM   #16
Senior Member
Registered: Sep 2009
Location: Yorks. W.R. 167397
Distribution: Slackware
Posts: 1,307
Blog Entries: 4

Rep: Reputation: Disabled

So, here I am bumping a necro-thread. Why? Because I've had this exact error on a new system that I bought just one week ago, and I've researched it this afternoon, and I now know the answer.

This exact machine check exception -- specifically, with "STATUS 0x90000040000f0005", or something very similar ending in 000f0005 -- is caused by Intel erratum HSD131. The exception is spurious and can therefore be ignored. For avoidance of doubt, it has nothing to do with temperatures, faulty motherboards or faulty memory.

See Desktop 4th Generation Intel® Core™ Processor Family, Desktop Intel® Pentium® Processor Family, and Desktop Intel® Celeron® Processor Family Specification Update [, pdf] page 51:

HSD131. Spurious Corrected Errors May be Reported

Problem: Due this erratum, spurious corrected errors may be logged in the IA32_MC0_STATUS register with the valid field (bit 63) set, the uncorrected error field (bit 61) not set, a Model Specific Error Code (bits [31:16]) of 0x000F, and an MCA Error Code (bits [15:0]) of 0x0005. If CMCI is enabled, these spurious corrected errors also signal interrupts.

Implication: When this erratum occurs, software may see corrected errors that are benign. These corrected errors may be safely ignored.

Workaround: None identified.

Status: For the steppings affected, see the Summary Table of Changes.
A list of the affected Intel processors is given on pages 17-20. There are quite a lot of them.

FreeBSD actually elides the error: see

For me, it occurs only when executing 32-bit code, which presumably ties in with the mention of the IA32_MC0_STATUS register above. This probably explains why the net is full of people wrongly blaming this error on VMWare Player, qemu, etc. (see e.g.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Hardware or software problem? psionl0 Slackware 14 07-08-2011 03:18 AM
mcelog: HARDWARE ERROR. This is *NOT* a software problem! olego Linux - Hardware 11 01-17-2011 03:12 AM
Hardware or software problem ? czezz Linux - Networking 3 04-18-2008 11:10 AM
Internet and LAN access is unstable-is this a hardware problem or a software problem? soren625 Linux - Networking 1 06-07-2004 06:43 AM > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 08:37 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration