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
17 REPLIES 17
-
Previous
-
- 1
- 2
-
Next
Содержание
- Memory parity error hp proliant
- Hello: I am looking for help in resolving this problem that occurred on a HP Proliant DL360 G5 server running Windows Server 2003 Standard. This server has been running find for about a year and this occured today. When trying to load OS this error comes up. I changed the memory SIMs but problem persists. Also tried to repair OS installation but could not get to see the installed OS on a RAID system. Found the following document on a HP site and it refers to a Hotfix from Microsoft. Any ideas are appreciated?
- Business Support Center
- Tasks for my selected product
- Resources for my selected product
Memory parity error hp proliant
Сообщения: 2077
Благодарности: 141
Конфигурация компьютера | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Материнская плата: Gigabyte GA-EP45-DS3L | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
HDD: ST3500410AS, 500 Gb, SATA | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Звук: Realtek ALC888 @ Intel 82801JB ICH10 — High Definition Audio Controller | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
CD/DVD: PHILIPS SPD2514T | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ОС: Windows Corporate, x86 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Доброе время суток. Имеется вышеуказанный сервер в конфигурации: процессор — 4 ядра, Xeon E5606, 8 GB памяти, 4 SATA диска, управляемые RAID-контроллером HP SMART Array P410. OS Windows Server 2008R2 Standard. Время от времени сервер перезагружается (не BSOD, просто перезагрузка). Саму перезагрузку не видел, но увидел проблему, при запуске Everestа — при запуске программы, сразу после появления окна программы появляется синее окно (не BSOD): ***HARDWARE MALFUNCTION В журналах системы ничего интересного нет, кроме «Предыдущее завершение работы системы было неожиданным». Что делал: Источник Hello: I am looking for help in resolving this problem that occurred on a HP Proliant DL360 G5 server running Windows Server 2003 Standard. This server has been running find for about a year and this occured today. When trying to load OS this error comes up. I changed the memory SIMs but problem persists. Also tried to repair OS installation but could not get to see the installed OS on a RAID system. Found the following document on a HP site and it refers to a Hotfix from Microsoft. Any ideas are appreciated?
|
Windows Operating System (OS) users may encounter the NMI Parity Check/Memory Parity Error during the computer start-up process. The error is normally displayed when a computer hangs or stops responding during the Windows start-up process, and may be the result of a number of hardware or hardware configuration problems.
What does the NMI Parity Check/Memory Parity Error Look Like?
A number of error codes can be displayed when the error occurs. These include:
NMI: Parity Check/Memory Parity Error, NMI: Bus Timeout, NMI: Software NMI generated, NMI: Eisa IOCHKERR board x, NMI: Channel Check/IOCHK, or NMI: Fail-safe timer
The error codes typically start with the “*** Hardware Malfunction” message and a display message indicating that the computer or system has been “halted” follows.
Why does the NMI Parity Check/Memory Parity Error Occur?
The NMI Parity Check/Memory Parity error typically occurs if a computer hardware component is damaged, malfunctions, or if an incompatible driver is installed on the computer.
How to Fix the NMI Parity Check/Memory Parity Error
Most hardware problems that trigger this error involve the computer’s RAM, motherboard, cache memory, or a hardware adapter on the computer. The following are troubleshooting steps that can be taken to identify the cause of the error:
Verify Your Computer’s Memory
Step 1 – Remove any new RAM modules that have been installed on the computer.
Step 2 – Restart the computer to see if the error message continues to be displayed.
Step 3 – If the error is eliminated, then replace the RAM modules that were installed. If it persists, repeat the process but only leave the minimum amount of RAM necessary to boot the computer in order to determine if the computer has faulty RAM.
Step 4 – Replace the faulty RAM modules if they are the source of the problem.
The Microsoft RAM diagnostic tool found at: http://oca.microsoft.com/en/windiag.asp may also be used in order to help identify faulty computer modules.
Verify the Adapters on the Computer
Step 1 – Remove all adapters that are not required to run or start the computer. Most Windows computers can be run with only the video and drive subsystem controller adapters.
Step 2 – Restart the computer. If the error does not appear, then the problem is one of the adapters removed in step 1.
Step 3 – Reinstall one adapter at a time until the error is displayed again. This determines the adapter that was the source of the error. Visit the adapter manufacturer’s website and download and install the latest version.
Step 4 – Re-seat all adapter hardware cards if the error is not eliminated to ensure that this is not the cause of the problem.
Verify the Computer BIOS
Step 1 – Ensure that the latest revision of the computer’s BIOS and firmware configuration are installed.
Step 2 – Open the BIOS and change the configuration to “load Fail-safe defaults” or “BIOS defaults,” set “Plug and Play OS” to “No,” and disable anti-virus protection options located in the BIOS.
Step 3 – Restart the computer to see if the error has been corrected.
Check for Driver Updates
If Windows OS was recently upgraded or new hardware installed, then an outdated device driver may be the cause of the error.
Step 1 – Ensure that Windows Updates is configured to automatically update the computer from the “Windows Updates” application found in the computer’s “Control Panel.” Manually update the Operating System. Restart the computer after completing the manual Windows update.
Step 2 – If any new hardware was installed, remove the hardware drivers in the “Add/Remove Programs” menu after updating the OS in Step 1 and restart the computer.
Step 3 – Check the other device drivers installed on the computer for updates if the error is still being displayed and an update as required. Restart the computer after each device driver update to complete troubleshooting it.
Автор | Сообщение | ||
---|---|---|---|
Заголовок сообщения: NMI: Parity Check / Memory parity error зашел в тупик…….
|
|||
|
При установке винды, по началу ноут просто вис. Оказалось жестяк сбойный, поменяли, сейчас выдает такую ошибку, NMI: Parity Check / Memory parity error. Я с такой проблемой первыйраз столкнулся, даже не знаю что с ним делать, развожу руки. Может кто подмогнет немного? _________________ Если человек говорит что знает все, значит, он полный дурак. |
||
Вернуться к началу |
|
||
Артур.Т |
Заголовок сообщения:
|
|
А модель апарата трудно написать? |
Вернуться к началу |
|
Gaal Gyorgy |
Заголовок сообщения:
|
||
|
NMI parity check может обозначать все что угодно. Но в первую очередь — аппаратные проблемы. Я лично смог заработать такое сообщение на своем IBM, после того как угробил USB в ЮМ 82801DBM. При этом компьютер работает, но при подключении у-в — BSOD. |
||
Вернуться к началу |
|
||
ccdevice |
Заголовок сообщения:
|
|
Артур.Т писал(а): А модель апарата трудно написать? Это встречается не только на данной модели аппарата. А вообще его зовут Toshiba Satellite A100-811 _________________ Если человек говорит что знает все, значит, он полный дурак. |
Вернуться к началу |
|
Хе-Хемуль |
Заголовок сообщения:
|
|
Цитата: надо будет выпаивать контроллер? попробуйте — отпаяйте. Софтово обычно подобное не лечится. Если не поможет — значит проблема была все-таки не в сетевухе. Правда, если сетевуха BGA, то экспериментировать без отлаженной технологии пайки не рекомендую. |
Вернуться к началу |
|
ccdevice |
Заголовок сообщения:
|
|
Хе-Хемуль писал(а): Цитата: надо будет выпаивать контроллер? попробуйте — отпаяйте. Софтово обычно подобное не лечится. Если не поможет — значит проблема была все-таки не в сетевухе. Правда, если сетевуха BGA, то экспериментировать без отлаженной технологии пайки не рекомендую. Чип бга, но отпайка ничего не дала, таже ошибка. Значит дело в другом. Вот только в чем он ничего более не говорит. Что, ни у кого такой проблемы не возникало никогда? Помогите. Уже не знаю на что думать. Может все таки биос. _________________ Если человек говорит что знает все, значит, он полный дурак. |
Вернуться к началу |
|
Mobimas |
Заголовок сообщения: Re: NMI: Parity Check / Memory parity error зашел в тупик…
|
|
Тема старая, но вопрос может оказаться актуальным. |
Вернуться к началу |
|
Кто сейчас на конференции |
Зарегистрированные пользователи: aleksnfs, Bing [Bot], eugenowt, Google [Bot], Iceberg, Koner, lomn172, Newbie1980, nikolayy, ORBITER, Renat, Stoun1978, Yandex [Bot] |
Вы не можете начинать темы Вы не можете отвечать на сообщения Вы не можете редактировать свои сообщения Вы не можете удалять свои сообщения Вы не можете добавлять вложения |
- Remove From My Forums
-
Вопрос
-
Hello: I am looking for help in resolving this problem that occurred on a HP Proliant DL360 G5 server running Windows Server 2003 Standard. This server has been running find for about a year and this occured today. When trying to load OS this
error comes up. I changed the memory SIMs but problem persists. Also tried to repair OS installation but could not get to see the installed OS on a RAID system. Found the following document on a HP site and it refers to a Hotfix from Microsoft. Any ideas are
appreciated?HP Support document
Tasks for my selected product
» Download drivers and software » Troubleshoot a problem » Setup, install, and configure » Discover and use a product » Perform regular maintenance » Upgrade and migrate » Recycle and dispose » Resources for my selected product
» Customer
Self Repair» Repair videos and animations » Support Forums » Manuals
(guides, supplements, addendums, etc)» Frequently
asked questions» Submit a support case » See more… » Help » Site map » IT Resource Center SUPPORT COMMUNICATION — CUSTOMER ADVISORY
Document ID: c01177414
Version: 2
Advisory: (Revision) STOP 0x9C Blue Screen Message May Occur During System Shutdown of Microsoft Windows Server 2003 on ProLiant Servers Running Certain Versions of the Microsoft Storport Storage Port Driver (STORPORT.SYS)
NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice.
Release Date: 2007-10-26
Last Updated: 2007-10-26
DESCRIPTION
Document Version
Release Date
Details
2
10/26/2007
Revision created to update description by removing title of KB932755 article and adding statement that using the driver from the KB932755 article may also result in a blue screen.
1
10/02/2007
Original Document Release.
Some ProLiant servers running Microsoft Windows Server 2003 SP2 with the Microsoft Storport storage port driver (STORPORT.SYS) may display the following blue screen STOP code or message during the system shutdown:
STOP 0x0000009C BugCheck 9C, (0, f77452b0, 0, 0)
MACHINE_CHECK_EXCEPTIONOR
*** Hardware Malfunction
Call your hardware vendor for support
NMI: Parity check / memory parity error
*** The system has halted ***This also occurs if the updated Storport storage driver (STORPORT.SYS) is installed from the Microsoft KB article KB932755. Therefore, using the driver from the KB932755 article may also result in a blue screen.
SCOPE
Any ProLiant server configured with any HP storage controllers when the STORPORT.SYS storage driver is installed with Microsoft Windows Server 2003 SP2 or installed from the MS KB article KB932755.
While this has been observed on a ProLiant DL380 G4 server configured with two HP StorageWorks FC1142SR HBAs, this behavior could occur on other server platforms.
RESOLUTION
A supported Hotfix is available from Microsoft to resolve only the specific functionality issues described in this advisory. Only apply the Hotfix to servers that are experiencing the symptoms described above.
HP strongly recommends contacting Microsoft Customer Support Services to obtain the Hotfix to prevent either of the blue screens described in the Description section above from occurring. The Knowledge Base article mentioned above should be referenced
when contacting Microsoft to obtain the Hotfix. Information on how to contact Microsoft for technical support is available at the following Microsoft URL:http://support.microsoft.com/default.aspx
Ответы
-
Qué acciones has realizado, aparte de cambiar la RAM? Qué te dice el Insigth Manager?
Buscando una versión del storport posterior al SP2 de Windows, he encontrado esto:
http://support.microsoft.com/kb/945119/en-us¿Qué versión del driver tienes?
Saludos,
Marc
MCSA/MCSE 2003
MCITP: Enterprise Administrator (Windows Server 2008)
MCITP: Enterprise Messaging Administrator (Microsoft Exchange 2007)
Citrix CCA-
Помечено в качестве ответа
14 октября 2010 г. 22:30
-
Помечено в качестве ответа
-
Gracias.
Ya resolvi el problema. La tarjeta principal (Main Board) fue reemplazada.
Rich Puerto
-
Помечено в качестве ответа
Marc SalvadorModerator
16 октября 2010 г. 10:54
-
Помечено в качестве ответа