[comp.sys.ibm.pc.hardware] Parity Error on Motherboard

kaleb@thyme.jpl.nasa.gov (Kaleb Keithley ) (09/18/90)

This is a last ditch effort, before I go out and replace my motherboard.

I just added four more meg to my (generic Taiwan) 386SX motherboard, bringing
it to a total of eight meg.  The machine boots, memory test finds no errors, 
but both my protected mode operating systems, OS/2 1.1 and ESIX 3.2.C, crash.
Good old M'soft provides the wonderfully intuitive "Parity Error ????", 
while ESIX says "PANIC: Parity Error on Motherboard" followed by a dump 
message.

By taking the two SIMMs out of the fourth bank, everything works ok.  I
swapped all eight SIMMs around in the first three banks, so I know they're
all good.  I only get the parity error when I plug SIMMs into the fourth bank.

Anyone have any thoughts?
-- 
Kaleb Keithley                      Jet Propeller Labs
kaleb@thyme.jpl.nasa.gov

"So that's what an invisible barrier looks like!"

richard@pegasus.com (Richard Foulk) (09/18/90)

>This is a last ditch effort, before I go out and replace my motherboard.
>
>I just added four more meg to my (generic Taiwan) 386SX motherboard, bringing
>it to a total of eight meg.  The machine boots, memory test finds no errors, 
>but both my protected mode operating systems, OS/2 1.1 and ESIX 3.2.C, crash.
>Good old M'soft provides the wonderfully intuitive "Parity Error ????", 
>while ESIX says "PANIC: Parity Error on Motherboard" followed by a dump 
>message.
>
>By taking the two SIMMs out of the fourth bank, everything works ok.  I
>swapped all eight SIMMs around in the first three banks, so I know they're
>all good.  I only get the parity error when I plug SIMMs into the fourth bank.

It is still possible that some of your SIMMs are bad.

Are some of them Samsung brand?

-- 
Richard Foulk		richard@pegasus.com

poffen@sj.ate.slb.com (Russell Poffenberger) (09/18/90)

In article <1990Sep18.073020.3330@pegasus.com> richard@pegasus.com (Richard Foulk) writes:
>>This is a last ditch effort, before I go out and replace my motherboard.
>>
>>I just added four more meg to my (generic Taiwan) 386SX motherboard, bringing
>>it to a total of eight meg.  The machine boots, memory test finds no errors, 
>>but both my protected mode operating systems, OS/2 1.1 and ESIX 3.2.C, crash.
>>Good old M'soft provides the wonderfully intuitive "Parity Error ????", 
>>while ESIX says "PANIC: Parity Error on Motherboard" followed by a dump 
>>message.
>>
>>By taking the two SIMMs out of the fourth bank, everything works ok.  I
>>swapped all eight SIMMs around in the first three banks, so I know they're
>>all good.  I only get the parity error when I plug SIMMs into the fourth bank.
>
>It is still possible that some of your SIMMs are bad.
>
>Are some of them Samsung brand?

It is also possible (since only the fourth bank causes problems) that the board
itself is bad, or one of the SIMM sockets in the fourth bank is bad. Many board
manufacturers don't test all the ram sockets.


Russ Poffenberger               DOMAIN: poffen@sj.ate.slb.com
Schlumberger Technologies       UUCP:   {uunet,decwrl,amdahl}!sjsca4!poffen
1601 Technology Drive		CIS:	72401,276
San Jose, Ca. 95110             (408)437-5254

JCS120@psuvm.psu.edu (09/21/90)

If I am reading your problem correctly, it sounds like the motherboard
may have a bad memory connection in the fourth bank.

Hope this helps!  JCS120

root@neon.UUCP (Thomas Ziemer) (09/22/90)

kaleb@thyme.jpl.nasa.gov (Kaleb Keithley	) writes:

> but both my protected mode operating systems, OS/2 1.1 and ESIX 3.2.C, crash.
>Good old M'soft provides the wonderfully intuitive "Parity Error ????", 
>while ESIX says "PANIC: Parity Error on Motherboard"

I think, I have had the same problem some time ago. While installing
interactive's unix I get the same message. The solution was changing
my VGA card. The old one seemed to access forbidden memory addresses.
Perhaps this will help you.

Greetings ... thomas
--
 __   ______________________________________________________________________
(00)  N E O N  Research Caboose                    Computer Science Research
 \`\/ Thomas Ziemer, 1000 Berlin 20, West Germany, Phone#: +049-30-361 89 95
  ""  thomas@neon.UUCP, thomas@neon.mbx.sub.org [tmpmbx!zelator!neon!thomas]
      ----------------------------------------------------------------------
                 Wenn man es versteht, ist es veraltet... (Bitton's Theorem)