Thread: Memory Parity Error (What's that?)

yeah, buy an iMac, this never happens on a Mac

Have a look here

Memory parity errors.

In your case the memory sticks seem to have an extra parity bit for checking. The mainboard memory controller has a circuit that checks the parity of the data from the memory sticks and detect an error.

Changing of the memory sticks did not correct the problem so probably that checking circuit on the MoBo is defective. If under warranty you could have that mainboard changed. If not you could look for some BIOS-option. Maybe that parity check can be switched off.

But if you do that look out for unexpected random failures that would indicate some more serious problem.

^ Thanks for the info. I think repairing it isn't worth it as it only cost 10k at the time. And as i don't have the knowledge to do it myself i'll bin or sell to the shop that offered my 1000bht for it!

Ta

I don't mention that i dropped down the stairs a few days before the issue. Although i cushion the blow on my foot about 4 days later the problems started.

^^
Thanks for the link but that may as well be Russian. I haven't figured out how to upload photos on this forum yet.

Originally Posted by Butterfly

yeah, buy an iMac, this never happens on a Mac

My friend has a mac, but he's gay. I'm not saying you're gay of course but the mac does look good on him. He's a bitch at times too.

Netbooks don't take kindly to being dropped. Get the data off it and write it off. Get an Asus 1215N.

Originally Posted by Jesus Jones

I think repairing it isn't worth it as it only cost 10k at the time. And as i don't have the knowledge to do it myself i'll bin or sell to the shop that offered my 1000bht for it!

you don't have to repair anything, turn-off the parity check in the BIOS, it takes 2sec

or are you so computer retarded, you don't even know how to use a BIOS ? if this is the case, buy an iPad and stay away from real computers

^Yep, will that be in the F4 or F8 setup thing.

usually it's F1, but it could be F4 on some MB

don't wait for WinXp to boot to press F8 though

Originally Posted by Butterfly

Originally Posted by Jesus Jones

I think repairing it isn't worth it as it only cost 10k at the time. And as i don't have the knowledge to do it myself i'll bin or sell to the shop that offered my 1000bht for it!

you don't have to repair anything, turn-off the parity check in the BIOS, it takes 2sec

or are you so computer retarded, you don't even know how to use a BIOS ? if this is the case, buy an iPad and stay away from real computers

Yes, listen to Butters he is a expert innit.

i MUST BE RETARDED BECAUSE IN BIOS AND UNDER TABS BOOT, SECURITY OR ADVANCED I CAN'T SE ANYTHING THAT ALLOWS ME TO TURN PARITY OFF.

You cannot be sure it is available as an option. But was worth a try.
But it would probably somewhere under peripherals and where other memory options are. There are probably options about memory timing. You could also try to trim down memory speed to see if the problem disappears.

Netbook BIOSes tend to have less options available than their big brother laptops.

Originally Posted by Butterfly

you don't have to repair anything, turn-off the parity check in the BIOS, it takes 2sec

and if the brake failure lamp in your car comes on then disconnect it.
It is probably a fault in the fault detection circuit..

Originally Posted by lom

and if the brake failure lamp in your car comes on then disconnect it. It is probably a fault in the fault detection circuit..

You are right. I realise now how disabling parity check endangers the life of every single internet user.

Originally Posted by Takeovers

Originally Posted by lom

and if the brake failure lamp in your car comes on then disconnect it. It is probably a fault in the fault detection circuit..

You are right. I realise now how disabling parity check endangers the life of every single internet user.

Interesting conclusion you draw there instead of understanding the metaphor, a metaphor which was intended to highlight a logical thinking flaw and your reply shows that you suffer badly from it.

Error detection circuitry increase manufacturing cost and is not something the manufacturers just throws in because they think it is fun.
Disabling such a circuitry, wherever it is used, whenever it reports an error is not so smart and assuming that the error detection circuitry is faulty is a bad assumption.
Each parity bit is protecting its own set of 32 data bits and will trigger an error if any of them (including the parity bit) should have an error.
The chance of the error being in the data bits is therefore 97% and the chance that the parity bit itself is the erroneous one is 3%.
But yeah, go ahead and disable the checking..

Originally Posted by Takeovers

Originally Posted by lom

and if the brake failure lamp in your car comes on then disconnect it. It is probably a fault in the fault detection circuit..

You are right. I realise now how disabling parity check endangers the life of every single internet user.

indeed, nobody is really using the parity bit thing, made sense in the 1950s I suppose, or for military computer equipments

Feck, it's off to Samsung service center for me.

Originally Posted by lom

Interesting conclusion you draw there instead of understanding the metaphor, a metaphor which was intended to highlight a logical thinking flaw and your reply shows that you suffer badly from it.

yes, we got the logic flaw, but parity checking is hardly used except for certain purposes. It's more likely a false alarm

the best test is to use it and see how long it takes to crash using a well optimized WinXP

Originally Posted by lom

Error detection circuitry increase manufacturing cost and is not something the manufacturers just throws in because they think it is fun. Disabling such a circuitry, wherever it is used, whenever it reports an error is not so smart and assuming that the error detection circuitry is faulty is a bad assumption.

I recommend you read this thread again.

There is a parity error alarm. The memory was changed but the alarm still persists. That makes it quite likely the error detection circuitry is defective rather than the memory.

Hence my advice to save the data, switch parity error detection off and observe if other unclear errors occur. This is the alternative to throwing the device into the wast bin right away.

So there is no logical flaw with my argument. But there is an incomplete understanding or interpretation of the situation by you.