Joemt
asked on
SBS2011 - WHEA-Logger Event 47 a corrected hardware error has occurred - component memory - corrected machine check
SBS2011 WHEA-Logger error. This Server has an intel MB. I suspect I have a bad stick of RAM. I'm trying to identify which stick is bad.
I've also seen where it is recommended to upgrade the bios. If I do that will I have to manually reset the bios settings or will it maintain the original settings?
Here are the details:
Log Name: System
Source: Microsoft-Windows-WHEA-Log
Date: 7/7/2015 5:29:06 PM
Event ID: 47
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer:
Description:
A corrected hardware error has occurred.
Component: Memory
Error Source: Corrected Machine Check
The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WH
<EventID>47</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2015-07-07T23:
<EventRecordID>1827189</Ev
<Correlation ActivityID="{1A375298-CCE4
<Execution ProcessID="1116" ThreadID="12036" />
<Channel>System</Channel>
<Computer> <Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ErrorSource">1</Data
<Data Name="FRUId">{00000000-000
<Data Name="FRUText">
</Data>
<Data Name="ValidBits">0x0</Data
<Data Name="ErrorStatus">0x0</Da
<Data Name="PhysicalAddress">0x0
<Data Name="PhysicalAddressMask"
<Data Name="Node">0x0</Data>
<Data Name="Card">0x0</Data>
<Data Name="Module">0x0</Data>
<Data Name="Bank">0x0</Data>
<Data Name="Device">0x0</Data>
<Data Name="Row">0x0</Data>
<Data Name="Column">0x0</Data>
<Data Name="BitPosition">0x0</Da
<Data Name="RequesterId">0x0</Da
<Data Name="ResponderId">0x0</Da
<Data Name="TargetId">0x0</Data>
<Data Name="ErrorType">0</Data>
<Data Name="Length">873</Data>
<Data Name="RawData">43504552100
</EventData>
</Event>
I've also seen where it is recommended to upgrade the bios. If I do that will I have to manually reset the bios settings or will it maintain the original settings?
Here are the details:
Log Name: System
Source: Microsoft-Windows-WHEA-Log
Date: 7/7/2015 5:29:06 PM
Event ID: 47
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer:
Description:
A corrected hardware error has occurred.
Component: Memory
Error Source: Corrected Machine Check
The details view of this entry contains further information.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-WH
<EventID>47</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000
<TimeCreated SystemTime="2015-07-07T23:
<EventRecordID>1827189</Ev
<Correlation ActivityID="{1A375298-CCE4
<Execution ProcessID="1116" ThreadID="12036" />
<Channel>System</Channel>
<Computer> <Security UserID="S-1-5-19" />
</System>
<EventData>
<Data Name="ErrorSource">1</Data
<Data Name="FRUId">{00000000-000
<Data Name="FRUText">
</Data>
<Data Name="ValidBits">0x0</Data
<Data Name="ErrorStatus">0x0</Da
<Data Name="PhysicalAddress">0x0
<Data Name="PhysicalAddressMask"
<Data Name="Node">0x0</Data>
<Data Name="Card">0x0</Data>
<Data Name="Module">0x0</Data>
<Data Name="Bank">0x0</Data>
<Data Name="Device">0x0</Data>
<Data Name="Row">0x0</Data>
<Data Name="Column">0x0</Data>
<Data Name="BitPosition">0x0</Da
<Data Name="RequesterId">0x0</Da
<Data Name="ResponderId">0x0</Da
<Data Name="TargetId">0x0</Data>
<Data Name="ErrorType">0</Data>
<Data Name="Length">873</Data>
<Data Name="RawData">43504552100
</EventData>
</Event>
Is this a custom built machine or is it a brand (HP/DELL etc)?
ASKER
The Server is an Equus with an Intel Server chassis SC5650
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We all knew it was a bad stick of ram we were just trying to determine if the event I posted called out a location...it did not and later as the component failed......it did call out a location.
As for checking memory the O/S may include a memory check routine that can identify a problem unfortunately it may not identify the memory slot .. you can use memcheck
Memcheck86 has a bootable iso that you can burn to optical media
http://www.memtest86.com/download.htm