Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
A corrected hardware error has occurred.
Error Source: Corrected Machine Check
Bus : Device:Function: 0x0:0x3:0x0
Vendor ID : Device ID: 0x8086:0x340a
Class Code: 0x30400
|English: Request a translation of the event description in plain English.|
|Concepts to understand:|
What is WHEA?
According to some support forums, this issue affected certain motherboards (such as some offered by MSI). The suggestion is to make sure that all the hardware have the latest firmware updates (motherboard, I/O controllers, video, etc). Also, if the board is overclocked, reset the parameters within the recommended values and check if the error persists.
EV100574 (HP Document ID: c03282091) provides troubleshooting information for HP products using the Intel Xeon Processor E7 family.
Per Dell Support (PowerEdge T620, but phrased as though it applies to many servers) WHEA doesn't work very well with Dell hardware and the event can be disregarded. I have seen this event on 2 different PET620s purchased a few months apart, OMSA is not reporting RAM errors on either one, and both are working well, so I'm inclined to agree.
See also EV100252 (WHEA Hardware Error Events) for a list of events recorded by WHEA.
According to ME912310, in Microsoft Windows Server 2003, a periodic timer polls the system for corrected hardware error conditions. This process may interfere with the system firmware. Te article describes how to disable the corrected machine check to work around this problem.
The "Component" field mentioned in the event provides a clue as to what part of the hardware has generated the error. Various components can be reported:
- PCI Express Root Port
- Processor Core
A common suggestion on many support forums is to install the latest drivers for the motherboard and the chipsets installed on it. Some users confirmed that updating the drivers fixed the problem.
From a support forum: "I've managed to find the cause of the issue after sourcing another RAM module and testing it alone it turns out that all of my own ram seems to be faulty and is getting pretty hot for some reason so must have overheated. Despite the amount of fans I'm running the RAM still manages to get to ridiculous temperatures, too hot to touch. I have had one odd cl 2.5 DIMM, the rest are cl3, voltage shows as 2.6 in BIOS. After replacing with one single 1 GB stick the error has cleared."
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated