home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.ms-windows.misc
- Path: sparky!uunet!wupost!gumby!destroyer!ubc-cs!fs1.ee.ubc.ca!johnt
- From: johnt@ee.ubc.ca (john jay tanlimco)
- Subject: Re: Memory parity error detected. SYSTEM HALTED.
- Message-ID: <1992Sep13.061626.8684@ee.ubc.ca>
- Keywords: WINDOWS 3.1, CRASH
- Organization: University of BC, Electrical Engineering
- References: <1992Sep10.133717.21198@funet.fi> <1992Sep10.162106.14993@mksol.dseg.ti.com> <1992Sep12.234254.6893@techbook.com>
- Date: Sun, 13 Sep 1992 06:16:26 GMT
- Lines: 28
-
- In article <1992Sep12.234254.6893@techbook.com> jwettern@techbook.com (Joern Wettern) writes:
- >In article <1992Sep10.162106.14993@mksol.dseg.ti.com> mccall@mksol.dseg.ti.com (fred j mccall 575-3539) writes:
- >>In <1992Sep10.133717.21198@funet.fi> ms86817@cs.tut.fi (Matti Suokko (OH5MRM)) writes:
- >>
- >>> SYSTEM ERROR: Memory parity error detected. System halted.
- >>
- >>
- >>> What will cause the error message above ?
- >>> When I upgraded WIN 3.0 to WIN 3.1 it worked fine, but then
- >>> I formatted my HD and installed WIN 3.1 again, and
- >>> now it crashes 50 times a day.
- >>
- >>This is generally caused by either bad memory or having memory with
- >>different speed ratings (on some motherboards). The reason it worked
- >
- >That seems to be the case for me. I have 2M of 80 ns SIMMS and 2M of 70 ns
- >SIMMs. What I don't understand is WHY this would cause a partity error. My
- >system needs 80ns and everything faster should not make any difference.
- >Would anyone care to expalin this to me?
-
- I have 4 1x9 80ns and 4 1x3 70ns running Win3.1 happily. Are you sure
- you don't have bad SIMMs?
-
- --
- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
- John Jay Tanlimco | University of British Columbia | Tel: (604) 526-3160
- johnt@ee.ubc.ca | M.A.Sc. Electrical Engineering | Fax: (604) 522-7833
- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-