Произошла устраненная аппаратная ошибка whea logger 47

Сервер WIN 2008 R2 Standart, Motherboard TYAN S8230GM4NR, CPU - AMD Opteron 6172, RAM 32 GB
  • Remove From My Forums

  • Вопрос

  • Сервер WIN 2008 R2 Standart, Motherboard TYAN S8230GM4NR, CPU — AMD Opteron 6172, RAM 32 GB

    После установки обновлений в системе начала появляться ошибка WHEA-Logger error code 47

    Согласно MSDN ошибка памяти, память полностью заменили, но на ошибку это не повлияло, после перезагрузки ошибка исчезает, но через 2-3 часа работы появляется снова, обновление BIOS и перенастройка схемы электропитания результатов не дали, после появления
    ошибки постепенно падает производительность системы с последующим зависанием сервера, при этом на win 2003 r2 этот же сервер работает нормально без сбоев, лицензия позволяет перейти на 2003-й, но по ряду причин это не возможно. До установки обновлений
    проблемы не было.

    Код ошибки:

    Произошла устранимая аппаратная ошибка.

    Компонент: память
    Источник ошибки: Исправленная ошибка проверки компьютера

    [ Name] Microsoft-Windows-WHEA-Logger
    [ Guid] {C26C4F3C-3F66-4E99-8F8A-39405CFED220}
    Keywords 0x8000000000000000
    [ SystemTime] 2012-08-18T12:31:11.797962000Z
    [ ActivityID] {83A563F9-DA85-4948-8715-9B573D980251}
    [ ProcessID] 800
    [ ThreadID] 7256
    FRUId {00000000-0000-0000-0000-000000000000}
    PhysicalAddress 0x2e1162be0
    RawData 435045521002FFFFFFFF03000200000002000000690300000A1F0C0012080C140000000000000000000000000000000000000000000000000000000000000000BDC407CF89B7184EB3C41F732CB57131B18BCE2DD7BD0E45B9AD9CF4EBD4F89063D840285F66CD01000000000000000000000000000000000000000000000000580100004900000001020000010000001411BCA5646FDE4EB8633E83ED7C83B100000000000000000000000000000000020000000000000000000000000000000000000000000000A1010000C00000000102000000000000ADCC7698B447DB4BB65E16F193C4F3DB0000000000000000000000000000000002000000000000000000000000000000000000000000000061020000080100000102000000000000011D1E8AF94257459C33565E5CC3F7E80000000000000000000000000000000002000000000000000000000000000000000000000000000002000000000000000000000000000000E02B16E102000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000007F010000000000000002040000030000910F100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000010000000200000060A118593D7DCD01000000000000000000000000000000000000000004000000130A0800004004D4E02B16E10200000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

Ответы

  • Судя по информации из сообщения у Вас исправимая машинная ошибка, обнаруженная  в процессоре.

    Обращайтесь к поставщику сервера. MS за ваше битое железо не отвечает.

    Слава России!

    • Помечено в качестве ответа

      28 сентября 2012 г. 9:02

  • Из вашей ссылки:

    Beginning with Windows Server 2008 and Windows Vista SP1, when a hardware error occurs, the operating system creates an

    error record that describes the error condition and sends an event tracing for Windows (ETW) event that contains the error record to user mode.

    Именно поэтому

    … при этом на win 2003 r2 этот же сервер работает нормально без сбоев

    На Windows Server 2003 R2 точно не отмечается никаких внешних проявлений проблемы? Вы проверяли на 32- или на 64-битном Windows Server 2003?

    • Изменено
      osr_MVP
      11 сентября 2012 г. 7:09
    • Помечено в качестве ответа
      Yuriy Lenchenkov
      28 сентября 2012 г. 9:02

Источник

My HP Z820 workstation (BIOS v. 3.52) encounters prolonged periods of extremely frequent (several times each second) System Warnings in Windows 7 64-bit Event Viewer: (here is part of it)

Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          03/01/2014 18:11:16
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

 When it first happened in June 2013 it lasted for more than a month. The System Event Viewer archive filled up with all those repeated warnings (>100 GBytes in all!). Sometimes it was accompanied by BIOS error messages during start-up:

942 Memory Training Error DIMM 8 on CPU1 experienced an error during training (Code 301C).

It offered to press F1 to boot.

Then the Z820 began failing to boot or restart, and finally HP local support replaced 2 of my four 8-GByte memory units. It helped for a few months.

Last week WHEA-logger Event ID: 47 reappeared in full presence and already filled 1.7 GBytes of System Event Viewer archive. Sometimes it is inactive but then the warnings reappear. (without 942 errors this time… and no problem at boot time — yet.)

