Computer throwing parity error

Yourdogsdead

Distinguished
Apr 30, 2010
12
0
18,510
I just replaced a single RAM module on an HP p6180t. However, when I plug the new module into any slot, the computer won't POST or do anything. The motherboard's speaker beeps. HP's error codes say that is is a Parity Error.

Is the module dead, or did I perhaps get the wrong RAM?
 


The RAM I purchased was this from Amazon.

Here is the RAM in the computer


  • Slot 1 DDR3 [PC3-10600] 2048 MBytes Micron Technology 16JTF25664AY-1G4D1
    Slot 2 DDR3 [PC3-10600] 1024 MBytes Samsung M378B2873EH1-CH9
    Slot 3 DDR3 [PC3-10600] 2048 MBytes Micron Technology 16JTF25664AY-1G4D1

The motherboard is an IPIEL LA3, and it has an American Megatrends BIOS.
 
Hello,:hello:

Does this error occur when you install just the new memory without the old memory? Is the system working with just the old memory? Let me know the number of beeps you are hearing.

The memory looks compatible and I think the memory is defective. Try running a memory test using memtest86 run at least a few passes with no errors. (Download the boot able version so that you can run it during POST). Good luck.
 
The system works fine with just the old modules in place. It even worked with the failed module, but would blue screen. Whenever I place the new module in, no matter which socket, the error occurs. I have removed every module except trouble causing one, and it still caused the issue. It is currently giving me 2 beeps, which according to HP's diag page means a partity error.

I cannot run memtest on the module because it won't boot. It doesn't boot from the HDD or USB.
 
Are you able to boot till BIOS using the new memory? If yes then memtest86 will work during POST just download the .iso image version. Then maybe it's time to return the memory, I think it might be defective. But try updating your BIOS, sometimes can be a compatibility issue. If the BIOS upgrade doesn't help then return the memory and try getting a new memory. Good luck.

If you are going for a refund then try directly getting the memory from crucial or try here.

Good luck. Hope everything works out.:hihi: