ProLiant Servers (ML,DL,SL)
1748252 Members
3896 Online
108760 Solutions
New Discussion юеВ

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

 
ubaid
New Member

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

I have same error with my brand new server. DL360G7 WHEA-logger Event ID:47 and 46. Server 2008 R2 installed.(service pack 1 update error also).  Server automatically restarting in particular intervene. It also show memory fault light up. I have 3x4 gb PC310600R memory. I've checked the system by removing the memory and put only one. It didn't help. Is it the problem of Memory or any other. Thanks in advance..

Dave73
Regular Advisor

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

As it is a brand new server i would log a call with HP support.

Ali
HPE Pro

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

Hi,

 

Updating the latest system bios and proliant Service pack has resolved the similar (Microsoft-Windows-WHEA-Logger- EVENT ID: 47) issue on one of my DL580 G7 servers.

 

update the System bios and Support pack:

https://support.hpe.com/hpsc/swd/public/detail?swItemId=MTX-7200f4a5778f4f39910b6d4793

 

Was the post useful? Click on the white KUDOS! Star.
For HP Guided Troubleshooting; https://support.hpe.com/hpesc/public/home

 

Thanks,

Aftab

I work for HPE
Looking for a quick resolution to a technical issue for your HPE products? HPE Support Center Knowledge-base тАУ Just a Click Away!
See Self Help Post for more details

Accept or Kudo

Kos_HP
New Member

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

I had a new two DL580 G7 servers.
Update the system bios and last support pack.
use Dave73' advice.

and continue to receive a mistake (Microsoft-Windows-WHEA-Logger- EVENT ID: 47) sometimes (((
Doof
Visitor

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

Thanks for posting this Dave!  Made the changes and it works great.  Looks like that saved us a lot of troubleshooting.  :)


@Dave73 wrote:

Firmware issue to be corrected at a later stage.

 

1. In RBSU

                Select Power Management Option

                Select Minimum Processor Idle Power State and change from the default value of C6 to No C-states


2.            Set Power management to Maximum performance in BIOS:

    a.        Boot into BIOS.

    b.        Go to Power Management Options.

    c.        Select HP Power Profile.

    d.        Select Maximum Performance.

    e.        Press Enter.

    f.        Exit BIOS.



3.            Set Power Management in Windows to High performance:

    a.        Go to Control Panel/System and Security/Power Options.

    b.        Change to high performance.


 

Rich Holt
Occasional Contributor

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

There is a HPE Support Document regarding this issue, see:

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=c03282091

 

 

 

 

Vague Assumption
Frequent Advisor

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

I have encountered a similar error; in my case, the W2K8SP2 server posts an error every day or two, which claims has been automatically corrected.

 

However, in my case, no errors regarding memory appear in either the IML or the HP Insight Diagnostics.  Instead, the error messages refer include the line:

 

Error Type:  Memory controller error.

 

How should I proceed?

Dominique_10
Advisor

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

Hello,

 

The same error for me...


A corrected hardware error has occurred.

Component: Memory
Error Source: Corrected Machine Check

The details view of this entry contains further information.

 

What is the firmware version related to:

"Firmware issue to be corrected at a later stage." in this thread?

 

I have :

BayDevice ModelFirmware ComponentCurrent VersionFirmware ISO Version7ProLiant BL460c G7
Discovered: NoSystem ROMI27 05/05/2011   iLO31.50 Sep 12 2012   Power Management Controller

1.6

 

Also should the error Event47 be catched by the HP Management Pack for SCOM 1.40.3.0

Let me know,

Thanks,

DOm

Andrzej007
Visitor

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

Hallo,

 

We have w2008 R2 WHEA-Logger ID 47 event  every 1  minute

 

on

 HP ProLiant DL120 G6  

XEON X3450;

4 x   4GB 2Rx8 PC3-10600 ECC REG;  

SOFTPAQ NUMBER:  SP62832

PART NUMBER: N/A

FILE NAME:  SP62832.EXE

TITLE:  System ROMPaq Firmware Upgrade for HP ProLiant DL120 G6 Servers (For USB Key-Media).

VERSION:  2013.07.01A

LANGUAGE:  English

ROM FAMILY: O26

REVISION: A ;

2008 R2 standard os up-to-date;

There is HP Lightsout 100 тАУ no errors to cancel and no dedicated option in RBSU

to switch "Package C3 State" to "No Package State".  

I have switched off all CPU powersaving features in RBSU that I have found.   

Ram was tested with w2008 utility at startup тАУ no errors.

There are also bluescreen crashes time to time.

 

I am out of ideas now. Any advice pls?

 

 

 

 

 

 

 

 

waaronb
Respected Contributor

Re: DL380G7 WHEA-logger Event ID: 47 "A corrected hardware error has occurred"

If your WHEA errors indicate a memory problem, it's probably a bad module.

The RAM test it does at startup when the memory configuration changes is pretty basic. Unless it's a *really* bad RAM module, it will probably pass that quick test.

I had a DL360 G7 that tested fine on every single RAM test I could find, even the ones where you boot to a floppy or USB and it has a full comprehensive test. Every time, no problems.

But when I ran MSSQL on that server, as soon as the memory usage reached some particular size, hitting some specific memory block, then boom, the system would blue screen and IML would log an error.

Fortunately for me, it logged the specific memory slot so I was able to replace that module, and it's been fine ever since.

The lesson to learn is, just because your memory tests are coming up clean, don't assume you don't have a memory problem, especially when the server's monitoring is telling you that you do. :)

Fortunately in many cases, a memory error is correctable if it's just a single-bit error, and that's probably what's happening if you're getting messages like that. If it's a double-bit, it's being detected but not corrected and you'll probably BSOD sooner or later.

There are more advanced memory modes like lockstep, mirroring, spare, etc. and some of those advanced modes can detect *and* correct double-bit errors too, but it slows down your memory access. Unless you have some mission critical system, you probably want performance, and you'll just replace bad modules when you find them.

Hopefully the system is logging which memory slot had the error.

Then again, it could be something else and not a memory problem at all, but probably not as long as you have the latest firmware and drivers installed.