The Advisory blames Intel Xeon E7-8800/4800/2800 processors for this and offers a workaround by modifying «Minimum Processor Idle Power Package State — Package C3 State» Using the ROM-Based Setup Utility (RBSU) in the ProLiant DL580 G7 series servers BIOS.

So, my questions are:

1. Is the WHEA-logger Event ID: 47 in my Z820 related to the peculiar behavior of the dual Intel Xeon processors — in this case the initial E5-2670 type, not E7 — installed in Z820, and not a real memory hardware fault?

2. How do I apply this workaround in Z820 BIOS, where the BIOS Setup (F10) OS Power Management options are different from those in the HP Proliant Server Support Advisory?

Please advise.

Источник

My HP Z820 workstation (BIOS v. 3.52) encounters prolonged periods of extremely frequent (several times each second) System Warnings in Windows 7 64-bit Event Viewer: (here is part of it)

Log Name:      System
Source:        Microsoft-Windows-WHEA-Logger
Date:          03/01/2014 18:11:16
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

 When it first happened in June 2013 it lasted for more than a month. The System Event Viewer archive filled up with all those repeated warnings (>100 GBytes in all!). Sometimes it was accompanied by BIOS error messages during start-up:

942 Memory Training Error DIMM 8 on CPU1 experienced an error during training (Code 301C).

It offered to press F1 to boot.

Then the Z820 began failing to boot or restart, and finally HP local support replaced 2 of my four 8-GByte memory units. It helped for a few months.

Last week WHEA-logger Event ID: 47 reappeared in full presence and already filled 1.7 GBytes of System Event Viewer archive. Sometimes it is inactive but then the warnings reappear. (without 942 errors this time… and no problem at boot time — yet.)

The Advisory blames Intel Xeon E7-8800/4800/2800 processors for this and offers a workaround by modifying «Minimum Processor Idle Power Package State — Package C3 State» Using the ROM-Based Setup Utility (RBSU) in the ProLiant DL580 G7 series servers BIOS.

So, my questions are:

1. Is the WHEA-logger Event ID: 47 in my Z820 related to the peculiar behavior of the dual Intel Xeon processors — in this case the initial E5-2670 type, not E7 — installed in Z820, and not a real memory hardware fault?

2. How do I apply this workaround in Z820 BIOS, where the BIOS Setup (F10) OS Power Management options are different from those in the HP Proliant Server Support Advisory?

Please advise.

Источник

ProLiant Servers (ML,DL,SL)

    • Forums

      • Advancing Life & Work
      • Alliances
      • Around the Storage Block
      • HPE Ezmeral: Uncut
      • OEM Solutions
      • Servers & Systems: The Right Compute
      • Tech Insights
      • The Cloud Experience Everywhere
      • HPE Blog, Austria, Germany & Switzerland
      • Blog HPE, France
      • HPE Blog, Italy
      • HPE Blog, Japan
      • HPE Blog, Latin America
      • HPE Blog, Poland
      • HPE Blog, Hungary
      • HPE Blog, UK, Ireland, Middle East & Africa
    • Blogs

    • Information

  • Forums

  • Blogs

    • Advancing Life & Work
    • Alliances
    • Around the Storage Block
    • HPE Ezmeral: Uncut
    • OEM Solutions
    • Servers & Systems: The Right Compute
    • Tech Insights
    • The Cloud Experience Everywhere
    • HPE Blog, Austria, Germany & Switzerland
    • Blog HPE, France
    • HPE Blog, Italy
    • HPE Blog, Japan
    • HPE Blog, Latin America
    • HPE Blog, UK, Ireland, Middle East & Africa
    • HPE Blog, Poland
    • HPE Blog, Hungary

  • Information

  • English

21 REPLIES 21


  • Previous

    • 1
    • 2
    • 3

  • Next

Источник

Понравилась статья? Поделить с друзьями:

Читайте также:

  • Произошла техническая ошибка поэтому мы отменили ваш заказ уже конечно
  • Произошла техническая ошибка повторите попытку google play при покупке
  • Произошла ошибка при создании личной ссылки
  • Произошла ошибка при установке драйверов для этого устройства windows 10 код 28
  • Произошла ошибка при создании дочернего процесса для этого терминала

    • 0 0 голоса
    Рейтинг статьи
    Подписаться
    Уведомить о
    guest

    0 комментариев
    Старые
    Новые Популярные
    Межтекстовые Отзывы
    Посмотреть все комментарии