ProLiant Servers (ML,DL,SL)
1745802 Members
3285 Online
108722 Solutions
New Discussion юеВ

NMI: Parity Check/Memory Parity Error

 
Adolfo Wolf Filho
New Member

NMI: Parity Check/Memory Parity Error

Sorry my poor englis...

My Server:
ML330 G3 2GB RAM, SmartArray 642 3 HD 36 GB 10K.

When i'm installing Win2K Server an error occur when the installation is about to finalize:
Graphical interface don't initialize and appears an error in blue screen:

*** Hardware Malfunction
Call your hardware vendor for support
NMI: Parity Check/Memory Parity Error
*** The system has halted

Memory is ok... another operate system has installed without problem, and the system test results OK.

Please.... what to do?

Adolfo
3 REPLIES 3
Olivier Drouin
Trusted Contributor

Re: NMI: Parity Check/Memory Parity Error

I wonder what would hp or microsoft say to this. Try HP support and come back here with the results! ;-)
Brian_Murdoch
Honored Contributor

Re: NMI: Parity Check/Memory Parity Error

Hi Adolfo,

If you have any third party PCI cards installed, for example NIC or modem, please remove them and try again.

Regards,

Brian
e4services
Honored Contributor

Re: NMI: Parity Check/Memory Parity Error

Adolfo,

Here is what Microsoft has to say:
CAUSE
This behavior can occur if a hardware component malfunctions, or if there are damaged or incompatible drivers installed.
RESOLUTION
To try to resolve this behavior, use the following troubleshooting techniques. Because Windows can display only basic error messages when hardware malfunctions occur, troubleshooting can be difficult. Most equipment problems center around the motherboard, the RAM on a motherboard or on an adapter, or the cache memory on a motherboard or on an adapter.

To troubleshoot basic hardware problems, try one or more of the following:
Check the Memory
Remove any extra memory modules that are in the computer, leaving only the least amount that is required for the computer to start and run Windows. Restart the computer to see whether the error messages persist.

If the error does not reappear, the issue is isolated to one or more of the RAM modules that you removed from the computer. Continue to remove and replace the minimum amount of RAM required, using the memory modules that you removed. When the error returns, you have isolated the individual memory module that is responsible for the problem.

This process may require you to restart your computer several times to pinpoint the specific memory module that is not working correctly.

Microsoft has released a software memory diagnostic tool, Windows Memory Diagnostic. Windows Memory Diagnostic tests the Random Access Memory (RAM) on your computer for errors. To download this tool, visit the following Microsoft Web site:
http://oca.microsoft.com/en/windiag.asp

Check the Adapters
Remove any adapters that are not required to start the computer and run Windows. In many cases, you can start your computer with only the drive subsystem controller and the video adapter.

If the error message does not appear, one of the adapters that you removed is the source of the problem. Reinstall each adapter separately, restarting after each adapter is installed, to see whether the error returns. If the error does not return after you reinsert all of the adapters, it is possible that one of the adapter cards just needed to be reseated. After your computer is running again, monitor the computer to make sure that the error does not return.
Solution
If reseating the adapters does not solve the problem, replace the adapter that is causing the error.
Check the Computer BIOS/Configuration
Verify that you have installed the latest revisions for your computer's BIOS or firmware configuration software. Go into the BIOS and set load Fail-safe defaults or BIOS defaults, disable any antivirus protection in the BIOS, and then set Plug and Play OS to No.

The type of hardware that your computer uses and the design of the motherboard determine what part of your computer's firmware can actually be updated. Various manufacturers provide diagnostic tools for roubleshooting.
Solution
Update the BIOS, the firmware, and/or the EISA configuration.
Hot Swap Hard Drives